The Hamster MinerLink to this section
TL;DRLink to this section
- The Hamster Miner is a physical mining device that records accepted wheel-magnet passages as work.
- A sensor detects the magnet, and a small computer saves the accepted measurements.
- Independent cameras provide video; a working feed doesn't mean work is being counted, or vice versa.
What is the device?Link to this section
The Hamster Miner is a physical hamster mining device built around a wheel, a wheel-mounted magnet, and a sensor. When the magnet passes the sensor, the device checks the reading and saves an accepted passage as one work unit. It's different from a virtual Miner NFT: owning an NFT doesn't give you control of the device.
A Raspberry Pi Pico carries the sensor readings to a Raspberry Pi, which applies the counting rules and saves the results. Independent cameras let you watch the device, but video doesn't measure work, fill gaps in the sensor record, or authorize settlement.
How it worksLink to this section
The wheel-mounted magnet produces active and inactive readings from the Hall sensor. The Pico passes those observations to the Pi, which checks them and saves accepted passages in ten-minute rounds. The production signing chip signs saved measurement records for delivery to the Oracle.
If a camera loses its feed while the sensor and measurement computer remain healthy, counting and round closure continue. The reverse is also possible: video can show a moving wheel while a measurement fault prevents new work from being counted.
Technical detail: hardware responsibilitiesLink to this section
| Part | Function | Boundary |
|---|---|---|
| Wheel and magnet | Trigger active/inactive sensor readings | Do not identify what moved the wheel or in which direction |
| Hall sensor and Pico | Send readings with their order and timing | Do not count accepted work, close rounds, or sign records |
| Pi measurement service | Check counting rules and save passages and completed rounds | Cannot replace uncertain measurements with guesses |
| Durable SQLite state | Save work, round history, and records awaiting delivery | Must be preserved, unlike a replaceable display cache |
| Production signing chip | Sign records with a key that cannot be exported | Cannot verify the data supplied by its host |
| Cameras | Supply independent video feeds | Cannot access the measurement database or authorize settlement |
NoIR and OV CSI cameras and an Arducam UVC camera run as separate services. Public playback reveals viewing information, not camera controls or publishing credentials.
Rules and boundariesLink to this section
- One accepted passage is one work unit. It does not prove that an animal completed a wheel revolution.
- At startup, the Pi must observe an inactive sensor before counting a new passage.
- Camera or playback failure alone does not stop counting, round closure, or measurement delivery.
- Captured audio must not leave the device. If a provider requires silent audio, it is not microphone audio.
- The Hamster Miner does not hold settlement signer or relayer keys.
- Software updates must preserve saved measurement history; an update does not justify resetting the counter.
- Video cannot fill gaps in the sensor record.
Separate reporting historiesLink to this section
The Pi keeps a physical counter and separate reporting histories. Each reporting history has its own installation identity, counter epoch, start time, and delivery state, so its total isn't the physical counter's lifetime total. Comparisons need to use the matching reporting history.