MAINNET· live since 2020BLOCK #32,732,325FINALITY 5.00sOPS / BLOCK 0VALIDATORS 11 · 5 ORGSTOTAL XBN 369B XBNCIRCULATING 74.10B XBNHFBA CONSENSUS · 3–5s FINALITYMAINNET· live since 2020BLOCK #32,732,325FINALITY 5.00sOPS / BLOCK 0VALIDATORS 11 · 5 ORGSTOTAL XBN 369B XBNCIRCULATING 74.10B XBNHFBA CONSENSUS · 3–5s FINALITY
Bantu
AboutFor Regulators

Built for oversight.

Bantu's properties — an immutable public ledger, known validators, sub-five-second settlement finality, and a dual public/permissioned deployment model — make on-chain activity legible to regulators by default. Asset-control primitives (Authorization Required, Freeze, Clawback) live at the protocol layer, not in upgradeable smart contracts.

Settlement
Final in 2–4s

No probability of chain-reorg reversal. Eliminates legacy settlement-risk windows.

Ledger
Public & immutable

Every operation recorded permanently. Real-time access via the public explorer.

Validators
Known, on record

Identities are public. Trust is configurable per quorum. Accountability is legible.

Modes
Public + Permissioned

Same protocol, two deployment shapes. Same audit and asset-control primitives apply in both.

//Protocol properties relevant to oversight

Legible by default.

Four properties of the protocol that matter most to oversight bodies. None of them depend on Foundation goodwill or platform policy — they are mechanical features of the chain.

Immutable, auditable ledger

Every transaction, asset issuance, account operation, and network event is permanently recorded and publicly accessible in real time via the Bantu Blockchain Explorer. A complete, tamper-proof transaction history available for inspection without requiring cooperation from any intermediary.

Known validators

Unlike proof-of-work networks where mining participation is anonymous, Bantu's HFBA consensus relies on a defined set of validator nodes whose identities are on the public record. Participants choose which validators to trust, creating accountability structures that are legible to oversight bodies.

Settlement finality

Transactions reach finality in 2–4 seconds with no probability of reversal through chain reorganisation. Eliminates the settlement-risk windows that exist in proof-of-work systems and significantly simplifies the regulatory treatment of on-chain transactions.

Dual-mode architecture

The public network and the private/permissioned network share the same protocol — meaning the same compliance tools, audit capabilities, and asset-control primitives apply in both modes. Regulators engaging with a permissioned Bantu deployment are engaging with the same well-understood, documented protocol as the public network, not a black-box proprietary system.

//Regulatory engagement to date

A track record, not a pitch.

Bantu's institutional history includes three notable counterparties — a central bank, a multilateral system at continental scale, and one of the world's largest regulated payment networks.
Central Bank of Nigeria (CBN)

cNGN — Nigeria's first regulated stablecoin

Bantu served as the primary issuance network for cNGN, operating within the CBN's regulatory sandbox under the requisite CBN license. cNGN is issued by the Africa Stablecoin Consortium and is accessible only through licensed digital-asset exchanges.

Read the cNGN case study →
PAPSS · Afreximbank

Continental cross-border settlement, 19 countries

The PAPSS African Currency Marketplace — launched at the 2025 Afreximbank Annual Meeting and endorsed by the African Union — is built on a permissioned Bantu deployment. The first multinational blockchain deployment adopted by African governments at continental scale, operating across 19 countries.

papss.com ↗
Visa Fast Track Program

First Africa-led blockchain admitted (2022)

In 2022, Bantu became the first Africa-led blockchain infrastructure admitted to Visa's Fast Track Program — institutional validation from one of the world's largest regulated payment networks.

Visa Fast Track ↗
// Asset control mechanisms

At the protocol layer — not as smart contract logic.

Assets on Bantu can be configured with compliance primitives that are enforced by the network itself. Not by a separately deployed contract that could contain errors or be upgraded unilaterally — by the chain.

Authorization Required

Issuers can require explicit approval before any account may hold or trade the asset — enabling KYC-gated asset distribution. The protocol enforces this at the network layer; no unauthorised account can receive the asset regardless of what happens at the application layer.

Freeze

Issuers can freeze an individual account's ability to send or receive a specific asset — enabling sanction compliance and AML-triggered holds with a clear, auditable on-chain operation.

Clawback

With the appropriate flag set at issuance, issuers can recover assets from accounts under defined conditions — enabling regulatory seizure or error-correction workflows. Each clawback is itself a public, attributable on-chain event.

Asset limits

Account-level controls can cap how much of an asset a given account may hold — useful for tier-based exposure rules, retail-vs-institutional segmentation, and regulated-product caps.

// Engage with the Foundation

Open the explorer. Read the architecture. Then talk to us.

The Foundation works directly with central banks, ministries of finance, and regulators evaluating Bantu for issuance, settlement, or permissioned-deployment use. We will brief, walk through any architectural question, and provide live data on the chain's behaviour.