Revenue and getting paid

Revenue accrues per project and per organisation. Getting it out is a request the platform team approves, paid to a wallet you have proved you control.

📷 Screenshot placeholder — Revenues, the per-network balance tiles and the fee-charge feed.

Where revenue comes from

Every fee a farmer pays on your projects — task and bonus claiming fees, token-claim fees and project fees — is split the moment it is charged: the platform's share, the commission pool your formula pays to the farmer's upline, and the rest to you. That rest is your revenue. It is held against the scope that earned it — the project, and through it the organisation above — and, because money is an address on a network, it is kept per network: revenue earned on Devnet and revenue earned on Mainnet are separate balances that are never added together.

Reading the Revenues page

Revenues shows a balance tile per network and a feed of every charge with its receipt: the gross amount the farmer paid, the platform's cut, the affiliate commission and your receivable. You can search by project or payer and filter by project or fee type. A chart shows revenue over time, and a breakdown splits it by fee type and by project. The headline cards — total earned, this month against last, withdrawable now and the top project — are converted to USD when a rate is available, one set per network.

📷 Screenshot placeholder — a fee receipt: gross → platform cut → affiliate commission → your receivable.

Requesting a withdrawal

Withdraw revenue shows a card per scope that has a balance — each project and each organisation — with what is available on each network. Choose a scope, choose the network, enter an amount and confirm. If you have turned on two-factor authentication for withdrawals on your account, the request asks for a code.

The amount is reserved at once, so the same money cannot be requested twice.
The request waits for the platform team — Awaiting SuperAdmin, usually within a day.
On approval the payout runs automatically and the transaction hash appears on the request. On rejection the reserve is released back to your balance and the request is marked as rejected.

The amount must be within the scope's available balance and above the platform's minimum, which is shown on the page. An organisation request is filled from that organisation's projects, largest balance first, so one request can appear as several rows.

Which wallet receives it

You never type an address on the request. The payout goes to the wallet set for the scope, in a fixed order:

the project's payout wallet, if it has one;
otherwise the organisation's wallet;
otherwise your business unit's default wallet under Settings.

A wallet only counts once it is verified — connected and signed from the wallet itself, which proves you hold its key. An address that was never signed is skipped as if it were not there, and the search moves on to the next scope. If nothing in the chain is verified, the request is refused with No destination wallet — connect one on the organisation or project page and try again.

📷 Screenshot placeholder — Settings → Wallets with a verified and an unverified wallet.

The withdrawal fee

The platform may charge a withdrawal fee, taken out of the amount: the wallet receives the amount minus the fee. It is a percentage set by the platform team, with a cap so that a large withdrawal does not pay many times what a small one does. Two things make it zero: a plan that waives it, or a free monthly allowance — a number of withdrawals per calendar month that carry no fee. The allowance counts withdrawals that were actually paid, per network, so a rejected request never uses one up and a Devnet withdrawal never uses up a Mainnet one. The rate, the cap, the minimum and how much of the allowance is left are all shown on the page before you confirm.

When a withdrawal is blocked

If the organisation behind a project is not yet verified, that project's revenue cannot be withdrawn. It keeps accruing and becomes available the moment verification clears; the check runs when you request and again when the platform team approves. Instant launches are exempt, because their distribution never touches the platform. A suspended organisation's revenue is locked while the suspension lasts. See Why revenue can be locked.

Farmer withdrawals are a different page

Your affiliates and influencers withdraw their earnings through their own requests, which you see under Withdrawals. There you can approve a request or report it to the platform team; you cannot reject one. Only the platform team rejects.