to add eosio.md #5
Draft
+226
−0
Conversation
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
17 tasks
bumblefudge
added
next meeting
and removed
help wanted
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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!