Nothing here asks you to trust us

Follow the money.

Every payment can be traced from the trade that produced it to where it lands: a charity's on-chain balance, or the wallet of the organisation or person it was launched for. Below is each step, what proves it, and the few places the trail depends on someone other than the chain.

Delivered
—
Payments
—
Coins
—
Our cut of fees
0%

The chain of custody

The first six steps are the same for every coin. After that the route depends on who is being paid.

01

A vault exists, with the recipient and split fixed

Read forwarder(), destinationChainId() and charityBps() on the vault. It has no owner and no setter, and nothing in it can move the coin's fees elsewhere.

on-chain
02

Pons pays the coin's fees to that vault

Read the creator fee recipient from Pons (getLaunchedToken). It must equal the vault. Only Pons itself can change it, behind a public 3-day timelock, and the keeper checks every coin on every run.

on-chain
03

Trading fees are swept to the vault

Fees wait on the bonding curve, or the pool hook after graduation, until anyone sweeps them into the Pons fee escrow for the vault.

on-chain
04

A stock-paired coin's fees are swapped to ether

PairConverted. Uniswap on Robinhood Chain, refused if any pool on the route has moved more than about 1% from its 30-minute average. Ether-paired coins skip this step.

on-chain
05

The vault splits by the locked ratio

SentViaAcross carries the recipient's share and the creator's share. Check them against charityBps(). The recipient is paid first.

on-chain
06

The recipient's share crosses to their chain

Across, usually in seconds. The destination address is sealed into the deposit, so whoever fills it cannot change where it lands.

on-chain

Then, depending on the recipient

A

An organisation, a person, or a custom address

Paid in ether straight into that wallet. Nothing to claim, and nothing after this: the deposit fill is the delivery. A custom address is whatever the creator typed, and is always shown as "Custom address", never as a name.

on-chain
B

A charity on Endaoment

The forwarder on Base swaps to USDC and donates. EntityDonationReceived on the charity's org, net of Endaoment's 1.5%. The org address is derived from the charity's IRS number, which /verify checks in your browser.

on-chain
B+

Endaoment pays the charity

You can see USDC leave the org on-chain. The bank transfer itself is not a blockchain event.

partly
C

A charity on donate.gg

The forwarder sends ether to donate.gg for that charity's account. The chain shows it leaving; confirming the account is the charity's means checking donate.gg's directory.

partly

Every coin

Who each coin pays, the locked split, and what is waiting to be swept. Click a coin for its page, or the vault to read it on the explorer.

CoinPaysSplitPending feesStatus
Loading…

Every payment delivered

WhenRecipientRouteAmountProof
Loading…

Endaoment amounts are what the charity was credited, read from Endaoment's own EntityDonationReceived event, after their 1.5%. Wallet and donate.gg amounts are the ether that arrived.

Check it yourself

Don't take these tables' word for it.

Is an address a Tithe coin or vault, and who does it pay?Address checker →
Does each charity's address really come from its tax ID?Verify →
Read the source of every contract that makes a vaultVerified contracts →
Watch the keeper that sweeps and pays, and run your ownKeeper →

How all of this works →