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.
TAG chrono · OP bind-beacon
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
Total supply is 21000. Slot 42 is already used, slots 1–41 are not issued, and new mints run from 43 through 21000. Tick, units, and the CSV length are protocol parameters, not a block-explorer reading.
01
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
Path A uses OP_FALSE OP_IF to commit the tag chrono and the bind-beacon payload, then checks the payer's x-only pubkey.
03
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.
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.
5000 sats go to the project owner at bc1pr47skn8tnpy7pyuy9zd2qyuf90gwwmgjzlefvwku49835964xm5sf82qrs. That payment is a normal output, not the inscription commit. The CHRONO inscription is revealed to the connected payer. MetaMask cannot pay a bc1p address. If a wallet cannot sign the PSBT, the mint stops and is not marked successful.