Tremor
A coin that grows only when a quake affects people.
When the USGS reports a magnitude 6 or larger earthquake that it expects to affect people, and three of five fixed bots agree, Tremor creates a small, capped amount of new supply for a fixed relief list. Nobody votes, there is no admin, and every rule is written into the contract.
Listening…
The seismogram replays real events from the committed USGS catalog. It is an animation, not a live sensor.
How it works
Three steps, all enforced by the contract. Nothing on this page is needed for any of them to happen.
Magnitude 6 or more, and the USGS's own estimate of impact (its PAGER alert level) at yellow or higher. Remote or low-impact quakes never count.
Five bots read the official record on their own. A quake counts only when three attest exactly the same thing. Coins give no say.
A small amount of new TREM is split between five fixed relief accounts, inside weekly and monthly caps. Holders can also give their own coins to the same five accounts, and a reserve tops each gift up.
Honest limits: this is a testnet prototype with no value. Trust sits in the five bots, here all run by one entrant on one server. See how to check every claim yourself.
Try it yourself simulation
Play with the whole mechanism in your browser: tell the contract about a quake, watch five bots decide, and see the coins appear. No wallet, nothing to install, and nothing that can be offline.
Live on NEAR testnet
This is the real contract, read straight from the chain. –
New quake coins are capped for any 7 days and any 30 days, so nobody can be diluted past a fixed amount. These meters show how much of each allowance is used.
Supply only ever grows, and only when a confirmed quake mints for the relief list. Gifts and the donation match move existing coins and create none.
Every quake the contract knows about
Which of the five bots have attested it, whether it counted, and a check against the USGS record made by this page in your browser.
Real quakes the bots have not reported yet
USGS events of magnitude 6 or more, with expected impact of yellow or higher, that the contract has not seen yet. The bots pick these up by themselves once they are old enough.
The rules, fixed at launch
Read straight from the contract. There is no owner and no method that changes any of these.
Proof there is no admin
–
Access keys on the contract account, read live. The demo keeps one key until the build is final; at the very end every key is deleted and this reads 0. Run make verify-onchain to also check the deployed code has no owner, admin or upgrade method.
1Get coins
2Give to the relief list
Five fixed accounts, set at launch and never changed. Every gift and every quake mint is split equally between them. On testnet they are stand-ins: nothing real is donated.
3Tell the contract about a quake
Givers board
Any holder can send their own coins to the relief list. It creates no new coins and gives no say in what counts; the contract only keeps the total each account has given.
The evidence
Do not trust this page. Everything here comes from committed data and code you can run yourself.
Sixty days of real earthquakes
Every dot is a USGS event of magnitude 5 or more in the committed window. Press replay: each M6+ sends out waves and shakes the map; orange dots are the ones that count (USGS expects at least yellow impact), and the supply responds to those, using the chosen parameters from the simulation.
We simulated it before choosing the numbers
Loading…
Full simulation results
Watch the bots decide
Nobody votes and coins give no say. Five fixed bots check the official record on their own, and a quake counts only when three of them attest exactly the same thing. Here is a recording of a real run on testnet, including what would happen if bots disagreed or turned bad.
How to check me
Run these yourself. Each one is a command in the repository.
git clone https://github.com/samuel025/tremor.git && cd tremor
make test # Python reference and golden vectors
make conformance # Rust contract vs Python on random scenarios
make sim # the simulation scenarios on real data
make replay # recompute the chain log offline
make verify-onchain # read the live contract and compare