Chain ID
A chain ID is a unique identifier that represents a blockchain network. We use it to distinguish different blockchain networks from each other and to ensure that transactions and messages are sent to the correct network. Slinky network follows the format of identifier_EIP155-version
format.
Official Chain IDs
Mainnet
Name | Chain ID | Identifier | Version | Active |
---|---|---|---|---|
Slinky Hyperloop | 88335 |
| - | 🚫 |
Testnet
Name | Chain ID | Identifier | Version | Active |
---|---|---|---|---|
Slinky Neo Testnet | 88338 |
| 1 | ✅ |
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, Slinky-compatible chains must implement a special structure for their chain identifiers.
Structure
The Slinky 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 the Slinky-compatible chain-id in genesis is the following:
The following are ChainIDs for Slinky Mainnet and Slinky Testnet:
Name | ChainID | Identifier | EIP155 Number | Version Number |
---|---|---|---|---|
Slinky Hyperloop Mainnet |
| slinky | 88335 | - |
Slinky Neo Testnet |
| slinky | 88338 | 1 |
Last updated