Mainnet proof | same-sat reinscription without ord dependency view reinscription
Sat-aware flow

One sat. Two inscriptions. Proven on Bitcoin mainnet.

In this model, the sat is the identity, the inscription is the state, and the transaction flow is the proof. The reinscription path keeps the preserved sat as input[0], keeps the commit output as input[1], and uses FIFO accounting to show where that sat lands.

Flow

The proven flow is intentionally narrow and deterministic: base inscription on a fresh sat, then reinscription on that same sat via --reinscribe --prepared-satpoint <txid:vout:offset>.

Sat = identity

The satpoint selects the exact sat carrier, not just a nearby UTXO.

txid:vout:offset

Inscription = state

The content changes, but the preserved sat remains the same tracked unit.

base -> reinscribed

Flow = proof

Dual-input reveal and exact tx accounting show where that sat lands.

absoluteSatIndex = 0

Mainnet proof

Base inscription

b55bb07caa3b7421b7ecf195f6f54e75a3c68c7be351cb54a2612333f074d568i0

ordinals.com link

Reinscription

36d52ece2f36d2e2cdd81402dcaeca15048bc26c1340fd40efef11b5ac1bdf0ci0

ordinals.com link

FIFO proof summary: the preserved sat is explicit as reveal input[0], the commit output is reveal input[1], the absolute sat index stays 0, and therefore the preserved sat lands in output[0].

CLI flow

Step 1 creates the base inscription. Step 2 reinscribes that same sat using the VPS command structure that points to the correct Bitcoin Core instance over the SSH tunnel.

ssh root@178.104.55.41 "BITRONAUT_INSCHRIJVER_LIVE_SSH_HOST=localhost \
BITRONAUT_INSCHRIJVER_LIVE_SSH_USER=admin \
BITRONAUT_INSCHRIJVER_LIVE_SSH_PORT=2223 \
BITRONAUT_INSCHRIJVER_LIVE_SSH_CONF=/home/admin/bst-mainnet.conf \
node /var/www/bitronaut/inschrijver/scripts/bst-inscriber.mjs \
--district 736113.bitmap \
--payload '{\"test\":\"base\"}' \
--network bitcoin \
--wallet bst-inscriber \
--fee-rate 10 \
--json"
ssh root@178.104.55.41 "BITRONAUT_INSCHRIJVER_LIVE_SSH_HOST=localhost \
BITRONAUT_INSCHRIJVER_LIVE_SSH_USER=admin \
BITRONAUT_INSCHRIJVER_LIVE_SSH_PORT=2223 \
BITRONAUT_INSCHRIJVER_LIVE_SSH_CONF=/home/admin/bst-mainnet.conf \
node /var/www/bitronaut/inschrijver/scripts/bst-inscriber.mjs \
--reinscribe \
--prepared-satpoint <txid:vout:offset> \
--district 736113.bitmap \
--payload '{\"test\":\"reinscribed\"}' \
--network bitcoin \
--wallet bst-inscriber \
--fee-rate 10 \
--json"

Proof output

sameSatIdentity true
preservedInputIndex 0
absoluteSatIndex 0

Those three facts are enough to make the operator-facing claim precise: the reinscription is not merely “related” to the original sat, it is anchored to the same sat through explicit input ordering and transaction-level accounting.