Skip to content

Components and responsibilitiesLink to this section

TL;DRLink to this section

  • Separate components count work, check records, settle on Ethereum, fund rewards, and display results.
  • Video and public displays are separate from the records that establish work and rewards.
  • Missing data stays unavailable; another component must not replace it with zero or a guess.

From the wheel to your screenLink to this section

The sensor detects wheel-magnet passages, and the device saves those that pass its counting rules. Hosted services check the saved records and submit eligible work to Ethereum. The website brings together measurement data, chain records, and independent video, but those sources don't all update at the same time.

Each component below has one part of that job. Displaying a record doesn't give the website or a data service permission to change it.

System mapLink to this section

Work and rewardsLink to this section

Signed records go from the Hamster Miner to the Oracle. The Reporter authorizes checked work, and the Relayer submits it to Core on Ethereum.

Hamster Miner --> Oracle --> Reporter --> Relayer --> Core
                                                        |
                          +------- settled work --------+
                          v
     NFT --ownership--> Mining <--funded SQK-- Token
                          |
                     claim payout
                          v
                     Owner wallet

Core, Mining, Token, and the NFT collection are on Ethereum. Mining reads settled work and NFT ownership, requests SQK from Token, and holds it until owners claim. The arrows show the records and funds each component uses, not automatic callbacks.

Public data and videoLink to this section

The website displays verified measurements and confirmed chain data through the public API. Video arrives through a separate playback path.

Oracle --verified records--------------------+
                                             |
                                             v
Ethereum --> Indexer --confirmed data--> Public API --> Website
                                                           ^
                                                           |
Cameras --> Playback --------------------------------------+

Neither the display path nor the video path can change accepted work or rewards.

Technical detail: component responsibilitiesLink to this section

The table separates who stores a record, who can authorize a change, and who only displays it.

Component Responsibility Authority or limit
Wheel and Hall sensor Produce magnetic readings Cannot prove identity or direction
Pico bridge Send raw readings with their order and timing Cannot count accepted work or sign records
Pi measurement service Count accepted passages, assign them to rounds, and sign records Applies the measurement rules
Pi SQLite Save accepted work, completed rounds, and records awaiting delivery Stores the original measurement history
Oracle and its database Check signed records, approve eligible rounds, and track settlement Cannot invent or repair measured work
Reporter signer Sign permission to settle exact work batches Cannot change the Pi's round records
Gas relayer Submit signed transactions and pay gas Cannot authorize settlement
Core on Ethereum Record rounds, work, and completed Squeek blocks Does not mint tokens or calculate rewards
Mining Calculate rewards, hold funded SQK, and pay claims Has its own rules and upgrade permissions
Token Limit minting to Mining and enforce the lifetime supply cap Does not check physical work
Miner NFT collection Record ownership and NFT properties Ownership gives no device control
Indexer Build chain views after enough confirmations Cannot sign telemetry or settlements
Public API Check and serve public data Cannot replace measurements or chain records
Public web interface Display data and help owners submit wallet actions Browser estimates are not settled facts
Cameras and playback Show the Hamster Miner Cannot affect accepted work or rewards

The API reads measurement and pending work from the Oracle, and confirmed chain data from the indexer. Presenting them together does not make them the same stage.

Mining uses settled Core history through the separate reward funding and claim path. Core itself does not mint SQK.

Video does not affect work acceptance, settlement, or rewards. Public playback information allows viewing, not camera control or access to measurement credentials.

Rules and boundariesLink to this section

  • The Pi sends signed records to the Oracle; they do not share database write access.
  • Oracle API and settlement services have different permissions. Neither can change the database schema.
  • The Pi and public API do not hold settlement private keys.
  • The indexer reads one configured deployment and waits for confirmations.
  • Display outages do not stop otherwise healthy measurement, telemetry delivery, or settlement.
  • A compromised measurement host can supply false records. Signatures do not remove trust in the host and its operators.
  • Token enforces a cap and restricts minting to Mining, but does not check Mining's reward rules. Mining code and its upgrade administrators remain trusted.

ExampleLink to this section

Illustrative outage: the indexer stops answering while the Pi, Oracle, and Reporter remain healthy. Public chain data becomes unavailable, but measurement delivery and settlement continue.

After recovery, the indexer rebuilds its view from chain events. It does not create work or execute missing settlements.