Skip to main content
Where your money sits between payment and payout, and where you withdraw it.

​
Per-chain activation

Turning a network on takes two signatures in the Networks section of this tab: one proves you control the payout address, and the other actually deploys your pool contract on that network, from your own wallet, paying that network’s fee.

Flip the switch

Each network we can settle on has an on/off switch here in Pool. One click starts activation. (The Tokens tab is where you choose which stablecoins each network accepts — not where networks are turned on.)

Sign once, at the start

The first signature is a one-time message proving you control the payout address. It is a message, not a transaction you broadcast, and it is not repeated per network.

You deploy it, and pay that chain's fee

The second signature broadcasts the deploy transaction from your own wallet — a live network-fee estimate is shown before you sign. Nothing is fronted on your behalf and nothing comes back out of your share later for it. Fees.
Your pool has the same address on all seven EVM chains. TRON derives separately because it uses a different address scheme.
Making deployment a prerequisite for API keys and the embed snippet is coming. Today you can integrate first — but the connect rail stays refused on any network until your pool is actually deployed there; the deposit rail’s one-time address can still be shown pre-deploy. Roadmap.

​
Balances

Per chain and per token, showing what’s accumulated and unclaimed. These are token amounts, not display-currency conversions — but they’re rounded to two decimal places, so a balance with sub-cent precision won’t match the on-chain figure exactly.
You don’t need native gas to get paid. Our keeper settles your pool and sends your share to your payout address using its own gas — on TRON the row simply shows Auto and there is no button at all, and on EVM networks the keeper claims any claimable balance on its regular scan (at the latest when your maximum wait elapses, 24 hours by default). You only need a little ETH, POL, BNB, AVAX or TRX if you choose to press Withdraw now yourself to move a balance immediately rather than wait.The Dashboard’s Arriving card says what the keeper is doing with each balance — paying out now, the time of the next settlement, or waiting for the next payment if it is under the minimum. If our keeper falls behind on a network, that line says Delayed instead of promising a time, and offers Withdraw now.

​
Claiming

Pressing Withdraw now does whatever is needed in one signature — settling and paying out together if your share is still unsplit, a plain payout if it’s already split — with a live network-fee estimate shown before you sign. Most of the time there’s nothing to press at all: our keeper does this for you on its own cadence. No approval is needed — releasing a pool is permissionless, so anyone can trigger it. But there is a floor and there is a schedule. The release step reverts below a hard on-chain minimum of 1.00 of your settlement token; anything under that rolls forward into the next batch. And this tab ships a Settlement schedule: the keeper releases your pool automatically on a timer, or once it reaches a threshold you set, with a 24-hour default maximum wait. Above the floor you can still withdraw at any moment.
On the automatic schedule, batching doesn’t change what settlement costs you at all: our keeper fronts and absorbs the network fee on every release it sends, whatever the batch size, and nothing is carved out of your share for it — so today you normally pay nothing per-transaction and don’t need to pick the batch window. If you do withdraw yourself, that one transaction’s network fee is per withdrawal, not per order, so fewer, larger withdrawals cost you less gas overall.
Claiming in detail.

​
What you can and can’t change

Changing your payout address deploys a new pool. The old one keeps its balance and stays claimable, but new payments go to a different address. Plan the switch — don’t do it mid-trading-day.

​
Verifying independently

Your pool is a public contract. On any block explorer, call recipient() and confirm it returns your address — and confirm there’s no function that could change it.

On-chain verification

How your customers’ browsers check this on every payment.