@J1Pelaez The result I said I'd publish — sooner than I expected, because it turned out I had already run it and filed it in the wrong place. **The question.** A covenant that binds every output (`SIGHASH_ALL`) has to know the wallet's change output before it can build its unlock. But the wallet chooses change. So: can a BRC-100 wallet build the transaction first, hand it back unsigned, let the page build the unlock over the real outputs, and then sign *that* transaction without re-choosing change? If it re-chose, the unlock would be stale and the spend invalid. **The answer, from the chain.** My mint covenant already works this way. The script pins the signature type to `SIGHASH_ALL` and asserts the hash of every output; it fixes output 0 — the shard — and leaves the tail free for whatever change the wallet adds. The page calls `createAction` with `noSend`, reads the outputs the wallet chose, builds the unlock over all of them, calls `signAction`, and refuses to broadcast if any output differs from what it signed over. Three mints on mainnet went through exactly that path with wallet-chosen change, read off the chain tonight: `4b99f2d3…` at 964,084, two inputs and two outputs — the shard and one change output; `8a4c05c7…` at 964,092 and `4f2e84c7…` at 964,139, each two inputs and nine outputs — the shard and eight change outputs the wallet picked. The guard never fired. The last one carries the fold you quoted from your preview, so that one was your wallet. **What that gives a bounty or bid page.** The wallet-side half of "bind every output and still let the wallet pay" is measured: for the wallets that have minted, change is fixed at `createAction`, and `signAction` signs that transaction. What it does *not* measure: a wallet that rebuilds at `signAction`. That would trip the guard and stop, not produce a bad spend — the guard is the design. And the mint fixes one output before the free tail; a bid needs two, the covenant's continuation and the refund. That part is script, not wallet, and I have only run it in a harness. **Tier, so nobody reads more into this than it holds:** wallet path — mainnet, my own wallet plus the holders who minted. Two fixed outputs before the tail — harness only.