# Glossary ## **A** #### **Account (contract)** A record in a distributed database that includes the balance, code, and data. #### **Ack** A message from the Verifier broadcast to all network participants by Block Verifier (Acki-Nacki) when a block is verified and deemed valid. #### Acki Nacki Igniter The decentralized network starter protocol (DNSP), it collects Node and [License](#license) information, tests and updates the node software and initiates Zerostate (first block) generation once all DNSP requirements are met. **Acki Nacki Wallet (Main Network Wallet)** A non-custodial smart contract wallet serving as the primary wallet of the Acki Nacki network. Available as a mobile and web application. Features ZK Login authentication via zero-knowledge proofs (zk-SNARKs, Groth16) with support for Google, Facebook, and other OpenID providers; multi-factor transaction confirmation; access recovery in case of device or credential loss. No user data is transmitted to external servers — the owner retains full control over assets. The wallet code undergoes formal verification. Install: [ackinacki.com/wallet](https://ackinacki.com/wallet) #### **Attestation** A message sent to the [Block Producer (BP)](#block-producer-bp) by any [Block Keeper (BK)](#block-keeper-bk) 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. ## B #### **Bee Engine** An embeddable client-side mining engine and blockchain verification system for background **NACKL** mining, providing cryptographic validation of computation results and reward distribution based on verifiable user contribution (see [**Bee Engine Integration**](https://dev.ackinacki.com/bee-engine/integration)) #### **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. #### **Block Keeper (BK)** A network participant with a deployed [Epoch](#epoch) contract that receives blocks from the [Block Producer (BP)](#block-producer-bp) and sends back an [Attestation](#attestation) containing the block hash and other metadata. A BK can also perform the roles of a [Block Verifier (Acki-Nacki)](#block-verifier-or-acki-nacki) or a BP. #### **BK Node (BK node)** This is a node that performs the role of a [Block Keeper (BK)](#block-keeper-bk). #### **BK Node Owner** [BK Node keys](#bk-node-owner-keys) owner. #### **BK Node Owner keys** The node management keys that provide access to the BK wallet. They are used for managing the node operations such as staking and adding licenses to the approved list. These keys cannot be used to withdraw Rewards from the BK wallet. #### **BK Reward System** Block Keepers earn rewards based on their participation in the network during each [Epoch](https://docs.ackinacki.com/glossary#epoch), regardless of their specific role ([Block Producer](https://docs.ackinacki.com/glossary#block-producer-bp), [Block Verifier (Acki-Nacki)](https://docs.ackinacki.com/glossary#block-verifier-or-acki-nacki), or [Block Keeper](https://docs.ackinacki.com/glossary#block-keeper-bk)). The reward depends on the [stake](https://docs.ackinacki.com/glossary#stake) and [Reputation Coefficient](https://docs.ackinacki.com/glossary#reputation-coefficient), and is evenly distributed among the licenses delegated to it. #### **BK set** A set of Block Keepers from which a Block Producer is selected for each [thread](#thread).\ Block Keepers are added to the BK set from the [Future BK set](#future-bk-set).\ The members of the BK‑set ensure the operation of the network: they send [attestations](#attestation), validate blocks, and issue [Ack](#ack)/[Nack](#nack) signals.\ The size of the BK‑set directly affects the network’s security parameters, defining how many attestations are required to confirm blocks and the percentage of [Block Verifiers (or Acki‑Nacki)](#block-verifier-or-acki-nacki) needed for each block. #### **BK Wallet** The wallet used for staking. The address of the BK Wallet serves as the identifier of the node. #### BK Wallet whitelist A list of [license numbers](#license-number) that can be delegated to this node. #### **Block Manager (BM)** 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. A BM operates in conjunction with a specific BK, and this pairing is defined during start of BM. #### **BM Reward System** The amount of NACKL tokens accrued for processing BM external messages during a single Epoch. The reward should be claimed once per Epoch, but it can only be claimed **after** the slashing period (approximately after 5% of the next epoch’s blocks have been processed). #### **Block Producer (BP)** The leader of a particular [Thread](#thread) responsible for block production. #### **Block Verifier (or Acki-Nacki)** A Block Keeper responsible for block validation, who notifies all network participants of whether the block is valid or not by sending an [ACK](#ack) or [NACK](#nack) message. #### **BLS keys** The keys used by BK to sign blocks. The lifespan of the keys is one [Epoch](#epoch). For a new Epoch, new BLS keys will need to be generated. Each BK stores a list of [BLS](#bls-keys) public keys of other BKs (for the current Epoch), which they use to verify [attestations](#attestation) on blocks. It is recommended to back up BLS keys every time they regenerated. ## C #### **Common section** The section of the block that contains information shared among all network participants. ## D #### **Dapp ID** 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. #### Denominations A denomination is a fixed lot size when selling [SHELL](#shell). There are four denominations, similar to banknotes: | Denomination (USDC ecc) | SHELL Equivalent | | :---------------------: | :--------------: | | 1 | 100 | | 10 | 1,000 | | 100 | 10,000 | | 1,000 | 100,000 | No other denominations exist. When selling SHELL, the AN Wallet automatically breaks down your amount into lots of these denominations. ## E #### **Epoch of the BK** The participation period in the Acki Nacki protocol during which a participant acts as a [Block Keeper](#block-keeper-bk). It begins immediately after the [Pre-Epoch](#pre-epoch) and lasts for 259,200 blocks (about 24 hours). The duration of a specific BK’s epoch may be extended if the number of BKs in the network is lower than required. #### **Epoch of the BM** The participation period in the Acki Nacki protocol during which a participant acts as a [Block Manager](#block-manager-bm). The length of an epoch is 259 200 blocks (about 24 hours). #### **Extra Currency Collection** A set of currencies within the Acki Nacki network designed to address various tasks beyond [VMSHELL](#vmshell) 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 ([NACKL](#nackl), index 1) or transferring funds between different [Dapp IDs](#dapp-id) for subsequent conversion ([SHELL](#shell), index 2) and settlement in a US dollar-pegged stablecoin ([USDC](#usdc-ecc), index 3) ## F #### Free Reserve The USDC held in the Accumulator contract that is not reserved for SHELL sellers. It is formed as follows: when a buyer purchases SHELL but there aren't enough sellers in the queues, the system creates (mints) new SHELL. The USDC paid for minted SHELL forms the free reserve. Seller funds are never touched. #### Future BK set A list of prospective [Block Keepers (BKs)](#block-keeper-bk) for whom a [Pre‑Epoch](#pre-epoch) contract has already been deployed.\ This list is used for pre‑approving access to the main [BK set](#bk-set).\ After the [Epoch](#epoch) contract is deployed, the future BK must be approved by the current BK set to be added to the active BK set. Otherwise, it will be removed from the Future BK set. ## L #### License The [**BK License**](https://docs.ackinacki.com/for-node-owners/protocol-participation/block-keeper/license/acki-nacki-vk-node-license) is a [contract](https://github.com/ackinacki/ackinacki/blob/main/contracts/bksystem/License.sol) that grants the right for a [Block Keeper (BK)](#block-keeper-bk) to participate in the protocol. The license is delegated to a specific BK. Each BK can be delegated up to 20 (twenty) licenses. The Licenses are delegated without restrictions. The **BM License** is a [contract](https://github.com/ackinacki/ackinacki/blob/main/contracts/bksystem/LicenseBM.sol) that grants a [Block Manager (BM)](#block-manager-bm) the right to participate in the network. Each BM License is delegated to a BM wallet *(1 wallet - 1 license)*. #### License number An **on-chain unique number** assigned during the deployment of the License contract. #### License Owner A person who [registered at the Acki Nacki Dashboard](https://docs.ackinacki.com/protocol-participation/license/license-dashboard-guide) and has acquired a [License](https://docs.ackinacki.com/protocol-participation/license/acki-nacki-node-license) and License Owner Keys to participate in the Acki Nacki protocol. #### License Owner Keys The keys used to manage license contracts (delegate and revoke delegation) and withdraw staking rewards. They can be obtained by [registering in the dashboard](https://docs.ackinacki.com/protocol-participation/license/license-dashboard-guide). #### Lot A lot is a single indivisible sell order for SHELL. Each lot is tied to a specific denomination and can only be sold in full. Partial selling of a lot is not possible. **Example:** a lot with denomination 10 USDC ecc means the seller deposited 1,000 SHELL and is waiting to receive 10 USDC ecc when their turn comes. ## M #### **Minimal Stake of the BK** 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. #### **Minimal Stake of the BM** The minimum amount of tokens locked on Block Manager wallet.\ It is calculated individually and represents the product of a coefficient and the total amount of [**NACKL**](#nackl) earned by the BM. The coefficient depends on the time elapsed since the network launch and decreases over time.\ If a BM stops operating in the middle of an [Epoch](#epoch-of-the-bm), no reward is accrued for that Epoch. #### Maximum stake The maximum number of tokens a Block Keeper can stake to participate in the network. This stake remains valid as long as the license stays active. The value is dynamically adjusted based on the current number of Block Keepers in the network, the total number of tokens minted exclusively by Block Keepers, and the number of tokens burned due to slashing penalties. #### **Mobile Verifier** 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. ## N #### **Nack** A message from the Verifier broadcast to all network participants by Block Verifier (Acki-Nacki) when a block is verified and deemed invalid. #### **NACKL** The native network token, used for security guarantees: staking, slashing and block rewards.\ (currency collection index: 1) #### Node Provider An off-chain entity that for provides [Block Keeper (BK) nodes](#bk-node-bk-node) to license owners, allowing them to participate in the protocol by delegating their licenses to specific nodes. Node Provider keys are used to sign and validate the delegation to a particular Node Provider before Network start to form the zerostate, they do not operate on-chain. Subsequently, the license owner receives a share of the rewards earned by the BK for participating in the protocol ## P #### **Pre-Epoch** The period before the [Epoch](#epoch) during which a [BK node](#block-keeper-node-bk-node) synchronizes states with the network. #### Proxy A specialized network service designed to optimize block exchange between participants in the Acki Nacki network. Its primary purpose is to reduce overall network traffic between nodes and to improve the scalability and stability of the network. ## R #### **Reputation Coefficient** A metric that increases the rewards for [Block Keepers](#block-keeper-bk) based on their continuous participation in the protocol. ## S #### **SHELL** The utility token within the Acki Nacki network is designed to compensate [NACKL](#nackl) holders for the computing resources the network provides. Minted by depositing USDС ecc, but it isn't collateralized. It can be converted to [VMSHELL](#vmshell) 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 [Dapp IDs](#dapp-id). (currency collection index: 2) #### **Stake** The amount of [NACKL](#nackl) tokens required to participate in the Acki Nacki protocol. It is calculated as the total sum of all stakes from licenses delegated to a specific node. At the launch of the Acki Nacki network (zerostate), staking is not required if a [License BK](#license) is present. [Staking](https://github.com/ackinacki/ackinacki/tree/main?tab=readme-ov-file#staking) will become necessary for validation at a later stage. ## T #### **Thread** A subset of nodes that serve a particular subset of [Accounts](#account-contract). ## U #### USDC ecc A stablecoin pegged to the US dollar. Used for settlements when [buying](https://docs.ackinacki.com/for-users/buy-sell-shell/buying-shell/ways-to-buy-shell) and[ selling](https://docs.ackinacki.com/for-users/buy-sell-shell/selling-shell) SHELL (the rate is fixed and immutable: **1 USDC = 100 SHELL)**. Within the Acki Nacki network, USDC exists as ECC\[3] — an element of the [Extra Currency Collection](#extra-currency-collection). ## V #### VMSHELL The unit of account used to cover network fees. It is converted from [SHELL](#shell) and cannot be converted back to SHELL. VMSHELL can be transferred between contracts that belong to the same [Dapp ID](#dapp-id). ## Z #### **Zerostate** The initial state of the network, representing the first block state of the blockchain. It is created after all the requirements of the [**Decentralized Network Starter Protocol (DNSP)**](https://docs.ackinacki.com/protocol-participation/block-keeper/join-dnsp-gossip) have been fulfilled. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ackinacki.com/glossary.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.