Seasons, rates and claiming

A season is the window in which points are earned. Claiming is when they become tokens — and the rate between the two is the number your community will judge you on.

📷 Screenshot placeholder — the project's Conversion card during a live season: ceiling, implied rate, points so far and the payout share control.

What a season is

A season is the window in which farmers earn points on your project. It has a start, an optional end, and a life of its own: Starting soon until the start passes, In season while farming runs, and Ended once it closes. Behind the scenes an ended season goes through two more steps — the conversion rate is frozen and claiming opens — before it is finally closed.

Points earned in a season belong to that season. When farmers claim, they convert that season's points at that season's rate, so a project can run a second season without mixing the two.

Scheduling

You set the schedule when you create the project: a start date and a duration in hours. Leave the start out and the season is in season straight away; leave the duration out and it has no automatic end.

While the season is Starting soon you can change anything — nobody has entered yet.
Once it is In season, the only change allowed is to extend the end date. Shortening it is refused, because the published closing date is what your farmers signed up to.
You can end a season early from the project. It is recorded as an early close, with your reason, and the season is then finalised exactly as a natural close would be.

A community campaign's season additionally waits for its prize to be funded before it opens, however far past its start date it is.

The rate: ceiling, pool and points

Two numbers you set at launch decide what a point is worth:

the point rate — how many tokens one point converts to at most. This is the ceiling: a point is never worth more than this.
the airdrop allocation — the tokens set aside for farmers, funded into the project's airdrop pool when the token deploys.

While the season is live the console shows the implied rate: the smaller of the ceiling and the pool divided by the points earned so far. As long as the ceiling covers everyone, the rate simply is the ceiling and the season is under-farmed. Only once the points earned would draw more than the pool does the rate dilute below the ceiling — every farmer is scaled by the same factor — and the season reads as over-farmed. Nobody can drain the pool by claiming first.

📷 Screenshot placeholder — the Conversion card showing an over-farmed season with the diluted implied rate.

You can commit to paying less than the full suggested rate — a payout share below 100% — from the same card. It can only be set while the season is Starting soon or In season. That timing is deliberate: the share is applied when the rate freezes, so every farmer converts at one published number and an early claimer never gets a different rate from a late one.

Freezing and claiming

When the season ends, the platform freezes the rate — the smaller of the ceiling and pool ÷ total points, multiplied by your payout share — snapshots the total points, records the rate in the audit trail and opens claiming. Claims then convert at that frozen rate: a farmer with a balance of points receives points × rate in tokens, rounded down. In an under-farmed season the leftover tokens stay in the pool.

For a farmer to claim, the project token must be on-chain and they must have a wallet linked to receive the tokens. If a claiming commission is attached to the project, the farmer first pays its fee on-chain, and the platform verifies that payment before converting anything; an optional project commission adds a second charge in the same way. Each charge is then split — the platform's share, the commission pool for the farmer's upline, and the rest to your revenue. Token rewards on those commissions are always zero, because a claim is the very thing the points were for.

The tokens leave the airdrop wallet through the platform's payout queue. Claims on a suspended organisation's projects are blocked.

What you see under Claims

Claims lists every conversion, across all your projects or one at a time, with three totals for the current view — the count, the tokens paid and the points spent — and a filter by status:

Queued — the conversion is booked and the payout is waiting to be sent.
Broadcasting — the transaction has been sent and is awaiting confirmation.
Confirmed — paid; the transaction hash is on the row.
Failed — the payout could not be confirmed within the platform's retry limit and is parked for the platform team.

Open a claim to see the farmer's wallet, the payout wallet, the transaction, and the conversion facts: points spent, tokens, the effective rate, chain, the farmer's email and when it was created. You can search by farmer or payout wallet.

📷 Screenshot placeholder — Claims, a confirmed claim's detail with the conversion facts.