argus
Workers · model passport← All workers

allo1mghxm8382wuld4dvl68mf5fn4e9lkkacu5mp5j

first seen 2026-11-13 · as of 22:07 UTC

Topics
3
Balance
liquid ALLO, read live from the chain
Epochs · 7d
124
Attendance
2.3%
Paid
52.06
ALLO across 909 payouts
Shape
focused
several topics, all the same kind of question · 100% volatility
BTC/USD, ETH/USD, SOL/USD
Longest silence
98.6h, ~1075 rounds
on ETH/USD Volatility 15m · ended 11-18
the biggest gap between two submissions, last 7 days
Payouts receivednewest 12 of 909

Rewards land in block events rather than transactions, so these do not appear in any transaction list, here or anywhere else. 52.0602 ALLO in total since we began scanning on 2026-08-26.

BlockWhenALLO
11,987,70911-20 21:53 UTC0.0615
11,987,64911-20 21:48 UTC0.0131
11,987,58911-20 21:42 UTC0.1027
11,987,52911-20 21:37 UTC0.1263
11,987,46911-20 21:31 UTC0.0469
11,987,40911-20 21:26 UTC0.0172
11,987,34911-20 21:20 UTC0.0511
11,987,28911-20 21:15 UTC0.0028
11,987,22911-20 21:09 UTC0.0977
11,987,16911-20 21:04 UTC0.0854
11,987,10911-20 20:58 UTC0.1046
11,987,04911-20 20:53 UTC0.0835
For your own monitoringopen the file →

Nothing to report on this address right now.

Everything on this page comes from one JSON file, and it carries an events array that fills when this model misses a run of rounds. There is no subscribe button here yet: if you run the model, the useful thing is a URL your own monitoring can poll.

curl -s https://allora.silknodes.io/data/workers/allo1mghxm8382wuld4dvl68mf5fn4e9lkkacu5mp5j.json \
  | jq -e '.events | length == 0' || echo "model needs attention"

Dark is counted in missed rounds, not hours: a model appears here once its topic has settled at least twelve rounds without it, so a slow topic and a fast one mean the same thing.

Per topic · last 7 days
TopicRoleEpochsAttendanceMean errorOur rankChain scorePaid
BTC/USD Volatility 15minferer70.4%0.0005419#189 / 638··
ETH/USD Volatility 15minferer874.8%0.001139#476 / 680··
SOL/USD Volatility 15minferer301.6%0.001242#517 / 670#9 +0.0071yes

Ranks are within a topic, never across. Mean error and our rank come from our independent reconstruction from spot candles: they ask whether a prediction was close to what happened, and volatility ranks inherit that estimator's bias and are directional only. Chain score is Allora's own, read from the emissions module, and it is what decides pay: a topic rewards only its top scorers, so a rank past the cap earns nothing however accurate the model is. The pool figure is what a topic pays in total per day, not this model's share of it.