Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Protocol for blockchain addressing #156

Open
MidnightLightning opened this issue May 15, 2023 · 0 comments
Open

Protocol for blockchain addressing #156

MidnightLightning opened this issue May 15, 2023 · 0 comments

Comments

@MidnightLightning
Copy link

This project aims to identify things "in a network", and for the most part focuses on the TCP/IP networking stack, but extends into the IPFS network and Onion/Tor network too.

But I don't see a means to indicate content to be looked up on a blockchain? IPFS content has a lot of usage with blockchain-based projects, and if there were reflexive ways for referring back to blockchain-based data, I think that would be very helpful.

Similar to how the main README gives examples of /http/example.com/index.html and /tls/sni/example.com/http/example.com/index.html for accessing web content (not just connecting to the web server that controls the content), I believe the following for blockchain-related content would fit that pattern:

/web3/<CHAINID>/<ADDRESS>/<FUNCTION>.<RETURN_TYPE>
/web3/<CHAINID>/ens/<ENS_NAME>/<FUNCTION>.<RETURN_TYPE>

This proposal puts the chain ID first, which makes this different than ERC4804 in the ordering of the address parts, but the other logic of turning functions into path parts from ERC4804 could apply here too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant