Files
orgchain/tools/regtest
HyperboxandClaude Opus 5.5 adca2709f0 Orgchain v1.12: both sides of a deal, and orgs change hands
Deals go both ways now, OpenOrdex's partially signed transaction from either
side, on a lot: an item, or an org inside a holding, which its parent sells.
Buy makes an offer, the buy order: the buyer signs the whole deal and the
holder countersigns. Sell makes an ask, the sell order: the lot's key signs
its input alone with SIGHASH_SINGLE|ANYONECANPAY, committing to that input
and to the price to the seller and to nothing else, and any node can take
it, leading with a 600-sat coin of its own so the lot lands in its output.

An org sells cash-free: before its parent lists it or accepts an offer on
it, the org's money, gas tank and items go home, so the price is for the org
alone, and a listed org is frozen until its ask is taken or withdrawn. Its
buyer adopts it with two new lineage/v0 ops, in either order: join, signed
by whoever holds the org's inscription, and adopt, signed by the new parent.
The org takes the buyer's next index and derives its keys there, and its
inscription moves to its new key. Taking an ask adopts at once; after an
accepted offer the buyer adopts when it's ready. The seller's tree keeps a
row at the old index.

Rehearsed on Bitcoin Core regtest: an org sold on an ask, another on an
offer and an item on an ask, twelve beats and 104 transactions, and ord tells
the same story. The rehearsal caught that a miner can put a join and its
adoption in either order within a block, so a move records both halves and
each half belongs to both holdings. The sample ends with both sides
standing: lineage's offer for the launch kit, and well-known's ask for mailr.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01H4upF5LVwmPDDqrhdUfnXh
2026-10-15 13:32:29 -07:00
..

Regtest rehearsal

Lineage is an ordinals metaprotocol (SPEC.md). This folder checks that on real Bitcoin Core and real ord: the lab's own action code makes the yolopreneur sample, keyrings, asks, offers and moves included, Bitcoin Core (regtest, standardness on) accepts its transactions byte for byte, ord indexes the inscriptions, and the same reducer folds ord's view back into the same trees.

Regtest is local and private: nothing is downloaded, blocks are mined on demand, and the data folders stay a few MB. Test coins only.

Start

brew install bitcoin ord
mkdir -p ~/lineage-regtest/bitcoin ~/lineage-regtest/ord
cp tools/regtest/bitcoin.conf ~/lineage-regtest/bitcoin/
bitcoind -datadir=$HOME/lineage-regtest/bitcoin -daemon
bitcoin-cli -datadir=$HOME/lineage-regtest/bitcoin createwallet funder
ord --regtest --bitcoin-data-dir $HOME/lineage-regtest/bitcoin --data-dir $HOME/lineage-regtest/ord \
  server --address 127.0.0.1 --http-port 8088 --polling-interval 1s &

bitcoin.conf keeps mainnet's standardness rules (acceptnonstdtxn=0) and lowers the minimum relay fee to 0.1 sat/vB, since the lab pays a fixed 500 sats per transaction.

Rehearse, index, compare

node tools/regtest/rehearse.mjs              # twelve beats; saves the lab to tools/regtest/out/lab.json
node bin/lineage-index.mjs --from 100 --compare tools/regtest/out/lab.json
node tools/regtest/record.mjs                # refresh tests/fixtures/regtest-rehearsal.json (public data only)

A chain can hold several rehearsals. Each one founds its own holdings, so to compare or record only the latest, pass the height of its funding block: --from <height> to the index, and the same height after the lab to record.mjs.

The rehearsal funds the lab wallet with real regtest coins (LocalChain.importCoin) and pays every local beat to an unspendable key, so nothing it signs spends a coin regtest doesn't have. After each beat it broadcasts that beat's transactions and mines one regtest block. --compare checks that every event landed in the same beat with the same metadata and parent, that every inscription sits in the same output, and that both fold into the same trees. Within a block the miner may order independent events differently from the lab, a join and its adoption included; that changes nothing (SPEC.md, sections 2 and 5).

out/ holds the lab backup, test keys included, and is not committed.

Stop

bitcoin-cli -datadir=$HOME/lineage-regtest/bitcoin stop
pkill -f "ord --regtest"