From trading fee to dividend

DIVIDENDS charges a fee on every trade and pays that income out to its holders as ETH. This page walks through the whole process: where the fee comes from, when it is claimed, who qualifies, how each share is worked out, how the payments go out, and how to check every step on chain.

The numbers that matter

Documented defaults; the live values load with the treasury.

1. Fee income

Every DIVIDENDS trade pays a fee: 6% on a buy and 6% on a sell. The fee is part of the launch itself, not something the treasury adds, so it applies to every venue the token trades on.

• On the bonding curve, before the launch graduates, the fee accrues on the curve contract.
• In the Uniswap v4 pool, after graduation, the fee is charged by the launch hook and accrues there.

In both cases the fee is credited to the launch’s creator fee recipient, which is the treasury wallet. Accrued fees are periodically swept into the pons fee escrow, where they become claimable. The treasury sweeps them itself whenever doing so would carry the escrow over the minimum claim; a sweep that would not reach the minimum is skipped so gas is not spent on dust. Some sweeps require an internal swap that only the protocol’s sweep operator may perform, and those are left to it.

2. The claim

Every 300 seconds the treasury reads what it can claim. When the escrow holds at least 0.01 ETH, it opens a cycle and claims the whole balance out of the escrow as ETH. The claimed amount is read back from the escrow’s own Claimed event, not assumed from the balance beforehand.

The income that is recycled into dividends is then set aside as that cycle’s budget, together with anything an earlier cycle could not hand out (see what carries over). Before any payment is signed, the wallet must hold the whole budget plus the gas reserve of 0.005 ETH; if it does not, the cycle waits rather than paying some holders and stranding the rest.

3. Who qualifies

Holdings are taken at the moment the cycle runs. There is no record date to register for and no snapshot to sign up to: whatever a wallet holds when the distribution is computed is what counts.

• Minimum holding. A wallet must hold 0.1% of supply. That is measured against total supply at the time of the cycle. It also caps the list at 1,000 wallets, which bounds what one cycle can spend on gas.
• Contracts are excluded. Most of a launch’s supply sits in contracts that are part of its own machinery: the bonding curve, the token contract itself, the pool manager that holds the pool’s token side, the hook, the fee escrow, the factory, the Uniswap position manager and router, the launch locker and vault, and the treasury wallet. None of these is a holder in any meaningful sense and ETH sent to most of them would be lost, so they are never paid. The zero and dead addresses are excluded too.
• Balances come from the token’s own transfers. The treasury keeps an index of every Transfer event and computes balances from it, so a distribution is a database read rather than thousands of chain calls.

4. How shares are computed

The budget is split in proportion to balances among the wallets that qualify. If you hold three times as much DIVIDENDS as another qualifying wallet, you receive three times as much ETH.

Dust. A share smaller than 0.00002 ETH would cost more in gas than it delivers. Such shares are dropped and the budget is split again over the remaining wallets, so a small holder can qualify on holdings and still receive nothing in a small cycle. Nothing is lost: the dropped amount stays in the budget for those who are paid, and rounding left over after the split is carried forward.

5. How payments are made

Each payment is a plain ETH transfer from the treasury wallet to the holder. There is no contract to interact with and nothing to accept.

1. Every planned payment is written to the database first, so a crash mid-way cannot pay anyone twice or forget anyone.
2. Before signing, the treasury checks the recipient can receive a plain transfer. A contract without a payable fallback cannot, so it is skipped and its share carried forward rather than failing the whole distribution.
3. The transaction is signed and its raw bytes stored before it is broadcast. If the network is slow, the same transaction is re-broadcast rather than a second one signed, so a payment can never be duplicated.
4. If a transaction reverts or is superseded, that payment is rewound and re-signed on the next run. The rest of the distribution is unaffected.
5. When every payment has been sent, the cycle is marked complete with the totals actually paid, read back from what was sent, and it appears in the distribution history on the dashboard.

The treasury also refuses to sign at gas prices above its own ceiling, whatever the node quotes, so a hostile or broken RPC cannot drain the wallet through fees.

6. What carries over

Anything a cycle cannot hand out waits for the next one rather than staying in the wallet unaccounted for:

• the rounding remainder after the split,
• the share of a holder that could not receive ETH,
• the whole budget, when nobody qualifies yet.

The carried amount is added to the next cycle’s budget the moment that cycle claims, and cleared in the same database write, so it can never be spent twice. The dashboard shows it as accrued, unpaid.

7. Before and after graduation

A launch trades on its own bonding curve until it graduates to a Uniswap v4 pool. The dividend process is identical in both phases, and in the short window between the curve closing and the pool being created, because paying holders needs no trading venue at all. The only difference is where the fee accrues and which contract the sweep targets.

8. Verifying it yourself

Every stage leaves a transaction on Robinhood Chain, and the dashboard links each one:

• sweep — moving accrued fees into the escrow, when the treasury did it itself;
• claim — the escrow paying the fees out to the treasury wallet;
• payments — one transfer per holder, listed under each distribution.

The same data is available as JSON. /api/treasury/overview is the headline state, /api/treasury/actions the distribution history, and /api/treasury/distributions?cycle=<id> every holder payment of one cycle with its transaction hash. Amounts shown are what was actually sent, read back from receipts, never what was planned. The treasury wallet’s full history is on the explorer regardless.

Questions

Do I have to claim my dividend?

No. It is sent to your wallet. If you qualified, it is already there.

Do I have to stake or lock anything?

No. Holding DIVIDENDS in a wallet you control is the only requirement.

Why did I not receive anything this cycle?

Either your wallet held less than 0.1% of supply at the moment the cycle ran, or your share of that cycle was below 0.00002 ETH and was dropped as dust. Larger cycles pay smaller holders.

I hold through an exchange or a contract. Am I paid?

The address that holds the tokens is what is paid. An exchange’s wallet would receive the dividend, not you, and contracts that cannot accept ETH are skipped.

Does the fee ever change?

The fee is set by the launch contracts, not by this treasury. The parameters above are read live from the treasury and update if they change.

What are the dividends paid in?

ETH, the native asset of Robinhood Chain. Never in DIVIDENDS itself.