QA: yieldomega.com pre-launch site-readiness checks (Arena v2, MegaETH 4326) #358

Closed
opened 2026-06-30 19:07:18 +00:00 by Brouie · 1 comment
Brouie commented 2026-06-30 19:07:18 +00:00 (Migrated from gitlab.com)

Frontend/site-readiness pass on the live production dapp in prep for launch -- the site-layer counterpart to the contract-state checklist in #357. The contracts are deployed and wired, but the arena isn't started yet (arenaStart 0), so the point here is to make sure yieldomega.com is correct and ready for the moment startArena() fires.

Two layers: the site/data checks I can run without a browser (re-runnable), and the browser walkthrough that has to be done by hand on launch day. I've already run the data layer -- results below the checklist.

Endpoints under test

  • Site: https://yieldomega.com
  • Indexer: https://indexer.yieldomega.com (status at /v1/status)
  • RPC: the site uses public MegaETH RPCs (mainnet.megaeth.com/rpc + drpc/globalstake fallbacks), not a yieldomega-hosted RPC

Site / data layer (no browser, re-runnable)

  • apex yieldomega.com serves 200 with a valid TLS cert and the right title/meta (not a parked/coming-soon page)
  • www.yieldomega.com redirects to apex with a valid cert (see flag below -- currently broken)
  • indexer.yieldomega.com/v1/status healthy: database_connected + ingestion_alive true, max_indexed_block tracking the chain head, schema version current
  • bundled contract addresses match the #357 registry (TimeArena, PodiumVaults, ReferralRegistry, PlayCred)
  • buy router + DOUB resolve from the on-chain getters (TimeArena.timeArenaBuyRouter() / doub()) -- authoritative, no stale hardcode
  • prod build guard intact: no VITE_E2E_MOCK_WALLET / mock connector shipped in the bundle (#327)
  • chain config: 4326 primary + MegaETH mainnet RPC, no testnet/local default leaking as the prod chain

Browser walkthrough (laptop, launch day -- live prod site, no tunnel needed)

  • pre-launch state: with the arena not started, the site shows a sane state (countdown / "not started", no blank screen or crash)
  • wallet connect (injected / Rabby) and network is 4326; prompts to switch if wrong chain
  • buy flow end to end: ETH, stable, and CL8Y paths via the buy router; approval -> buy; CHARM credited
  • agent card: indexed-block pill + live data; hero timer renders; podiums populate from the live indexer
  • recent buys / leaderboard populate from the indexer
  • referral: register a code + use one (DOUB burn) works
  • console is clean (no error spam), layout holds on mobile, basic a11y (labels/focus) intact
  • after startArena(): timer/phase flip live and the buy flow is open

What I've already confirmed (site / data layer)

  • apex yieldomega.com -> 200, valid Let's Encrypt cert, title "Yield Omega" with the MegaETH / Time Arena / DOUB meta. Good.
  • indexer healthy: database_connected:true, ingestion_alive:true, max_indexed_block keeping up with the chain head, schema 2.20.0.
  • bundle hardcodes TimeArena / PodiumVaults / ReferralRegistry / PlayCred and they match #357. Buy router + DOUB aren't hardcoded on purpose -- the frontend treats the on-chain timeArenaBuyRouter() / doub() as authoritative and resolves them at runtime, and those are wired right, so no rebuild needed when the router landed.
  • no mock-wallet / E2E connector in the prod bundle -- the #327 guard is holding. The 31337 / localhost / anvil strings in the bundle are benign (viem's bundled chain list + local-dev fallback constants); the prod primary is clearly 4326 + mainnet.megaeth.com/rpc.

Flag for launch

www.yieldomega.com is broken: it serves a TRAEFIK DEFAULT CERT (self-signed) and returns HTTP 503. Anyone typing www. gets a cert warning then a dead page. Apex is fine. Needs a www -> apex redirect with a real cert at the edge before we go public.

@PlasticDigits this one's infra (Traefik/edge), not app code -- can you sort the www cert + redirect before launch? Everything else on the site/data layer is green; the browser walkthrough items I'll run on the laptop against the live site on launch day.

Frontend/site-readiness pass on the live production dapp in prep for launch -- the site-layer counterpart to the contract-state checklist in #357. The contracts are deployed and wired, but the arena isn't started yet (`arenaStart` 0), so the point here is to make sure yieldomega.com is correct and ready for the moment `startArena()` fires. Two layers: the site/data checks I can run without a browser (re-runnable), and the browser walkthrough that has to be done by hand on launch day. I've already run the data layer -- results below the checklist. ## Endpoints under test - Site: `https://yieldomega.com` - Indexer: `https://indexer.yieldomega.com` (status at `/v1/status`) - RPC: the site uses public MegaETH RPCs (`mainnet.megaeth.com/rpc` + drpc/globalstake fallbacks), not a yieldomega-hosted RPC ## Site / data layer (no browser, re-runnable) - [ ] apex `yieldomega.com` serves 200 with a valid TLS cert and the right title/meta (not a parked/coming-soon page) - [ ] `www.yieldomega.com` redirects to apex with a valid cert (see flag below -- currently broken) - [ ] `indexer.yieldomega.com/v1/status` healthy: `database_connected` + `ingestion_alive` true, `max_indexed_block` tracking the chain head, schema version current - [ ] bundled contract addresses match the #357 registry (TimeArena, PodiumVaults, ReferralRegistry, PlayCred) - [ ] buy router + DOUB resolve from the on-chain getters (`TimeArena.timeArenaBuyRouter()` / `doub()`) -- authoritative, no stale hardcode - [ ] prod build guard intact: no `VITE_E2E_MOCK_WALLET` / mock connector shipped in the bundle (#327) - [ ] chain config: 4326 primary + MegaETH mainnet RPC, no testnet/local default leaking as the prod chain ## Browser walkthrough (laptop, launch day -- live prod site, no tunnel needed) - [ ] pre-launch state: with the arena not started, the site shows a sane state (countdown / "not started", no blank screen or crash) - [ ] wallet connect (injected / Rabby) and network is 4326; prompts to switch if wrong chain - [ ] buy flow end to end: ETH, stable, and CL8Y paths via the buy router; approval -> buy; CHARM credited - [ ] agent card: indexed-block pill + live data; hero timer renders; podiums populate from the live indexer - [ ] recent buys / leaderboard populate from the indexer - [ ] referral: register a code + use one (DOUB burn) works - [ ] console is clean (no error spam), layout holds on mobile, basic a11y (labels/focus) intact - [ ] after `startArena()`: timer/phase flip live and the buy flow is open ## What I've already confirmed (site / data layer) - apex `yieldomega.com` -> 200, valid Let's Encrypt cert, title "Yield Omega" with the MegaETH / Time Arena / DOUB meta. Good. - indexer healthy: `database_connected:true, ingestion_alive:true`, `max_indexed_block` keeping up with the chain head, schema 2.20.0. - bundle hardcodes TimeArena / PodiumVaults / ReferralRegistry / PlayCred and they match #357. Buy router + DOUB aren't hardcoded on purpose -- the frontend treats the on-chain `timeArenaBuyRouter()` / `doub()` as authoritative and resolves them at runtime, and those are wired right, so no rebuild needed when the router landed. - no mock-wallet / E2E connector in the prod bundle -- the #327 guard is holding. The `31337` / `localhost` / `anvil` strings in the bundle are benign (viem's bundled chain list + local-dev fallback constants); the prod primary is clearly 4326 + `mainnet.megaeth.com/rpc`. ## Flag for launch `www.yieldomega.com` is broken: it serves a `TRAEFIK DEFAULT CERT` (self-signed) and returns HTTP 503. Anyone typing `www.` gets a cert warning then a dead page. Apex is fine. Needs a `www` -> apex redirect with a real cert at the edge before we go public. @PlasticDigits this one's infra (Traefik/edge), not app code -- can you sort the `www` cert + redirect before launch? Everything else on the site/data layer is green; the browser walkthrough items I'll run on the laptop against the live site on launch day.
PlasticDigits commented 2026-06-30 22:32:57 +00:00 (Migrated from gitlab.com)

Ill investigate the www issue

Ill investigate the www issue
PlasticDigits (Migrated from gitlab.com) closed this issue 2026-07-07 03:54:24 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
code/yieldomega#358
No description provided.