autonomous AI agent
The Rite
An autonomous AI agent watches the cycle, seals it, gives part of the offerings back to the market and tallies another part to the wallets the Lot selects. The owner funds; the agent counts; the contract checks both. Every number on this page comes from the config of the cycle that is running right now, not from copy.
four acts, every cycle
The Seven Glances
Through the cycle the agent records who holds the token and who trades it. It glances up to seven times, at moments fixed in advance by a secret it sealed a cycle earlier. Each glance is sealed on chain the moment it is taken. Holding for three days out of seven weighs far more than holding for one minute.
The Sealed Cycle
At Sunday 23:59:59 UTC the cycle closes. The Sealed Glances are folded into one final commit and put on chain before any Lot exists. From that moment the list of those counted cannot change.
The Return
A part of the offerings buys the token back on the open market, in twelve acts a cycle at moments no one is told. The Altar shows how many acts are done and how much was taken from the market — never when the next act comes.
The Lot and the Tally
A signature from the public drand beacon, fixed before the cycle closed, becomes the Lot. It selects the Marked from each pool, weighted but without replacement; the list is published, and then the Reliquary sends ETH and the token in one transaction per batch. Reckoning Day, Monday 18:00 UTC.
the division of offerings · cycle 4
Every trade of the token leaves an offering: a creator fee of 1.70% of its volume. This cycle it is divided as Kept · Returned · Tallied:
- 60%keptoperations, infrastructure, the treasury
- 20%returnedthe Return: bought back on the open market, in twelve acts
- 20%talliedthe Tally: given on Monday to the Marked
The division is set in the config of the cycle and announced at least a cycle before it changes. When a push ends and the division goes back to base, that is back to normal — it was the push that was unusual.
the faithful, the movers and the threshold
Two pools, counted apart. The Tally of the cycle is divided between them by the config: 35% to the Faithful, 65% to the Movers. Inside a pool, every one of the Marked receives the same share. A wallet can be in both.
- the Faithful
- Hold at least 165,000 the token at the moment of a glance — above the Threshold. Your weight is your average presence across the glances. Between 25 and 150 wallets are marked, about 5% of everyone above the Threshold.
- the Movers
- Trade at least 0.004 ETH in the cycle, buys and sells together. Between 25 and 200 wallets are marked, about 8% of everyone above the Threshold. Offerings are an action, not a posture.
The Threshold is a token amount and an ETH amount, fixed for the whole cycle in the config. It is chosen from the price when the config is made, and the price does not stand still — so the number you see here is the number that counts, not its value in dollars.
seven glances, not one
One glance would be a target: watch the clock, buy a minute before, sell a minute after. Seven glances at moments fixed by a secret remove the target. Arriving one minute before a glance weighs almost nothing.
The weight of a wallet is its average presence across the glances. A wallet present in six of seven with a steady balance weighs roughly six times the wallet that appeared once. There is no way to be present at the right moment on purpose, because the moments are not known — not to you, and not to anyone who could tell you.
the moments are secret until the cycle ends, then they are verifiable
A cycle before it starts, the agent publishes keccak(nonce, cfgHash) on chain. The nonce stays secret; the glance and Return moments are derived from it, together with a public drand beacon that only appears after that commitment. So the moments cannot be chosen afterwards, and no nonce can be searched for to suit anyone.
When the cycle closes, the nonce and the config are revealed. Anyone can then recompute every moment, every weight and every one of the Marked, and compare them with what happened on chain.
While the cycle runs, this site shows only what has already happened: glances already taken, acts of the Return already done. There is no page, no API and no message that contains a future moment.
what you can verify, and what you have to trust
you can check this yourself
- The glance moments came from the nonce sealed a cycle earlier — recompute them.
- The Sealed Cycle was on chain before the Lot existed.
- The Lot is a real drand round, and the relay serves the same signature to everyone.
- The Marked follow from the Lot and the published weights, deterministically.
- The amounts in the Tally transactions match the published list, wallet by wallet.
- Run the Proof end to end:
pipx run lootbox-verify week N.
you have to trust this
- The offerings are read from the chain by an indexer the operator runs. You can re-index them yourself from the same public data, but the number on this page is the operator's until you do.
- The owner funds the Return budget once a day and funds the Tally on Monday after checking the list, and can veto a list before it is sealed. A sealed list cannot be edited — but the timing of the transfer is a human decision, visible on chain.
- The accumulated funds sit in the owner's treasury, not in the Reliquary. The Reliquary holds only a day's Return budget and the Monday Tally, for a few hours.
- The operator knows the current cycle's moments, because the engine has to execute them. A leak of the hot wallet would leak the moments of the current and next cycle; that is reported, not hidden.
- The moments of the first cycle depend on the hour the token launched.
splitting your holdings across wallets
One wallet, one mark per hand. Splitting shifts the count a little — I measured it and published the measurement. Shares are equal inside a pool and a wallet can be marked only once, so several wallets are several entries instead of one. It is not fought; it is measured, and how much of each cycle went to clusters that look related is published with the cycle.