Chain id naming convention #77
Labels
No Label
bug
C:CLI
C:Crypto
C:Encoding
C:Proto
C:Types
dependencies
docker
documentation
duplicate
enhancement
go
good first issue
help wanted
high priority
in progress
invalid
javascript
low priority
medium priority
question
Status: Stale
Type: ADR
Type: Build
Type: CI
Type: Docs
Type: Tests
urgent
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/laconicd-deprecated#77
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Figure out a naming convention for chain ids.
The current one follows {string}_{number/port}-{number} --adopted from ethermint. Example: laconic_9000-1.
But the conventional approach to naming chains in the cosmos ecosystem has been {string}-{number}. Example: cosmoshub-4
There is no strict rule to follow for chain-ids, but it's better to decide on the best one for us.
Once decided on the naming convention, change the regex check and few other tests to work accordingly.
ab2ea51aac/types/chain_id.go (L18)
The Evmos Chain ID contains 3 main components
Identifier: Unstructured string that defines the name of the application.
EIP155 Number: Immutable EIP155 CHAIN_ID that defines the replay attack protection number.
Version Number: Is the version number (always positive) that the chain is currently running. This number MUST be incremented every time the chain is upgraded or forked in order to avoid network or consensus errors.
The EIP155 corresponds to the ethereum based ChanID. https://chainlist.org/?search=evmos&testnets=true
Every chain must have a unique identifier or chain-id. Tendermint requires each application to define its own chain-id in the genesis.json fields. However, in order to comply with both EIP155 and Cosmos standard for chain upgrades, Evmos-compatible chains must implement a special structure for their chain identifiers.
Hence, laconicd should also adopt the same chain-id format with a unique EIP155 number.
The format for specifying Evmos compatible chain-id in genesis is the following:
{identifier}_{EIP155}-{version}
Helpful Links:
https://docs.evmos.org/users/technical_concepts/chain_id.html
https://chainlist.org/?search=evmos&testnets=true
https://github.com/cosmos/chain-registry/blob/master/evmos/chain.json#L8
https://eips.ethereum.org/EIPS/eip-155
Next steps: Decide on a EIP155 chain id
@AFDudley @i-norden
@AFDudley @i-norden any updates on this?