Protocol Documentation

Unique indexes into the set of keys in AuthorizationV0.

Number of keys requred to authorize an update.

Whether this is an initial or normal account.

Address of the newly created account.

Credential registration ID of the first credential.

Identify the account by the address of the account.

Identify the account by the credential that belongs or has belonged to it.

Identify the account via its index.

Next sequence number to be used for transactions signed from this account.

Current (unencrypted) balance of the account.

Release schedule for any locked up amount. This could be an empty release schedule.

Map of all currently active credentials on the account. This includes public keys that can sign for the given credentials, as well as any revealed attributes. This map always contains a credential with index 0.

Lower bound on how many credentials must sign any given transaction from this account.

The encrypted balance of the account.

The public key for sending encrypted balances to the account.

Internal index of the account. Accounts on the chain get sequential indices. These should generally not be used outside of the chain, the account address is meant to be used to refer to accounts, however the account index serves the role of the baker id, if the account is a baker. Hence it is exposed here as well.

Present if the account is a baker or delegator. In that case it is the information about the baker or delegator.

Canonical address of the account. This is derived from the first credential that created the account.

Block in which to query the account information.

Specification of the account.

The account is a baker.

The account is a delegator.

Amount staked at present.

A flag indicating whether rewards paid to the baker are automatically restaked or not.

Information about the baker that is staking.

If present, any pending change to the delegated stake.

Present if the account is currently a baker, i.e., it is in the baking committee of the current epoch.

The amount that the account delegates.

Whether the earnings are automatically added to the staked amount.

The entity to which the account delegates.

If present, any pending change to the delegated stake.

The cost of the transaction. Paid by the sender.

The sender of the transaction.

The effects of the transaction.

No effects other than payment from this transaction. The rejection reason indicates why the transaction failed.

A smart contract module with the attached reference was deployed.

A smart contract was initialized.

A smart contract instance updated was issued.

A simple account to account transfer occurred.

A baker was added.

A baker was removed.

A baker's stake was updated.

A baker's restake earnings setting was updated.

A baker's keys were updated.

An encrypted amount was transferred.

An account transferred part of its public balance to its encrypted balance.

An account transferred part of its encrypted balance to its public balance.

A transfer with a release schedule was made.

Keys of a specific credential were updated.

Account credentials were updated.

Some data was registered on the chain.

A baker was configured. The details of what happened are contained in a list of BakerEvents.

A delegator was configured. The details of what happened are contained in a list of DelegatorEvents.

Amount that was transferred.

Receiver account.

Memo.

If the stake was updated (that is, it changed and did not stay the same) then this is present, otherwise it is not present.

The credential ids that were added.

The credentials that were removed.

The (possibly) updated account threshold.

Transaction type of a failed transaction, if known. In case of serialization failure this will not be set.

Reason for rejection of the transaction.

Receiver account.

The list of releases. Ordered by increasing timestamp.

Optional memo.

Sender of the transaction.

Sequence number of the transaction.

Maximum amount of energy the transaction can take to execute.

Latest time the transaction can included in a block.

A pre-serialized payload in the binary serialization format defined by the protocol.

A transfer between two accounts. With an optional memo.

A map from `CredentialIndex` to `SignatureMap`s. The type `CredentialIndex` is not used directly, as messages cannot be keys in maps. The map cannot contain more than 2^8 signatures.

Must not exceed 100000.

The block to get ancestors of.

The maximum number of ancestors returned.

Unique identifier of the anonymity revoker.

Description of the anonymity revoker.

Elgamal encryption key of the anonymity revoker.

Hash of the block.

Absolute height of the block, height 0 is the genesis block.

The set of keys authorized for chain updates.

New emergency keys.

New protocol update keys.

Access structure for updating the consensus parameters. Previously, this was the election difficulty.

Access structure for updating the euro per energy.

Access structure for updating the micro CCD per euro.

Access structure for updating the foundation account.

Access structure for updating the mint distribution.

Access structure for updating the transaction fee distribution.

Access structure for updating the gas rewards.

Access structure for updating the pool parameters. For V0 this is only the baker stake threshold, for V1 there are more.

Access structure for adding new anonymity revokers.

Access structure for adding new identity providers.

Access structure for updating the cooldown periods related to baking and delegation.

Access structure for updating the length of the reward period.

A baker was added.

A baker was removed.

The baker's stake was increased.

The baker's stake was decreased.

The baker's setting for restaking earnings was updated.

Baker keys were updated.

The baker's open status was updated.

The baker's metadata URL was updated.

The baker's transaction fee commission was updated.

The baker's baking reward commission was updated.

The baker's finalization reward commission was updated.

The keys with which the baker registered.

The amount the account staked to become a baker. This amount is locked.

Whether the baker will automatically add earnings to their stake or not.

Baker's id.

The new value of the flag.

Baker's id

The baking reward commission

Baker's id

The finalization reward commission

Baker's id.

The URL.

Baker's id.

The new open status.

Baker's id.

The transaction fee commission.

Baker's id.

The new stake.

Baker's id.

The new stake.

Identity of the baker. This is actually the account index of the account controlling the baker.

Baker's public key used to check whether they won the lottery or not.

Baker's public key used to check that they are indeed the ones who produced the block.

Baker's public key used to check signatures on finalization records. This is only used if the baker has sufficient stake to participate in finalization.

ID of the baker whose keys were changed.

Account address of the baker.

The new public key for verifying block signatures.

The new public key for verifying whether the baker won the block lottery.

The new public key for verifying finalization records.

Whether the pool allows delegators.

The URL that links to the metadata about the pool.

The commission rates charged by the pool owner.

The baker id and public keys for the baker.

The effective stake of the baker for the consensus protocol. The returned amount accounts for delegation, capital bounds and leverage bounds.

The effective commission rate for the baker that applies for the reward period.

The amount staked by the baker itself.

The total amount of capital delegated to this baker pool.

Whether the baker is a finalizer or not.

Minimum threshold required for registering as a baker.

Affected baker.

New stake.

A boolean which indicates whether it increased (`true`) or decreased (`false`).

The IP address of the banned peer.

The quorum certificate. Is present if and only if the block is not a genesis block.

The timeout certificate. Is present only if the round prior to the round of the block timed out.

The epoch finalization entry. Is present only if the block initiates a new epoch.

There is no finalization data in the block.

There is a single finalization record with the block.

Query for the best block.

Query for the last finalized block.

Query for the block specified by the hash. This hash should always be 32 bytes.

Query for a block at absolute height, if a unique block can be identified at that height.

Query for a block at height relative to a genesis index.

Genesis index to start from.

Height starting from the genesis block at the genesis index.

Whether to return results only from the specified genesis index (`true`), or allow results from more recent genesis indices as well (`false`).

Hash of the block.

Absolute height of the block, height 0 is the genesis block.

The parent block hash. For a re-genesis block, this will be the terminal block of the previous chain. For the initial genesis block, this will be the hash of the block itself.

The last finalized block when this block was baked.

The genesis index for this block. This counts the number of protocol updates that have preceded this block, and defines the era of the block.

The height of this block relative to the (re)genesis block of its era.

The time the block was received.

The time the block was verified.

The slot number in which the block was baked. Present in protocol versions 1-5.

The time of the slot in which the block was baked.

The baker id of account baking this block. Not provided for a genesis block.

Whether the block is finalized.

The number of transactions in the block.

The energy cost of the transactions in the block.

The total byte size of all transactions in the block.

The hash of the block state after this block.

Protocol version to which the block belongs.

Block round. Present from protocol version 6.

Block epoch. Present from protocol version 6.

The hash of the block item that identifies it to the chain.

Account transactions are messages which are signed and paid for by an account.

Credential deployments create new accounts. They are not paid for directly by the sender. Instead, bakers are rewarded by the protocol for including them.

Update instructions are messages which can update the chain parameters. Including which keys are allowed to make future update instructions.

Block item is received, but not yet in any blocks.

Block item is committed to one or more blocks. The outcomes are listed for each block. Note that in the vast majority of cases the outcome of a transaction should not be dependent on the block it is in, but this can in principle happen.

Block item is finalized in the given block, with the given summary.

Index of the transaction in the block where it is included.

The amount of NRG the transaction cost.

Hash of the transaction.

Details about an account transaction.

Details about an account creation.

Details about a chain update.

The block hash.

The block item summary.

The key type

The value type

The amount awarded to each baker.

The remaining balance of the baker reward account.

The total fees paid for transactions in the block.

The old balance of the GAS account.

The new balance of the GAS account.

The amount awarded to the baker.

The amount awarded to the passive delegators.

The amount awarded to the foundation.

The baker of the block, who will receive the award.

The total fees paid for transactions in the block.

The old balance of the GAS account.

The new balance of the GAS account.

The amount awarded to the baker.

The amount awarded to the foundation.

The baker of the block, who receives the award.

The foundation account.

The amount awarded to each finalizer.

The remaining balance of the finalization reward account.

The amount allocated to the banking reward account.

The amount allocated to the finalization reward account.

The amount allocated as the platform development charge.

The account to which the platform development charge is paid.

The account that got rewarded.

The transaction fee reward at payday to the account.

The baking reward at payday to the account.

The finalization reward at payday to the account.

The account that got rewarded.

The transaction fee reward at payday to the account.

The pool owner (passive delegators when not present).

Accrued transaction fees for pool.

Accrued baking rewards for pool.

Accrued finalization rewards for pool.

The absolute block height.

Genesis index to start from.

Height starting from the genesis block at the genesis index.

Whether to return results only from the specified genesis index (`true`), or allow results from more recent genesis indices as well (`false`).

Live blocks at the given height.

The hash of the block.

Further blocks branching of this block.

Share of the encryption of IdCredPub.

Chain parameters that apply when the block is a protocol version 1-3 block.

Chain parameters that apply when the block is a protocol version 4-5 block.

Chain parameters that apply when the block is a protocol version 6- block.

Election difficulty for consensus lottery.

Euro per energy exchange rate.

Micro CCD per euro exchange rate.

Extra number of epochs before reduction in stake, or baker deregistration is completed.

The limit for the number of account creations in a block.

Current mint distribution

Current transaction fee distribution.

Current gas reward parameters.

The foundation account.

Minimum threshold for becoming a baker.

Keys allowed to do root updates.

Keys allowed to do level1 updates;

Keys allowed to do parameter updates.

Election difficulty for consensus lottery.

Euro per energy exchange rate.

Micro CCD per euro exchange rate.

Extra number of epochs before reduction in stake, or baker deregistration is completed.

Current time parameters. The time parameters indicates the mint rate and the reward period length, i.e. the time between paydays.

The limit for the number of account creations in a block.

Current mint distribution

Current transaction fee distribution.

Current gas reward parameters.

The foundation account.

Parameters governing baking pools and their commissions.

Keys allowed to do root updates.

Keys allowed to do level1 updates;

Keys allowed to do parameter updates.

Consensus parameters.

Euro per energy exchange rate.

Micro CCD per euro exchange rate.

Extra number of epochs before reduction in stake, or baker deregistration is completed.

Current time parameters. The time parameters indicates the mint rate and the reward period length, i.e. the time between paydays.

The limit for the number of account creations in a block.

Current mint distribution

Current transaction fee distribution.

Current gas reward parameters.

The foundation account.

Parameters governing baking pools and their commissions.

Keys allowed to do root updates.

Keys allowed to do level1 updates;

Keys allowed to do parameter updates.

Finalization committee parameters

The range of allowed finalization commissions.

The range of allowed baker commissions.

The range of allowed transaction commissions.

Fraction of finalization rewards charged by the pool owner.

Fraction of baking rewards charged by the pool owner.

Fraction of transaction rewards charged by the pool owner.

Hash of the current best block.

Hash of the (original) genesis block.

Time of the (original) genesis block.

(Current) slot duration in milliseconds. Present only in protocol versions 1-5.

(Current) epoch duration in milliseconds.

Hash of the last finalized block.

Absolute height of the best block.

Absolute height of the last finalized block.

Total number of blocks received.

The last time a block was received.

Exponential moving average latency between a block's slot time and received time.

Standard deviation of exponential moving average latency between a block's slot time and received time.

Exponential moving average time between receiving blocks.

Standard deviation of exponential moving average time between receiving blocks.

Total number of blocks received and verified.

The last time a block was verified (added to the tree).

Exponential moving average latency between a block's slot time and its arrival.

Standard deviation of exponential moving average latency between a block's slot time and its arrival.

Exponential moving average time between block arrivals.

Standard deviation of exponential moving average time between block arrivals.

Exponential moving average number of transactions per block.

Standard deviation of exponential moving average number of transactions per block.

Number of finalizations.

Time of last verified finalization.

Exponential moving average time between finalizations.

Standard deviation of exponential moving average time between finalizations.

Currently active protocol version.

The number of chain restarts via a protocol update. A completed protocol update instruction might not change the protocol version specified in the previous field, but it always increments the genesis index.

Block hash of the genesis block of current era, i.e., since the last protocol update. Initially this is equal to 'genesis_block'.

Time when the current era started.

The current duration to wait before a round times out. Present from protocol version 6.

The current round. Present from protocol version 6.

The current epoch. Present from protocol version 6.

The first block in the epoch with timestamp at least this is considered to be the trigger block for the epoch transition. Present from protocol version 6.

Parameters controlling round timeouts.

Minimum time interval between blocks.

Maximum energy allowed per block.

The index of the smart contract.

The subindex of the smart contract instance. Currently not used, so it is always 0.

Contract version.

Module with the source code of the contract.

The newly assigned address of the contract.

The amount the instance was initialized with.

The name of the contract.

Any contract events that might have been genereated by the contract initialization.

A contract instance was updated.

A contract transferred an amount to an account.

A contract was interrupted. This occurs when a contract invokes another contract or makes a transfer to an account.

A previously interrupted contract was resumed.

A contract was upgraded.

The contract interrupted.

The events generated up until the interruption.

The contract resumed.

Whether the action that caused the interruption (invoke contract or make transfer) was successful or not.

Sender contract.

Amount transferred.

Receiver account.

The that was upgraded.

The module from which the contract was upgraded.

The module to which it was upgraded.

Number of seconds that pool owners must cooldown when reducing their equity capital or closing the pool.

Number of seconds that a delegator must cooldown when reducing their delegated stake.

Commitment to the PRF key.

Commitment to the counter used to generate the credential registration id.

Commitment to the `max_accounts` value, which determines the maximum number of credentials that may be created from the identity object.

Commitments to the attributes which have not been revealed in the policy.

List of commitments to the coefficients of the sharing polynomial. This polynomial is used in a shared encryption of `id_cred_pub` among the anonymity revokers.

A raw payload, which is just the encoded payload. A typed variant might be added in the future.

A free-form string used to distinguish between different chains even if they share other parameters.

Generators for the bulletproofs. It is a serialized list of 256 group elements in the G1 group of the BLS12-381 curve.

A shared commitment key known to the chain and the account holder (and therefore it is public). The account holder uses this commitment key to generate commitments to values in the attribute list. It is a serialized pair of group elements in the G1 group of the BLS12-381 curve.

The delegator's stake increased.

The delegator's stake decreased.

The delegator's restaking setting was updated.

The delegator's delegation target was updated.

A delegator was added.

A delegator was removed.

Delegator's id

New delegation target

Delegator's id

Whether earnings will be restaked

Delegator's id

New stake

Delegator's id

New stake

Delegate passively, i.e., to no specific baker.

Delegate to a specific baker.

The delegator account address.

The amount of stake currently staked to the pool.

Pending change to the current stake of the delegator.

The delegator account address.

The amount of stake currently staked to the pool.

The name.

A link to more information about the anonymity revoker or identity provider.

A free form description of the revoker or provider.

The current block state is undefined. It should be initialized with a 'load_block_state' request before any other operations.

The requested block was not found, so its state could not be loaded. Response to 'load_block_state'.

The specified account was not found. Response to 'get_account_info', 'mint_to_account' and 'run_transaction'.

The specified instance was not found. Response to 'get_instance_info'.

The amount to mint would overflow the total CCD supply. Response to 'mint_to_account'.

The balance of the sender account is not sufficient to pay for the operation. Response to 'run_transaction'.

The energy supplied for the transaction was not sufficient to perform the basic checks. Response to 'run_transaction'.

The contract invocation failed. Response to 'invoke_instance'.

The maximum amount that can be minted without overflowing the supply.

The minimum balance required to perform the operation.

The currently-available balance on the account to pay for the operation.

The minimum energy required for the transaction to be included in the chain. Note that, even if the energy supplied for the transaction is enough to prevent a `EnergyInsufficient`, the transaction can still be rejected for having insufficient energy. In that case, a `TransactionExecuted` response will be produced, but indicate the transaction was rejected.

If invoking a V0 contract this is not provided, otherwise it is potentially return value produced by the call unless the call failed with out of energy or runtime error. If the V1 contract terminated with a logic error then the return value is present.

Energy used by the execution.

Contract execution failed for the given reason.

Invoker of the contract. If this is not supplied then the contract will be invoked by an account with address 0, no credentials and sufficient amount of CCD to cover the transfer amount. If given, the relevant address (either account or contract) must exist in the blockstate.

Address of the contract instance to invoke.

Amount to invoke the smart contract instance with.

The entrypoint of the smart contract instance to invoke.

The parameter bytes to include in the invocation of the entrypoint.

The maximum energy to allow for the invocation. Note that the node imposes an energy quota that is enforced in addition to this limit.

The account to mint to.

The amount to mint and credit to the account.

Load the state of the specified block to use for subsequent requests. The state is taken at the end of execution of the block, and the block’s timestamp is used as the current timestamp. The energy cost for this operation is 2000.

Run a query on the state.

Run a (non-transaction) operation to modify the state.

The request produced an error. The request otherwise has no effect on the state.

The request was successful.

The remaining available energy quota after the dry run operation.

Credential index. Must not exceed 255.

Key index. Must not exceed 255.

Sets the current block time to the given timestamp for the purposes of future transactions. The energy cost of this operation is 50.

Add a specified amount of newly-minted CCDs to a specified account. The amount cannot cause the total circulating supply to overflow. The energy cost of this operation is 400.

Dry run a transaction, updating the state if it succeeds. The energy cost of this operation is 400 plus the energy used by executing the transaction.

Look up information on a particular account. The energy cost for this query is 200.

Look up information about a particular smart contract. The energy cost for this query is 200.

Invoke an entrypoint on a smart contract instance. No changes made to the state are retained at the completion of the operation. The energy cost for this query is 200 plus the energy used by the smart contract execution.

The state from the specified block was successfully loaded. Response to 'load_block_state'.

Details of the requested account. Response to 'get_account_info'.

Details of the requested smart contract instance. Response to 'get_instance_info'.

The smart contract instance was invoked successfully.

The current timestamp was set successfully. Response to 'set_timestamp'.

The specified amount was minted and credited to the account. Response to 'mint_to_account'.

The specified transaction was executed. Note that the transaction could still have been rejected. Response to 'run_transaction'.

The timestamp of the block, taken to be the current timestamp.

The hash of the block that was loaded.

The protocol version at the specified block. The behavior of operations can vary across protocol versions.

If invoking a V0 contract this is absent. Otherwise it is the return value produced by the contract.

Energy used by the execution.

Effects produced by contract execution.

The amount of energy actually expended in executing the transaction.

The details of the outcome of the transaction.

If this is an invocation of a V1 contract that produced a return value, this is that value. Otherwise it is absent.

The account to use as the sender of the transaction.

The energy limit set for executing the transaction.

The payload of the transaction.

Which credentials and keys should be treated as having signed the transaction. If none is given, then the transaction is treated as having one signature for credential 0, key 0. Therefore, this is only required when the transaction is from a multi-signature account. There are two reasons why you might want to specify signatures: * The cost of the transaction depends on the number of signatures, so if you want to get the correct cost for a multi-signature transaction, then specifying the signatures supports this. * When changing account keys on a multi-credential account, the transaction must be signed by the credential whose keys are being changed. Note that the signature thresholds are not checked as part of the dry run. Duplicated signatures are only counted once.

Which file to dump the packages into. Requires a valid path.

Whether the node should dump raw packages.

Baking lottery election difficulty. Present only in protocol versions 1-5.

Current leadership election nonce for the lottery.

List of the currently eligible bakers.

The ID of the baker.

The account address of the baker.

The lottery power of the baker, rounded to the nearest representable "double".

The affected account.

The new self encrypted amount on the affected account.

The input encrypted amount that was removed.

The index indicating which amounts were used.

Encrypted amount that is a result of this account's actions. In particular this list includes the aggregate of - remaining amounts that result when transferring to public balance - remaining amounts when transferring to another account - encrypted amounts that are transferred from public balance When a transfer is made all of these must always be used.

Starting index for incoming encrypted amounts. If an aggregated amount is present then this index is associated with such an amount and the list of incoming encrypted amounts starts at the index `start_index + 1`.

If present, the amount that has resulted from aggregating other amounts If this field is present so is `num_aggregated`.

The number of aggregated amounts (must be at least 2 if present). This field is present if and only if `aggregated_amount` is present.

Amounts starting at `start_index` (or at `start_index + 1` if there is an aggregated amount present). They are assumed to be numbered sequentially. The length of this list is bounded by the maximum number of incoming amounts on the accounts, which is currently 32. After that aggregation kicks in.

The affected account.

The new self encrypted amount of the account.

The amount that was transferred from public to encrypted balance.

The quorum certificate for the finalized block.

The quorum certificate for the block that finalizes the block that 'finalized_qc' points to.

A proof that the successor block is an immediate successor of the finalized block.

Query by genesis index and epoch number.

Query for the epoch of a specified block.

The genesis index to query at. The query is restricted to this genesis index, and will not return results for other indices even if the epoch number is out of bounds.

The epoch number to query at.

The minimum size of a finalization committee before `finalizer_relative_stake_threshold` takes effect.

The maximum size of a finalization committee.

The threshold for determining the stake required for being eligible the finalization committee. The amount is given by `total stake in pools * finalizer_relative_stake_threshold`

Block that was finalized by the finalization record.

Index of the finalization round that finalized the block.

Finalization delay used for the finalization round.

List of all finalizers with information about whether they signed the finalization record or not.

Baker ID. Every finalizer is in particular a baker.

The weight of the finalizer in the committee. This is an "absolute" weight.

Whether the finalizer's signature was present on the particular finalization record.

Hash of the block.

Absolute height of the block, height 0 is the genesis block.

The round that was signed off.

The finalizers (identified by their 'BakerId' that signed off the in 'round'.

The fraction paid to the baker.

Fraction paid for including a finalization proof in a block.

Fraction paid for including each account creation transaction in a block.

Fraction paid for including an update transaction in a block.

The fraction paid to the baker.

Fraction paid for including each account creation transaction in a block.

Fraction paid for including an update transaction in a block.

Block in which to query the delegators.

The 'BakerId' of the pool owner.

The keys.

The number of keys needed to make a chain update.

Amount of CCD to send to the instance.

Reference to the module from which the instance will be created.

Name of the contract to initialize. This is expected to be in the format `init_name`.

Parameter to call the `init` of the contract with.

Public keys of the credential.

Its registration ID.

The identity provider who signed the identity object from which this credential is derived.

Policy of this credential.

The state of the instance.

The account address which deployed the instance.

The amount of CCD tokens in the balance of the instance.

A list of endpoints exposed by the instance.

The name of the smart contract of the instance.

The module reference for the smart contract module of the instance.

The account address which deployed the instance.

The amount of CCD tokens in the balance of the instance.

A list of endpoints exposed by the instance.

The name of the smart contract of the instance.

The module reference for the smart contract module of the instance.

The block to be used for the query.

The address of the smart contract instance.

The block to be used for the query.

The address of the smart contract instance.

Key to look up. If the instance is a V0 instance then this will not be used.

Contract version.

Address of the affected instance.

The origin of the message to the smart contract. This can be either an account or a smart contract.

The amount the method was invoked with.

The parameter passed to the method.

The name of the method that was executed.

Any contract events that might have been generated by the contract execution.

Block to invoke the contract. The invocation will be at the end of the given block.

Invoker of the contract. If this is not supplied then the contract will be invoked by an account with address 0, no credentials and sufficient amount of CCD to cover the transfer amount. If given, the relevant address (either account or contract) must exist in the blockstate.

Address of the contract instance to invoke.

Amount to invoke the smart contract instance with.

The entrypoint of the smart contract instance to invoke.

The parameter bytes to include in the invocation of the entrypoint.

And what amount of energy to allow for execution. This cannot exceed `100_000_000_000`, but in practice it should be much less. The maximum block energy is typically in the range of a few million.

If invoking a V0 contract this is not provided, otherwise it is potentially return value produced by the call unless the call failed with out of energy or runtime error. If the V1 contract terminated with a logic error then the return value is present.

Energy used by the execution.

Contract execution failed for the given reason.

If invoking a V0 contract this is absent. Otherwise it is the return value produced by the contract.

Energy used by the execution.

Effects produced by contract execution.

Unique identifier of the identity provider.

Description of the identity provider.

Pointcheval-Sanders public key of the identity provider.

Ed25519 public key of the identity provider.

The level 1 keys were updated.

The level 2 keys were updated.

The level 2 keys were updated. This is similar to `level_2_keys_update_v0` except that a few more keys can be updated.

Mint rate per slot.

The fraction of newly created CCD allocated to baker rewards.

The fraction of newly created CCD allocated to finalization rewards.

This will never exceed 255 and can thus be stored in a single byte.

The block to be used for the query.

The reference of the module.

The account onto which the amount was added.

The index the amount was assigned.

The encrypted amount that was added.

Effective time of the release in milliseconds since unix epoch.

Amount to be released.

The best guess for the available account sequence number.

Whether the guess relies on any non-finalized transactions. If true all of the relevant transactions are finalized.

Updates to the root keys.

Updates to the level 1 keys.

Updates to the level 2 keys.

Protocol updates.

Updates to the election difficulty parameter.

Updates to the euro:energy exchange rate.

Updates to the CCD:EUR exchange rate.

Updates to the foundation account.