Repository navigation
docs(#77): the demo's one simulated link, said once and early - #91
Conversation
…he evidence for every other Option 3 on #77: the success path runs on the rehearsal contract, where claims are signed by the published test witness. This page gives the video (#28) its opening card, voice-over and closing line, a table of what is simulated and what is live with a link for each, and four rules for the cut.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Lexirieru
left a comment
There was a problem hiding this comment.
Approved, and the wording is right — I would put this in front of a Chapter Lead as it stands.
I checked the table rather than reading it
Every factual row, live this session:
| Claim | Checked | Result |
|---|---|---|
13bdff8b… (verifier accepts, one byte refused) |
Horizon | successful: true, ledger 5193392 |
3f824388… (USDC payout) |
Horizon | successful: true, ledger 5381039 |
23b698c4… (nullifier) |
Horizon | successful: true, ledger 5381041 |
b8ab84b1… (repayment) |
Horizon | successful: true, ledger 5381042 |
| "25% of proven revenue, 1–100 USDC" | sizing() on CCQFL2Q6…I2HS |
rate_num 25 / rate_den 100, min 10000000, cap 1000000000 stroops — 25%, 1 to 100 USDC |
| The run exists and holds those hashes | tools/runs/2026-10-25T114611Z/EVIDENCE.md |
present, all three found |
Both evidence.md anchors |
the file | ## Why there are two contracts, ### The three negative cases, each correctly rejected |
| Links | python3 -I tools/check_links.py docs/demo-disclosure.md on your branch |
16 distinct links, every link resolves, contract verified |
One premise of mine that was wrong
I went in sceptical of this row:
the rehearsal contract
CD25Q4TD…HQN4only points at a verifier that knows the test witness
I thought the probe instance skipped signature checking, which would have made "signed by a test witness" an overstatement — no signature is actually checked. It does not skip it. verifier() on CD25Q4TD…HQN4 returns CASAIKW7…WZURP, which runs Reclaim's own wasm with an epoch whose witness is 19e7e376…, derived from the published 0x1111…1111. The signature is recovered and compared, against a key anyone can read. So the row is accurate, and the distinction your card draws — a test witness, not a missing check — is the honest one and the stronger one.
And one claim I could prove harder than you did
The production contract
CCQFL2Q6…I2HShas never paid an advance
claim_template() on it returns null. With no template pinned, request_advance cannot get past TemplateNotSet (#10). So it is not that it happens not to have paid one — it could not have. liquidity() reads 1050000000 stroops, exactly the 105 USDC funded and never moved. Worth having that in hand if anyone asks on camera.
One thing to add: the sign-in on camera
Rule 4 tells the cutter to show the Google sign-in and the relay. Per #86's own record, the consent screen has not been submitted for review yet — Search Console verification is still open. Until it is published, that sign-in shows Google's unverified-app warning, and only accounts added as test users can get through it.
That is not a reason to change rule 4, and it is not an error in this PR. But a reviewer watching an "unverified app" screen with no explanation will draw their own conclusion, and this is the page whose whole job is that nobody has to. One line under rule 4 would cover it — something like: the consent screen is in review (#86), so the sign-in shows Google's unverified-app notice; the operator's account is a test user. Please fold it in on a follow-up; I am not holding a verified 75-line doc for a sentence.
Correcting myself: I flagged on #87 and #89 that the OAuth client's Authorized JavaScript origins still needed https://app.forepay.xyz. That was stale — you added it on 2026-10-23 and said so here. The origin is done; publishing the consent screen is what is left.
Merging.
Refs #77 (option 3) and #28. Adds
docs/demo-disclosure.md, the draft @Lexirieru asked for on #77: the part of the demo that says which link is simulated.What is in it
What to say.
This follows the request on Find an approved (READY) AdSense account for the gate and the demo #77: say it once, plainly, early, and in the demo itself.
A table of every link in the chain, simulated or real, with the evidence for each:
prove:smokeon the relay host;13bdff8b…and refusing the one-byte flip;Four rules for the cut.
tools/runs/.app.forepay.xyzpoints at the production contract.What changes if a real account turns up. Only the first row of the table.
For review
Checked
python3 -I tools/check_links.py docs/demo-disclosure.mdreports that every link resolves. One deep anchor intodeployments.mdwas dropped: the checker collapses the double hyphen GitHub keeps in#16--17--…, so it reads as missing. The link now goes to the page and names the section. Docs only.