Audit-grade by design.
Every operation on Bantu — asset issuance, transfer, swap, authorisation, trustline, freeze, clawback — is permanently recorded on an immutable, publicly-accessible ledger. KYC/AML integration points exist at three layers: the asset, the anchor, and the application. Finality is reached in 2–4 seconds, so reconciliation is final at ledger close — not probabilistic, not pending.
Every operation visible via the Bantu Blockchain Explorer — no privileged access required.
Authorization Required flag means unauthorised accounts cannot receive the asset, period.
No "pending" or "unconfirmed" state persisting beyond a ledger close.
The ledger is the record. End-of-day reconciliation simplifies dramatically.
Real-time. Public. Permanent.
- Asset issuance — public, attributable, timestamped
- Transfer of any asset — sender, recipient, amount, memo
- Account authorisation events — when access is granted or revoked
- Trustline creation — every opt-in to hold a non-native asset
- Freeze and unfreeze — clear, named operations on the ledger
- Clawback — recoverable assets, with full on-chain provenance
- Path payments and swaps — multi-hop conversions on the built-in DEX
Three layers. Three enforcement points.
Authorization Required as a programmatic gate.
Issuers set the Authorization Required flag on any asset that needs verified holders. Before any account can receive or trade the asset, the issuer must explicitly authorise the trustline. Compliance teams get a programmatic enforcement point — no unauthorised account can hold the asset regardless of what the application layer does.
Identity at the on/off-ramp boundary.
Organisations running fiat on/off ramps (anchors) implement their own KYC/AML processes before allowing users to deposit or withdraw. The anchor model cleanly separates the identity-verification layer from the asset-movement layer, while maintaining a full on-chain record of all asset flows.
Full transaction history into your tooling.
The Horizon REST API and the SDKs expose full transaction history, account balances, asset holders, and operation details. Pipe directly into AML monitoring tools, transaction screening systems, or regulatory reporting workflows. The data is structured, well-documented, and consistent across deployments.
cNGN — the compliance stack, demonstrated.
- Issued only by licensed consortium members under CBN authorisation
- Minted 1:1 against naira deposits held in licensed bank accounts
- Accessible only through licensed exchanges (Quidax, Busha, Xend Finance, and others)
- Interoperable with other blockchains via AMTP — while maintaining regulated issuance provenance
Final at ledger close. Nothing pending. Nothing probable.
Bantu reaches transaction finality in 2–4 seconds with no probability of reversal through chain reorganisation. There is no concept of a “pending” or “unconfirmed” transaction persisting beyond a ledger close — once a transaction is included in a closed ledger, it is final. End-of-day reconciliation is straightforward. The uncertainty that characterises legacy payment systems and probabilistic blockchain confirmation simply does not apply here.
Walk an asset, sender, or memo through the explorer. Then call us.
The Foundation works with compliance and risk teams evaluating Bantu for regulated-asset issuance, settlement, and on-chain reporting. We'll walk through architecture, integration points, and any specific control flag your jurisdiction requires.