Sorphera - contract hardening, integration tests and deployment preparation

Tagline: Weekly ETH & NFT lottery ball jackpots. Powered by FWA.

Repo: Sorphera repository

IMD launch: 961

Parent job: a3707b79-51b8-4d04-9e32-3e786d91c1d9

Reviewed commit: b06997d42012b7ad7ffe943b3acdd816b2092c4e

Continue from the current repo head; check changes since the reviewed commit. Keep this contracts-only: implement contracts, tests, deployment scripts, docs and integration artifacts. Target Ethereum mainnet, testing FWA on a pinned mainnet fork. Do not broadcast mainnet transactions, spend real funds or enable public sales.

PRESERVE PRODUCT RULES

Two separate weekly lottery-ball games:

ETH Jackpot: settle FWA acquisitions to ETH. Winning tickets split distributable ETH equally; no winners means rollover.

NFT Jackpot: take the NFTs. No winners means inventory rollover; one winning ticket receives all inventory. Multiple winning tickets trigger a separate verifiable random tie-break selecting ONE winning ticket for all inventory.

Keep three distinct unordered main numbers 1-20 plus bonus 1-5, existing ticket ownership, 0.005 ETH default tickets and 10% operator fee / 90% acquisition defaults.

Total ticket sales remain uncapped; transaction batches and processing remain bounded.

Company builder rewards stay separate from purchaser reward entitlements, prizes and refunds.

Preserve custody/refund/claim/rollover guarantees and economics; explain necessary changes.

Use verifiable randomness and expose draw/tie-break events for future animations. No website work.

FIX THE FAILED DEPLOYMENT REHEARSAL

Launch was parked after 6/7 gates passed. protected_invariants failed with "application constructor failed" in setUp(), gas 0. Sorphera checks for code at the factory and VRF coordinator; the factory checks router code.

Capture the failing contract, resolved constructor arguments, chain state and revert trace. Check dependency order, $owner/$contract substitutions and coordinator code. Match IMD compiler/optimizer/EVM settings. Local tests passed 64/64 on Forge 1.7.1; IMD reported 1.8.3. Investigate, rather than assume, the cause.

Fix the cause without weakening safeguards or mocking production dependencies. If IMD's private harness is unavailable, supply a public reproduction and exact platform follow-up. Never claim its gate passed without evidence.

VERIFY MAINNET INTEGRATION AND NETWORK CONFIGURATION

Primary references:

FWA deployments

Builder revenue

FWA testing

Builder examples

Chainlink networks

Published mainnet pool: 0x958C41181182e76F221331b2755b77D9e1426A98

Published mainnet rewards: 0xA54b44C7a894AA19C49734A753D01f9B8C5f6516

Reviewed Sepolia lacked builder attribution. Mainnet source/ABI includes it; an explorer read reported builderRewardBps() = 1500. Reverify compatibility and current settings; the rate can change.

Record chain/block, bytecode, ABIs and pool/rewards/token/randomness bindings. Verify the transfer helper, Permit2, distributor/deposit permissions and liquidity. Prove router builder attribution as immediate acquire caller, with round vaults retaining purchaser rights.

Replace the Sepolia-only restriction with validated network configuration: chain ID, dependencies, coordinator, key hash and subscription. Fail closed on wrong chains/incompatible dependencies. Separate production and test-only simulation.

Read live quotes, VRF charges, gas-price assumptions, slippage limits and settlement windows. Do not hardcode 0.06 ETH pulls or source defaults.

TEST COMPLETE LIFECYCLES AND FAILURE PATHS

Run existing tests and add pinned mainnet-fork tests using deployed FWA code unchanged. Record commands/RPC requirements; disclose fork-only balances, impersonation and oracle simulation.

Cover both games: tickets -> FWA requests -> allocation -> ETH/NFT settlement -> draw -> finalization -> claims. Verify real builder allowance accounting, eligible acquisition/settlement credits, reward purchase, transfer-helper queueing and next-block treasury delivery. Test purchaser rewards separately.

Required coverage:

ETH prize splits, duplicate winning tickets, no-winner rollover and rounding dust.

NFT single winner, multiwinner tie-break, rollover and bounded delivery/recovery.

Failed/expired acquisitions, immediate/deferred refunds, stale/slipping quotes, unavailable inventory, delayed allocation and missed settlement windows.

Cross-round isolation, conservation of funds/inventory, locked liabilities, correct fee accounting and prevention of operator withdrawal of prizes/refunds/purchaser rewards.

Number validation/canonical ordering, quick-pick/draw sampling bias, bonus independence, cutoff boundaries and immutable terms for sold tickets.

Unauthorized, duplicate, delayed and out-of-order VRF callbacks; request-to-round binding and separate tie-break requests.

Reentrancy, reverting recipients, NFT receiver failures, unauthorized administration, paused paths and changed dependency/helper permissions.

Large ticket/inventory counts: demonstrate bounded gas and progress without processing every ticket in one transaction.

Forks receive no automatic live Chainlink callbacks. Document test-only fulfillment for FWA and lottery VRF. Separately test lottery VRF on Sepolia with controlled FWA test dependencies and the real coordinator if test funding/access exists. Otherwise deliver scripts, exact prerequisites and a NOT RUN result. Never label simulation as live VRF verification.

Review lockups from permanent VRF failure, pending acquisitions and missed settlement windows. Document fair recovery options; prohibit discretionary rerolls, winner replacement and post-sale rule changes.

PREPARE DEPLOYMENT AND OPERATIONS

Deliver build/deployment rehearsals, owner/treasury inputs, dependency order, factory binding, router setup, company VRF subscription/consumer setup and funding/preflight checks. Sales default to disabled.

Separate mainnet/Sepolia/fork artifacts. Check current IMD rules: a continuation may update code without redeploying or retargeting the parked Sepolia launch. Document the supported mainnet route and any new launch/platform action required.

Provide keeper/operations scripts and a runbook for acquisitions, allocation processing, timely settlement, closing rounds, randomness requests, finalization and reward claims. Specify permissions, funding, monitoring and safe retries.

DELIVER EVIDENCE

Commit fixes/tests to the existing project and summarize the changes. Update dependency records, test reports, manifests, ABIs, events and configuration schemas. Leave undeployed addresses null and label simulated/example artifacts.

Report:

Root cause, fix, files changed and protected-gate status.

Exact commands and passed/failed/skipped test counts.

Mainnet fork block/dependencies and real vs simulated oracle coverage.

Gas/scaling results and supported deployment procedure.

Remaining blockers, each with the exact external input/action required.

Complete all unblocked work. Distinguish verified, unrun and blocked steps. State readiness for independent security review/deployment rehearsal; passing tests is not an audit or approval for public sales.