Build "Squeek Archive", the history layer for Squeekchain. Every existing Squeekchain site shows the present moment; this one reconstructs the past: each Squeek NFT's life story, its merge ancestry, and an arithmetic audit of whether the reported hamster work matches the wheel that supposedly did it. A working prototype has already been validated against live data, so the facts below are measured, not assumed. Follow them exactly.

IDENTITIES. Read contract addresses at runtime from GET https://api.squeekchain.com/v1/economy/state, field "identities". Do NOT use https://docs.squeekchain.com/assets/deployments/sepolia.json: that record is a previous deployment (it names core 0x74665dAe..., while the live core is 0x980b4424c007caf7a1f3670b48c8eaef7ebc3d44) and building against it reads dead contracts. The Squeek NFT collection is identities.genesis, currently 0xcb98349c134ab983da5bfd80527dfe2552bdb70f with 9987 minted.

READING THE CHAIN. Use raw eth_call over JSON-RPC with hand-built calldata; no web3 library. CORS-enabled Sepolia endpoints, try in order with failover: https://ethereum-sepolia-rpc.publicnode.com then https://sepolia.drpc.org (https://rpc.sepolia.org sends no CORS header, do not use it). These four-byte selectors are verified against the live contracts: art() 0x301bd28e, collectionSeed() 0x5752a646, renderer() 0x8ada6b0f, totalSupply() 0x18160ddd, ownerOf(uint256) 0x6352211e, and on the renderer renderSVG(address,bytes32,uint256) 0x4e026d42. Encode each argument as one 32-byte word, left-padded. The renderSVG return is an ABI dynamic string: read the offset word, then the length word at that offset, then that many bytes of UTF-8. Measured result: the genesis collection returns art page 0x0677aCa34747cD8e60f988F75e2f89d5E00Bb27D, seed 0x722cd60a3d3e96a969adea9a7ae78b9b6dad188f4f04a59a26084d887a16d649, renderer 0x50888Ea2469Cc4E619bfcBdc4A7E7d58d4Ddd165, and Squeek #8936 renders as roughly 52 KB of SVG in about 300 ms. Inject that SVG markup directly into the page. Do not proxy it, cache it on a server, convert it to a raster image or fetch it from IPFS: rendering straight from the contract is the point, and the page must say so with the renderer address and the call duration.

THE HISTORY FEED. GET https://api.squeekchain.com/v1/events?limit=100 returns the newest page plus nextCursor; pass it back as &cursor=... to walk backwards. Only two category values are accepted, "all" (the default) and "measurement"; ?category=nft and ?category=account return HTTP 400, and ?type= is rejected too, so filter by type in the client. Walking the whole feed currently takes about 18 pages for roughly 1,800 events reaching back to 2026-10-26. Show a progress count while walking and keep the parsed result in memory for the session.

Event payload fields, taken from live responses, must be used exactly: nft.deposited and nft.withdrawn carry account, collection, tokenId, basePower. nft.merged carries account, collection, survivorTokenId, donorTokenId, level, nextMergeHeight, custody, nftPowerDelta. nft.launch_claimed carries the claim. account.rewards_claimed carries account, recipient, amountBaseUnits and asset{address,symbol,decimals}. account.claim_recipient_set carries account and a nullable recipient. account.sqk_staked, account.sqk_unstaked and account.rewards_staked cover SQK movements. system.settlement_completed carries previousSettledThroughRound, settledThroughRound, activeRoundCount, workAdded, completedBlockCount, cumulativeWork, blockHeight. system.mining_checkpointed carries afterRound, throughRound, completedBlockCount, cumulativeWork, amountBaseUnits and asset - it does NOT have a processedThroughRound field, and assuming one prints an empty round number. measurement.speed_record carries previousRecordMmPerSecond and recordMmPerSecond; measurement.speed_milestone thresholdSpeedMmPerSecond; measurement.distance_milestone thresholdDistanceMm and observedLifetimeDistanceMm; measurement.daily_distance_milestone thresholdDistanceMm, observedDayDistanceMm, utcDate; measurement.distance_streak days, minimumDailyDistanceMm, endingUtcDate. Every event also has occurredAt and source.transactionHash: link each one to https://sepolia.etherscan.io/tx/.

PAGES AND PANELS. One page with a single search box that accepts either a Squeek number (1 to 9987) or a 0x wallet address. For a number: render its art from the chain, list its life story in chronological order from every event whose tokenId, survivorTokenId or donorTokenId matches, and draw its merge ancestry by following survivor to donor recursively, indenting each generation, so a level 4 Squeek shows the three it consumed and what those consumed in turn. For a wallet: list everything that wallet did, with SQK amounts formatted from amountBaseUnits and the 18 decimals in the asset field. Also show the full chain history feed with its event count and the date it reaches back to.

THE AUDIT PANEL, titled "Is the work real?". Poll GET https://api.squeekchain.com/v1/status every 15 seconds and keep the samples. The telemetry field is measurement.speedMmPerSecond; there is no measurement.speed field, and reading the wrong name silently produces NaN. Each row must print the numbers it judged, never a bare colour. Rows: sensor freshness, comparing the age of measurement.observedAt against measurement.staleAfterSeconds. Attestation, naming signer.kind, signer.algorithm, signer.keySlot and the age of signer.lastVerifiedAt. Lifetime work per revolution, computed as cumulativeWorkUnits divided by distanceMm over a rim circumference the visitor can edit, defaulting to 471 mm; on live data this gives 3.015, which rounds to 3, so state the implied magnet count per revolution and flag it CONSISTENT while it stays within 0.1 of a whole number and DRIFTING otherwise. Then, between consecutive samples: distance must never decrease, cumulative work must never decrease, work must not rise while rpmMilli is zero in both samples, and the distance added must not exceed the faster of the two reported speeds multiplied by the elapsed seconds plus a 25 percent margin plus one revolution. If measurement.counterEpoch differs between samples the hardware counter restarted, so discard that delta and say so rather than counting it. Summarise all rows in one header ribbon reading CONSISTENT, CHECK or IMPLAUSIBLE.

CONSTRAINTS. Plain HTML, CSS and vanilla JavaScript; no build step, no dependencies, no analytics, no third-party fonts, no wallet connection, no backend. Light and dark through prefers-color-scheme. Readable at 360 px and at 1920 px. Never blank a panel on a failed request: keep the last known value and show its age. Ship a README naming every endpoint, every selector with its signature, the audit formulas, and the two field-name traps above.