Repository navigation
Description
The map for the Forepay Instawards build. Scope comes from instawards/Forepay Instawards SOW.pdf. 29 issues, four milestones, four owners.
Milestones
| Milestone | Window | Gate |
|---|---|---|
| M1 — Feasibility | Oct 9–16 | One real AdSense revenue proof verified on testnet |
| M2 — Advance contract | Oct 17–23 | A valid proof sizes and disburses USDC on testnet |
| M3 — Relay and front end | Oct 24–30 | A creator completes the flow in a browser |
| M4 — Demo and negative cases | Oct 31 – Nov 8 | Full pipeline + three negative cases, video ≤3 min, evidence pack |
Owners
| Who | Issues | What |
|---|---|---|
| @Lexirieru | #2 #3 #6 #8–#15 #18 #23–#27 | Advance contract, digest canonicalisation, evidence |
| @Lin1er | #1 #4 #5 #16 #17 #18 | AdSense provider, proof relay, backend, CI |
| @AncungAulia | #19 #20 #21 #22 | Creator front end |
| @Nabil-Aufa | #7 #28 #29 | Footage, demo video, Chapter Lead |
Four things I checked that are not in the SOW
Verified against live sources on 2026-10-09, not taken from the proposal text.
1. The Reclaim verifier is real and live ✅ — testnet CA3EMXR6JOOTNP44T3OAJFMMMGKRRETDJKBLZP2RU3SIY4SDFAH54DU5, mainnet CD4M2KHW3ESOV3RUT7KCTC6BX37PIL2Z3BEK47IA74KIMFIFUI3JJDMO. Testnet instance created 2025-12-21. The SOW's central feasibility claim holds.
2. verify_proof does far less than the SOW sentence implies
verify_proof(message_digest: BytesN<32>, signature: BytesN<64>, recovery_id: u32)It recovers a secp256k1 signer and checks it is a witness in the current epoch. It does not parse a claim, build the digest, or extract the revenue figure or bound address. We must canonicalise the claim into exactly the bytes the witness signed. That is the sharpest edge in the project, it is unnamed in the SOW, and it is #3 — scheduled before the gate on purpose.
3. The example repo the SOW names is a 404 zkfetch-stellar-example does not exist. Use reclaimprotocol/reclaim-stellar-example (pushed 2026-09-11). See #4.
4. Testnet is protocol 29, not 27 soroban-sdk = "29". See #1.
Also confirmed: USDC testnet SAC CBIELTK6YBZJU5UP2WWQEUCYKLPU6AUNZ2BQ4WWFEIE3USCIHMXQDAMA = USDC-GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5. A SAC transfer to a G… address fails without a USDC trustline — covered in #12 and #19.
Explicitly out of scope — SOW section 4.1
No issues exist for these, so nobody builds them by accident:
| Excluded | Why |
|---|---|
| Real underwriting, credit risk, default or recovery | The durable business, not a 30-day deliverable |
| Licensing, KYC, AML, mainnet funds | Consumer lending is regulated; testnet only |
| Blend integration | Permissioned-pool dependency and audit surface; funding backend comes later |
| Revenue sources beyond AdSense | Each provider is its own build |
| Third-party audit, production hosting, attestor SLAs | Budget is development and testing only |
The scaffolded landing-page/ is not an Instawards deliverable and has no issue. Say if you want one and it will be added labelled out-of-sow.
Open questions for @Lexirieru
- The 30-day clock. The SOW suggested 2026-08-14; acceptance is now. Milestones are dated 2026-10-09 → 2026-11-08. Confirm, or give the real window and every milestone shifts.
- @Nabil-Aufa's email — the SOW lists
nabilaufa2005@gmail.com; Sterun and Sterish usesharkzneverending@gmail.com. Same person? - Nabil's load is light until Week 4, because the SOW gives him no landing page or design deliverable. He has footage from Week 1 (Capture footage as each milestone lands #7) so the video is not scrambled at the end, the video (Demo video, 3 minutes or less #28), and Chapter Lead coordination (Final demo with the Chapter Lead, and the submission #29). No scope was invented to fill the column — say if you want more.
The one that matters most
#5 is the make-or-break feasibility gate, due 16 October. Everything downstream assumes it. If it does not pass, @Nabil-Aufa tells the Chapter Lead in Week 1 — not Week 4.
Activity
Nabil-Aufa commentedon Oct 10, 2026
Answers to the open questions
AncungAulia commentedon Oct 15, 2026
Ownership change, agreed between Ancung and Nabil (2026-10-15).
out-of-sow)The "Owner" line and assignee on #19 to #22 are updated. Nothing else about those issues changed: same branches, same scope, same M3 window (24 to 30 October).
Handoff for Nabil: every screen and state for #19 to #21 is designed in
docs/design/forepay.pen, merged in #52. Readdocs/design/brief.mdfirst.Worth watching: #22 deploy lands at the end of M3, right before #28 (video) and #29 (Chapter Lead) in M4.
🤖 Generated with Claude Code
Lexirieru commentedon Oct 15, 2026
Role swap recorded, and one consequence worth a decision
@AncungAulia and @Nabil-Aufa have swapped: Nabil takes the creator front end, Ancung takes the landing page (#54, correctly labelled
out-of-sowwith its own guardrail that it must not pull time from M3 or M4).The swap itself is clean. The load it leaves is not, and it is a PM call rather than mine.
Where the work sits now
Why that is a risk rather than just uneven
Deliverable 2's evidence is "live demo link, screenshots" — that is #22, and it depends on #19 → #20 → #21. All four are now one person's.
Deliverable 3's video (#28) and the Chapter Lead demo (#29) are the same person's.
So one person is the single point of failure for two of the three deliverables, with M3 due 30 October and M3 currently 3/8.
Meanwhile the person who just designed those exact screens — #52, with every state and failure named — has moved off the critical path to a page that is explicitly not a deliverable.
What I would do
Split the front end rather than hand over all four. @AncungAulia wrote the design brief for #19–#21 and knows the states better than anyone; keeping one or two of them with her costs nothing in ramp-up and removes the single point of failure. #54 stays hers and stays last.
Not reassigning anything myself — @Lexirieru, your team and your call. Flagging it now rather than on 29 October.
Unaffected by this
M4's contract side is done: #23 #24 #25 #26 closed, with the harness at 7/7 GREEN and real USDC moving. #27 is the evidence pack and is mine. The front end is the only thing between us and Deliverable 2.
Nabil-Aufa commentedon Oct 16, 2026
@Lexirieru, the creator front end status (#19, #20, #21), and what only you can unblock.
Ready for review, stacked: merge in this order
Each PR passed a strict review against the pen file and the brief (Playwright at 1440 and 390, plus real Chrome). Every commit typechecks on its own, and CI is green. All of this front-end work is still testnet-unproven past onboarding: #20 and #21 run on a Reclaim mock, API fixtures and a stubbed RPC in e2e.
What blocks testnet, on your side
set_claim_templateonCCQFL2…I2HS. Until it is set, every proof is refused with10 TemplateNotSet, so 2b, 2c and 2d cannot happen with a real wallet. It needs the first real AdSense proof (FEASIBILITY GATE: one real AdSense revenue proof verified on testnet #5).Open items
stellar/rs-soroban-envatfced8a124103, not through Raven. The MCP was not available in our sessions. Can someone with Raven confirm them (working agreement 3)?adsense.readonlytoken from the OAuth Playground, and no password is shared.Lin1er commentedon Oct 20, 2026
@Lexirieru @Nabil-Aufa backend status (@Lin1er), 2026-10-20.
Ready for review, in this order
/advancesand/transactions, verified live. This is the last open item in M2, which is due 23 Oct.POST /proofsandGET /proofs/:id, stacked on #16 /advances and /transactions, from Horizon and the contract's own record #66.proveRevenueseam.Under the working agreement, if verified work hasn't had an ACC within two days, I merge it and say so in the PR. For #66 that point is about 21–22 Oct.
Blocked
READYAdSense account (#5)Lin1er commentedon Oct 20, 2026
@Lexirieru @Nabil-Aufa @AncungAulia I opened three issues for the blockers, so each one has an owner:
extractedParameters). Waiting on @Lexirieru to take it, or to OK me opening the PR.READYAdSense account. Unassigned; it needs a volunteer. If you have an approved AdSense account, or know someone who does, comment there.Lin1er commentedon Oct 25, 2026
For the risk list, from #93 (@Lexirieru's note there):
Per-creator exposure is 2× the cap per window once AdMob lands (#94). The AdMob nullifier is tagged with its source, so one
pub-id can take an AdSense advance and an AdMob advance for the same window. That is intended: website and in-app ad revenue are different money. It does mean the limit per creator per window is 2 × 100 USDC, not 100 USDC. Nothing changes on testnet. It becomes a real limit question past this grant. Post-SOW,out-of-sow.