Every fee, followed from trade to recipient

The contract records the allocation. The operator handles withdrawal and provider funding. Each stage is recorded against the claim that produced it.

How it works
Permissions01

Clear rules.
Visible responsibilities.

Who can act, and how.

Can harvest fees for registered tokens. Funds stay in the contract’s pools until withdrawn.

Can mark an alias as do-not-pay. That blocks new launches for the alias and redirects its future attributed allocations to treasury.

Can pause new launches, disable methods, manage keepers and change the launch configuration. Can withdraw either pool and recover ETH or ERC-20 tokens in an emergency: unaccounted ETH first, then treasury, then recipient funds.

Reviews recipient accounts, funds provider balances, submits payments and reconciles uncertain outcomes.

Read about controls
The flow02

Three stages.
One record.

/01≡

Trade

Fees accrue on pons

  • Every trade pays pons’ 1% fee: 30% to pons, 70% credited to the contract in the pons escrow.
  • Any creator tax (2% to 10%) is credited in full.
  • After 4.2 ETH the market moves to a locked Uniswap V4 pool; fees keep paying.
/02≡

Harvest

Split once, 80/20

  • A harvest sweeps each token’s pending fees and claims the escrow.
  • 80% to the payout pool, 20% to the treasury, with FeesAttributed events.
  • Pre-swept fees emit UnattributedClaimed for keeper reconciliation.
/03≡

Settle

Funded, then paid

  • The owner withdraws payout funds for an approved off-ramp.
  • At a milestone, the keeper pays through the provider with a stable request ID.
  • A payment is complete only after provider confirmation.
Live record03

Read straight from the keeper.

These figures update from the indexer that follows the contract and pons. Real payouts only: simulation and sandbox runs are excluded.

—+

Creator fees harvested

Claimed from the pons escrow and booked 80/20 in the contract.

—+

Trades indexed

Buys and sells on the curves of tokens launched through the contract.

—$

Paid to recipients

Confirmed by a payment provider. Allocated but unpaid balances are not counted here.

Built on and paid through04
Why it exists05

Most people you’d want to pay don’t have a wallet.

Creator fees usually stop at a wallet address. This protocol gives them a destination people already use: a PayPal, Venmo, Wise or bank account, with the split fixed in the contract.

The path06

Seven stops between
a trade and a payout.

Accrued fees, claimed funds, conversion and completed payouts are separate stages, each recorded against the claim that produced it.

Contract reference07

Follow the record.

Inspect each contract and its activity on the explorer. These are the addresses the site reads and writes.

Get startednow

Give your token
a destination.

One alias
One fixed route
Every harvest

Starting from

2% tax

Charged on every trade on top of the 1% pons fee, and paid to the contract. The recipient earns 2.16% of volume.

No wallet needed on the other endpons launch fee 0.0005 ETH + gasPayouts from $5 after verification
Create token
MRecipient@maria_k
Recipient allocation · example
$80.00
Payout route
PAYPALUSD · PayPal Payouts
Payout route
VENMOUSD · by phone
Payout route
WISEEUR · SEPA
RegisterLaunchHarvestPaid
Recipient pool
$80.0080%
Protocol
$20.0020%