Exchange-Pair Contract Specification • PYTH
PYTH:FUDUSD — FUD (FUD) Contract & Regulatory Dossier
Technical symbology specification, parent asset custody metadata, and execution venue regulatory audit for PYTH:FUDUSD (FUD against USD) on PYTH.
Coverage: Underlying Asset: FUD (FUD) • CMC ID: 29051 • Sibling Markets: 10
- Canonical Pair
- PYTH:FUDUSD
- Global Asset Rank
- #3701
- Venue 6D Score
- —
- Venue Licences
- 0 on file
PYTH:FUDUSD Contract & Symbology Specification
Standardised cross-venue instrument metadata and settlement parameters.
| Specification Field | Recorded Parameter | Verification & Settlement Notes |
|---|---|---|
| Canonical TradingView / Feed Symbol | PYTH:FUDUSD | Provider ID pyth • Instrument code FUDUSD |
| Parent Underlying Asset | FUD (FUD) | Product Catalogue ID #3701 • CoinMarketCap ID #29051 • Global Liquidity Rank #3701 |
| Base / Quote Leg Breakdown | Base: FUD / Quote: USD | Spot / Margin order book settled in base and quote units |
| Primary Execution Venue | PYTH | Verify regional operating entity and VASP registration before trading |
| 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: PYTH
Supervisory filings and 6D risk standing for the exchange operating PYTH:FUDUSD.
Provider code PYTH is tracked as a market-data and order-book feed source. Browse our regulated institution directory to inspect licensed digital-asset and derivatives counterparties.
PYTH:FUDUSD Market Structure & Custody Architecture
Deterministic vector exhibit mapping ticker symbology, venue licensing, and cross-exchange liquidity.
Cross-Exchange Sibling Markets for FUD (FUD)
Compare PYTH:FUDUSD 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 → |
| MEXC:FUDUSDT | mexc | FUDUSDT | USDT | Contract Spec → |
| DEFILLAMA:4TOKEN_TVL | defillama | 4TOKEN_TVL | USD | Contract Spec → |
| BITGET:FUDUSDT | bitget | FUDUSDT | USDT | 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: PYTH:FUDUSD (FUD)
Contract specification, exchange regulation, and custody due diligence answers.
What is the PYTH:FUDUSD trading instrument and contract specification?
PYTH:FUDUSD is the cross-exchange symbology identifier for FUD (FUD) quoted against USD on PYTH. In FXMacro Wire'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 PYTH (PYTH) regulated?
Our current supervisory snapshot does not bind active onshore Tier-1 broker licences directly to the provider code "PYTH". 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 PYTH:FUDUSD is settled either directly on PYTH's omnibus exchange ledger or via standard native network wallets supporting FUD.
Which alternative exchanges list FUD (FUD) alongside PYTH?
Cross-exchange sibling order books for FUD (FUD) include TVC:FUDUSD, TVC:FUDTUSD, HTX:FUDUSDT, MEXC:FUDUSDT, DEFILLAMA:4TOKEN_TVL, BITGET:FUDUSDT, 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.