Exchange-Pair Contract Specification • BITGET
BITGET:FUDUSDT — FUD (FUD) Contract & Regulatory Dossier
Technical symbology specification, parent asset custody metadata, and execution venue regulatory audit for BITGET:FUDUSDT (FUD against USDT) on Bitget Wallet: Crypto, Bitcoin.
Coverage: Underlying Asset: FUD (FUD) • CMC ID: 29051 • Sibling Markets: 10
- Canonical Pair
- BITGET:FUDUSDT
- Global Asset Rank
- #3701
- Venue 6D Score
- —
- Venue Licences
- 0 / 0
BITGET:FUDUSDT Contract & Symbology Specification
Standardised cross-venue instrument metadata and settlement parameters.
| Specification Field | Recorded Parameter | Verification & Settlement Notes |
|---|---|---|
| Canonical TradingView / Feed Symbol | BITGET:FUDUSDT | Provider ID bitget • Instrument code FUDUSDT |
| Parent Underlying Asset | FUD (FUD) | Product Catalogue ID #3701 • CoinMarketCap ID #29051 • Global Liquidity Rank #3701 |
| Base / Quote Leg Breakdown | Base: FUD / Quote: USDT | Spot / Margin order book settled in base and quote units |
| Primary Execution Venue | Bitget Wallet: Crypto, Bitcoin (bitget-wallet-crypto-bitcoin-terminal-629) → | 0 active regulated licence(s), 0 warning flag(s) |
| Official Asset Reference Website | fudthepug.com ↗ | Always verify token contract addresses against official protocol documentation |
| Supported Custody Wallets (0) | Exchange omnibus custody or standard native chain wallet support | |
Execution Venue Regulatory Dossier: Bitget Wallet: Crypto, Bitcoin
Supervisory filings and 6D risk standing for the exchange operating BITGET:FUDUSDT.
BITGET:FUDUSDT Market Structure & Custody Architecture
Deterministic vector exhibit mapping ticker symbology, venue licensing, and cross-exchange liquidity.
Cross-Exchange Sibling Markets for FUD (FUD)
Compare BITGET:FUDUSDT against 10 alternative exchange order books listing FUD.
| Exchange Pair Ticker | Provider / Exchange | Instrument Symbol | Quote Asset | |
|---|---|---|---|---|
| TVC:FUDUSD | tvc | FUDUSD | USD | Contract Spec → |
| TVC:FUDTUSD | tvc | FUDTUSD | TUSD | Contract Spec → |
| HTX:FUDUSDT | htx | FUDUSDT | USDT | Contract Spec → |
| PYTH:FUDUSD | pyth | FUDUSD | USD | Contract Spec → |
| MEXC:FUDUSDT | mexc | FUDUSDT | USDT | Contract Spec → |
| DEFILLAMA:4TOKEN_TVL | defillama | 4TOKEN_TVL | USD | Contract Spec → |
| COINEX:FUDUSDT | coinex | FUDUSDT | USDT | Contract Spec → |
| GATEIO:FUDUSDT | gateio | FUDUSDT | USDT | Contract Spec → |
| BLUEFIN:FUDSUI_2EBBD7.USD | bluefin | FUDSUI_2EBBD7.USD | USD | Contract Spec → |
| TURBOSFINANCE:FUDSUI_BD85F6.USD | turbosfinance | FUDSUI_BD85F6.USD | USD | Contract Spec → |
Frequently Asked Questions: BITGET:FUDUSDT (FUD)
Contract specification, exchange regulation, and custody due diligence answers.
What is the BITGET:FUDUSDT trading instrument and contract specification?
BITGET:FUDUSDT is the cross-exchange symbology identifier for FUD (FUD) quoted against USDT on Bitget Wallet: Crypto, Bitcoin. In Terminal Ledger Desk's instrument catalogue, FUD (FUD) carries global market rank #3701 (CMC ID #29051) and trades across 11 tracked exchange pair feed(s).
Is the execution venue Bitget Wallet: Crypto, Bitcoin (BITGET) regulated?
Our current supervisory snapshot does not bind active onshore Tier-1 broker licences directly to the provider code "BITGET". Institutional allocators should verify the exact regional operating subsidiary and VASP/CASP registration before routing orders.
Which custody wallets and settlement rails support FUD (FUD)?
Custody for BITGET:FUDUSDT is settled either directly on Bitget Wallet: Crypto, Bitcoin's omnibus exchange ledger or via standard native network wallets supporting FUD.
Which alternative exchanges list FUD (FUD) alongside BITGET?
Cross-exchange sibling order books for FUD (FUD) include TVC:FUDUSD, TVC:FUDTUSD, HTX:FUDUSDT, PYTH:FUDUSD, MEXC:FUDUSDT, DEFILLAMA:4TOKEN_TVL, COINEX:FUDUSDT, GATEIO:FUDUSDT. Use the Cross-Exchange Sibling Matrix above to compare venue regulatory standing across each listing.
Structured against supervisory register snapshots and public regulatory filings. Verify your contracting legal entity and current authorisation status directly on the issuing regulator’s official register before transacting.