Proof bundles & agent logs
Canonical marketing URL for the project: https://growthbase-web.vercel.app. The public purchase API is the live Railway host: https://growthbase-production.up.railway.app.
Submission overview
One-page honest summary of live vs demo vs evidence: docs/SUBMISSION.md.
Canonical payment proof for the demo video
Use this one historical example consistently when you need a reviewer-facing payment proof from the public Railway host.
Transaction hash evidence: 0x436ecfefe0a4fea553e85350ca2d44ee5ee9d2c193d6b4d1264fd66bf66efe6e
Proof bundle: data/proofs/external-purchase-proof-railway-live-funded.latest.json
Explanation path: docs/external-purchase-proof.md
Scope: this proves accepted payment and transaction-hash evidence on the public Railway host. It does not prove successful live artifact delivery under current market conditions.
ReceiptAnchor contract proof
ReceiptAnchor is the optional on-chain trust layer for anchoring receiptHash, policyHash, and artifactHash. It complements the main verify-bundle flow rather than replacing it.
Source contract: contracts/ReceiptAnchor.sol
This deployment has not published a public ReceiptAnchor address yet. The repo is wired to surface it here once Vercel sets NEXT_PUBLIC_RECEIPT_ANCHOR_ADDRESS.
Agent logs (append-only)
Additional proof JSON (repo paths)
Open on GitHub for machine-readable request/response evidence. Labels describe what each bundle represents — they are not interchangeable as "live success" proofs.
- data/proofs/external-purchase-proof-railway-live-funded.latest.json — Canonical historical payment proof on the public Railway host (accepted payment + transaction-hash evidence)
- data/proofs/external-purchase-proof-railway-live-submission-2026-03-23.latest.json — Current live submission-labeled proof (pre-charge 503 fail-closed outcome)
- data/proofs/external-purchase-proof-public-fixture-postdeploy-2026-03-23.latest.json — Historical fixture-host success bundle for offline-repeatable comparison (not a public production host)