E2E Pipeline Testing

End-to-end testing of the LightChallenge pipeline — from challenge creation through LightChain v2 worker judgment to on-chain payout.

Test scripts

Run:

npx tsx scripts/demoChallengeFullLifecycle.ts

Requires webapp/.env.local with: PRIVATE_KEY, DATABASE_URL, LCAI_WORKER_PK, CHALLENGEPAY_LIGHTCHAIN_ATTESTOR_ADDRESS, NEXT_PUBLIC_CHALLENGEPAY_ADDR. A funded wallet on chain 8200 with ~0.15 LCAI is enough for one run.

What the full lifecycle test covers

Nothing is simulated — every step talks to chain 8200, the LightChain v2 gateway, and a real Postgres database. Total runtime: ~90s, mostly waiting for proofDeadlineTs.

Phase details

Phase 1: Create challenge

ChallengePay.createChallenge({
  kind: 0,                                  // Solo
  currency: 0,                              // Native LCAI
  stakeAmount: parseEther("0.001"),
  startTs: now + 60,
  duration: 60,                             // 1 min for the test
  proofDeadlineTs: startTs + duration + 60, // 60s grace
  verifier: CHALLENGEPAY_LIGHTCHAIN_ATTESTOR_ADDRESS,
  ...
})

The creator’s stake is deposited into the Treasury bucket. c.payoutsDone is false; status = Active.

Phase 6: LightChain v2 judging

judgeChallengeViaLightchain performs the SIWE → gateway → relay round trip and returns:

{
  passed: boolean,
  rawResponse: string,         // decrypted verdict JSON
  jobId: bigint,
  worker: `0x${string}`,
  responseHash: `0x${string}`,
  ciphertextHash: `0x${string}`,
  txs: { jobCompleted: `0x${string}` },  // on-chain audit trail
}

The on-chain JobCompleted event from JobRegistry is the public audit trail — anyone can verify our attestation against the worker’s signed event.

Phase 7: Attest

ChallengePayLightchainAttestor.attest(
  challengeId, subject, jobId, jobCompletedTx,
  responseHash, ciphertextHash, worker, true
);

One tx. Idempotent — re-attesting the same (challengeId, subject) reverts with AlreadyAttested.

Phase 8: Submit proof

ChallengePay.submitProofFor(challengeId, subject, abiEncodedProof)
  → calls attestor.verify(challengeId, subject, proof)
  → reads attestation row → returns true
  → c.winner[subject] = true
  → c.winnersPool += contrib
  → c.winnersCount += 1

If verify() returns false (no attestation, attestation says passed=false, or proof bytes don’t match the attestation’s hashes), submitProofFor does NOT mark the participant as winner.

Phase 10-11: Finalize + auto-distribute

After proofDeadlineTs passes:

• finalize(id) sets c.status = Finalized, c.outcome = Success (since winnersPool > 0)
• _snapshotAndBook books the per-winner bonus, protocol fee, creator fee
• autoDistribute(id, [subject], []) pushes the Treasury allowance to the participant’s wallet

If winnersPool == 0 (no one passed): outcome = Fail, the entire distributable goes to the protocol multi-sig. See incident #13 for the recovery pattern.

What is real

There’s no simulation layer in v2 — workers run real LLM compute and emit signed JobCompleted events on chain. The only thing the script “fakes” is the iOS / webapp UX — it inserts evidence directly into the DB instead of going through POST /api/aivm/intake.

Smaller demos

For unit-level testing without spending a full 0.15 LCAI per run:

# Test gateway + relay only (no on-chain writes)
npx tsx scripts/demoLightchainJudge.ts
 
# Test gateway + relay + attestor (one on-chain attest tx)
npx tsx scripts/demoChallengeLeanE2E.ts

Both write to the testnet but skip ChallengePay challenge creation, so they’re cheaper.

Contract test suite

npx hardhat test

Covers ChallengePay, ChallengePayLightchainAttestor, Treasury, MultiSigWallet, EventChallengeRouter, ChallengeAchievement, both fitness + gaming evaluators, and the lifecycle resolver (test/lifecycle.test.ts — pins the incident #13 UI fix).