You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Find an approved (READY) AdSense account for the gate and the demo #77
Today: create an access token in the OAuth 2.0 Playground with scope https://www.googleapis.com/auth/adsense.readonly only. Send it to @Lin1erby private DM. The token is read-only and expires within an hour. Never post it here.
Done when
pnpm -C be prove:adsense, or POST /proofs on the relay, produces an audited AdSense claim from a READY account. #5 then records it.
Working agreement
One issue, one owner. 2. Branch per issue, named above — not the GitHub-suggested one. 3. MCP Stellar Raven for any Stellar/Soroban fact that gets written down. 4. Merge through PR review by Axel (PM); no self-merge. If an ACC has not arrived within two days on something already verified, merge and say so in the PR. 5. Deploys need evidence: contract address or tx hash on stellar.expert, recorded in docs/deployments.md. 6. Secrets live in .env, gitignored, chmod 600 — never printed, never committed, never pasted into an issue or PR. Only public G… and C… addresses appear anywhere. 7. Issues, commits and PRs in English.
Taking this off the "someone will do it" pile, because after today it is the only thing left blocking the gate, and it is the one item no one on this team can solve with code.
The proving path itself already works on the relay host: prove:smoke produced a claim in 54 seconds, signed by Reclaim's production attestor, and Reclaim's own deployed verifier accepted the digest and rejected a one-byte change. That is the whole mechanism, proven, against a public endpoint.
The only missing input is an AdSense account Google will serve a report for.
What is actually needed
An AdSense account in state READY. pub-1144314860018910 is CLOSED, and Google serves no reports for a closed account — no proof can ever come from it.
Whoever owns it grants a https://www.googleapis.com/auth/adsense.readonly token. Read-only, one scope, and the token never enters the claim: zkFetch keeps it in secretOptions.headers, inside the TLS session.
Revenue only has to be non-zero in the last three complete calendar months. It does not have to be large: the advance floor is 1 USDC, which needs about $4.00 of proven quarterly revenue. Four dollars.
What the owner is exposed to
Worth being straight about this, because "give us an API token for your ad revenue account" is a real ask:
the scope is read-only and AdSense-only; it cannot change anything, and it cannot read Gmail, Drive or anything else;
the token expires in about an hour and is revocable immediately from the Google account's permissions page;
the revenue figure becomes public. It goes into a signed claim and a testnet transaction, and this repository is public. Three months of AdSense earnings, to the cent, permanently on a public ledger. For a $4-$400 hobby account that is nothing; for anyone's real business it is not nothing, and nobody should hand this over without being told that first.
A dormant or hobby AdSense account with a few dollars in it is the ideal candidate, and is strictly better for the demo than a large one.
Three ways this gets unblocked
Someone on the team or one person they know has a dormant AdSense account. Fastest, and most likely.
Open a fresh AdSense account. Needs a site with content and Google's review — historically days to weeks, and it has to earn something before there is a figure to prove. Too slow for the 2026-11-08 window, so this is a fallback, not a plan.
Ship the demo against the probe witness and say so. The contract logic, the disbursement, the repayment and all three negative cases are already proven end to end on testnet (7/7 green, tools/runs/); what would be missing is one real attestor signature over one real AdSense response. The honest version of this is a demo that shows the mechanism working and states plainly which single link is simulated — not one that implies a real proof happened.
Option 3 is a worse submission than option 1, but it is a real submission, and it is available today. Option 1 is worth asking around for this week.
@Lexirieru@Lin1er @sharkzneverending @AncungAulia — does anyone have, or know someone with, an AdSense account that is not closed? That is the whole ask.
@Lexirieru agreed on the order: option 1 this week, with option 3 prepared alongside it so it is not a scramble at the end.
What changed on my side since your comment, which makes option 1 cheaper for whoever turns up:
The owner never hands anyone a token. The OAuth Web client from Google OAuth Web client for the AdSense sign-in popup #78 exists, so the owner signs in through Google's own popup on our page (adsense.readonly only). The token goes once to the relay and is held only in memory. Nobody has to DM a token.
One step before they can sign in: the consent screen is in Testing, so their Google account has to be added as a test user. That is a one-minute change on my side once I have the email (privately).
Proposal for a cut-off: if there is no non-CLOSED account by 2026-10-27, we build the demo on option 3. That still leaves time before the 2026-10-30 milestone. The script states plainly that the attestor signature over a real AdSense response is the one simulated link. If an account turns up later, the real proof replaces that one step and nothing else changes.
@sharkzneverending @AncungAulia@Nabil-Aufa the ask stands: any AdSense account that is not closed, with a few dollars over the last three months. The owner should read the "What the owner is exposed to" section above first: the figure becomes public.
Researched this properly rather than leaving it as "someone find an account". Three findings, and the second one may unblock the gate today without anyone's AdSense account.
1. A new AdSense account cannot work. Not "too slow" — impossible.
This was worth settling first, because it was the obvious fallback.
The provider asks for the last three complete calendar months (trailingMonths, be/src/adsense/request.ts). Computed for today, that is:
Every one of those windows is in the past. An account created today earned nothing in them, the proven figure is 0.00, and the contract refuses with #31 AdvanceTooSmall before anything else — correctly.
So Google's review time ("usually a few days, in some cases 2-4 weeks", plus identity verification from June 2026) does not even matter. Any account we use must already have been earning before October. That removes option 2 from the list permanently.
2. Our own code may be the blocker, not Google. This is testable in five minutes.
be/src/adsense/account.ts:82 refuses before ever calling reports:generate:
if(acct.state==="READY")return;thrownewProveError("account",`… is ${acct.state}, not READY. Google does not serve reports for it.`);
That last sentence is an assumption we wrote, not something anyone measured. And the evidence points the other way:
the API reference defines CLOSED as "The account is closed and can't serve ads." It says nothing about reporting;
Google's help page for accessing a closed account says that after signing in you can "view your past account performance";
NEEDS_ATTENTION is refused by the same gate, and that state means the account is open with issues — it almost certainly does serve reports.
A closed account keeps its historical reporting data. Whether reports:generate serves it over the API is the one thing nobody has checked, and it is the difference between "blocked indefinitely" and "done this afternoon".
The test
Someone with access to that Google account gets a one-hour read-only token — OAuth 2.0 Playground, scope https://www.googleapis.com/auth/adsense.readonly, authorise, exchange — and runs:
That is byte for byte the URL the provider signs. Three outcomes:
Result
What it means
A totals figure comes back
The gate is ours. Relax assertAccountReady to allow CLOSED/NEEDS_ATTENTIONfor reads, and #5 can run today.
403 / 404 / an error
Google really does refuse. The assumption was right and we move to finding #3.
0.00 earnings
The account existed but earned nothing in Jul–Sep. Same dead end as a new account.
I cannot run this myself: GOOGLE_ACCESS_TOKEN in be/.env is empty, and these tokens last about an hour so any stored one would be stale anyway. It needs whoever owns that Google account, for two minutes.
Worth knowing before anyone relaxes that check: allowing a non-READY account is only safe for reading history. It must not become a general relaxation — a NEEDS_ATTENTION account can have an unverified identity or an unpaid balance, and we would be advancing against revenue Google itself may never pay out. If the test passes, the right change is a narrow allowlist of states for the report read, with the reason written next to it.
3. If Google does refuse: reactivation is real, and has one hard precondition
Reactivating a closed AdSense account exists — adsense.google.com/adsense/signup/reactivate, resubmit the site, "usually a few days, in some cases 2-4 weeks". Dead after 7 years of inactivity.
But: an account closed by Google for policy reasons can never be reopened, and that publisher may not open a new one either (policy closures).
So the question nobody has recorded: was pub-1144314860018910 closed by its owner, or by Google? Owner-closed means reactivation is worth starting now, in parallel with the test above, because 2-4 weeks runs past 2026-11-08 and starting it costs nothing. Policy-closed means that path is shut and only finding #2 or a different account remains.
One point of law worth being precise about
AdSense's terms "don't permit transfers of account ownership" (sign-up page). That rules out "give us your account".
It does not rule out what we are actually asking for: the owner keeps the account and grants a scoped, read-only, one-hour, revocable OAuth token. That is ordinary API access authorised by the owner, the same thing every analytics dashboard uses. Worth stating plainly when asking someone, so the ask does not sound like something it is not.
Keep asking around for a dormant account with earnings before October 2026. Four dollars of quarterly revenue is enough.
If none of that lands by ~2026-10-27, ship the demo on the probe witness and state which single link is simulated. The evidence pack is already written to be honest about exactly that.
@Lexirieru@Lin1er — steps 1 and 2 need whoever has that Google account.
@Lin1er — I ran the test from my previous comment and it came back inconclusive, in a way that points at you. Two minutes of your time would settle it.
What I ran
@Lexirieru authorised a adsense.readonly token from his own Google account, and I made three read-only calls:
GET /v2/accounts → {} HTTP 200
GET /v2/accounts/pub-1144314860018910/reports:… → PERMISSION_DENIED HTTP 403
GET /v2/accounts/pub-1144314860018910 → PERMISSION_DENIED HTTP 403
The token has since been revoked.
Why this does not answer the question
{} with a 200 means that Google account has no AdSense accounts the API will list. And pub-1144314860018910 answers 403 PERMISSION_DENIED — not 404, not a CLOSED state, but "you have no permission on this publisher".
Two explanations produce identical output, and I cannot tell them apart from here:
Axel's Google account simply never had AdSense. Then this says nothing about closed accounts — it is the wrong account, and the real one is someone else's.
Google hides closed accounts from the Management API entirely. Then this is the answer: not "no reports for a closed account" but "a closed account is not visible to the API at all", and assertAccountReady never even gets to run because resolvePublisherId fails first on an empty list.
I am not going to claim either one. But explanation 2 has a problem: somebody saw state: CLOSED at some point, because that is where this issue's premise comes from. The API only reports a state for an account it will show you. So whoever observed that had a Google account the API did list it under — and it was not Axel's.
That is almost certainly you.
What would settle it
Same thing, from the Google account you used when you found the account was closed:
OAuth 2.0 Playground, "Input your own scopes" → https://www.googleapis.com/auth/adsense.readonly → Authorize → sign in with that account → Exchange authorization code for tokens.
Copy the access token, then run (it reads from the clipboard, so the token never reaches your shell history or the screen):
Paste the output, not the token. Nothing in the output is secret. If a ya29. string ever appears in it, redact that.
What each outcome means
Call 1
Call 2
Conclusion
lists the account, state: CLOSED
a totals figure
🟢 The blocker is our own code. Relax assertAccountReady for reads only and #5 runs the same day.
lists the account, state: CLOSED
403 / 400
Google really does refuse reports for a closed account. Our assumption was right; reactivation is the only path.
{} again
403
Closed accounts are invisible to the API entirely. Same practical answer as the row above, different reason — and worth writing down, because our error message currently says something we would then know to be wrong.
lists it, state: READY or NEEDS_ATTENTION
a figure
The account was never the problem.
And the question that matters regardless
Was pub-1144314860018910 closed by its owner, or by Google for a policy violation?
Owner-closed → reactivation is available, "a few days, in some cases 2-4 weeks". That runs past 2026-11-08, so it has to start now or not at all.
The closure email, or the AdSense dashboard when signed in to that account, says which.
Also settled while researching this, so nobody spends time on it: a newly created AdSense account cannot work at all. The provider asks for the last three complete calendar months — today that is 2026-07-01 → 2026-09-30, which is in the past. An account created now earned nothing in that window, so the figure is 0.00 and the contract refuses with #31 AdvanceTooSmall. Google's review time is irrelevant. Any account we use must already have been earning before October.
@Lexirieru ran it from the Google account that owns the publisher. The token is revoked, and the display name is left out below:
GET /v2/accounts → HTTP 200
accounts/pub-1144314860018910 state: READY
createTime: 2023-12-06 timeZone: Asia/Jakarta
pendingTasks: ["billing-profile-creation"]
GET /v2/accounts/pub-1144314860018910/reports:generate (2026-07-01 → 2026-09-30, ESTIMATED_EARNINGS, USD)
→ HTTP 200, headers + startDate + endDate only: no "rows", no "totals"
What it settles:
The account is READY, not CLOSED. The premise of this issue was wrong. Your 403 was row 1 of your table: your Google account has no access to this publisher. It says nothing about closed accounts.
The figure is $0.00 for Q3. With no earnings, Google omits rows and totals instead of sending zeros. pendingTasks: billing-profile-creation fits that: the account has never earned enough to need a billing profile.
So the blocker is no longer the account. It is revenue in the window. A zero figure cannot produce a proof at all, before the contract's #31 AdvanceTooSmall even matters. TOTAL_REGEX needs a "totals" cell, so the relay stops at its live check with provider and never calls the attestor.
What that leaves:
Someone with a few dollars earned in July–September. Your point about new accounts applies to this one too: nothing earned now lands in the window until the window moves. After 2026-10-31 the last three complete months are Aug–Oct, so October earnings would count from 2026-11-01. That is still before 2026-11-08, but only just, and only if this account earns ~$4 in October.
Option 3, as agreed, with the 2026-10-27 cut-off.
One more read from this account would tell us whether it has earned anything since 2023-12. That decides whether 1 is even plausible for it. I will run it and post the result here.
The history read, as promised. Same account, token revoked:
reports:generate 2023-12-01 → 2026-10-21, dimensions=MONTH,
metrics=ESTIMATED_EARNINGS, PAGE_VIEWS, CLICKS
→ HTTP 200, headers only: no rows, no totals
pub-1144314860018910 has never recorded a single page view, click or cent since it was created in 2023-12, October included. It is an approved account with no site serving ads. October cannot rescue it, and neither can any later month in time for 2026-11-08.
So option 1 rests entirely on someone else's account that earned something in July–September. My account is out.
Given that, I suggest we start option 3 now instead of waiting for the 2026-10-27 cut-off, and keep the ask for an account open alongside it. If one turns up, a real proof replaces exactly one step. Nothing else in the demo changes, and the relay is live and verified, so that swap is an afternoon.
@Lexirieru your call on the demo script. I can draft the part that states which link is simulated, and the evidence behind every other link (tools/runs/, docs/deployments.md, the production-attestor smoke proof on the relay host), if that helps.
@Lin1er — agreed on all of it. Start option 3 now, and yes please to the draft.
Your history read settles this, and it settles it harder than "closed" ever did. An account that is approved, in good standing, and has never recorded a page view, a click or a cent since 2023-12 has nothing to prove. October cannot rescue it and no later month arrives in time.
What I got wrong, and have corrected
I spent a research pass on "does Google serve reports for a closed account?" — reading the API's State enum, the reactivation path, the policy-closure rules. All of it was answering a question that was never the question. The account was never closed. I inherited "CLOSED" from this issue's opening line and did not check the premise before researching around it.
Two things came out of it that are still worth having, so it was not wasted:
A new AdSense account cannot work either, and not because approval is slow. The window proven is the last three complete calendar months — today 2026-07-01 → 2026-09-30, always in the past. An account created now earned nothing in it however fast Google approves. That removes the obvious fallback permanently.
assertAccountReady's message, "Google does not serve reports for it", is an assumption we wrote and never measured. It did not matter here — the account is READY so the check passes — but it is still a sentence in our code that asserts something nobody has tested. Worth softening to what we actually know when someone is next in that file.
I have corrected docs/evidence.md, which told a reviewer the account was closed and that Google serves no reports for closed accounts. Both wrong. It now says what is true: approved, zero revenue, no rows across the whole history — and why a new account cannot substitute.
Option 3, and what it has to say
Please do draft the part that states which link is simulated. One request about its shape: say it once, plainly, early, and in the demo itself — not only in the written evidence. A reviewer who discovers the probe witness on their own has to wonder what else they were not told; a reviewer who is told in the first thirty seconds spends the rest of the demo looking at what works.
The honest framing is narrow, and it is narrower than people assume:
What is simulated: one signature. The claims in the demo are signed by a witness key published in this repository, instead of Reclaim's production attestor signing a real AdSense response.
What is not simulated: everything else. The contract, the sizing, the disbursement, the nullifier, the repayment ledger, all three negative cases and the borrower binding run on live testnet with real USDC movement — tools/runs/, 7/7 green, latest 2026-10-25T114611Z against the upgraded contract.
And the cryptography itself is not simulated either, which is the part worth saying out loud: a real production-attestor signature was accepted by Reclaim's own deployed verifier, and the same digest with one byte changed was rejected. Plus your prove:smoke on the relay host — a real claim, production attestor, 54 seconds. So the attestor path is proven; what is missing is one real AdSense response to put through it.
Put the other way: we are not missing a mechanism. We are missing four dollars of someone's ad revenue.
Your line "a real proof replaces exactly one step... that swap is an afternoon" is the right note to end on, and it is true — the relay is live, tools/pin_template.py (#83) derives and proves the template, and both contracts now run the #76 encoding as of today.
Keeping the ask open
Still worth asking around, and the ask is smaller than it sounds — an AdSense or AdMob account that earned anything at all between July and September 2026. Four dollars of quarterly revenue clears the 1 USDC floor. A dormant hobby account is ideal and better than a large one.
Worth pairing with #90 when anyone asks: either product works for the same request.
Where this leaves the deliverables
Deliverable 1 keeps its one stated gap, Deliverable 3 needs the video (#28). Both are written as such in docs/evidence.md already — we mark them ourselves rather than letting a reviewer find them.
Leaving this issue open: the ask stays live until the submission, because a proof arriving on 2026-11-05 is still worth having.
Option 3's disclosure draft is merged: docs/demo-disclosure.md (#91). I verified every factual row in it live before merging — the four transactions on Horizon, sizing() on the contract, both evidence.md anchors, and all 16 links. Review notes are on the PR.
Two things that came out of checking it, both worth having on this issue:
The production contract could not have paid an advance, not merely has not. claim_template() on CCQFL2Q6…I2HS returns null, so request_advance cannot get past TemplateNotSet. liquidity() is 1050000000 stroops — the 105 USDC funded, untouched. That is the cleanest possible answer if a reviewer asks whether the live contract has been exercised.
The rehearsal contract's verifier does check signatures. I went in assuming the probe instance skipped verification, which would have made "signed by a test witness" an overstatement. It does not: CASAIKW7…WZURP runs Reclaim's own wasm with an epoch whose witness is the published 0x1111…1111 key. The signature is recovered and compared against a key anyone can read. "A test witness, not a missing check" is both accurate and the stronger thing to say.
What is still open here is only the first row of that table: an AdSense or AdMob account that earned anything between July and September 2026, even a few dollars. #93 part 2 needs the same thing for AdMob's non-zero row, so it is one ask serving two issues now.
This issue stays open until submission. If an account turns up, only that first row changes: the owner signs in, the relay proves it, and request_advance on the production contract replaces the rehearsal payout.
An account that has income is being checked for the first row: AdSense revenue in Jul–Sep 2026, with AdMob's non-zero row for #93 in the same pass. It belongs to someone outside the team. The check is read-only, and its results stay local. I will report here only whether it qualifies.
If it does, nothing goes on chain until the owner has read "What the owner is exposed to" above and agreed. They would also have to be added as a test user on the consent screen while it is in Testing (#86).
The account from my last comment does not qualify for the first row. Its AdSense is READY, but it has no totals for Jul–Sep 2026, which means zero. It does have AdMob revenue in that window, but an AdMob proof cannot be checked until #94 lands, after 2026-11-08. Details are on #93. Option 3 stays the plan, and the ask stays open: an AdSense account with any revenue in Jul–Sep 2026.
The owner of the account outside the team (#93) has agreed, after reading this issue's exposure note. That covers both steps: a local proof for the AdMob template (#96), and a real advance on chain, which makes their AdMob publisher id, the Jul–Sep 2026 window and the revenue figure public permanently. They are named here only as "an account outside the team", and the borrower will be the team's GA2CD6…WWH2, so no wallet of theirs is involved.
This unblocks the first row of the disclosure table through AdMob, once #94 is deployed. @Lexirieru, your go on #90 is the only thing left before the contract work, and the 24 h timelock sets the pace.
does not exist, and cannot be made from any account we have
The account from #93 has AdSense in READY, but zero for Jul–Sep 2026 — and zero means the relay refuses before the attestor (ProveError("empty") in be/src/adsense/account.ts), so there is no signed claim at all. Not a small figure: nothing.
So the AdMob route closes the end-to-end demo, but it cannot close #5, whose wording is "one real AdSense revenue proof verified on testnet".
What is actually needed: someone with an AdSense account that earned anything above zero between 2026-07-01 and 2026-09-30. Their part is about five minutes now that the consent screen is published — they open https://app.forepay.xyz, sign in with Google, and nothing else. Nobody handles a token, and they do not need to be added as a test user any more.
The exposure is the same as recorded above and unchanged: their publisher id, the Jul–Sep 2026 window and the revenue figure become public permanently on testnet. The borrower stays the team's GA2CD6…WWH2, so no wallet of theirs is involved.
@Lexirieru@Lin1er@Nabil-Aufa@AncungAulia — nine days to 2026-11-08. This one is outreach, not engineering, and it needs one person to own it rather than four to notice it.
Activity
Lexirieru commentedon Oct 20, 2026
Taking this off the "someone will do it" pile, because after today it is the only thing left blocking the gate, and it is the one item no one on this team can solve with code.
Everything downstream of it is now ready
contextMessagethe contract does not expectapi-forepay.jameshub.fun(#17)sizing()(#63)The proving path itself already works on the relay host:
prove:smokeproduced a claim in 54 seconds, signed by Reclaim's production attestor, and Reclaim's own deployed verifier accepted the digest and rejected a one-byte change. That is the whole mechanism, proven, against a public endpoint.The only missing input is an AdSense account Google will serve a report for.
What is actually needed
pub-1144314860018910is CLOSED, and Google serves no reports for a closed account — no proof can ever come from it.https://www.googleapis.com/auth/adsense.readonlytoken. Read-only, one scope, and the token never enters the claim: zkFetch keeps it insecretOptions.headers, inside the TLS session.What the owner is exposed to
Worth being straight about this, because "give us an API token for your ad revenue account" is a real ask:
A dormant or hobby AdSense account with a few dollars in it is the ideal candidate, and is strictly better for the demo than a large one.
Three ways this gets unblocked
tools/runs/); what would be missing is one real attestor signature over one real AdSense response. The honest version of this is a demo that shows the mechanism working and states plainly which single link is simulated — not one that implies a real proof happened.Option 3 is a worse submission than option 1, but it is a real submission, and it is available today. Option 1 is worth asking around for this week.
@Lexirieru @Lin1er @sharkzneverending @AncungAulia — does anyone have, or know someone with, an AdSense account that is not closed? That is the whole ask.
Lin1er commentedon Oct 20, 2026
@Lexirieru agreed on the order: option 1 this week, with option 3 prepared alongside it so it is not a scramble at the end.
What changed on my side since your comment, which makes option 1 cheaper for whoever turns up:
adsense.readonlyonly). The token goes once to the relay and is held only in memory. Nobody has to DM a token.request_advancefit in one sitting with the owner.Proposal for a cut-off: if there is no non-CLOSED account by 2026-10-27, we build the demo on option 3. That still leaves time before the 2026-10-30 milestone. The script states plainly that the attestor signature over a real AdSense response is the one simulated link. If an account turns up later, the real proof replaces that one step and nothing else changes.
@sharkzneverending @AncungAulia @Nabil-Aufa the ask stands: any AdSense account that is not closed, with a few dollars over the last three months. The owner should read the "What the owner is exposed to" section above first: the figure becomes public.
Lexirieru commentedon Oct 20, 2026
Researched this properly rather than leaving it as "someone find an account". Three findings, and the second one may unblock the gate today without anyone's AdSense account.
1. A new AdSense account cannot work. Not "too slow" — impossible.
This was worth settling first, because it was the obvious fallback.
The provider asks for the last three complete calendar months (
trailingMonths,be/src/adsense/request.ts). Computed for today, that is:Every one of those windows is in the past. An account created today earned nothing in them, the proven figure is
0.00, and the contract refuses with#31 AdvanceTooSmallbefore anything else — correctly.So Google's review time ("usually a few days, in some cases 2-4 weeks", plus identity verification from June 2026) does not even matter. Any account we use must already have been earning before October. That removes option 2 from the list permanently.
2. Our own code may be the blocker, not Google. This is testable in five minutes.
be/src/adsense/account.ts:82refuses before ever callingreports:generate:That last sentence is an assumption we wrote, not something anyone measured. And the evidence points the other way:
CLOSEDas "The account is closed and can't serve ads." It says nothing about reporting;NEEDS_ATTENTIONis refused by the same gate, and that state means the account is open with issues — it almost certainly does serve reports.A closed account keeps its historical reporting data. Whether
reports:generateserves it over the API is the one thing nobody has checked, and it is the difference between "blocked indefinitely" and "done this afternoon".The test
Someone with access to that Google account gets a one-hour read-only token — OAuth 2.0 Playground, scope
https://www.googleapis.com/auth/adsense.readonly, authorise, exchange — and runs:That is byte for byte the URL the provider signs. Three outcomes:
assertAccountReadyto allowCLOSED/NEEDS_ATTENTIONfor reads, and #5 can run today.403/404/ an error0.00earningsI cannot run this myself:
GOOGLE_ACCESS_TOKENinbe/.envis empty, and these tokens last about an hour so any stored one would be stale anyway. It needs whoever owns that Google account, for two minutes.Worth knowing before anyone relaxes that check: allowing a non-
READYaccount is only safe for reading history. It must not become a general relaxation — aNEEDS_ATTENTIONaccount can have an unverified identity or an unpaid balance, and we would be advancing against revenue Google itself may never pay out. If the test passes, the right change is a narrow allowlist of states for the report read, with the reason written next to it.3. If Google does refuse: reactivation is real, and has one hard precondition
Reactivating a closed AdSense account exists —
adsense.google.com/adsense/signup/reactivate, resubmit the site, "usually a few days, in some cases 2-4 weeks". Dead after 7 years of inactivity.But: an account closed by Google for policy reasons can never be reopened, and that publisher may not open a new one either (policy closures).
So the question nobody has recorded: was
pub-1144314860018910closed by its owner, or by Google? Owner-closed means reactivation is worth starting now, in parallel with the test above, because 2-4 weeks runs past 2026-11-08 and starting it costs nothing. Policy-closed means that path is shut and only finding #2 or a different account remains.One point of law worth being precise about
AdSense's terms "don't permit transfers of account ownership" (sign-up page). That rules out "give us your account".
It does not rule out what we are actually asking for: the owner keeps the account and grants a scoped, read-only, one-hour, revocable OAuth token. That is ordinary API access authorised by the owner, the same thing every analytics dashboard uses. Worth stating plainly when asking someone, so the ask does not sound like something it is not.
What I would do, in order
@Lexirieru @Lin1er — steps 1 and 2 need whoever has that Google account.
Lexirieru commentedon Oct 20, 2026
@Lin1er — I ran the test from my previous comment and it came back inconclusive, in a way that points at you. Two minutes of your time would settle it.
What I ran
@Lexirieru authorised a
adsense.readonlytoken from his own Google account, and I made three read-only calls:The token has since been revoked.
Why this does not answer the question
{}with a200means that Google account has no AdSense accounts the API will list. Andpub-1144314860018910answers 403 PERMISSION_DENIED — not404, not aCLOSEDstate, but "you have no permission on this publisher".Two explanations produce identical output, and I cannot tell them apart from here:
assertAccountReadynever even gets to run becauseresolvePublisherIdfails first on an empty list.I am not going to claim either one. But explanation 2 has a problem: somebody saw
state: CLOSEDat some point, because that is where this issue's premise comes from. The API only reports a state for an account it will show you. So whoever observed that had a Google account the API did list it under — and it was not Axel's.That is almost certainly you.
What would settle it
Same thing, from the Google account you used when you found the account was closed:
https://www.googleapis.com/auth/adsense.readonly→ Authorize → sign in with that account → Exchange authorization code for tokens.Paste the output, not the token. Nothing in the output is secret. If a
ya29.string ever appears in it, redact that.What each outcome means
state: CLOSEDtotalsfigureassertAccountReadyfor reads only and #5 runs the same day.state: CLOSED403/400{}again403state: READYorNEEDS_ATTENTIONAnd the question that matters regardless
Was
pub-1144314860018910closed by its owner, or by Google for a policy violation?Owner-closed → reactivation is available, "a few days, in some cases 2-4 weeks". That runs past 2026-11-08, so it has to start now or not at all.
Policy-closed → that path is permanently shut, and the publisher may not open a new account either.
The closure email, or the AdSense dashboard when signed in to that account, says which.
Also settled while researching this, so nobody spends time on it: a newly created AdSense account cannot work at all. The provider asks for the last three complete calendar months — today that is 2026-07-01 → 2026-09-30, which is in the past. An account created now earned nothing in that window, so the figure is
0.00and the contract refuses with#31 AdvanceTooSmall. Google's review time is irrelevant. Any account we use must already have been earning before October.Lin1er commentedon Oct 20, 2026
@Lexirieru ran it from the Google account that owns the publisher. The token is revoked, and the display name is left out below:
What it settles:
READY, notCLOSED. The premise of this issue was wrong. Your 403 was row 1 of your table: your Google account has no access to this publisher. It says nothing about closed accounts.200fromreports:generatewith our exact parameters.rowsandtotalsinstead of sending zeros.pendingTasks: billing-profile-creationfits that: the account has never earned enough to need a billing profile.So the blocker is no longer the account. It is revenue in the window. A zero figure cannot produce a proof at all, before the contract's
#31 AdvanceTooSmalleven matters.TOTAL_REGEXneeds a"totals"cell, so the relay stops at its live check withproviderand never calls the attestor.What that leaves:
One more read from this account would tell us whether it has earned anything since 2023-12. That decides whether 1 is even plausible for it. I will run it and post the result here.
Lin1er commentedon Oct 20, 2026
The history read, as promised. Same account, token revoked:
pub-1144314860018910has never recorded a single page view, click or cent since it was created in 2023-12, October included. It is an approved account with no site serving ads. October cannot rescue it, and neither can any later month in time for 2026-11-08.So option 1 rests entirely on someone else's account that earned something in July–September. My account is out.
Given that, I suggest we start option 3 now instead of waiting for the 2026-10-27 cut-off, and keep the ask for an account open alongside it. If one turns up, a real proof replaces exactly one step. Nothing else in the demo changes, and the relay is live and verified, so that swap is an afternoon.
@Lexirieru your call on the demo script. I can draft the part that states which link is simulated, and the evidence behind every other link (
tools/runs/,docs/deployments.md, the production-attestor smoke proof on the relay host), if that helps.docs: #76 executed and the dev template re-pinned, with a 21,370 XLM …
Lexirieru commentedon Oct 25, 2026
@Lin1er — agreed on all of it. Start option 3 now, and yes please to the draft.
Your history read settles this, and it settles it harder than "closed" ever did. An account that is approved, in good standing, and has never recorded a page view, a click or a cent since 2023-12 has nothing to prove. October cannot rescue it and no later month arrives in time.
What I got wrong, and have corrected
I spent a research pass on "does Google serve reports for a closed account?" — reading the API's
Stateenum, the reactivation path, the policy-closure rules. All of it was answering a question that was never the question. The account was never closed. I inherited "CLOSED" from this issue's opening line and did not check the premise before researching around it.Two things came out of it that are still worth having, so it was not wasted:
assertAccountReady's message, "Google does not serve reports for it", is an assumption we wrote and never measured. It did not matter here — the account isREADYso the check passes — but it is still a sentence in our code that asserts something nobody has tested. Worth softening to what we actually know when someone is next in that file.I have corrected
docs/evidence.md, which told a reviewer the account was closed and that Google serves no reports for closed accounts. Both wrong. It now says what is true: approved, zero revenue, no rows across the whole history — and why a new account cannot substitute.Option 3, and what it has to say
Please do draft the part that states which link is simulated. One request about its shape: say it once, plainly, early, and in the demo itself — not only in the written evidence. A reviewer who discovers the probe witness on their own has to wonder what else they were not told; a reviewer who is told in the first thirty seconds spends the rest of the demo looking at what works.
The honest framing is narrow, and it is narrower than people assume:
tools/runs/, 7/7 green, latest2026-10-25T114611Zagainst the upgraded contract.prove:smokeon the relay host — a real claim, production attestor, 54 seconds. So the attestor path is proven; what is missing is one real AdSense response to put through it.Put the other way: we are not missing a mechanism. We are missing four dollars of someone's ad revenue.
Your line "a real proof replaces exactly one step... that swap is an afternoon" is the right note to end on, and it is true — the relay is live,
tools/pin_template.py(#83) derives and proves the template, and both contracts now run the #76 encoding as of today.Keeping the ask open
Still worth asking around, and the ask is smaller than it sounds — an AdSense or AdMob account that earned anything at all between July and September 2026. Four dollars of quarterly revenue clears the 1 USDC floor. A dormant hobby account is ideal and better than a large one.
Worth pairing with #90 when anyone asks: either product works for the same request.
Where this leaves the deliverables
Deliverable 1 keeps its one stated gap, Deliverable 3 needs the video (#28). Both are written as such in
docs/evidence.mdalready — we mark them ourselves rather than letting a reviewer find them.Leaving this issue open: the ask stays live until the submission, because a proof arriving on 2026-11-05 is still worth having.
docs(#22): record the live front end and its screenshots
docs(#22): record the live front end and its screenshots (#89)
fix(#77): say only what was measured about an account that is not REA…
docs(#77): the demo's one simulated link, said once and early, with t…
Lexirieru commentedon Oct 25, 2026
Option 3's disclosure draft is merged:
docs/demo-disclosure.md(#91). I verified every factual row in it live before merging — the four transactions on Horizon,sizing()on the contract, bothevidence.mdanchors, and all 16 links. Review notes are on the PR.Two things that came out of checking it, both worth having on this issue:
claim_template()onCCQFL2Q6…I2HSreturnsnull, sorequest_advancecannot get pastTemplateNotSet.liquidity()is1050000000stroops — the 105 USDC funded, untouched. That is the cleanest possible answer if a reviewer asks whether the live contract has been exercised.CASAIKW7…WZURPruns Reclaim's own wasm with an epoch whose witness is the published0x1111…1111key. The signature is recovered and compared against a key anyone can read. "A test witness, not a missing check" is both accurate and the stronger thing to say.What is still open here is only the first row of that table: an AdSense or AdMob account that earned anything between July and September 2026, even a few dollars. #93 part 2 needs the same thing for AdMob's non-zero row, so it is one ask serving two issues now.
This issue stays open until submission. If an account turns up, only that first row changes: the owner signs in, the relay proves it, and
request_advanceon the production contract replaces the rehearsal payout.Lin1er commentedon Oct 25, 2026
An account that has income is being checked for the first row: AdSense revenue in Jul–Sep 2026, with AdMob's non-zero row for #93 in the same pass. It belongs to someone outside the team. The check is read-only, and its results stay local. I will report here only whether it qualifies.
If it does, nothing goes on chain until the owner has read "What the owner is exposed to" above and agreed. They would also have to be added as a test user on the consent screen while it is in Testing (#86).
Lin1er commentedon Oct 26, 2026
The account from my last comment does not qualify for the first row. Its AdSense is
READY, but it has nototalsfor Jul–Sep 2026, which means zero. It does have AdMob revenue in that window, but an AdMob proof cannot be checked until #94 lands, after 2026-11-08. Details are on #93. Option 3 stays the plan, and the ask stays open: an AdSense account with any revenue in Jul–Sep 2026.Lin1er commentedon Oct 26, 2026
The owner of the account outside the team (#93) has agreed, after reading this issue's exposure note. That covers both steps: a local proof for the AdMob template (#96), and a real advance on chain, which makes their AdMob publisher id, the Jul–Sep 2026 window and the revenue figure public permanently. They are named here only as "an account outside the team", and the borrower will be the team's
GA2CD6…WWH2, so no wallet of theirs is involved.This unblocks the first row of the disclosure table through AdMob, once #94 is deployed. @Lexirieru, your go on #90 is the only thing left before the contract work, and the 24 h timelock sets the pace.
Lexirieru commentedon Oct 30, 2026
This issue is now the critical path, and it has no assignee. Open since 2026-10-20.
Where everything else stands as of today:
admob.readonlyin Data AccessThe account from #93 has AdSense in
READY, but zero for Jul–Sep 2026 — and zero means the relay refuses before the attestor (ProveError("empty")inbe/src/adsense/account.ts), so there is no signed claim at all. Not a small figure: nothing.So the AdMob route closes the end-to-end demo, but it cannot close #5, whose wording is "one real AdSense revenue proof verified on testnet".
What is actually needed: someone with an AdSense account that earned anything above zero between 2026-07-01 and 2026-09-30. Their part is about five minutes now that the consent screen is published — they open
https://app.forepay.xyz, sign in with Google, and nothing else. Nobody handles a token, and they do not need to be added as a test user any more.The exposure is the same as recorded above and unchanged: their publisher id, the Jul–Sep 2026 window and the revenue figure become public permanently on testnet. The borrower stays the team's
GA2CD6…WWH2, so no wallet of theirs is involved.@Lexirieru @Lin1er @Nabil-Aufa @AncungAulia — nine days to 2026-11-08. This one is outreach, not engineering, and it needs one person to own it rather than four to notice it.