TAG chrono · OP bind-beacon

On-chain time,set on beacon slots.

Chrono is a Bitcoin Taproot inscription protocol. A mint seals the beacon payload into the script path. The tick is CHRONO. Path A is the inscription envelope. If it is not spent in time, path B returns to the consensus key after a 48-block CSV.

Protocol parameters · not live chain stats

Tick
CHRONO
Protocol parameter
Network
Bitcoin mainnet
Protocol parameter
Units
1000 / mint
Protocol parameter
Next slot
43+
42 is already used
Amount
5000 sats
Protocol parameter
CSV fallback
48 blocks
Protocol parameter

Slot 42 is already used. New mints start at 43. Tick, units, and the CSV length are protocol parameters, not a block-explorer reading.

Mint

MINT CARD

Open mint. Anyone can pay 5000 sats on Bitcoin mainnet to the next slot's bc1p address. The server assigns the slot. A mint is recorded here only after the wallet returns a transaction id.

Amount5000 sats
NetworkBitcoin mainnet
SlotNext, from 43

Not connected yet. Mint opens the wallet list.

Protocol

SCRIPT PATH

01

Taproot script path

The internal key is the BIP-341 NUMS point, so the key path cannot be spent. Both leaves use version 0xc0. Spends go through the script path.

02

Inscription envelope

Path A uses OP_FALSE OP_IF to commit the tag chrono and the bind-beacon payload, then checks the minter's x-only pubkey.

03

48-block CSV fallback

Path B is 48 OP_CHECKSEQUENCEVERIFY. The spend is a version-2 transaction with nSequence 0x30, so it can move only after about 48 blocks.

Docs

Payload fields

p is chrono-utxo and op is bind-beacon. The other fields are slot, tick, units, tier, and weight. The envelope commits that JSON into the leaf script.

Payment boundary

A mint pays 5000 sats to the bc1p address for the next slot. UniSat, OKX Wallet, and the other Bitcoin wallets call their send method when it exists. MetaMask stays in the list and cannot pay a bc1p address.

Run locally

npm install
npm run dev

The dev server listens on 0.0.0.0:47231.