Skip to main content
Payments accumulate in your pool. Claiming moves your share to your payout address — and in most cases it already happens for you.

​
How

Today, most of the time you do nothing. Our keeper scans every 5 minutes, releases the balance in your pool, and sends your share to your payout address, fronting the network fee itself. If you want the money sooner, or a payout is still sitting in the pool, you can move it yourself:

Open Pool

Your balance per chain and per token is shown.

Release, if it hasn't happened yet

If funds are still undistributed, use the Release now control to split the pool on demand.

Press Withdraw

One button per token. There is no fee estimate in the dashboard — your wallet shows the estimated network fee on its own confirmation screen.

Sign

Your share moves to your payout address.
No approval and no review — distribute() is permissionless and nobody can gate it. Two things do apply: a batch must hold at least 1.00 of the settlement token before it can be released (below that the call reverts and the dust rolls forward into the next batch), and your pool runs on a settlement schedule you set in Pool → Settlement schedule — On a timer, or When it builds up to a threshold amount you name, with a maximum wait either way. You are never stuck waiting for it: Release now splits the pool on demand at any time.
A single Claim button that collapses release and withdrawal into one signature, with a live network-fee estimate, is Coming. Today those are two controls and two transactions. Either way it is your transaction and nobody can gate it. Roadmap.

​
What it costs

The percentage cost is 1% flat, all-in on a connect-rail order — the platform fee on the gross, and nothing else. You keep 99%. On a €100 order you receive €99.00. A deposit-rail order nets slightly less, by the network fee shown against that order — it comes off the payment at the forwarder before it reaches your pool, not off the release here. See How the fee is calculated. Native gas for release and payout is a separate matter, and today you spend none of it yourself:

If you leave it to us

You spend no native gas. Our keeper signs the release and the payout to your address and fronts that gas itself — and doesn’t recover it from you. It’s a cost the platform absorbs, not a deduction you’ll find anywhere in your settlement token. A chain where you hold zero ETH, POL, BNB, AVAX or TRX still pays out.

If you move it yourself

On an EVM chain, Release now and Withdraw are your transactions, so you pay their network fee in that chain’s native token — two fees if the pool has not been released yet, one if it has.
On TRON there is no manual step at all. The keeper sweeps, releases and pays out automatically, so you never need to hold TRX — and TRON batching is not something you control.

​
Choosing a cadence

Cadence changes when you are paid, not what it costs. Our keeper fronts and absorbs the release gas whatever the batch size, so automatic settlement costs you nothing extra either way. Batching only affects the network fee on payouts you sign yourself.
If you never touch it, you settle at least daily and you never sign a transaction. Lower the maximum wait or set a threshold if you want the money sooner; raise it if you would rather receive fewer, larger payouts.
Coming Cadence becomes a real economic decision once you pay for the release transaction yourself: batching then amortises a network fee you actually bear, and the automatic backstop lengthens from daily to roughly monthly. See The automatic backstop below for what that changes. Roadmap.

​
Nobody can stop you

distribute() — the function that releases funds — is callable by anyone. Not gated on us and not gated on an account review. The one gate is on-chain and mechanical: a pool must hold at least 1.00 in undistributed settlement token or the call reverts, and smaller amounts roll forward into the next batch. Once your share is credited, withdrawing it with claim() has no minimum at all.
This is deliberate and it’s the core of the non-custodial claim. A processor that could withhold your funds is a custodian, with the counterparty risk that implies. We built ourselves unable to.
A practical consequence: even if we vanished entirely, your funds remain claimable by anyone willing to send the transaction — including you, directly against the contract.

​
The automatic backstop

A keeper tick runs every 5 minutes. It releases any pool whose undistributed balance is at or above the on-chain minimum once that pool’s maximum wait has elapsed — 24 hours by default — and immediately on the first tick for a pool that has never been released. In practice pools settle at least daily. It also claims your credited share for you, so the funds land at your payout address with no action from you, and it retries on the next scan if a claim fails. It can only ever pay the address credited on-chain, never itself, and claiming yourself always remains possible.
Coming This is the part that changes most. Once claiming is a transaction you sign, releasing your pool becomes something you trigger and pay for, and we stop claiming your credited share on your behalf. The safety net that runs if you never press anything drops from every few minutes to roughly monthly — and it fires only when releasing is worth doing rather than on a fixed clock, so a small balance in a quiet pool can sit longer than that cadence suggests. In plain terms, “we push your money to you” becomes “you collect your money”.What does not change: distribute() stays permissionless, so your money is always claimable — by you, at any time, without asking us. Roadmap.

​
Reconciliation

Each release produces a pool.distributed webhook and a row in the dashboard with the transaction hash, so you can tie payouts to on-chain records for your accountant. The event fires when the release transaction confirms.

How the fee is calculated

1% flat, all-in, on the connect rail. You keep 99%.