One accepted magnet passage is one work unit under the configured sensor policy.
A signature proves which key signed the data, not whether the measurement is physically true.
Ethereum records contract execution and settled work. Video doesn't affect those records.
A compromised measurement host can still supply false data, even with a protected signing key.
A work record says that a wheel-magnet passage was accepted under the configured sensor rules. It doesn't identify an animal, prove the wheel's direction, or establish what caused it to move. “Hamster proof of work” describes these recorded passages, not a way of proving animal identity or securing Ethereum consensus.
A zero-work round proves only that no passage was accepted in it. It does not prove the wheel was observed and idle: when the Pi restarts, it closes every round that elapsed while it was stopped as a zero-work round. Statistics built from settled rounds therefore show the ledger, not continuous observation.
A signature links a record to a signing key. Settlement on Ethereum shows that the contract accepted an authorized batch. Neither step independently checks the physical wheel, so a valid signature and a successful transaction don't remove the need to trust the measurement host and its operators.
Video is independent of measurement. You can see movement while counting is stopped, and a missing feed doesn't mean no work was recorded. Video cannot repair missing sensor records.
The production signing chip protects its key from export, but it signs data supplied by the host. A compromised host can supply false data. Sensor placement, counting rules, host security, and enrollment of the signing key still matter.
| Layer | Evidence it supplies | What it cannot establish |
|---|---|---|
| Pico | Raw sensor readings with identity, sequence, and timing | Accepted work, completed rounds, or signed telemetry |
| Pi | Saved accepted passages and completed rounds | Animal identity, direction, intent, or what caused movement |
| Oracle | Checks on signatures, identity, counter history, and policy | Physical truth or Ethereum settlement |
| Reporter | Signed permission to settle an exact batch | Anything beyond the eligible measurement records |
| Squeekchain SqueekCore contract on Ethereum | Executed round, work-total, and Squeek-block rules | Which animal or physical cause produced a reading |
| Camera and public display | Video and displayed status | Accepted measurements or proof of their cause |
Only the Pi accepts passages and assigns them to rounds. Hosted services check its records; they cannot invent a starting total, reduce cumulative work, or spread an unexplained increase across rounds.
SqueekCore checks signed settlements, not the sensor or Oracle database. Indexers and APIs display records but cannot change Ethereum history.
The Oracle checks the signature before reading the telemetry contents and preserves accepted round-data hashes. It recognizes a retry by its record identity and contents, not by identical signature bytes.
Production signing chips keep telemetry keys non-exportable, and the Oracle checks signatures against the registered public key. Enrollment proves a genuine chip participated, but the chip cannot attest that it holds the telemetry key or that a measurement is true.
SqueekCore rejects reused settlement authorizations and checks the chain, proxy, and implementation named by the signature. These checks prevent misuse of an authorization, not false physical measurements.
A compromised measurement host can send false data to its signing chip. Sensor placement, counting rules, host security, and key enrollment therefore remain trusted.
Oracle administrators and its database provider can affect hosted records, while SqueekCore upgrades depend on trusted governance. SqueekMining checks SqueekCore's expected interface and reward rules; SqueekToken does not independently check work or rounds.
An invalid telemetry signature creates no Oracle receipt or accepted work.
Rejected or quarantined telemetry leaves review records but creates no accepted rounds.
The Pi stops counting missing, conflicting, or uncertain sensor readings rather than guessing passages.
Rounds that elapse while the Pi is stopped are closed as zero-work rounds when it restarts; the ledger cannot tell downtime from an idle wheel.
A video failure neither proves nor disproves a passage and cannot change rounds.
Local checks and code review do not prove that deployed contracts match the reviewed code or that services are operating correctly.
Applies SqueekCore or SqueekMining upgrades authorized by its governing Timelock.
Generates Squeek images and metadata from fixed onchain visual data.
Records physical work and earned block units on Ethereum, with difficulty adapting after active rounds.
Calculates rewards from settled work, holds funded SQK, and pays eligible NFT owners.
The Squeeks ERC-721 contract. Tracks NFT ownership and coordinates minting and merges with SqueekMining.
The SQK ERC-20 contract. Enforces the lifetime supply cap; only SqueekMining can mint SQK.
Queues governance operations and enforces a delay before they can be executed.
Checks that visual data conforms to the required DotGrid format.
When new power starts earning. Minting and merging schedule it for the next round, and a checkpoint applies it.
A reward update that processes settled Squeek blocks, issues their SQK, and applies scheduled power changes.
The Squeek permanently burned in a merge. Its unclaimed rewards move to the survivor, but its image is not combined or kept.
SQK issued as settled Squeek blocks are processed: 5,600 SQK for each completed block, up to the lifetime cap.
Squeekchain's record of accepted wheel-magnet passages.
Combining two eligible same-level Squeeks you own into one higher-level Squeek. One NFT is burned; the survivor keeps both Squeeks' unclaimed rewards.
The completed Squeek blocks a Squeek waits through before it can merge again. It follows the Squeek through transfers.
What a Squeek earns with. Its level sets its maximum power; each Squeek block's SQK is divided across all active power in proportion.
A ten-minute period used to group measured work. The device saves a completed round's work total when measurement remained uninterrupted.
The token each completed Squeek block issues, shared by active power. It has a lifetime supply cap.
An NFT that owns a share of the Squeekchain network. It receives SQK from the hamster's work according to its active power, set by its level and the SQK staked to it.
One billion block units earned from settled work at each round's difficulty. Completed blocks supply SQK under the mining reward rules.
Squeekchain's ecosystem for hamster-powered onchain finance, built on the public work record.
The Squeek you keep in a merge. It gains a level, keeps its ID and image, and receives both Squeeks' unclaimed rewards.
A Squeek's recorded reward balance that hasn't been paid to a wallet. It stays with the Squeek when ownership changes.
The hamster mining device. It records accepted wheel-magnet passages as work.
One wheel-magnet passage that met the device's counting rules.