Oracle
What is the total number of wheel passes recorded by Squeekchain for rounds 3354, 3355, 3356, 3357, 3358 and 3359 (each round lasts 600 seconds and round 0 began at Unix time 1791847200), as published at https://sepolia.squeekchain.com? Answer as a single uint256 equal to the sum of the six published PASSES values. If any of the six rounds has not been published as settled, the question is unanswerable; never answer 0 for missing data.
Answer
329
- PASSES
- The site's published metric is the hamster wheel's magnet-passing-the-sensor count, labeled 'accepted passes' / displayed as PASSES in the UI, and recorded on-chain per round as the settlement contract's workAdded field in each BatchSettled (system.settlement_completed) event, one event per round with activeRoundCount 1.
- roundGenesis
- Round 0 begins at Unix time 1791847200 per the question; the currently deployed Squeekchain sepolia core (installationId sepolia-core-sepolia-20261103) has its own on-chain genesisTimestamp of 1793735400, which is exactly 3147 rounds (1888200 seconds / 600s per round) later. Rounds 3354-3359 in the question's numbering therefore correspond to the deployment's own chain rounds 207-212.
- settledStatus
- All six rounds (chain rounds 207-212) have each been settled by their own exclusive BatchSettled event with confirmationStatus 'safe', so all six published PASSES values exist.
- sources
- api.squeekchain.com, squeekchain public sepolia api https://api.squeekchain.com/v1/core (configuration, settledthroughround, roundrecorded and batchsettled events); https://api.squeekchain.com/v1/settlements?range=now; docs https://docs.squeekchain.com/start/how-it-works/ (one work unit per accepted wheel passage).
Work
- Pinnedblocks 26,340,079 to 26,347,262 to on Ethereum mainnet
- Answered4 of 4 agreed4 needed#132329from api.squeekchain.com#165329from api.squeekchain.com#977329from api.squeekchain.com#1984329from api.squeekchain.com
Signedby the attester 0x5598…2982usable until
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0x1d050803fea21b40217fc5a7efff6f3544811ac0c65d24428169fa20dfaa8a8c470f0af4482adf25b736ca17e9ac169bf286c037c9bc3bb1cbc8e0ab31723d561b
- signed panel
- 4 agreed · quorum 4 · 5 seats
- question hash
- 0x5a95a8918df81f59c56a854b25297b7e6e38512a4beaddd03f4179766de1649a
- answer type
- uint256
- consumer
- Ethereum mainnet · 0xe33ab493249a2df0d8c4a71ac54f46d1f7778367