Controls at the protocol layer.
Bantu is a financial-market infrastructure blockchain for issuing, distributing, governing, exchanging and settling tokenised value. The controls a regulated institution actually needs — allow-listing, freeze, clawback, multisignature governance, atomic settlement — are native protocol functions rather than bespoke smart-contract code. That removes an entire class of deployment, audit and upgrade risk before a single line of it is written.
HFBA reaches externalisation in approximately three to five seconds. Final at ledger close — not probabilistic, not pending.
Validators establish trust through declared quorum relationships rather than hash power or token ownership.
Issuance, authorization, freeze and clawback are protocol operations. There is no token contract to deploy, audit or upgrade.
The Expansion API exposes finalised ledgers, transactions, operations, effects, balances, signers, trustlines, assets and order books.
Financial infrastructure, not a speculative chain.#
Bantu's architecture is built for commercial banks, central banks, payment service providers, regulated stablecoin issuers, national switches, treasury platforms and cross-border settlement networks. Unlike chains that require a custom smart contract for every token, Bantu provides core financial controls natively at protocol level. A regulated institution can issue a fiat-backed stablecoin, tokenised bank deposit, CBDC, government bond, commodity token or settlement asset using issuer accounts, trustlines, authorization flags, multisignature accounts, path payments and the built-in exchange layer.
Its strongest position is not as a speculative blockchain. It is as an African and emerging-market financial infrastructure layer.
Two layers — one of which you do not have to write.#
The most important policy controls in a regulated deployment do not depend on custom code. They are protocol functions, which reduces smart-contract risk, deployment complexity and audit burden simultaneously.
- Core banking
- KYC / KYB
- Sanctions & PEP screening
- Transaction monitoring
- Treasury
- Regulatory reporting
- Asset issuance
- Trustlines
- Authorization flags
- Freeze & revocation
- Clawback
- Multisignature
- Atomic transactions
- Path payments
- Order book
- Claimable balances
- Sponsored reserves
- 3–5 second finality
- Non-mining
- Non-staking
- Quorum-defined trust
- Immutable ledger history
- A custom token contract for every asset
- An external audit for every contract
- Deployment and upgrade risk
- Bespoke access-control code
- Contract-level attack surface
What a regulated institution can issue.#
Every regulated asset on Bantu is associated with an identifiable issuer account. The asset is uniquely defined by its asset code and its issuing account, which cryptographically identifies the institution responsible for issuance and redemption. Two institutions may each issue a USD-denominated asset; they remain distinct because each is tied to its own issuer.
- CBDCs
- Tokenised commercial-bank deposits
- Fiat-backed stablecoins
- Settlement coins
- Tokenised treasury bills and government bonds
- Commodity-backed assets
- Carbon credits
- Trade-finance instruments
- Loyalty and closed-loop instruments
Issuance, trustline distribution and issuer controls are native Bantu operations. They do not require a separate token contract to be deployed or audited.
What Bantu enforces — and what it does not.#
Bantu provides enforcement hooks. It does not independently conduct KYC, sanctions screening, transaction monitoring or regulatory reporting. Those functions remain the responsibility of the licensed institution: the central bank, commercial bank, licensed fintech, payment service provider, stablecoin issuer, anchor, regulated custodian or compliance provider operating on the network. Any vendor claiming otherwise is describing something the protocol layer cannot do.
Off-chain, inside your own regulated perimeter, under your own licence.
- KYC and KYB
- Sanctions and PEP screening
- Adverse-media checks
- Transaction monitoring
- Suspicious-activity reporting
- Regulatory reporting
- Customer legal terms
- Liquidity provisioning
On-chain, deterministic, and visible to every party to the transaction.
- Allow-list enforcement
- Trustline authorization
- Account-level freeze
- Clawback execution
- Multisignature thresholds
- Atomic settlement
- Immutable audit trail
- Real-time ledger visibility
What you must bring.#
Bantu provides the controls. Regulated institutions must provide the governance. A financial institution deploying on Bantu should establish each of the following before it issues a single unit.
- Clear legal terms for asset holders
- Formal KYC/KYB and sanctions policy
- Transaction-monitoring and suspicious-activity workflows
- Clawback and freeze governance
- Multisignature key-management policy
- HSM or MPC custody architecture
- Segregation of duties
- Independent audit trail
- Disaster-recovery procedures
- Validator and quorum governance
- Liquidity and market-making policy
- Data-privacy and PII-protection rules
- Smart-workflow testing and change management
- Regulatory reporting and supervisory access
Six chapters.#
Every factual claim about controls, finality, custody, supervision and programmability lives here. Other pages on this site summarise and link to these chapters; they do not restate them.
Bring us your control requirements.
The fastest way to evaluate Bantu is to put your own risk, compliance and treasury requirements against the register in chapter 01 and tell us where the gaps are. We will answer against the protocol, not against a roadmap.