Demo Weather Over Under

Guardrails

• Avoid mixing old number-pick contest UX with yes/no market UX.
• If no pool/bets yet, display neutral 50/50.
• Keep oracle errors actionable in UI (refresh oracle, strict mode notes).
• Do not warn on initial page load that a market is missing if the backend has not actually failed to create/find it yet.
• Prefer the button label Place Bet; temporary statuses can replace the button label during the in-flight action but should reset cleanly after success/failure.
• Do not let demo daily-market projections drift away from the actual on-chain market identity.
• Do not leave resolved/claim UI dependent on stale daily rows; once a market rolls off the active window it still needs to appear in resolved history via hosted wallet metadata.

Build Recommendations

• Local success is not enough. Hosted startup, sync order, and stale seeded daily-market files caused real regressions.
• Do not create extra hosted services to compensate for stale UI reconciliation. Fix the source-of-truth mismatch first.
• Fresh zkApp rollouts need explicit bootstrap:
  • initialize the zkApp
  • create the rolling markets
  • sync local state
  • only then let the UI claim a date is active or missing
• If the market feed and daily-market feed disagree, trust the real on-chain market feed first and repair the projection layer second.
• For hosted operation:
  • market renders quickly from shared state
  • oracle runs background lifecycle work
  • tx-prover handles bet/claim proving
  • browser wallet signs
• If the tx-prover throws a raw Field.assertEquals(): ... != ... after a few bets/claims, suspect stale witnesses from a root update rather than a broken wallet flow; refresh state, rebuild context, and retry once.
• Past-date resolution must retry on the next oracle cycle if a market missed its first nightly window; do not make users wait another full day.
• If Resolved Markets empties after a real resolve/claim, suspect sync regression before blaming the UI. The demo should preserve monotonic resolved/claimed state rather than allowing an incomplete event snapshot to erase it.
• In the resolved-markets card:
  • keep progress on the claim button itself (Generating tx proof, Sign Wallet Tx, Finalizing claim...)
  • avoid long raw market identifiers unless they are needed for debugging
  • do not stretch the claim button full-width when a compact action affordance reads better