Exchange-Pair Contract Specification • BINANCE
BINANCE:PEPEJPY — PepeAI (PEPEAI) Contract & Regulatory Dossier
Source-listed ticker, product, and provider records for BINANCE:PEPEJPY (PepeAI) on Binance.
Coverage: Underlying Asset: PepeAI (PEPEAI) • CMC ID: 24961 • Sibling Markets: 24
BINANCE:PEPEJPY Contract & Symbology Specification
Standardised cross-venue instrument metadata and settlement parameters.
| Specification Field | Recorded Parameter | Verification & Settlement Notes |
|---|---|---|
| Canonical TradingView / Feed Symbol | BINANCE:PEPEJPY | Provider ID binance • Instrument code PEPEJPY |
| Parent Underlying Asset | PepeAI (PEPEAI) | Product Catalogue ID #3498 • CoinMarketCap ID #24961 • Global Liquidity Rank #3498 |
| Base / Quote Leg Breakdown | Base: PEPEAI / Quote: JPY | Spot / Margin order book settled in base and quote units |
| Primary Execution Venue | Binance (binance-2807) → | 15 active regulated licence(s), 0 warning flag(s) |
| Official Asset Reference Website | pepeai.org ↗ | Always verify token contract addresses against official protocol documentation |
| Supported Custody Wallets (2) | https://www.trustwallet.com/https://s2.coinmarketcap.com/static/cloud/img/dex/default-icon-day-v3.svg?_=bf072d5 | |
Execution Venue Regulatory Dossier: Binance
Supervisory filings and 6D risk standing for the exchange operating BINANCE:PEPEJPY.
| Regulator | Tier | Certificate No. | Status | Contracting Entity | |
|---|---|---|---|---|---|
| KAS | unknown | RDWW – 465 | Regulated | Binance Poland Spółka z Ograniczoną Odpowiedzialnością | Verify → |
| FSCA | unknown | FSP 51619 | Regulated | Binance Bahrain BSC © | Verify → |
| CNV | unknown | 76 | Regulated | Binance Services Latinoamérica S.A. de C.V. | Verify → |
| CNAD | unknown | PSDA/001-2003 / 648c5c0751164005aa47d43a | Regulated | Binance El Salvador S.A. de C.V. | Verify → |
| FSPR | unknown | FSP1003864 | Regulated | Investbybit Limited | Verify → |
| ICDX | unknown | 001/BAPPEBTI/CP-AK/11/2019 | Regulated | PT. ASET DIGITAL BERKAT | Verify → |
| AUSTRAC | unknown | 100576141-001 | Regulated | InvestbyBit Pty Ltd | Verify → |
| VARA | unknown | VL/24/04/001 | Regulated | Binance FZE | Verify → |
BINANCE:PEPEJPY Market Structure & Custody Architecture
Deterministic vector exhibit mapping ticker symbology, venue licensing, and cross-exchange liquidity.
Cross-Exchange Sibling Markets for PepeAI (PEPEAI)
Compare BINANCE:PEPEJPY against 24 alternative exchange order books listing PEPEAI.
Frequently Asked Questions: BINANCE:PEPEJPY (PepeAI)
Contract specification, exchange regulation, and custody due diligence answers.
What is the BINANCE:PEPEJPY trading instrument and contract specification?
BINANCE:PEPEJPY is the cross-exchange symbology identifier for PepeAI (PEPEAI) quoted against JPY on Binance. In Offshore Firm Ledger's instrument catalogue, PepeAI (PEPEAI) carries global market rank #3498 (CMC ID #24961) and trades across 50 tracked exchange pair feed(s).
Is the execution venue Binance (BINANCE) regulated?
In our supervisory database, Binance (Binance) holds 15 recorded regulatory filing(s) (15 marked regulated) across KAS, FSCA, CNV, CNAD, FSPR, with a composite 6D compliance score of —/10.
Which custody wallets and settlement rails support PepeAI (PEPEAI)?
Recorded self-custody and institutional wallet integrations for PepeAI (PEPEAI) include: https://www.trustwallet.com/, https://s2.coinmarketcap.com/static/cloud/img/dex/default-icon-day-v3.svg?_=bf072d5. Always verify smart-contract addresses or native chain deposit memos directly on Binance before transferring assets.
Which alternative exchanges list PepeAI (PEPEAI) alongside BINANCE?
Cross-exchange sibling order books for PepeAI (PEPEAI) include POLONIEX:PEPEAIUSDT, MEXC:PEPEAIUSDT, BITMART:PEPEAIUSDT, POLONIEX:PEIPEIUSDT, BITFINEX:PEPEUST.P, TVC:PEIPEI2USD, TVC:PEPEUSD, MEXC:PEIPEIUSDT. 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.
