Repository navigation
feat(#94): AdMob as a second revenue source, and refuse an unpinned claim owner - #106
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…wner A revenue source selects the template, and the template pins the host. So the caller's `source` argument cannot make a claim verify against the wrong API: an AdMob claim checked as AdSense is rebuilt into a request to adsense.googleapis.com, the identifier differs, and the signature recovers to nobody. Tested in both directions. The value order is NOT in the template. `rebuild_parameters` interleaves positionally, so the order is part of the source's shape and lives in `claim_values`. AdMob needs the reverse of AdSense's because the attestor sorts the parameter keys, putting `body` (which holds the window) before `url` (which holds the publisher id) — #93. Getting it wrong would surface as an unexplained ClaimMismatch, so three places check the same ordering without deriving it from each other: this contract, pin_template.py, and the relay. Micros truncate to cents, never round up. The figure's key is per source (`revenueUsd` / `revenueMicros`) and sits inside the signed context, because the two mistakes are not symmetric: dollars read as micros fail loudly, while micros read as dollars return the 100 USDC cap for any revenue at all, silently. Measured on the deployed contract, not reasoned about: quote("123450000") is 1000000000 stroops. The nullifier is tagged for AdMob only. One Google account's AdSense and AdMob publisher ids are the same `pub-` id (#93, on a real account), so untagged an AdMob proof would spend the AdSense nullifier for the same window. AdSense stays untagged because advances already on chain are keyed on those bytes — pinned against a literal derived independently in Python, so it is not the contract agreeing with itself. The source of an advance is `DataKey::AdvanceSource`, beside the `Advance` rather than a field in it: a required field would retype an existing stored value and every advance recorded before this upgrade would fail to decode. Those are debts. Also carries the two changes asked for on #103: an unpinned claim owner is refused with `ClaimOwnerNotSet` rather than falling back to the borrower, and `set_claim_owner` has its own `ClaimOwnerMalformed` instead of reusing `ClaimMismatch`. Refusing forced the test harness to adopt the real owner shape, which is the actual fix for the class of bug #102 was: a `G…` address cannot be pinned at all, so the pre-#102 form cannot be written here by accident any more. Every test now runs through an app-signed claim. make_claim_fixture.py gains the AdMob chain. Its identifier is byte-identical to the one be/src/admob/fixture.test.ts derives in TypeScript (#101) — a Python encoder and a TypeScript one agreeing on the canonical parameters, the context, and the keccak over them. 61 contract tests pass, plus 9 in reclaim-claim. fmt, clippy -D warnings, the wasm build, the no_std wasm check, make_claim_fixture --check and pin_template --self-test are all clean. The linux wasm row is PENDING for CI to measure. Refs #94, #102, #93. Base is #103. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QdNuoJ9e954ojofNVGUezW
Filled in from the measurement the runner printed for the PENDING row, rather than from a local build: wasm is byte-identical only within a host triple and toolchain, so the macOS hash is not the one CI checks. x86_64-unknown-linux-gnu 28.1.0 4c5b24de377fab73a55db715739f8b4d9f7e48e75484cad0c8f9df8f52b7a049 Every other step of that run passed, including "Test snapshots are committed", so the snapshots in the previous commit are complete and stable. Coverage was skipped because the job stopped at the PENDING row; this push is the first run that exercises it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QdNuoJ9e954ojofNVGUezW
Verified against the official state-archival docs via MCP Stellar Raven: a persistent entry whose TTL lapses is archived, not deleted, and the host makes the caller restore it before the read. So an AdMob advance cannot quietly read back as AdSense once its TTL runs out. The line itself would be a silent debt-relabelling bug in temporary storage, and nothing in the code said why it is not one here. Same property the nullifier already rests on. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QdNuoJ9e954ojofNVGUezW
aac0e61 to
faf9540
Compare
|
@Lin1er @Nabil-Aufa review needed, please. #103 is merged ( I am not merging this one myself, and I want to be explicit about why. @Lexirieru has approved me merging today's work, and I merged #103 on that basis because I was its reviewer. This PR is mine. Merging it would be a self-merge of a contract change on a contract that holds funds, which working agreement item 4 forbids, and the "two days without an ACC" clause does not apply to a PR opened the same day. I have quietly broken that rule before — #79, #80, #82 and #83 were all mine and all merged by me — so I am not repeating it on the change that decides whether a real advance can happen. What I would most like a second pair of eyes on, in order:
Verified with Raven since the PR was writtenRaven was disconnected when I wrote this, which I flagged in the PR body. It is back, and I have now checked the Soroban claims against it. Two of my design decisions turn out to be the documented pattern, not just defensible:
That is
That is "absent means AdSense", written only for a source that is not AdSense. I also walked the whole of that red-flags checklist against this diff. Five pass outright: no variable-length data in a ledger key ( The sixth is worth a sentence, because it is the one place
So an archived Method note corrected: the PR body says the Stellar facts came from the skill rather than Raven. They have now been checked against Raven too, and nothing in them changed. |
The previous row was measured before faf9540, which added a doc comment and nothing else. That changed the wasm. Proven rather than assumed, by building twice with nothing else different: with the doc comment on advance_source 0c5c70c9...acdd (aarch64-apple-darwin) with that one comment removed 57f3ebce...04b3 and `strings` finds the comment's text inside the wasm. soroban-sdk embeds the doc comments of #[contractimpl] functions in the contract-spec metadata section, so they are part of the deployed bytes. Two consequences, now in the wasm-hashes.txt header so the next person does not spend an afternoon on it: - A "docs only" commit is not docs-only for the artifact. It needs this row re-recorded, and on a released contract a new release and a new verification. - These comments are published on chain and readable by anyone. Good to have on purpose, surprising to discover by accident. Linux row from CI's own measurement on the rebased branch: x86_64-unknown-linux-gnu 28.1.0 f4fd10d646307bd4f204a26be3b64c35141587b9e12aca0f41b48c049d3a5a36 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QdNuoJ9e954ojofNVGUezW
|
CI green on It went red once in between, and the cause is worth more than the fix. @Lin1er @Nabil-Aufa @AncungAulia — this one will bite whoever touches the contract next. A doc comment changes the wasm hash
And Two things follow, and both are now in the
I had assumed Status
Review asks are in my previous comment, in priority order. The first one ( |
|
@Lexirieru, a reminder: the deadline is today, 2026-10-30, and the submission has to go in today. Your note on #81 plans the combined upgrade around a submission on 2026-11-08. Please confirm which date holds. If it is today, the real-advance path (#106 release → |
|
@Lexirieru, one thing from the front end's side, for the deploy order. #106 puts On #104 now: both calls lead with the source ( Deploy order, from the front end:
Between 1 and 2 nobody can accept an advance, but nothing is lost: the refusal comes at simulation, before the wallet is asked to sign. |
…urce, once the contract takes it #106 (#94) puts `source: Source` first in both calls. Behind NEXT_PUBLIC_CONTRACT_TAKES_SOURCE=1 the front end sends it, as `vec[symbol("AdSense")]` or `vec[symbol("AdMob")]`; unset, the calls are what they were, so this can merge before the upgrade and the switch is one env change when it executes. The relay e2e build runs as against #106's contract and the mock build as before it. The stub sizes an AdMob request_advance from its micros, and the AdMob test now goes through to 2d. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Lin1er
left a comment
There was a problem hiding this comment.
Approved, with your four review asks checked in order. One deploy dependency is on the API side: #107, below.
1. claim_values: verified against a real proof, not just the fixture
I ran this PR's contract code (648f864) against the real AdMob proof from prove:admob (#96). The proof is signed by the production attestor 0x244897572368eadf65bfbc5aec98d8e5443a9072, from an account outside the team. I used a temporary test that is not committed, because the proof carries that account's publisher id and figure. The test does this:
- It pins your
ADMOB_TEMPLATEconstant fromtest_admob.rs, unchanged. - It pins
set_claim_ownerwith the app id. - It uses a verifier that recovers the signer and accepts only the real attestor's address.
- It calls
verify_claim(AdMob, …)with the proof's real borrower, publisher id, window,revenueMicros, provider hash,timestampS,epochand signature.
| Case | Result |
|---|---|
Source::AdMob, app owner pinned |
Verifies, and returns the signed micros as revenue_usd |
Same proof, Source::AdSense (AdSense value order and key) |
Refused |
| Same proof, a different owner pinned | Refused, so the verifier really checks the signer |
So the AdMob value order [sy, sm, sd, ey, em, ed, pub_id], the revenueMicros key in the context, and the template's literal segments together rebuild exactly the identifier and digest the production attestor signed. That includes the escaped separators and the User-Agent / accept / content-type header set. This check is independent of make_claim_fixture.py, pin_template.py --self-test and be/src/admob/request.test.ts, and it is the only one of the four that uses Reclaim's own signature.
2. revenue_cents and the context key
- The key is fixed by the source.
revenue_keyisrevenueMicrosonly forSource::AdMob, and that key is inside the signed context. A micros string can therefore only verify as AdMob. The silent-cap direction would need a claim signed withrevenueUsdholding micros, and the relay never extracts that: the audit on #100 refuses anyrevenueUsdin an AdMob proof. parse_micros_centstruncates and refuses well. It refuses., an empty string, anything over 32 bytes, and anything abovei128::MAX / 1e6before the multiply.- Answering @Nabil-Aufa: yes, for AdMob
revenue_usdcarries the signed micros string.verify_claimchecks the argument against the context underrevenueMicros, and the real-proof run above passed the micros exactly that way.
3. the_adsense_nullifier_bytes_did_not_change: a third derivation
Computed in Node (crypto.createHash("sha256")), which shares no code with the contract or with Python:
AdSense pub-1234567890123456, 2026-07-01, 2026-09-30 3140b7a01c306d98cfed42ae54092856f38808a69e15ef94ce26d57a734ba31a
AdMob the same, + len ‖ "admob" b4e9944247251fa09409c71406da72d4f03dc9e7a374a708bd92459521d93a58
AdSense equals your literal. AdMob equals this PR's nullifier_for(AdMob, …), which I ran on 648f864. The AdMob value is now pinned in be/ on #107.
4. source_tag's doc comment
It reads clearly. "Forced, not chosen", the orphaned-debt reason, and "the only place the exception lives" are what stop someone from tidying it up. I would not change it, and with your finding on this PR, changing it would also move the wasm hash.
Deploy dependency: #107
Putting source first broke the API as well as the front end. /advances and /transactions read request_advance's arguments by position. After execute_upgrade, the source would have been read as the borrower, and every new advance would have vanished from the ledger silently, AdSense included. #107 reads both shapes, since calls already on chain keep five arguments. It tags AdMob's nullifier and adds source to /advances. It is safe to merge before the upgrade, and I want it on the relay host before execute_upgrade runs. With #107, the deploy order is:
- #107 merged and on the relay host (any time before the upgrade)
execute_upgradeNEXT_PUBLIC_CONTRACT_TAKES_SOURCE=1on Vercel plus a redeploy (@AncungAulia, per @Nabil-Aufa)set_claim_owner, then the templates, reading the fee at simulation
The date question @Nabil-Aufa raised (today, or 2026-11-08) is still yours to answer.
|
Merging on @Lin1er's approval, with @Lexirieru's go as PM. Thank you for the review, and for finding #107 while doing it — that one is the difference between an upgrade and a silent outage. Verified locally on
So three independent implementations of the tagged nullifier now agree: this contract's Rust, #107's TypeScript, and a Python derivation written from the spec in Merging changes nothing on chain. The deployed contract is still v0.4.0 (
#102 stays open until step 6 and a real proof verifying on chain. |
…ob's nullifier (#107) #106 puts a Source first in request_advance. The history routes read its arguments by position, so after the upgrade every new advance would have read the source as the borrower and dropped out of /advances and /transactions without an error. Calls already on chain keep the old five arguments, so both shapes are read. An AdMob nullifier appends len || "admob", as claim::nullifier_of does on #106; the value is checked against that contract's nullifier_for. /advances rows gain source.
) * feat(#97): choose AdSense or AdMob on 2a, and prove the chosen one - 2a asks where the creator earns, AdSense (websites) or AdMob (apps). The Google sign-in asks for that source's read-only scope only, and a token without it counts as the creator stopping. - POST /proofs carries `source: "admob"` for AdMob only, so an AdSense request is what it was before. The kept job records its source, and a resumed job proves what it was started for. - The relay's `token` and `account` failures name AdMob for an AdMob proof (googleSignInAdmob, noAdmob). The waiting, checking and offer copy name the source. - An AdMob figure is sized from its micros truncated to cents (`provenUsd`). `request_advance` gets the signed micros; its AdMob arguments land with #94. - The mock answers AdMob the relay's way, so the flow runs without a relay. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(#97): e2e for proving AdMob, and stack the source tiles on the narrowest phones - relay.spec: choosing AdMob asks Google for admob.readonly only, sends `source: "admob"`, sizes the offer from the micros truncated to cents and names AdMob on the offer. A Google account with no AdMob gets the AdMob panel, and Prove again stays on AdMob. - The two source tiles sit side by side from about 19rem of card, and stack below it, where "AdSense" spilled out of its tile at 320 (layout.spec). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(#97): the chosen source's tile is highlighted from state, and e2e pins which one Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(#97): a resumed AdMob proof stays AdMob, and every screen of it says so From a strict review: - A job kept as AdMob made the choice again only for its own resume. After leaving and coming back, Prove again asked Google for adsense.readonly and the relay proved AdSense. `proofRunning` now returns the kept job's source, and `prove(src)` makes it the choice, so Prove again and Back stay on it. - "Reading your revenue" names the source, from the kept job on a resume. - The contract's refusals that name AdSense (10, 11, 14, 30) name AdMob for an AdMob proof. - The source tiles say "Websites" and "Apps", so neither wraps where the other does not, and the tile's ring is the only focus indicator. - An AdMob request without micros is cut to cents before `quote`, which refuses a third decimal place. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(#97): wait for the second proof before reading what it sent Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(#97): lead request_advance and nullifier_for with the revenue source, once the contract takes it #106 (#94) puts `source: Source` first in both calls. Behind NEXT_PUBLIC_CONTRACT_TAKES_SOURCE=1 the front end sends it, as `vec[symbol("AdSense")]` or `vec[symbol("AdMob")]`; unset, the calls are what they were, so this can merge before the upgrade and the switch is one env change when it executes. The relay e2e build runs as against #106's contract and the mock build as before it. The stub sizes an AdMob request_advance from its micros, and the AdMob test now goes through to 2d. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Nabil-Aufa <181296848+Nabil-Aufa@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
|
@Lexirieru, step 1 is done. #107 is on the relay host. You can go ahead with steps 2 and 3 whenever you are ready.
For step 5, AdMob (#96): the eight template parts are on #96. They come from the real proof and match your Then a real AdMob advance: the account owner signs in on #100 and #101 are now out of draft so the host can go back to |
|
@Lexirieru @AncungAulia, the real AdMob advance now waits only on the upgrade. Everything else is live: the relay with #107 at @Lexirieru: steps 2, 3 and 5 are yours. As of now there is no v0.5.0 release, and
@AncungAulia: step 4 is yours, straight after After step 5: the AdMob account owner signs in on Please reply here with the time you plan to propose, so we can line up steps 4 to 6. |
The `aarch64-apple-darwin` row still held `2aefbf74...6ed25`, measured before #103 and #106. The row is reference only and nothing checks it — which is exactly why a stale value is worse than an absent one: it is still read, and it still gets trusted. Re-measured on main at 2ea1e15, the tree v0.5.0 is tagged from, with the same stellar-cli 27.0.0: 0c5c70c9...e1acdd. That is the value the header already records for "with a doc comment on advance_source", which is this tree. The CI-verified linux row is unchanged: `sc/` has not moved since #106 merged, so f4fd10d6...a5a36 is still current and still the hash CI rebuilds on every push. Neither hash is the one that goes on chain. That one comes from the release workflow's artifact, per docs/deployments.md. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QdNuoJ9e954ojofNVGUezW
|
@Lin1er, answering your question with a time rather than a "soon". Everything that was waiting on a merge is merged.
Verified locally before each merge, on v0.5.0 is tagged and building
That puts Confirmed independently before tagging:
@AncungAulia — this is the ten minutes I need you forNot today. Tomorrow, 2026-10-31, at the same hour, I will post here before I run
Between my One thing still owed on #99The host runs |
|
@Lexirieru, the #99 item is done. The host is on I will watch the relay around |
|
Checked the proposals independently. Both are on chain, and both match the v0.5.0 release artifact.
I downloaded @AncungAulia, the rebuild window is 2026-10-31 from 20:50 WIB. |
* docs(#17): the relay host runs main, at 03da644 The host was fast-forwarded from 29d6719 and restarted. The only runtime change is #92's wording; health, config, ready and CORS were checked from outside afterwards. * docs(#17): the relay host runs feat/admob-relay at 3102f64, for AdMob before #100 merges * docs(#17): the relay host runs feat/admob-relay rebased onto main, at 1095ba6 * docs(#17): #107 is on the relay host, at 8097128, before #106's upgrade * docs(#17): the relay host is back on main, at 2ea1e15
Closes #94. Refs #102, #93, #96.
Base is
fix/claim-owner(#103), notmain— these share one upgrade and one 24 h timelock, and #81 took three days of slack that would have let them go separately. Merge #103 first and this retargets itself. @Lin1er, please do not deletefix/claim-owneron merge; deleting a base branch auto-closes its child PR, which has bitten this repo before (#57).It also carries the two changes I asked for on #103
I implemented them here rather than sending them back, because they are two lines each and the clock matters:
ClaimOwnerNotSet, 15) instead of falling back to the borrower.set_claim_ownerhas its own error (ClaimOwnerMalformed, 16) instead of reusingClaimMismatch.Refusing turned out to be a stronger change than I argued for. A
G…address cannot be pinned at all —set_claim_ownertakes0xand 40 hex digits — so there is no longer any way to write the pre-#102 owner shape into the harness by accident. The fixture,setup()andfx()all now run through an app-signed claim, which is the only shape that exists in the wild. That is the actual fix for the class of bug #102 was, not just for the instance.The cost is one extra admin call after each
execute_upgrade, which is the point: a contract that cannot verify says so instead of looking configured.The design, and the one thing that is not where you would look for it
A source selects the template, and the template contains the host. So no argument a caller supplies can make a claim verify against the wrong API — an AdMob claim checked as
AdSenseis rebuilt into a request toadsense.googleapis.com, the identifier differs, and the signature recovers to nobody. Tested both directions.The value order is not in the template.
rebuild_parametersinterleaves N parts with N−1 values positionally, so the order lives inclaim_valuesinlib.rs. AdMob needs the reverse of AdSense's, because the attestor canonicalises the parameters with keys sorted —body, headers, method, responseMatches, responseRedactions, url— so the window (inbody) comes before the publisher id (inurl).pub_id, sy, sm, sd, ey, em, edsy, sm, sd, ey, em, ed, pub_id=, and/beforepub_id\"year\":,\"month\":,\"day\":,/accounts/revenueUsd, dollarsrevenueMicros, microsadmobAdvanceSourceThree places check that ordering without deriving it from each other: this contract,
pin_template.py --self-test(#101), andbe/src/admob/request.test.ts. They can only agree by being right.Micros, and the asymmetry that decides the key name
parse_micros_centstruncates:1239999micros is 123 cents, never 124, so an advance is never sized from more than was attested.The figure's key is per source and sits inside the signed context. Not cosmetic — the two mistakes are not symmetric, and I measured it on the deployed contract rather than reasoning about it:
Micros read as dollars neither overflow nor error. Every advance would silently be the maximum, for any revenue at all, and a reviewer would see plausible numbers. Dollars read as micros truncate to zero cents and refuse. So one direction is loud and the other is silent, which is why they never share a name — and the name is inside the identifier, so it cannot be fixed afterwards.
dollars_and_micros_are_never_interchangeablepins exactly this.Storage, all append-only
ParamsTemplateFor(Source)/ProviderHashFor(Source). AdSense falls back to the pre-AdMob (#90): contract, a revenue source in the template, the nullifier and sizing #94 singleton keys, so neither deployed contract needs re-pinning to keep verifying. Nothing else falls back to anything.AdvanceSource(BytesN<32>) -> Source, absent means AdSense, written only for a source that is not AdSense. Not a field onAdvance: a required field would retype an existing stored value and every advance already recorded would fail to decode, and those entries are debts.ClaimOwner, from fix(#102): verify the attestor's owner against a pinned app id, not the borrower #103.On which — worth recording, because it came up as nervousness about touching
DataKey: variants are encoded on the ledger by name, not by index. The committed snapshots showvec[symbol("Admin")],vec[symbol("ParamsTemplate")]. So a new variant may sit anywhere in the enum and no existing entry moves. Stronger than append-only requires.The nullifier tag, and what it is not
sha256(pub_id ‖ start ‖ end ‖ "admob"), each field length-prefixed. AdSense hashes exactly the bytes it always has — pinned inthe_adsense_nullifier_bytes_did_not_changeagainst a literal derived independently in Python, so it is not the contract agreeing with itself. If that test ever needs updating, advances on chain are orphaned.The asymmetry is forced, not chosen, and
source_tagis the only place it lives.Fixture
make_claim_fixture.pygains the AdMob chain, so CI's--checkcovers it. Its identifier comes out byte-identical to the onebe/src/admob/fixture.test.tsderives in TypeScript:A Python encoder and a TypeScript one agreeing on the canonical parameters, the context and the keccak over them — independently written, never compared until now. That is the property the AdSense fixture exists to give, and the AdMob one now has it too. It is also a signed claim, which
tools/fixtures/admob-claim.jsonis not, so the contract can verify it end to end.The derivation asserts its own split three ways (round trip, structure, arity) before writing anything, so a template split at the wrong occurrence of
"1"or"7"cannot reach the fixture.Checked
cargo test --workspace --all-features: 61 passed (was 51), plus 9 inreclaim-claimcargo fmt --all --checkclean,cargo clippy --workspace --all-targets --all-features -- -D warningscleanstellar contract build --package forepay-advancesucceeds, 39,499 bytescargo check -p reclaim-claim --lib --target wasm32v1-noneclean (stillno_std)make_claim_fixture.py --check,pin_template.py --self-test,secp256k1_probe.pyall passcheck_links.py --no-network docs/interface.md docs/evidence.md README.md: every link resolvessc/wasm-hashes.txtlinux row set toPENDINGfor CI to measureThe eleven new tests, with what each is for:
an_admob_claim_verifies_against_its_own_templatean_admob_claim_cannot_be_checked_against_the_adsense_templatean_adsense_claim_cannot_be_checked_against_the_admob_templatean_unpinned_source_refuses_rather_than_falling_back_to_adsensepinning_admob_leaves_the_adsense_template_untouchedthe_adsense_nullifier_bytes_did_not_changeadmob_and_adsense_do_not_share_a_nullifierpub-idmicros_truncate_to_cents_and_never_round_up.refuseddollars_and_micros_are_never_interchangeablean_advance_with_no_recorded_source_reads_as_adsensean_unpinned_contract_refuses_rather_than_guessing_the_ownerNot done here, deliberately
#94 asked for a test writing an
Advancein the old shape, upgrading, and reading it back. I asked for that on #90 to check the premise before designing around it. It is not a unit test here, because the parallel key meansAdvanceis untouched and a unit test would only restate that. The honest version is on chain: the dev contract holds realAdvanceentries written by the old wasm, and reading one back afterexecute_upgradeis the actual evidence. That read goes indocs/deployments.mdwith the upgrade, and I will not claim the upgrade is verified until it is done.The AdMob template on chain is still #96's, from a real proof via
pin_template.py. Nothing here pins anything.Deploy order, once this and #103 are in
One wasm, one timelock, then four admin calls on production — three of which are easy to forget:
execute_upgradeset_claim_owner 0x6415200c713135e77157e1536d488df4f2bb7d04set_claim_template AdSense …(Pin the AdSense claim template on the deployed advance contract #61) — production'sclaim_template()is stillnullset_claim_template AdMob …(AdMob (#90): pin the AdMob claim template from a real proof #96, needs the real proof)Between 1 and 2 the contract refuses everything, by design. Keep them in one sitting, and read the fee at simulation:
set_claim_ownerandset_claim_templateboth callbump(), and #76's taught us that is rent, not computation — it wanted 21,370 XLM once.Method note: MCP Stellar Raven is disconnected in my session and needs re-authorisation, so the Stellar facts here come from the
stellar-dev:smart-contractsskill and live reads against testnet, not from Raven. Our working agreement names Raven for anything Stellar that gets written down, so I am flagging the substitution rather than leaving it implied.🤖 Generated with Claude Code
https://claude.ai/code/session_01QdNuoJ9e954ojofNVGUezW