to add eosio.md - #5
Draft
bumblefudge wants to merge 5 commits into
Draft
Conversation
bumblefudge
marked this pull request as draft
March 3, 2022 02:29
17 tasks
bumblefudge
added
next meeting
and removed
help wanted
riveign
added a commit
to riveign/namespaces
that referenced
this pull request
Aug 24, 2026
Switches the tron namespace reference from the 0x-prefixed hexadecimal form to decimal, per the consensus reached in TRON Wallet Dev Community Call ChainAgnostic#5 (2026-08-19, tronprotocol/pm#229): tron:0x2b6653dc -> tron:728126428 (Mainnet) tron:0xcd8690dc -> tron:3448148188 (Shasta) tron:0x94a9059e -> tron:2494104990 (Nile) The underlying value is unchanged; only its rendering differs. Decimal matches the eth_chainId return type, Tron's existing ethereum-lists/chains registration, MetaMask and tronwallet-adapter, and the eip155 namespace. Backwards Compatibility now documents the hexadecimal form as a deprecated alias with a normalisation path rather than as the recommended target. Also addresses outstanding review feedback: - discussions-to points at PR ChainAgnostic#170 instead of the XXX placeholder - RPC endpoint list defers to the Tron Foundation networks doc as the authoritative source, since inlined URLs go stale Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
paging @sebastianmontero -- I took a lot of liberties updated and rephrasing your work, please DM me on the CASA discord if you'd like to discuss! In particular, let me know if there's anyone in the EOSIO community I should be asking for help. I noticed googling around that LACChain is using EOSIO, it would be great to get their
chain_idinto the examples 😄 🇦🇷OPEN QUESTIONS:
1.) are the examples I manually composed accurate in the CAIP-10 section?
2.) should there be a CAIP-19/20/21 NFT section, or is the NFT development environment of EOSIO too young/unstandardized? I saw this in the docs and didn't have time to dig into how interoperable they are with one another, or with the EIPs governing NFTs...
3.) similarly, I didn't have time to look into whether the node-APIs support JSON-RPC (and thus justify a CAIP-25/27 section). full disclosure: adding such a section is definitely above my paygrade and availability, but happy to help edit it if someone else can!