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

Readability Problems #6

Open
BelfordZ opened this issue Mar 3, 2019 · 4 comments
Open

Readability Problems #6

BelfordZ opened this issue Mar 3, 2019 · 4 comments

Comments

@BelfordZ
Copy link
Owner

BelfordZ commented Mar 3, 2019

3.) Names that base on hashes can become very hard to read in my opinion. Especially when we have Replaces and Superseded-by as hashes. I suggest we add a short title to it e.g. *IP-{title}-{8_bytes_hash}

Originally posted by @phyro in #2 (comment)

@ghost
Copy link

ghost commented Mar 5, 2019

I think that, applied to ECIP, a format like

ECIP-06feed87-BlockGasReduction can be standardized.

*IP-{8_bytes_hash}-{title}

@phyro
Copy link
Collaborator

phyro commented Mar 5, 2019

Copying my response from the discord:

it'd put title first because it doesn't change for the machine and is easier for a human to read. Also, sorting them can group different versions of the same proposal

@YazzyYaz
Copy link
Collaborator

YazzyYaz commented Mar 5, 2019

I think some sort of standard is good for human readability:

  1. ECIP-{NUMBER}-{NAME}
  2. ECIP-{HASH}

So, original ECIP-{HASH} idea can reference an ECIP-{NUMBER}-{NAME} that is externally referenced and marketed to the community.

I guarantee that no one is gonna remember a hash number or they'll even make mistakes typing it, so if it can tie in a DNS way to a naming convention and an external numbering reference, might be easiest.

@phyro
Copy link
Collaborator

phyro commented Mar 5, 2019

another idea if we want to have easy ipfs links: ECIP-{title}-{IPFS hash of file content}

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

3 participants