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

24-ECIPURI: URI Marker for Federated Ethereum Classic Improvement Proposals #4

Open
sorpaas opened this issue Mar 7, 2019 · 2 comments

Comments

@sorpaas
Copy link
Contributor

commented Mar 7, 2019

@phyro

This comment has been minimized.

Copy link

commented Mar 9, 2019

interesting concept! I've been thinking about making a machine format (json) IPs and just made an argument for it here BelfordZ/starIPs#5 (comment)
If we adopted the json format for the IPs, then the specs.json could list the header part and have a link to the full *IP_{title}_{hash}.json file. I quite liked the idea from starIPs of having deterministic ecips and also the clients signal they are ready by merging the PR in, is there a way to do a smart merge of the two ideas?

@phyro

This comment has been minimized.

Copy link

commented Mar 10, 2019

I made a simple picture to explain how the json ecip format could fit well in the URI proposal https://imgur.com/a/d3jaJQC
There's a few things that are off in the image like the filenames don't match in the specs.json and the actual starIPs json but should give an idea of what i'm talking about

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.