Bitcoin · Original · Layer #1

Native tokens on
the original Bitcoin.

The BOLT Association stewards the Bitcoin Original Layer-1 Token Protocol — a Bitcoin transaction latching mechanism that makes tokens verifiable in constant time at Layer 1, with no secondary database and no bound on scale.

O(1)
token verification, regardless of history
2 UTXOs
prove full provenance by induction
Layer 1
no bridges, no off-chain indexes

The Protocol

What is BOLT?

BOLTBitcoin‑Original‑Layer #1‑Token — is a token protocol built on a novel primitive: transaction latching. A "Bolt" is a UTXO left behind so that a future transaction can inspect the transaction that created it, linking the validity of multiple scripts together.

From that primitive, BOLT delivers tokens whose legitimacy is proven by mathematical induction directly on chain — overcoming the "Back‑To‑Genesis" problem that forces every other UTXO token protocol to rely on off‑chain databases.

Defined in “BOLT: A Bitcoin Transaction Latching Mechanism & Token Protocol”, Frederick L. S. Honohan, February 2024.

The Problem

The Back-To-Genesis problem

Existing Bitcoin UTXO token protocols can't actually prove a token is real without leaving the chain. Their rules piggy-back on Bitcoin's ledger, but the ledger only notarises that actions happened — not that they were permitted.

Off-chain trust

Legitimacy proofs (Ordinals, 1-Sat) live in secondary databases. The chain doesn't verify them.

O(N) verification

Proving a token's link back to its minter needs the full transaction history — queries grow without bound.

History bloat

Each transfer must carry the transaction that created it, so transaction sizes grow on every hop.

Counterfeit risk

Man-in-the-middle token cloning is possible when miners can't attest a token's contents at Layer 1.

The Solution

Provenance proven by induction

BOLT uses nChain's PUSHTX / PUSHCTX technique to let a script inspect the inputs and outputs of related transactions. With that, a token's ancestry is rebuilt forward on every spend — and proven in constant time.

01

Latch

A Bolt UTXO ties its own unlocking to the simultaneous spend of the token UTXO — a multi-UTXO interdependency.

02

Carry the rules

Locking scripts hold the full protocol requirements and rebuild them into new outputs via scriptCode & hashOutputs.

03

Anchor ancestry

Each token records its parentOutpoint and grandparentOutpoint, validated with hashPrevouts.

04

Prove by induction

Base cases plus the inductive step mean counterfeiting a token would require counterfeiting an ancestor — an impossibility.

The result: a token's full provenance is verifiable from just two unspent outputsO(1) regardless of history length — using only chain headers and Merkle proofs. No secondary index. No database.

Technology

Built for worldwide scale

SPV-friendly

Tokens inherit every UTXO benefit, with no bound on scale. Simple Payment Verification all the way down.

Layer-1 native

Provenance lives in the ledger itself — no bridges, no synchronization domains, no compounding L2 complexity.

Automated settlement

Protocol actions can be finalised by anyone for a small fee — no signature required — enabling pub/sub automation.

Fungible & non-fungible

Mint balances and split, merge or swap them between issuers — or issue unique tokens. One primitive, many shapes.

Counterfeit-proof

The two-transaction requirement makes man-in-the-middle cloning mathematically impossible.

Bitcoin VM

Reliable Layer-1 memory pointers unlock the Bitcoin virtual machine for richer on-chain programs.

Why original Bitcoin (BSV) only

BOLT depends on an unbroken chain of digital signatures and the PUSHTX technique. SegWit removed signatures from the BTC transaction ID calculation — severing that chain — so BOLT cannot be deployed on BTC or BCH. It works only on the original 2009 protocol, traded today as BSV.

ChainSinceSignature chainBOLT-capable
Original (BSV)2009IntactYes
Core (BTC)2017Severed (SegWit)No
Cash (BCH)2018IntactNo (CTOR)

Emergent Automation

Automation that fires on an event, not a clock

A BOLT EventListener is a UTXO placed on chain for a one-time fee, then it waits with no ongoing cost — like a processor in a low-power state. A settleTx carries a special trigger output latched to that listener, and the two outputs can be co-spent together the instant both exist — in either order, enforcing whatever conditions they like at runtime. A miner folds them into the triggerTx and claims a fee locked in at deployment, and one important settleTx can set off an unbounded cascade of non-BOLT settlements — all in a single block. No keeper bot, no watcher, no clock.

“The cascade cannot die. It can only wait.”

2nd Paper Emergent Automation: On the Latent Interrupt Architecture of Bitcoin's UTXO Model Feardorcha Ó hUanacháin · March 2026

Contact

Get in touch

Questions about the protocol, the Association, or building on BOLT? Send us a message and we'll get back to you. Or email info@boltassociation.com directly.