We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
RFC5785 is internet standard for defining well known machine discoverable URIs https://tools.ietf.org/html/rfc5785
We should do something like https://bp.org/.well-known/eos/chain-id/bp.json
The text was updated successfully, but these errors were encountered:
@eosrio any opinion on this. I don’t like to litter the root of my URI path with that. It should be namespaced.
Sorry, something went wrong.
We agree with this new pattern, but since it will require everyone's adoption we would like more opinions on this.
I'm 👍 adding this pattern, 🤔 however the hard task will be:
I'd suggest this URI pattern be optional until there's a majority of BP's who are using it.
Easiest way to implement would be to use a symbolic link to support both URI's:
$ ln -s /var/www/html/bp.json /var/www/html/.well-known/eos/aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906/bp.json
@ellipticasec The final URI path would look something like this, correct?
https://bp.eosnation.io/.well-known/eos/aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906/bp.json
No branches or pull requests
RFC5785 is internet standard for defining well known machine discoverable URIs
https://tools.ietf.org/html/rfc5785
We should do something like
https://bp.org/.well-known/eos/chain-id/bp.json
The text was updated successfully, but these errors were encountered: