Add antelope CAIP-19 asset profile (EOS, WAX, Telos)

[okwme]

Adds a CAIP-19 asset profile to the existing antelope namespace. The CAIP-2 profile is already ratified and is not touched.

Who wrote this

I do not represent the antelope ecosystem. I maintain FAR, an open cross-reference between CAIP-19, CoinGecko and ISO 24165 (DTI) identifiers, which needs a way to name 6 assets on this chain. CASA's README invites profiles added to an existing namespace, so this documents how assets are addressed rather than claiming to speak for anyone. Offered for the antelope community to correct, adopt or replace.

Asset namespaces

slip44, token, nft

What this profile establishes

Contract first, then symbol, separated by a single -. Account names are [.12345a-z] and symbol codes are [A-Z], so the two halves have disjoint character classes and a reference self-validates offline with no escaping. Symbol-first with a dotted account name would have needed a parse-from-the-right rule.

The safety case is live and is the reason the contract must be in the identifier. On EOS mainnet the symbol EOS is issued by eosio.token, by iouiouiou123 (100,000,000.0000 EOS), and by eosiotokenis at zero precision — a consumer matching on symbol alone misreports that last one by a factor of 10⁴. USDT is issued by four different contracts.

Precision is deliberately excluded from the reference: an Antelope symbol is 4,EOS, , is not in the charset, and precision is not identity.

Every example was verified against a live node or explorer; anything that could not be verified is marked as such in the document rather than asserted. discussions-to points at 0xcounting/FAR#1.

[Jennie867-5309]

Everyone is using my crypto and Apple ID. I can’t get anything to work. I had a heart attack no food no medicine no bills paid please help me Jennifer Wages

…

On Mon, Sep 14, 2026 at 9:23 AM billy rennekamp ***@***.***> wrote: Adds a CAIP-19 asset profile to the existing antelope namespace. The CAIP-2 profile is already ratified and is not touched. Who wrote this *I do not represent the antelope ecosystem.* I maintain FAR <https://github.com/0xcounting/FAR>, an open cross-reference between CAIP-19, CoinGecko and ISO 24165 (DTI) identifiers, which needs a way to name *6 assets* on this chain. CASA's README invites profiles added to an existing namespace, so this documents how assets are addressed rather than claiming to speak for anyone. Offered for the antelope community to correct, adopt or replace. Asset namespaces slip44, token, nft What this profile establishes *Contract first, then symbol, separated by a single -.* Account names are [.12345a-z] and symbol codes are [A-Z], so the two halves have *disjoint character classes* and a reference self-validates offline with no escaping. Symbol-first with a dotted account name would have needed a parse-from-the-right rule. *The safety case is live and is the reason the contract must be in the identifier.* On EOS mainnet the symbol EOS is issued by eosio.token, by iouiouiou123 (100,000,000.0000 EOS), *and* by eosiotokenis at *zero precision* — a consumer matching on symbol alone misreports that last one by a factor of 10⁴. USDT is issued by four different contracts. Precision is deliberately excluded from the reference: an Antelope symbol is 4,EOS, , is not in the charset, and precision is not identity. Every example was verified against a live node or explorer; anything that could not be verified is marked as such in the document rather than asserted. discussions-to points at 0xcounting/FAR#1 <0xcounting/FAR#1>. ------------------------------ You can view, comment on, or merge this pull request online at: #224 Commit Summary - 79c6d66 <79c6d66> Add antelope CAIP-19 asset profile File Changes (1 file <https://github.com/ChainAgnostic/namespaces/pull/224/files>) - *A* antelope/caip19.md <https://github.com/ChainAgnostic/namespaces/pull/224/files#diff-4eeec2e931a1bdf2fc956b729d67c1a8a6ad9b83b60ea67ddb31d0f72283ce12> (230) Patch Links: - https://github.com/ChainAgnostic/namespaces/pull/224.patch - https://github.com/ChainAgnostic/namespaces/pull/224.diff — Reply to this email directly, view it on GitHub <#224?email_source=notifications&email_token=BGPM7QFU25VVW5M3NVCM7635O75PNA5CNFSNUABEM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UF42DKMRXGQYDCNBSGGTHEZLBONXW5KTTOVRHGY3SNFRGKZFFMV3GK3TUVRTG633UMVZF6Y3MNFRWW>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGPM7QFWW2C33TY7P6YPWI35O75PNAVCNFSNUABFKJSXA33TNF2G64TZHM2DINZWG4YTCNBRHNEXG43VMU5TKNBVGA2TOMZUGE32C5QC> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>