{
  "notes": "EPISODE 3 — snapshot 2026-10-27. Read all 21 results/schema. Six batches settled; no failures, refusals, requester notes or running work. 21/30 items used; episode 3/6. Spawn one Lighter history check (22 committed, 8 left); finish=false. Other work is ready for synthesis; no broad reruns.\n\nWHY ONE MORE ITEM: lighter-verbatim/lighter resolves current risks but finds stage-input changes May 19 and May 23. Its 'no numbered promotion' conclusion relies on Stage 1 remaining false; that does not distinguish earlier below-Stage-0, Stage 0 under review, or Stage 0. It checked lighter.ts, not the historical shared evaluator/baseline. Resolve before repeating 'no changes'. Episode 4: read lighter-stage-history/lighter then finish when the label is established or the limit documented. A bounded NOT FOUND is acceptable; do not repeat unavailable lookups. Preserve 21 existing results plus new one (22 <=30). Cancel nothing; wake on batch settlement or 60 minutes.\n\nSCOPE AND SNAPSHOT: scope/l2beat-list is the selection authority, API read 2026-10-27 14:20:19–14:22:30 UTC. Use its single TVS observation, not differing HTML/project-page refreshes. Strict >USD500M and L2BEAT rollup category selects FIVE: Base Chain $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. First three Stage 1 optimistic rollups; last two Stage 0 ZK rollups (Lighter Appchain). Source https://l2beat.com/api/scaling/summary and https://l2beat.com/layer2s/summary. Exclude Other: Hyperliquid $6,569,551,872, Polygon PoS $3,831,951,104, Robinhood $2,294,226,432. Explain exclusions; Robinhood may have a separate sidebar, never rank it as a qualifying rollup. Next rollup Starknet $371,292,320; others below cutoff in scope result. Six months means 2026-04-27 through snapshot, not calendar H1/H2.\n\nRESULT MAP: l2beat/{base,arbitrum,optimism,mantle,lighter,robinhood} covers points 1–5/history; docs/<same> corroborates from project sources; release/<same> covers versions/dates. lighter-verbatim/lighter supersedes the earlier Lighter paraphrases/guardian conflict; robinhood-stage/robinhood corrects earlier badge/listing summaries. Cite each fact using URLs in the results, L2BEAT first then project docs/code. Canonical pages: https://l2beat.com/layer2s/projects/{base,arbitrum,op-mainnet,mantle,lighter,robinhood}.\n\nCURRENT PROFILES:\nBASE: Stage 1; Stage 2 blocked by <30d exit and council actions beyond onchain bugs. Live optimistic single-round fraud proofs using ZK ('Fraud proofs (1R, ZK)'), Azul TEE+SP1. TEE proposing allowlisted; ZK challenges open. Page says Self propose and docs describe a permissionless ZK-only path, although docs worker did not establish allowlist bypass at game creation. Do not label all proving permissioned or call Base a validity rollup. Exit None. 2/2 upgrader = Coinbase Coordinator 3/6 plus Council 8/11; combined entities 9/12, no delay. Ethereum blobs/calldata; single sequencer, portal deposits force inclusion within 12h. Current software base/base (base-consensus/base-reth-node and proof services), replacing base/node/upstream clients. Stable v1.5.1 published 2026-10-22T17:47:20Z; newer RC tags are not stable releases.\n\nARBITRUM ONE: Stage 1, same Stage 2 blockers. Live permissionless interactive BoLD, 3,600 ETH assertion bond. Risk-panel exit 10d regular / None emergency. DAO and Council 9/12; regular route 8d L2 + 6d8h relay + 3d L1, emergency immediate. Preserve conflicting timing prose elsewhere in L2BEAT; full delay is not exit window. Ethereum blobs/calldata. Centralized sequencer; Delayed Inbox then forceInclusion up to 1d, buffered down to 30m. Project operator attribution differs (Offchain Labs/Foundation). Nitro newest v3.12.2, 2026-10-27T13:27:32Z: https://github.com/OffchainLabs/nitro/releases/tag/v3.12.2. release/robinhood's fresh HTML+API supersedes cached release/arbitrum v3.12.1 for BOTH chains. Arbitrum docs still pin v3.12.1.\n\nOP MAINNET: Stage 1, same blockers; live permissionless interactive Cannon/Kona fraud proofs, 0.08 ETH proposal bond. Current type 9 SUPER_CANNON_KONA; permissioned fallback is a privileged contingency. Exit None; 2/2 Foundation 5/7 plus Council 10/13, instant upgrades. Blog's 14d policy is not an enforced guarantee. Council liveness module can transfer control to Foundation below eight members; retain if comparing governance. Ethereum blobs/calldata, centralized sequencer, 12h portal forced inclusion. ethereum-optimism/optimism releases: op-node/v1.19.11 and op-reth/v2.6.1 both 2026-10-22; op-challenger/v1.11.0 2026-10-26; kona-client/v1.9.0 2026-10-23. Latest software != deployed prestate.\n\nMANTLE: Stage 0: Stage 1 principle, uncensorable withdrawals and >=7d exit unmet; prover/program reproduction met. Live permissioned OP Succinct/SP1 validity, 12h execution delay. Engineering 3/7 can enable proof-less fallback/delete roots; Security 6/14 instant core upgrades; no separate council established; SP1 gateway 2/3 affects safety/liveness. Exit None. Ethereum blobs/calldata now, not EigenDA. L2BEAT reclassification April 16 vs project Arsia encoding April 22, both pre-window. Centralized sequencer; portal inclusion 12h in L2BEAT/config vs 24h guide; proposer failure Cannot withdraw despite inclusion. mantle-v2 v1.6.3 published 2026-09-21T03:38:19Z; Mantle op-geth v1.6.3 same date; mantle-xyz/op-succinct mantle-v1.6.1 2026-09-16T12:28:26Z. Mainnet docs still pin v1.5.4; release != deployment.\n\nLIGHTER: current labels Validity proofs (SN), Onchain (SD), Exit None, Force via L1, Use escape hatch. Stage 0 Appchain, five Stage 0 requirements met; Stage 1 blocked by principle, censorable withdrawals, <7d exit and council setup. Approved validators alone advance batches/proofs; public source != permissionless submission. Governor Multisig 2 = 3/5, 21d notice; Council Multisig = 4/7 can zero delay, reportedly all upgrades fast-tracked. Emergency/Pause Guardians are EOA 2/3, not zero; pauses cannot block desert mode. Ethereum state-diff blobs. Centralized operators; L1 priority request, 14d expiry, anyone activates desert mode and proves exit from settled state (not guaranteed execution of a censored trade). L2BEAT reproduced public desert circuit/snapshot and roll-forward. Public node/sequencer release NOT FOUND; failed search does not prove closed source. lighter-prover has source but no tags/releases; Oct 12 commit is not a release. Component verifier v0.1.0 Oct 8 is not a main prover release.\n\nROBINHOOD: Other: fewer than five external challengers, live permissioned BoLD (two). API/filter says Stage 0, project headline 'not even a Stage 0 project', header/row data NotApplicable; proof decentralization fails, node source under review. Report discrepancy. New history first addition Feb 17 differs from old July 3 full-config addition; addedAt July 1 is not first-listing evidence. Censorship bypass not guaranteed because filterer can defeat forceInclusion. Emergency 7/8 instant, ordinary 6/8 with 7d delay. No more work on this excluded chain.\n\nSYNTHESIS: distinguish upgrade exit window, withdrawal/challenge period and inclusion delay. Keep source disagreements and NOT FOUNDs; stages measure decentralization, not overall security. Ranking is author analysis: likely Arbitrum first for delayed regular governance/open validation; OP/Base close, both open proof routes and instant joint upgrades. Do not rank solely by raw council fractions or TEE allowlist. Lighter above Mantle for independent escape despite both Stage 0. Explain weights, privileged overrides, bonding costs and uncertainty. No numbered stage change found for Base/Arbitrum/OP/Mantle in checked histories; Lighter pending reconstruction. May 19 escape/verifier improvement and May 23 node review change are not automatically promotions; April 30 framework challenge-period update is not itself a chain promotion.",
  "spawn": [
    {
      "name": "lighter-stage-history",
      "mode": "research",
      "brief": "Determine only whether {{name}}'s L2BEAT stage designation changed between 2026-04-27 and the 2026-10-27 snapshot. This is a historical-label audit, not a fresh profile. Use public L2BEAT pages and l2beat/l2beat code/history; project source only if needed to corroborate a dated event. Start with https://l2beat.com/layer2s/projects/{{slug}}#stage and packages/config/src/projects/{{slug}}/{{slug}}.ts in https://github.com/l2beat/l2beat.\n\nPrior result found 30 file commits in the window and these potentially relevant edits: 995eebbdd8d1f4c660341c19a27cbde34be98b24 (May 6: getStage -> getRollupStage); 307f5c3dfdab6a4f88448861a0bb75f0043b762b (May 19: verifierContractsReproducible false -> true and proposer failure -> ZK escape hatch); abff564c9d5cf273d1708b3509cfd10eb11a791e (May 23: rollupNodeSourceAvailable UnderReview -> true). Current headline is Stage 0 Appchain. Stage 1 requirements remaining false does NOT by itself establish the earlier Stage 0 designation.\n\nFind the last pre-window baseline and inspect stage inputs plus the exact shared stage evaluator, applicable countdowns and display logic at that revision and around these edits. Check inherited changes capable of changing this chain's designation, including possible temporary downgrades. Establish whether UnderReview changed only a warning or the actual label; distinguish below-Stage-0/NotApplicable, Stage 0 under review, Stage 0, and numerical 0/1/2 transitions. Never infer a stage from commit titles, current helper code applied historically, or absence of a literal stage field edit.\n\nReturn Markdown with: (1) bounded UTC observation date/window and sources/method, baseline commit and coverage; (2) chronological table of relevant checkpoints with UTC commit date, before/after inputs, computed or explicitly published designation, warning, and pinned links/line references; (3) a direct answer identifying every evidenced transition, or a carefully scoped no-change finding, and whether May 19/23 were only checklist improvements; (4) any missing evidence and exact limits. Cite each fact to its page/commit; distinguish calculated labels from observed historical website badges and code dates from public publication dates. If historical logic cannot establish the label, say NOT FOUND and why. Keep this one-chain audit under one hour; do not re-run software release, TVS, governance or ranking work.",
      "items": [
        {
          "key": "lighter",
          "vars": {
            "name": "Lighter",
            "slug": "lighter"
          }
        }
      ],
      "output": {
        "format": "markdown",
        "maxBytes": 20000
      },
      "merge": {
        "groupSize": 2,
        "brief": "Preserve the single-chain stage timeline, pinned citations, distinction between computed and observed labels, and explicit evidence limits without inventing a stage."
      }
    }
  ],
  "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": [],
  "wake": {
    "batches": [
      "lighter-stage-history"
    ],
    "afterMinutes": 60
  },
  "finish": false
}