Build on a chain that settles in seconds.
Bantu is a Layer-1 blockchain on Harambee Federated Byzantine Agreement consensus. No mining, no staking-based validator selection, no probabilistic confirmation — actual finality in 2–4 seconds, fees from 100 Spirits per operation, native asset issuance and a built-in DEX at the protocol layer. Build in Go, Java, or Flutter/Dart, or hit the Horizon REST API from anywhere.
Actual finality via federated quorum voting — not probabilistic confirmation.
0.00001 XBN per operation. Micropayment workloads are viable.
Hard-capped native utility token. 1 Spirit = 0.0000001 XBN.
Plus a REST API (Horizon) accessible from any language.
Harambee Federated Byzantine Agreement.
No mining
No Proof-of-Work. No energy-intensive competition to produce blocks.
No staking-based selection
Validators are chosen on trust and reputation within the network's quorum, not on capital lock-up.
Federated quorum voting
Consensus is reached among known validator nodes, producing transaction finality in 2–4 seconds.
Cost-predictable
100 Spirits (0.00001 XBN) per operation. Fees do not balloon under congestion.
XBN powers every operation. Spirits are the unit of count.
Every transaction requires a small XBN fee. The smallest unit is the Spirit. Total supply is hard-capped — no future inflation, no dilution by design.
The full stack — node, API, SDKs, sandbox.
Bantu Core
The node software that connects to the Bantu peer-to-peer network and maintains the shared distributed ledger. Run your own for production deployments, high-availability access, or to contribute to decentralisation. You do not need to run a node to build — a hosted Horizon is sufficient for most apps.
Horizon
The REST API surface to Bantu. Translates Bantu Core's internal data structures into clean JSON. Submit signed transactions, query balances and history, stream real-time ledger events via SSE, interact with the built-in DEX.
SDKs
Go, Java, and Flutter/Dart — official, published under github.com/bantublockchain. Covers key management, account creation, transaction construction and signing, and asset operations.
Bantu Laboratory
A developer sandbox for testing transactions and wallet operations against testnet and mainnet without risk, and for exploring the ledger programmatically.
Bantu Blockchain Explorer
Real-time, public visibility into all network activity — accounts, transactions, assets, operations, and node status. Available to anyone, no auth required.
Primitives, not promises.
Digital asset issuance.
Any account on Bantu can issue custom assets in a few lines of code using the protocol's native asset primitives. Stablecoins, tokenised commodities, reward tokens, carbon credits, equity instruments — configurable with authorisation flags that control who may hold or trade, whether the issuer can freeze balances, and whether clawback is enabled. Suitable for regulated asset classes that require lifecycle control.
Fiat on/off ramps.
Bantu's anchor model connects on-chain assets to external banking and payment rails. An anchor maintains a 1:1 reserve of an off-chain asset (naira, cedis, kwacha) and issues the equivalent on-chain. Users deposit through the anchor's off-chain rails and receive on-chain assets, and vice versa. The architecture that makes Bantu a practical bridge between bank rails and digital-asset rails.
Decentralised exchange.
A DEX built into the protocol layer. Any Bantu-issued asset can be listed and traded without deploying a separate smart contract. Path payments allow multi-hop trades — a sender can denominate in one asset while the receiver gets a different one, with conversion handled atomically.
AMTP — Automated Multi-chain Transfer Protocol.
Bantu-issued assets — including regulated assets like cNGN — move across Ethereum, Polygon, BSC, Base, Tron, and other networks via AMTP. Extend reach beyond the native network without sacrificing the compliance properties set at issuance.
Private deployments.
The same Bantu protocol deployed as a credentialed, access-controlled network. The mode used by regulated financial institutions and multilateral systems. Same speed and finality as the public network, with the access controls regulated environments require.
Account, asset, anchor — in an afternoon.
Spin up a testnet account, mint an asset, point an SDK at Horizon, sign a transaction. The full developer documentation walks every step.