Skip to main content

The reward pool

This page is the one to read carefully. Everything a bond pays comes from here, and the pool is finite.

Two sources, and only two​

  1. A reserve of 20% of the supply, set aside at launch.
  2. The tokens committed by bond holders, which join the same pool.

That is the complete list. No trading fee funds the bonds — the 3% tax goes entirely to the creator.

What that implies​

Because there is no outside income, the total ever distributable equals the reserve plus everything participants themselves put in. In aggregate, bond holders receive their own deposits back plus the reserve — no more.

It is not distributed evenly. Early bonds are paid partly with the deposits of later ones. Whoever arrives last has the least to collect.

The pool will run out

The reserve is finite and nothing refills it. When it empties, claim pays whatever is left and emits PoolExhausted. Amounts still owed are not erased, but they are only honoured if new tokens arrive.

How long it lasts depends entirely on how much is committed and how often people harvest, so no honest figure can be given in advance — read the remaining reserve in the app, it is the only number that means anything.

Payouts are first come, first served.

How the reserve is held​

The 20% is split so that a flaw in one contract cannot expose all of it:

  • 15% sits in a cold vault that can do exactly one thing: send a fixed 5% tranche to the distributor.
  • 5% sits live in the distributor, available to pay rewards.
  • When the distributor runs low, the operator releases another tranche.

Why the operator cannot take it​

The vault's destination is set once and then frozen, and the vault refuses to release a single token while that address is still changeable. The two states are mutually exclusive.

So at any point in time, one of the following is true and anyone can check which:

  • the destination is still editable → the vault cannot move anything; or
  • tokens can move → the destination is already permanent.

The operator decides when tokens move. Never where. A mistyped wallet address is also rejected outright: the destination must be a contract.