{
  "notes": "EPISODE 4 (2026-10-27). Read lighter-stage-history/lighter; all 7 batches settled, 22/30 items used, 0 failed, 0 refused, no requester notes, nothing running. DECISION: finish=true, no new batches. Every point of the goal has a sourced answer or an honest NOT FOUND, and the last open question (Lighter's stage label history) is now closed. The next step writes the deliverable from the 22 results listed in `read` plus these notes and the episode 2-3 fact sheets.\n\nLIGHTER HISTORY RESOLVED (lighter-stage-history/lighter): Lighter was Stage 0 (Appchain) at the pre-window baseline (l2beat/l2beat commit 25765a1, 2026-04-24; Wayback 2026-04-22) and stayed Stage 0 through 2026-10-27 (Wayback 05-12, 09-14, 10-12; live page; main b3346aa). Shared evaluator stage.ts unchanged across the window; stage-0 items can never lower the label, only add a message. Two states within Stage 0: until commit abff564 (2026-05-23) the page carried an under-review notice ('The requirement for available node software is under review', rollupNodeSourceAvailable='UnderReview'); after it the requirement is met (rollupNodeLink elliottech/lighter-prover) and the notice is gone. Commit 307f5c3 (2026-05-19) flipped Stage 1 item verifierContractsReproducible false->true and proposerFailure CANNOT_WITHDRAW->USE_ESCAPE_HATCH_ZK, and removed the desert-mode display.warning. Neither commit changed the badge. Never NotApplicable/UnderReview, no 0->1, no pending downgrade; the 2026-08-17 countdown could not affect a Stage 0 project. Deploy dates of the two changes NOT FOUND (no archive capture between 05-12 and 09-14). Labels calculated by reading evaluator source, not by running it; they agree with every observed badge.\n\nSTAGE CHANGES IN WINDOW (2026-04-27..2026-10-27), final: NONE of the five rollups (Base, Arbitrum One, OP Mainnet, Mantle, Lighter) changed its numbered L2BEAT stage; Robinhood Chain (excluded, Other) did not either. Report instead, dated and cited: Mantle reclassified Optimium->ZK Rollup 2026-04-16 (before window); L2BEAT framework Stage 1 challenge period 7d->5d 2026-04-30 (forum post, inside window, no chain promoted by it); Lighter checklist improvements 05-19/05-23 (inside window, badge unchanged); Base Azul multi-proof mainnet 2026-05-28 and Beryl 2026-06-25 (inside window, Stage 1 before and after); OP Mainnet game type 0->8 2026-06-30 and ->9 SUPER_CANNON_KONA 2026-09-24 (Stage 1 before and after); Robinhood config first added 2026-02-17 / full config 2026-07-03, mainnet 2026-07-01.\n\nWRITE-UP PLAN (for the deliverable episode). Structure: (A) Snapshot and selection: date 2026-10-27 ~14:20 UTC, source https://l2beat.com/api/scaling/summary and https://l2beat.com/layer2s/summary (scope/l2beat-list), the '>500M USD TVS AND L2BEAT category Optimistic/ZK Rollup' rule, the five qualifying chains with exact USD figures from scope/l2beat-list (Base 15,058,117,632; Arbitrum One 9,832,005,632; OP Mainnet 1,717,252,352; Mantle 1,301,224,448; Lighter 1,057,181,312), the >500M non-rollups named and excluded with L2BEAT's reason (Hyperliquid 6,569,551,872 Other/L3/no proofs; Polygon PoS 3,831,951,104 Other/no proofs; Robinhood Chain 2,294,226,432 Other/'Closed proofs' fewer than 5 external challengers), and the next rollup below cutoff (Starknet 371,292,320; World, Ink, Linea figures in scope result). State that TVS moves daily and the page shows 3 significant digits. (B) One profile per rollup with the six numbered points, every fact followed by its URL, L2BEAT page first (https://l2beat.com/layer2s/projects/{base,arbitrum,op-mainnet,mantle,lighter}) then project docs/code; use l2beat/<chain> for points 1-5, docs/<chain> as corroboration and for contradictions, release/<chain> for point 6; for Lighter use lighter-verbatim/lighter over l2beat/lighter wherever they differ (guardians are EOA 2/3, not zero; risk strings are 'Validity proofs (SN)', 'Onchain (SD)', exit window None, 'Force via L1', 'Use escape hatch'). (C) Ranking most to least trust-minimized with reasons: 1 Arbitrum One, 2 OP Mainnet, 3 Base, 4 Lighter, 5 Mantle. Method: L2BEAT stage first, then live proof system and whether proving/challenging is permissionless, forced inclusion, exit window, upgrade control (council threshold and delay), DA. Reasons: Arbitrum has permissionless BoLD (3,600 ETH bond), a 10d regular exit window with DAO + 9/12 council and emergency instant path; OP Mainnet permissionless Cannon/Kona (0.08 ETH bond) but exit window None with 2/2 Foundation 5/7 + Council 10/13 instant upgrades and a liveness module; Base open ZK challenge path but TEE proposer allowlisted, exit None, 2/2 Coordinator 3/6 + Council 8/11 instant; Lighter Stage 0, permissioned validity proving (validators set by 3/5 multisig), upgrades 21d notice cuttable to 0 by 4/7, but a 14d-expiry L1 priority queue and a permissionless desert-mode exit from settled state; Mantle Stage 0, permissioned OP Succinct/SP1 proving with 12h delay, proof-less fallback switchable by Engineering 3/7, 6/14 Security multisig instant upgrades, 'Cannot withdraw' on proposer failure. Say the ranking is the author's analysis, that stages measure decentralization not security, and that the three Stage 1 chains are close. (D) Stage changes section as above. (E) Robinhood Chain as a separate sidebar, never in the ranking: API/filter 'Stage 0' vs page 'not even a Stage 0 project' vs row NotApplicable; permissioned BoLD with 2 validators; Sequencer failure 'No mechanism' because the filterer can defeat forceInclusion; 7/8 instant and 6/8 + 7d; Nitro v3.12.2. (F) Source disagreements and NOT FOUNDs, all kept: Arbitrum forceInclusion ~24h (docs, 7200 blocks) vs 1d (L2BEAT) and operator attribution Offchain Labs vs Foundation; Mantle 12h (L2BEAT/config) vs 24h (docs guide), council threshold NOT FOUND in docs, stale docs still say EigenDA and pin v1.5.4; OP blog 14d non-emergency policy unverified on chain; Base docs do not establish allowlist bypass at game creation; Lighter node/sequencer release NOT FOUND (closed source not proven), lighter-prover has no tags/releases (last commit 2026-10-12), gnark-plonky2-verifier v0.1.0 2026-10-08 is a component; Lighter deploy dates of May changes NOT FOUND; release/arbitrum's cached v3.12.1 superseded by release/robinhood's v3.12.2 (same repo, read later with API confirmation, published 2026-10-27T13:27:32Z).\n\nRELEASES (point 6, final): Base base/base v1.5.1 2026-10-22T17:47:20Z (node + proof services; newer RC tags are not stable). Arbitrum One OffchainLabs/nitro v3.12.2 2026-10-27T13:27:32Z (docs still pin v3.12.1). OP Mainnet op-node/v1.19.11 and op-reth/v2.6.1 2026-10-22, op-challenger/v1.11.0 2026-10-26, kona-client/v1.9.0 2026-10-23. Mantle mantle-v2 v1.6.3 2026-09-21T03:38:19Z, op-geth v1.6.3 2026-09-21T03:25:25Z, prover mantle-xyz/op-succinct mantle-v1.6.1 2026-09-16T12:28:26Z (mainnet docs pin v1.5.4). Lighter main node NOT FOUND; see above. Robinhood Nitro v3.12.2 (docs pin v3.11.2, status notice recommends v3.12.2). Say explicitly that newest release != version deployed on mainnet.\n\nIf a judge returns findings: a repair batch should be one chain, one point, citing the exact URL to re-read; 8 items remain. No further batches are otherwise needed.",
  "spawn": [],
  "read": [
    "scope/l2beat-list",
    "l2beat/base",
    "l2beat/arbitrum",
    "l2beat/optimism",
    "l2beat/mantle",
    "l2beat/lighter",
    "l2beat/robinhood",
    "docs/base",
    "docs/arbitrum",
    "docs/optimism",
    "docs/mantle",
    "docs/lighter",
    "docs/robinhood",
    "release/base",
    "release/arbitrum",
    "release/optimism",
    "release/mantle",
    "release/lighter",
    "release/robinhood",
    "lighter-verbatim/lighter",
    "robinhood-stage/robinhood",
    "lighter-stage-history/lighter"
  ],
  "cancel": [],
  "finish": true
}