Components and responsibilities

Responsibilities, authority boundaries, and independent failure behavior across Squeekchain components.

TL;DR

Separate parts of the system record and verify work, settle it on Ethereum, issue and distribute $SQK, and display the results.
Video and public displays read from the records that establish work and rewards.
Each component shows missing data as unavailable.

From the wheel to your screen

The device saves wheel-magnet passages that pass its counting rules. Hosted services verify those records and submit eligible work to Ethereum. The website displays measurement data, chain data, and independent video, each updating at its own pace.

System map

Work and rewards

The Oracle receives the WHEELY9000's signed records, the Reporter authorizes verified work, and the relayer submits it to SqueekCore on Ethereum. SqueekMining then issues $SQK and funds SqueekStaking, which streams it to stakers by power.

WHEELY9000 --> Oracle --> Reporter --> Relayer --> SqueekCore
                                                       |
                                                settled blocks
                                                       v
                      SqueekToken --minted SQK--> SqueekMining
                                                       |
                                                all issued SQK
                                                       v
Owner wallet --Squeeks and SQK (deposit, stake)--> SqueekStaking
     ^                                                 |
     +- claims to you or your claim recipient ---------+

After each checkpoint, Mining funds Staking with all newly issued $SQK, and Staking streams it over 20 minutes. Anyone can submit a checkpoint. The arrows show data and fund flows.

Public data and video

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 --------------------------------------+

Both paths are read-only with respect to accepted work and rewards.

Technical detail: component responsibilities

The table shows what each component does and the limit of its authority.

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
Durable Pi storage (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	Sign permission to settle exact work batches	Cannot change the Pi's round records
Relayer	Submit signed transactions and pay gas	Cannot authorize settlement
`SqueekCore` on Ethereum	Record rounds, work, and completed Squeek blocks	Does not mint tokens or calculate rewards
`SqueekMining`	Issue scheduled $SQK for completed Squeek blocks after mining starts and send all of it to `SqueekStaking`	Holds no rewards, owner records, or claims; has its own pause and upgrade permissions
Keeper	Submit checkpoints so `SqueekMining` processes settled rounds	Pays gas only; cannot choose issuance amounts, rounds, or recipients
`SqueekToken`	Mint its fixed premint at deployment, then mint only for the bound `SqueekMining`, within the lifetime supply cap	Does not check physical work
`SqueekStaking`	Hold deposited Squeeks and staked $SQK, track each staker's power, stream funded $SQK, pay claims, and burn exit fees	Holds owners' NFTs, principal, and unpaid rewards; has its own pause and upgrade permissions
`SqueekNFT` (Squeeks)	Record ownership, levels, and merge cooldowns, and carry out merges	Ownership gives no device control; a Squeek adds power only while deposited in `SqueekStaking`
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 WHEELY9000	Cannot affect accepted work or rewards

Rules and boundaries

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.
Measurement records still rely on the host and its operators; signatures identify their source but don't prove the measurement is true.
$SQK's cap is fixed, while Mining's upgradeable code controls issuance within that cap.
Staking holds deposited Squeeks, staked $SQK, and unpaid rewards. Only the admin, acting through the Timelock, can upgrade it.