deep-stack/laconicd-deprecated
7
0
Fork 0
forked from cerc-io/laconicd-deprecated
Code Pull Requests Activity
d376ff9b8e
laconicd-deprecated/docs/basics/chain_id.md
Federico Kunze Küllmer 6794daf014
rpc, docs: private APIs (#525)
2021-09-04 10:18:32 +00:00

1.7 KiB
Raw Blame History

Chain ID

Learn about the Ethermint chain-id format {synopsis}

The Chain Identifier

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, Ethermint-compatible chains must implement a special structure for their chain identifiers.

Structure

The Ethermint 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.

Format

The format for specifying and Ethermint compatible chain-id in genesis is the following:

{identifier}_{EIP155}-{version}

The following table provides an example where the second row corresponds to an upgrade from the first one:

ChainID Identifier EIP155 Number Version Number
ethermint_9000-1 ethermint 9000 1
ethermint_9000-2 ethermint 9000 2
... ... ... ...
ethermint_9000-N ethermint 9000 N