Fund anyone on the internet.
Connect a fundraiser. Redirect token revenue. We convert it to USDC, deliver it through the rail the fundraiser already uses, and publish a receipt for every dollar.
- Delivered
- $0
- USDC out, to fundraisers
- Fees routed
- $0
- creator fees attributed to vaults
- Vaults
- 0
- 0 tokens · 0 causes
- Receipts
- 0
- hashed and anchored
One path from a swap to a stamped receipt.
Fees are attributed at the address level, swept to USDC, and delivered through whichever rail the fundraiser already accepts. Nothing here requires the fundraiser to know what a token is.
- 01Token tradingpump.fun · Bags · Meteora
- 02Creator feesSOL, on every swap
- 03Impact Vaultdedicated route address
- 04USDCswept via Jupiter
- 05Railcard or on-chain
- 06FundraiserGoFundMe · LaunchGood · wallet
- 07Receiptsha-256, anchored
Scroll to follow a dollar. Each stop is a table in the ledger: fee_events, sweeps, deliveries, receipt_artifacts. Nothing is aggregated before it is recorded.
GoFundMe doesn’t take crypto. Neither does the hospital.
Basmalah was diagnosed with Spinal Muscular Atrophy Type 1 at four months old. Untreated, SMA1 is fatal before the age of two. The one-time gene therapy that can stop it costs about $2.7 million, and her family’s fundraiser is on GoFundMe.
A community launched a token for her. Within days the trading fees were worth more than most of the donations. Then the practical problem: none of that money could reach the campaign. GoFundMe accepts cards. The hospital invoices in dollars. Nobody on the fundraiser’s side should have to learn what a wallet is.
Vouch is the piece in between. It routes the fees to a vault, converts them to USDC, pays the fundraiser through the rail it already uses, and publishes a receipt that anyone can check. The community keeps trading. The family gets dollars. The evidence is public.
Delivered through the rail the fundraiser already uses.
Vouch does not ask a family to open a wallet. It pays the way their page already accepts, and records how.
Operator card
live- Who
- GoFundMe, LaunchGood, JustGiving, any card checkout
- How
- Vault USDC tops up a Zentro card. A named operator makes the donation on the fundraiser's own page, attaches the confirmation, and signs the receipt.
A human executes each payment. That is deliberate: consumer fundraising platforms have no donation API and automating their checkout violates their terms.
On-chain USDC
live- Who
- Causes that hold a Solana wallet
- How
- A single USDC transfer from the vault treasury to the cause's address. The transfer signature is the rail reference.
Only works when the cause can custody USDC. Most cannot, which is why the other rails exist.
Issuing card
in integration- Who
- Platforms whose terms permit programmatic card donations
- How
- A virtual card issued per vault (Rain or Bridge), funded directly from USDC, charged at checkout without an operator in the loop.
Not yet used for any delivery. Listed so the roadmap is legible, not because it is done.
GoFundMe Pro
for nonprofits- Who
- Registered nonprofits on GoFundMe Pro (formerly Classy)
- How
- OAuth into the nonprofit's account and post donations through the official API, with the receipt id in the donation memo.
Does not apply to personal campaigns. Basmalah's page is a personal campaign.
Live vaults, live ledgers.
The first vault appears here the moment a fundraiser is connected and a token routes its fees. Every delivery after that prints a receipt.
Connect a fundraiserLaunch a token. Route the fees. Get matched.
Tokens launched through Vouch that follow the three rules are eligible for a fee match from the Commons vault, funded by $VOUCH creator fees. The match is paid on the same rail, with the same receipt.
- Rule 1
At least 50% of creator fees routed
The token's fee recipient must point at least half of creator fees at a Vouch route address, and the redirect must be locked on-chain.
- Rule 2
The cause is verified
A named operator confirms the organizer's identity, the campaign's ownership, and where money is actually going before the first delivery.
- Rule 3
Every receipt is public
Deliveries are hashed, anchored, and listed on the vault page. If a delivery cannot be evidenced, it does not count.