tip: 22 title: IOTA Protocol Parameters description: Describes the global protocol parameters for the IOTA protocol author: Wolfgang Welz (@Wollac)
discussions-to: https://github.com/iotaledger/tips/pull/43 status: Active type: Standards layer: Core created: 2021-11-29
This TIP describes the global protocol parameters for the IOTA protocol.
Various other protocol TIPs rely on certain constants that need to be defined for an actual implementations of nodes or other applications using the protocol. This TIP serves as a single document to provide these parameters. It also serves as a historical record of protocol parameter changes.
|Identifier string of the network. Its hash it used for the
Network ID field in transactions.
|Protocol version currently used by the network
|Max Block Length
|Maximum length of a block in bytes. Limits Tangle storage size and communication costs.
|Max Parents Count
|Maximum number of parents of a block.
|Min PoW Score
|Minimum PoW score for blocks to pass syntactic validation.
|First Milestone Index
|First valid milestone index.
|Max IOTA Supply
|Total amount of IOTA coins in circulation.
|Max Inputs Count
|Maximum number of inputs in a transaction payload.
|Max Outputs Count
|Maximum number of outputs in a transaction payload.
|Max Native Token Count
|Maximum number of different native tokens that can be referenced in one transaction.
|Max Tag Length
|Maximum length of a
Tag field in bytes.
|Max Metadata Length
|Maximum length of a
Metadata field in bytes.
|Minimum amount of IOTA that need to be deposited per vbyte of an output.
|SLIP-44 Coin Type (decimal)
|Registered coin type (decimal) for usage in level 2 of BIP44 described in chapter "Coin type".
|SLIP-44 Path Component (
|Registered path component for usage in level 2 of BIP44 described in chapter "Coin type".
|Bech32 Human-Readable Part
|HRP prefix to use for Bech32 encoded IOTA addresses. (e.g.
|Bech32 Human-Readable Part (Test)
|HRP prefix to use for Bech32 encoded IOTA addresses on test- or development networks. (e.g.
The block parameter
Max Block Length and
Max Parent Count, as well as the transaction parameters
Max Inputs Count,
Max Outputs Count,
Max Native Token Count,
Max Tag Length and
Max Metadata Length govern the block and transaction validity. Their values have been chosen to ensure functionality of the protocol within constrained resource restrictions. Furthermore, choosing more conservatives values here is preferable as increasing such limits can always been done preserving backward compatibility.
VByte Cost is the core parameter of the dust protection. The reasoning behind its value is explained in TIP-19 Dust Protection.
Copyright and related rights waived via CC0.