NABD blockchain

Settlement infrastructure for payment and asset networks that need deterministic finality, controlled validator operation, and a choice between transparent and private transaction views.

Protocol scope

Settlement with a defined operating model.

NABD combines the ledger, validator network, transaction APIs, and explorer required to run a controlled blockchain environment.

It can sit behind a wallet or payment application as the settlement layer while identity, authorization, and custody remain separate services.

Consensus and finality

The network uses a controlled validator set and Byzantine fault tolerant consensus to reach deterministic finality.

Defined validator membership and node roles
Finalized blocks without probabilistic confirmation windows
Governance and operating controls set per network

Transparent and private payments

Transaction visibility can match the payment context instead of forcing every transfer into one disclosure model.

Transparent flows expose normal explorer fields
Private flows retain settlement visibility while configured transfer fields are redacted
Useful for stablecoin and payment environments balancing audit needs with transaction confidentiality

Signing and key profiles

NABD supports post-quantum transaction signing profiles and can connect to software or hardware-backed key custody.

ML-DSA transaction signing support based on FIPS 204
Falcon/FN-DSA implementation path
Wallet and HSM integration kept outside the consensus boundary

Integration and operations

The protocol is accompanied by the interfaces and operational services needed to connect applications and run a network.

Node and transaction APIs
Wallet and POS transaction submission
Explorer, monitoring, deployment, and network administration tooling

Reference environment

Network state visible through the NABD explorer.

NABD explorer showing validator, block, account, and transaction activity — ExplorerValidator status, block activity, accounts, and transactions in the NABD explorer interface.

ResourcesRead the NABD technical overview

Project discussion

Define the requirement and deployment boundary.

ATL can scope this area as a focused component, an integration, or part of a complete engineering program.

Contact ATL