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
Deploy the front end and capture the screenshots #22
Deliverable 2's required evidence is "live demo link, screenshots." Deploy the creator front end to a public URL, pointed at testnet, reachable with no login.
A 200 is not proof the app is live
Both of our other projects got this wrong in opposite directions:
Sterun:sterun.xyz was reported as live on an HTTP 200. It was a Hostinger parked-domain page. The claim reached a project update and two tickets before it was corrected.
Sterish: the dashboard was recorded as missing for days after it had gone public, because nobody re-checked.
So verify by reading the rendered page — r.jina.ai or Claude Chrome — not from a status code, and not from a tool result that came back thin. An empty or minimal response is a tool limitation, not a fact about the site.
Done when
The public URL is in docs/deployments.md, verified by its rendered content.
Screenshots of each step of the flow are in docs/evidence/, which is what the Chapter Lead ticks Deliverable 2 against.
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.
Scope: instawards/Forepay Instawards SOW.pdf. Timeline assumes 2026-10-09 → 2026-11-08; tell Axel if the real window differs.
The contract changed under the live app 25 minutes ago. The deployed bundle needs one env var and a rebuild.
@Nabil-Aufa@AncungAulia — v0.5.0 is live on production CCQFL2Q66DHFAZU2KPRWNHU4FTZJW75N5XLNXECFFGMW3PROIXJPI2HS as of 2026-10-31 14:21 UTC (8de3c144…116655).
What is needed:NEXT_PUBLIC_CONTRACT_TAKES_SOURCE=1 on the forepay-vue5 Vercel project, and a redeploy. The variable alone does nothing — NEXT_PUBLIC_* is inlined at build time, so an unset flag and a set-but-not-rebuilt flag look identical from the outside. That is the part worth double-checking.
@Nabil-Aufa, you predicted exactly this on #106 on 2026-10-29: request_advance now takes source first, so a bundle built without the flag sends arguments that no longer line up and fails at simulation — for AdSense too, not just AdMob. #104 put the flag in (fe/src/lib/stellar/contract.ts, withSource / advanceArgs), so the code is already deployed; only the build-time value is missing.
It is urgent but not an outage. Production's claim_template() was null before today, so the live app could not complete an advance anyway — nothing that worked yesterday stopped working. What the rebuild unblocks is the AdMob advance @Lin1er's tester is standing by for.
I have no Vercel access and I am not going to guess at what is set there. Post here once the redeploy is out and I will read app.forepay.xyz and confirm it against the contract.
Activity
Docs: front end architecture, README and env names (#19 to #22) (#55)
docs(#22): the relay allows https://app.forepay.xyz (#87)
docs(#22): record the live front end and its screenshots
docs(#22): record the live front end and its screenshots (#89)
Lexirieru commentedon Oct 31, 2026
The contract changed under the live app 25 minutes ago. The deployed bundle needs one env var and a rebuild.
@Nabil-Aufa @AncungAulia — v0.5.0 is live on production
CCQFL2Q66DHFAZU2KPRWNHU4FTZJW75N5XLNXECFFGMW3PROIXJPI2HSas of 2026-10-31 14:21 UTC (8de3c144…116655).What is needed:
NEXT_PUBLIC_CONTRACT_TAKES_SOURCE=1on theforepay-vue5Vercel project, and a redeploy. The variable alone does nothing —NEXT_PUBLIC_*is inlined at build time, so an unset flag and a set-but-not-rebuilt flag look identical from the outside. That is the part worth double-checking.@Nabil-Aufa, you predicted exactly this on #106 on 2026-10-29:
request_advancenow takessourcefirst, so a bundle built without the flag sends arguments that no longer line up and fails at simulation — for AdSense too, not just AdMob. #104 put the flag in (fe/src/lib/stellar/contract.ts,withSource/advanceArgs), so the code is already deployed; only the build-time value is missing.It is urgent but not an outage. Production's
claim_template()wasnullbefore today, so the live app could not complete an advance anyway — nothing that worked yesterday stopped working. What the rebuild unblocks is the AdMob advance @Lin1er's tester is standing by for.I have no Vercel access and I am not going to guess at what is set there. Post here once the redeploy is out and I will read
app.forepay.xyzand confirm it against the contract.Lin1er commentedon Nov 1, 2026
@Lexirieru @Nabil-Aufa @AncungAulia: the rebuild you asked for is live. I checked the deployed bundle at https://app.forepay.xyz on 2026-11-01 at 03:30 UTC:
CONTRACT_TAKES_SOURCEis compiled in astrue, soNEXT_PUBLIC_CONTRACT_TAKES_SOURCE=1was set at build time.CCQFL2Q66DHFAZU2KPRWNHU4FTZJW75N5XLNXECFFGMW3PROIXJPI2HS.As far as the bundle goes, the app now sends
sourcefirst, which is what v0.5.0 expects. The end-to-end check is the first real advance on #102.