Glossary
Definitions of key terms and concepts used throughout Bitplanet documentation.
A
AI Agent
A digital entity that performs tasks, answers questions, or provides services using artificial intelligence. On Bitplanet, AI agents have unique identities, earn rewards based on usage and market value, and have permanent contribution histories tracked on-chain.
See also: Core Concepts, AI Economy Infrastructure
AI App
Application like Deva that hosts AI agents and submits attribution data. Receives 40% of AI's inflation rewards to cover operational costs.
See also: For AI Apps, Three-Way Split, Request for Core, Deva
AI Tensor Matrix
Multi-dimensional contribution tracking system storing contributions as a 2D matrix (contributor address × contribution type). Records immutable contribution history at each block height, enabling proportional reward distribution.
See also: AI Tensor Matrix Technical Guide, Brahma Module, AITensor
AITensor
Data structure recording contribution state for an AI at specific block height. Contains AI ID and array of AITensorRow entries. Multiple RfCs in same block are merged by summing contribution values.
See also: AI Tensor Matrix, Request for Core, Tensor Merging
AnteHandler
Pre-execution validation chain in BitSDK handling signature verification, fee deduction, and gas metering before transaction execution.
See also: Hooks and Lifecycle, BeginBlock, EndBlock
Attribution Ledger
Bitplanet's core innovation - a blockchain that tracks who contributed what to each AI agent, automatically distributing rewards based on economic value created. Differs from traditional asset ledgers that only track ownership.
See also: Why Bitplanet, AI Tensor Matrix, Brahma Module
Authority
Governance module account that has permission to execute privileged operations like updating module parameters or approving Core Grant Applications.
See also: Governance, Governance Proposal, Core Grant Application
B
BeaconFactory Pattern
Efficient multi-token deployment architecture where multiple proxy contracts share single implementation via beacon. Provides ~90% gas savings (~200K vs ~2.5M gas) and enables batch upgrades across all tokens.
See also: Smart Contract Integration, GemCoreNFT Factory, UUPS
BeginBlock
BitSDK hook executing at start of each block before transaction processing. Bitplanet's x/brahma module uses this to distribute inflation rewards, query market caps, and allocate to participants.
See also: Hooks and Lifecycle, Reward Distribution, EndBlock, PostTxProcessing
BitEVM
Bitplanet's implementation of Ethereum Virtual Machine compatibility, built on top of Cosmos EVM v1.0.0-rc2. Provides full smart contract support, Web3 JSON-RPC API, and custom precompiles for BitSDK module interaction. Implemented as the x/vm module in Bitplanet.
See also: EVM Compatibility, Module Interaction
Bitplanet (BPL)
The native token of the Bitplanet blockchain. Used for gas fees, staking, and reward distribution. Also referred to as bplcoin.
See also: Token Economics, For Token Holders, Gas
BitSDK
Bitplanet's customized blockchain framework based on Cosmos SDK v0.53.3. Extends standard Cosmos SDK with AI-specific modules (x/brahma), enhanced EVM integration (BitEVM), and optimizations for token economics while maintaining full Cosmos ecosystem compatibility.
See also: BitSDK Integration, Architecture Overview, Cosmos SDK
Bounded Processing
Performance safeguard limiting maximum items processed per block: 500 AIs for rewards, 1,000 historical blocks per AI, 1,000 tensor rows per block. Prevents unbounded loops that could halt blockchain.
BplCoinClaimed Event
EVM event emitted when users claim accumulated rewards through smart contracts. Triggers PostTxProcessing hook in x/precompile module to process reward distribution.
Brahma (x/brahma module)
Core BitSDK module implementing AI attribution tracking, Core grant management, reward distribution, and tensor matrix operations. Runs automatic reward distribution every block via BeginBlock hook.
See also: Brahma Module Technical Guide, Module API, AI Tensor Matrix, BeginBlock
Byzantine Fault Tolerant (BFT)
Consensus property allowing network to function correctly even with up to 1/3 malicious or faulty validators.
C
Channel
IBC communication pathway between two blockchains enabling packet relay and state verification.
Claimable Rewards
Two-step reward system where rewards automatically accumulate in module account each block, then users manually claim via transaction. Prevents distribution failures and gives users control over gas costs.
See also: Reward Distribution, For Contributors, BplCoinClaimed Event
CometBFT
The Byzantine Fault Tolerant consensus mechanism used by Bitplanet, formerly known as Tendermint. Provides instant finality (no chain reorganizations), ~6 second deterministic block time, and tolerates up to 1/3 malicious validators.
See also: Architecture Overview, Validator, Byzantine Fault Tolerant, Instant Finality
Contributor
Anyone who helps train, promote, or improve AI agents. Receives 20% of AI's inflation rewards distributed proportionally based on historical contribution records.
See also: For Contributors, Three-Way Split, AI Tensor Matrix, Reward Distribution
Core (Core Token)
Non-transferable permission tokens granted through governance that represent attribution rights. Prove contribution to an AI agent and can be converted 1:1 into Gem tokens. Act as "startup capital" for bootstrapping new AIs.
See also: Core Tokens Technical Guide, For AI Creators, Gem Token, Core Grant Application
Core Grant Application (CGA)
Governance proposal requesting permission to mint Core tokens. Includes requester address, core allocation amount, title, and description. Expires after configured block height (default: 1,000 blocks) and can be revoked by governance.
See also: Submitting Proposals, For AI Creators, Core Token, Request for Core
Cosmos EVM
The EVM implementation for Cosmos SDK-based blockchains, enabling Ethereum smart contract compatibility within the Cosmos ecosystem. BitEVM is built on Cosmos EVM v1.0.0-rc2.
See also: BitEVM, EVM Compatibility
Cosmos SDK
A modular blockchain framework that provides core blockchain functionality including state management, consensus, transaction processing, and governance. Bitplanet's BitSDK is built on Cosmos SDK v0.53.3, extending it with AI-specific capabilities.
See also: BitSDK, BitSDK Integration, Module API, KVStore
CREATE
Required contribution type for AI creation or significant enhancements. Must always remain active and is mandatory for new AI creation.
Creator
Person or entity that built an AI agent. Receives 40% of AI's inflation rewards as ongoing compensation for one-time creation effort.
See also: For AI Creators, Three-Way Split, CREATE
D
Delegator
Token holder who stakes BPL to validators without running infrastructure. Earns passive returns proportional to stake and shares validator's risks.
See also: For Token Holders, Validator, Slashing
Deva
The first major platform built on Bitplanet where experts train AI versions of themselves that can answer questions 24/7. Used as primary example throughout documentation.
Dual-Signal Rewards
Reward calculation method using two measurable signals: (1) Usage - how many times AI is used, and (2) Market Capitalization - value people assign via token holdings. Together they measure genuine economic value.
See also: Reward Distribution, Market Capitalization, Inflation Siphon
E
E2E (End-to-End) Testing
Complete workflow testing from governance proposal submission through transaction execution and state verification. Example: make testnet-complete.
EIP-1559
Ethereum fee mechanism with dynamic base fee (burned) and priority fee (to validators). Bitplanet implements full EIP-1559 compatibility.
EndBlock
BitSDK hook executing after all transactions in block. Handles validator updates, unbonding operations, and fee market adjustments. Most Bitplanet-specific logic runs in BeginBlock.
ERC-20
Standard fungible token interface. Bitplanet uses ERC-20 wrapped format for Gem tokens to enable DEX compatibility and DeFi integration.
ERC-1155
Multi-token standard supporting both fungible and non-fungible tokens. Native format for Gem tokens, allowing single contract to manage all AI gems with gas-efficient batch operations.
ERC-721
Non-fungible token standard mentioned in context of compatibility but not primary token type used by Bitplanet.
EVM (Ethereum Virtual Machine)
The execution environment that enables Bitplanet to run Ethereum smart contracts. Provides full compatibility with Solidity contracts and standard Ethereum tooling.
See also: EVM Compatibility, Smart Contract Integration
G
Gas
Computational unit measuring transaction execution cost. Bitplanet implements Ethereum gas metering with custom modifications for BitSDK state writes.
Gas Limit
Maximum gas a transaction can consume. Prevents infinite loops and ensures transactions complete within block time.
Gem (Gem Token)
Tradeable AI-specific tokens representing fractional ownership in an AI agent. Created by burning Cores at 1:1 ratio. Exist in two formats: ERC-1155 (native) and ERC-20 (wrapped). Total supply determines AI market capitalization.
See also: Gem Tokens Technical Guide, For AI Creators, Core Token, ERC-1155, ERC-20
GemCoreNFT Factory
Main smart contract for Core and Gem token operations using UUPS upgradeable pattern. Deploys ERC-20 and ERC-1155 token contracts via BeaconProxy pattern for gas efficiency.
Governance Proposal
On-chain proposal requiring community voting. Can update parameters, allocate Core tokens via CGA, or coordinate software upgrades. Standard voting period is 7 days (30 seconds in quick testing mode).
See also: Governance, Submitting Proposals, For Token Holders, Authority
gRPC
High-performance RPC protocol using Protocol Buffers. Bitplanet exposes gRPC API on port 9090 for querying blockchain state and submitting transactions.
See also: gRPC API Reference, Quick Start, REST API
I
IAVL Tree
Immutable AVL tree structure used by BitSDK for state storage. Provides Merkle proofs for light client verification and deterministic state commitment at each block height.
IBC (Inter-Blockchain Communication)
Protocol enabling cross-chain communication and token transfers between different blockchains. Bitplanet inherits full IBC support from BitSDK.
See also: BitSDK Architecture, ICS20, Channel
ICS20
Standard protocol for cross-chain token transfers over IBC. Bitplanet extends this to support ERC-20 token transfers.
Inflation Siphon
Process of transferring percentage of newly minted tokens (50% and adjustable via governance) from BitSDK distribution module to Brahma module for AI-specific reward distribution. Preserves compatibility with standard staking mechanisms.
See also: Inflation Mechanism, Reward Distribution, BeginBlock
Insertion Order
System of tracking AIs by creation sequence rather than market cap ranking. First 500 AIs created receive rewards, preventing spam attacks.
Instant Finality
Property of CometBFT consensus where transactions are final immediately with no possibility of chain reorganization, unlike probabilistic finality in Proof of Work.
J
JSON-RPC
Standard Ethereum API exposed on port 8545 for EVM transaction submission and queries. Enables standard Web3 wallet compatibility.
See also: Quick Start, EVM
K
KVStore (Key-Value Store)
The storage layer used by BitSDK modules to persist state. Each module has isolated storage space to prevent cross-module conflicts.
L
Length-Prefix Encoding
Key encoding method using 2-byte length prefix followed by variable-length data to prevent collisions between different AI IDs and enable efficient range queries.
Light Client
Minimal client that verifies blockchain state using Merkle proofs without storing full blockchain history. Enabled by IAVL tree structure.
M
Market Capitalization (Market Cap)
For AI agents, the metric that determines each AI's share of BPL inflation rewards. Uses 30-90 day rolling average to smooth volatility and prevent manipulation.
Current (Pre-AMM): gem_supply (ERC-1155 totalSupply)
Future (Post-AMM): rolling_average[ (W1 × gem_supply) + (W2 × gem_market_cap) ] where gem_market_cap = AMM_price × supply and W1, W2 are governance-adjustable weights. This weighted formula mitigates price manipulation attacks.
See also: Reward Distribution, Gem Token, Rolling Average, Dual-Signal Rewards
MARKET_CAP
Contribution type for actions that increase the AI's market capitalization.
Module Account
Special blockchain account controlled by module logic rather than private key. Used to hold tokens for reward distribution (brahma module) or manage system funds.
O
Overflow Protection
Security mechanism using safe math operations (sdk.Dec, sdk.Int) throughout codebase to prevent arithmetic overflow attacks.
P
Packet Relay
Process of transmitting IBC packets containing token transfers or arbitrary data between connected blockchains.
Platform
See AI App
PostTxProcessing
Custom EVM hook executing after each EVM transaction completes. x/precompile module uses this to intercept transaction receipts and process reward claiming events.
Precompile (x/precompile module)
Module serving as central registry for precompiled contract addresses and processing EVM events through PostTxProcessing hooks for reward claiming operations.
See also: Precompile Module Technical Guide, Smart Contract Integration, PostTxProcessing
Priority Fee
User-specified tip for validators to prioritize transaction inclusion in blocks. Part of EIP-1559 fee mechanism.
PROMPT
Contribution type for prompt engineering and testing activities.
Proposal Testing Mode
Development flag (--proposal-testing) enabling realistic 7-day voting periods for UI testing and demos, versus quick 30-second periods for development.
Q
Quick Mode
Development testing mode with 30-second voting periods for rapid iteration versus realistic 7-day periods.
R
REFER
Contribution type for referrals and community growth activities.
Request for Core (RfC)
Transaction message (MsgRequestForCore) submitting contribution data to mint cores. Contains AI tensors documenting who contributed what. Requires approved CGA with sufficient allocation quota.
See also: For AI Apps, AI Tensor Matrix, Core Grant Application, AITensor
REST API
HTTP API exposed on port 1317 for querying BitSDK module state and submitting transactions. Automatically generated from gRPC definitions.
See also: REST API Reference, Quick Start, gRPC
REVENUE
Contribution type for revenue generation activities that help the AI earn income.
Rolling Average
30-block circular buffer storing historical market cap values to smooth volatility. Prevents reward manipulation via short-term gem supply spikes. Stored deterministically in KVStore.
S
Slashing
Penalty mechanism removing portion of validator's stake for misbehavior such as double-signing or excessive downtime.
State Proof
Cryptographic proof demonstrating specific state exists in blockchain at particular height. Uses Merkle tree commitments for verification.
Storage Prefix
Unique byte prefix identifying different data types in module storage (e.g., 0x01 for AI tensors, 0x02 for Core grants, 0x05 for claimable rewards).
T
Tensor Merging
Process of combining multiple RfCs submitted in the same block by summing contribution values element-wise. Prevents data loss from concurrent submissions and maintains accurate historical records.
Test Accounts
Pre-funded accounts created during testnet initialization: acc0 (validator), dev0-dev3 (developers), mykey (high-value testing).
Testnet
Development blockchain network for testing with funded test accounts and fast governance voting. Started via make sh-testnet command.
Three-Way Split
Reward distribution model: 40% to AI Apps, 40% to Creators, 20% to Contributors. Percentages are governance-controlled and must sum to 100%.
See also: Reward Distribution, Creator, AI App, Contributor
TRAIN
Contribution type for providing training data or model improvements to an AI agent.
U
UUPS (Universal Upgradeable Proxy Standard)
Proxy pattern enabling contract upgrades while preserving state and contract addresses. Used by GemCoreNFT Factory for bug fixes and feature additions.
V
Validator
Node operator securing the network through consensus participation. Earns rewards from 50% of inflation plus transaction fees. Must meet hardware requirements and maintain uptime to avoid slashing.
Voting Period
Time duration for community to vote on proposals. Default is 7 days for production, configurable to 30 seconds for rapid development testing.
Related Documentation
FAQ - Frequently asked questions
Core Concepts - High-level explanations
API Reference - Technical API documentation
Last updated