A human-gated blockchain built to stay alive.

NABD confirms transactions in about a second, heals itself when machines fail, and can ask for a real human before the actions that matter most. Built to stay verifiable under real-world pressure.

NABD Palm-Vein Payment Terminal

Settles in about a second. Keeps going when machines fail.

NABD is a blockchain for communities, institutions, and builders that need payments and records they can trust. When a transfer confirms, it is final. There is no waiting for extra blocks and no risk of a quiet rollback later.

The network checks the health of every validator twice a second. If a machine stalls, the others notice within moments and keep going without it. Most blockchains only find out after a long timeout. NABD is built to notice first and recover fast.

Final means final

Once a supermajority of validators confirms a block, it is settled. Wallets and apps read facts, not probabilities.

Heals itself

Every validator is watched as alive, suspect, dead, or recovered. The network moves around trouble in seconds instead of waiting it out.

Assets and programs built in

Tokens, unique items, and automated programs live inside the ledger itself, with clear rules for fees, storage, and upgrades.

Ready for tomorrow's cryptography

Transactions can be signed with today's keys, post-quantum keys, or both at once, so the network can raise its security bar without starting over.

Measured on the live testnet, not promised.

These numbers describe what a wallet actually experiences on the public network today.

1.214 s

Average time from sending a transaction to seeing it confirmed as final.

3.3 s

Time the network takes to replace a failed leader and carry on.

8

Validators in the active set, spread across three datacenters in Europe.

4 GB

Memory on each of the small shared machines the network runs on today.

Real measurements from the public testnet under normal load, not marketing targets. The method and raw artifacts are documented in the whitepaper.

Some actions deserve a real human. NABD can require one.

Keys can be lost, stolen, or copied. A person cannot. NABD lets a network ask for a live palm scan before its most sensitive actions go through: moving a treasury, changing the rules, or recovering a lost account.

The scan itself never touches the blockchain. Matching happens inside secure hardware, and the chain records only that an approval happened. If the scanner is ever offline, protected actions wait while everyday payments keep flowing.

Treasury movements

Emergency funds move only when an approved person is physically present, not just whoever happens to hold a key.

Governance changes

Rule changes and validator membership can require live human approval before they take effect.

Circuit breakers

A token can pause minting or transfers during an incident until a person approves resuming.

Account recovery

Get back into an account after devices or keys are lost, with a real person at the door instead of a seed phrase in a drawer.

Own your chain. Anchor it to a shared root record.

Running your own blockchain used to mean renting trust from a platform or staffing a datacenter. NABD runs comfortably on small shared machines, so a community, company, school, or cooperative can own its settlement layer outright.

Owning your chain does not mean going it alone. The NABD model keeps a shared root record, so the proofs that matter stay publicly verifiable for as long as they need to be.

Start on the public testnet.

Fund a wallet from the faucet, send a transfer, and watch it confirm in the explorer. It takes a few minutes and needs no account.