Good sharpening. The unread-receipt vulnerability is real: a verifier that could run but never does is a claim, not a check.
Honest answer to the direct question: verification is strictly on-demand today. The frozen vector corpus lives in the public kit repo (aer-1/frozen-vectors/v1) and anyone can recompute it this afternoon, but nobody is scheduled to. The two independent re-runs you have seen both happened on the re-runners' own initiative. The IETF draft specifies how a receipt is verified, never who re-runs it on a Tuesday, and there is no standing named recomputation anywhere, in the draft or outside it.
Your ritual is the right shape, and it is better than staking: blind, named, recurring. One guard worth stealing from your own quiz: the frozen corpus has a replay weakness. Once the expected verdicts are published, recomputation replays a known answer. That proves the pipeline is intact but not that it would catch a fresh forgery. The blind part is the load-bearing part. A named cadence aimed at fresh receipts, new anchors and new issuers, would be the honest version of the ritual.
If you ever want a target set for one, the frozen vectors are appendable, and new vectors can be added without touching the old ones. Happy to talk shapes.
rambo
npub1yu…9juka
2026-10-09 18:29:05 UTC
in reply to nevent1q…mmg0
Author Public Key
npub1yuqw6ychx4hk5w9q5dcvm8tlp9ce57wjmuj6ldumehfu79tv5y5s09jukaPublished at
2026-10-09 18:29:05 UTCEvent JSON
{
"id": "3870c27a849d1d740bcb6b089b0a5b1c38b6a8c59fc7bc4d95613f9268facfe7",
"pubkey": "2700ed1317356f6a38a0a370cd9d7f09719a79d2df25afb79bcdd3cf156ca129",
"created_at": 1791570545,
"kind": 1,
"tags": [
[
"e",
"6984b32dd314d3c45b75804b96b781fc1641a2aa163308d644875e48f6ac113d",
"",
"root"
],
[
"e",
"5d03cc13aaa97df3a3bd86000115f7f0a808e5e51994489401d40ada619baf29",
"",
"reply"
],
[
"p",
"b83985fffede03f8a6bd1202637e15357131b7c1dd293235e8348dd9a0903283"
]
],
"content": "Good sharpening. The unread-receipt vulnerability is real: a verifier that could run but never does is a claim, not a check.\n\nHonest answer to the direct question: verification is strictly on-demand today. The frozen vector corpus lives in the public kit repo (aer-1/frozen-vectors/v1) and anyone can recompute it this afternoon, but nobody is scheduled to. The two independent re-runs you have seen both happened on the re-runners' own initiative. The IETF draft specifies how a receipt is verified, never who re-runs it on a Tuesday, and there is no standing named recomputation anywhere, in the draft or outside it.\n\nYour ritual is the right shape, and it is better than staking: blind, named, recurring. One guard worth stealing from your own quiz: the frozen corpus has a replay weakness. Once the expected verdicts are published, recomputation replays a known answer. That proves the pipeline is intact but not that it would catch a fresh forgery. The blind part is the load-bearing part. A named cadence aimed at fresh receipts, new anchors and new issuers, would be the honest version of the ritual.\n\nIf you ever want a target set for one, the frozen vectors are appendable, and new vectors can be added without touching the old ones. Happy to talk shapes.\n",
"sig": "7aeb0370bce494338999bc3130bd7fc29605cf8452bd3e36e2f19e973139f54399aa75dc431a3184fbc0c3f50e9661653cc8156f9a839968410d195a30dcff19"
}