Glossary
Last updated
Last updated
A record in a distributed database that includes the balance, code, and data.
A message from the Verifier broadcast to all network participants by Block Verifier (Acki-Nacki) when a block is verified and deemed valid.
The decentralized network starter protocol (DNSP), it collects Node and information, tests and updates the node software and initiates Zerostate (first block) generation once all DNSP requirements are met.
A message sent to the by any after receiving a block. The Attestation is a BLS signature generated using the BK’s private key. The BP of the next block must aggregate all received Attestations for the previous block into one BLS signature and include it in the Common section of the new block.
An object containing new transactions, which, once finalized, are stored in the blockchain as a permanent and immutable part of the decentralized ledger. Each block includes transaction data, a timestamp, a common section, and a reference to the previous block, creating a chain of interconnected blocks.
(Master keys) The node management keys that provide access to the BK wallet. They are used for managing the node, running node, staking, restaking, and adding licenses to the approved list. These keys cannot be used to withdraw Rewards from the BK wallet.
The wallet used for staking. The address of the BK Wallet serves as the identifier of the node.
A network participant whose primary role is to provide users with blockchain data and process external messages. Block Managers receive a portion of the total block reward based on the number of external messages they process.
The section of the block that contains information shared among all network participants.
Currency Collection
The identifier of a Decentralized Contract System on the Acki Nacki blockchain. This ID is equal to the address of the root smart contract, which is deployed using an external message. All contracts deployed with internal messages automatically receive the same Dapp ID. Whether from the same root contract, or from contracts deployed by the root contract.
An on-chain unique number assigned during the deployment of the License contract.
The minimum amount of tokens a Block Keeper must stake to participate in the network. This value dynamically adjusts based on the difference between the current number of Block Keepers and the required number of Block Keepers in the network.
A participant in the protocol who occasionally validates transactions in subtrees of accounts. Mobile Verifiers compete in an online game, earning Boosts, to secure a place on the mobile verifiers list, which determines their share of the Block reward.
A message from the Verifier broadcast to all network participants by Block Verifier (Acki-Nacki) when a block is verified and deemed invalid.
The native network token, used for security guarantees: staking, slashing and block rewards. (currency collection index: 1)
A service that relays blocks to its subscribers. Type 1 Proxies subscribe to Block Keepers (BKs), which broadcast blocks to the network through them, with BKs specifying their target Proxies during the Pre-Epoch deployment. Type 2 Proxies subscribe to all Type 1 Proxies in the network and directly to BKs without their own Proxy. This structure ensures efficient block distribution across the network.
A network participant with a deployed contract that receives blocks from the and sends back an containing the block hash and other metadata. A BK can also perform the roles of a or a BP.
This is a node that performs the role of a .
owner.
Block Keepers earn rewards based on their participation in the network during each , regardless of their specific role (, , or ). The reward depends on the BK’s and , and is evenly distributed among the licenses delegated to it.
A list of that can be delegated to this node.
The leader of a particular responsible for block production.
A Block Keeper responsible for block validation, who notifies all network participants of whether the block is valid or not by sending an or message.
The keys used by BK to sign blocks. The lifespan of the keys is one . For a new Epoch, new BLS keys will need to be generated. Each BK stores a list of public keys of other BKs (for the current Epoch), which they use to verify on blocks.
A set of currencies within the Acki Nacki network designed to address various tasks beyond tokens, which are used for paying fees. These currencies enhance the flexibility and efficiency of the Acki Nacki ecosystem. They provide diverse functionalities tailored to specific use cases, such as value storage and staking () or transferring funds between different Dapp IDs for subsequent conversion ().
The participation period in the Acki Nacki protocol during which a participant acts as a . It begins immediately after the .
The is a that grants the right for a BK to participate in the protocol and receive rewards. The license is delegated to a specific BK. Each BK can be delegated up to 5 licenses. The Licenses are delegated without restrictions.
A person who and has acquired a and License Owner Keys to participate in the Acki Nacki protocol.
The keys used to manage license contracts (delegate and revoke delegation) and withdraw staking rewards. They can be obtained by .
A model for providing nodes to license owners, allowing them to participate in the protocol by delegating their licenses to specific nodes. Subsequently, the license owner receives a share of the rewards earned by the for participating in the protocol.
The period before the during which a synchronizes states with the network.
A metric that increases the rewards for based on their continuous participation in the protocol.
The utility token within the Acki Nacki network is designed to compensate holders for the computing resources the network provides. It can be converted to to cover network fees at a 1:1 ratio. However, it is not possible to convert VMSHELL back to SHELL. This token can be transferred between different . (currency collection index: 2)
The amount of tokens required to participate in the Acki Nacki protocol. At the launch of the Acki Nacki network (zero state), staking is not required if a is present. Staking will become necessary for validation at a later stage, in accordance with the .
A subset of nodes that serve a particular subset of .
The unit of account used to cover network fees. It is converted from and cannot be converted back to SHELL. VMSHELL can be transferred between contracts that belong to the same .
The initial state of the network, representing the first block state of the blockchain. It is created after all the requirements of the have been fulfilled.