search

UCRegistry / chain-registry

Standardized registry for multi-interface blockchains
MIT License
37 stars 13 forks source link

Add section about network ID format #13

Closed webmaster128 closed 5 years ago

webmaster128 commented 5 years ago

Will be updated once https://github.com/interchain-registry/interchain-registry/issues/12 is resolved.

Open questions:

  1. Is 32 characters enough?
  2. Do we want to allow upper case characters?
  3. What are your feelings about changing eip155-x to ethereum-eip155-x and trying to start all chain IDs with the ecosystem (e.g. cosmos-hub2, ethereum-eip155-3, iov-lovenet, lisk-da3ed6a454).
pedrouid commented 5 years ago

It should be enough but do we really need to limit it? Is this limited on the Cosmos SDK?

webmaster128 commented 5 years ago

do we really need to limit it?

There are cases where it becomes very helpful when you know the absolute maximum to expect. One is storage in blockchains that need to be limited to prevent misuse. Another case is hardware wallets like the Ledger, where memory as well as display space is very very limited. Here you allocate a specific amount of memory in C that needs to be sufficient to hold the value but must not be larger than necessary.

RiccardoM commented 5 years ago

AFAIK this is not limited inside Cosmos so I would avoid putting a limit on it.

huynh922 commented 2 years ago

..........

Karembit commented 2 years ago

Will be updated once #12 is resolved.

Open questions:

  1. Is 32 characters enough?
  2. Do we want to allow upper case characters?
  3. What are your feelings about changing eip155-x to ethereum-eip155-x and trying to start all chain IDs with the ecosystem (e.g. cosmos-hub2, ethereum-eip155-3, iov-lovenet, lisk-da3ed6a454).

https://github.com/UCRegistry/chain-registry/pull/13#issue-484387531