Manual payouts
Money lands in one wallet. Someone opens a spreadsheet, does the math and sends N transfers, every month, forever. Late, error-prone and nobody's favourite job.
Concept · not live yet · Solana · USDC
SplitStream is a programmable payout address for teams, creators, DAOs and co-founders. Any USDC that lands is distributed by shares (say 60 / 25 / 15) with exact remainder math, a public ledger and verifiable monthly statements. Revenue share without a spreadsheet or a trusted treasurer.
Illustration with simulated payments. Branch thickness = share. Counters are exact to 0.000001 USDC.
The problem
Money lands in one wallet. Someone opens a spreadsheet, does the math and sends N transfers, every month, forever. Late, error-prone and nobody's favourite job.
Whoever holds the keys holds everyone's share. Collaborators have to trust them to pay on time, pay correctly and not disappear.
Percentages rarely divide evenly. Without a fixed rule for the leftover cents, totals drift and every statement becomes a negotiation.
How it would work
Sign in with your wallet and create a stream. It gets its own program-owned USDC account: one receiving address.
Add recipients and their shares in basis points. Shares must total exactly 100.00%, or the stream won't save.
Put it on your storefront, sponsor deck, invoice or marketplace payout settings. Payers see one address, not N wallets.
When USDC arrives, a permissionless crank distributes it by shares, exact to the base unit, with a memo tag and a ledger entry.
Interactive demo
Runs entirely in your browser. Nothing is sent anywhere, no wallet, no chain. It uses the same rules the real thing would: integer base units (1 USDC = 1,000,000), shares in basis points, and a deterministic rule for remainders.
Drag a slider: the other shares rebalance proportionally so the total is always exactly 10,000 bps.
| Recipient | Share | Payout (USDC) | Remainder |
|---|---|---|---|
| Press Send to split a payment. | |||
Rule: each recipient gets floor(amount × bps / 10,000). The few leftover base units go one each to the largest fractional remainders, ties broken by recipient order. Same input, same output, every time.
| # | Amount | Distribution | Memo |
|---|---|---|---|
| No distributions yet. | |||
Use cases
Merch, tips, sync fees and sponsorships into one address. Every member and the manager get their cut the moment it lands.
Client payments or app revenue split by the equity or effort you agreed on. No one person holding everyone's money.
Route protocol income to grants, treasury and contributors by share, with a ledger anyone can audit and statements anyone can re-hash.
One stream per partner deal: the seller keeps the majority, the referrer gets their percentage automatically, per sale.
Under the hood
SplitwiseNow already runs exact bigint ledgers, weighted splits with deterministic remainders, non-custodial USDC/USDT settlement with on-chain verification and SHA-256 receipts. SplitStream would add one new piece: the splitter.
Each stream's token account would be owned by a program PDA that stores the recipient list and shares. Nobody, including us, could withdraw from it except by running distribute, which pays every recipient by the stored shares. Anyone can crank it when the balance crosses a threshold; a worker would do it by default.
// all amounts are u64 base units (1 USDC = 1_000_000)
for i in recipients:
base[i] = amount * bps[i] / 10_000
frac[i] = amount * bps[i] % 10_000
left = amount - sum(base) // always < recipients.len
give +1 to top `left` by (frac desc, index asc)
transferCheckedSPL token transfers that check mint and decimals, with idempotent associated-token-account creation so first-time recipients just work.
A micro-dollar ledger at 6 decimals, the same as USDC base units. No floats anywhere, so payouts always sum to the deposit exactly.
Each distribution carries an SPL Memo such as splitstream:v1|<stream>|<seq>, and is booked only after the confirmed transaction is re-read on-chain.
A canonical JSON statement per stream per month, hashed with SHA-256, with every line linked to its Solana signature. Anyone can recompute it.
Pricing & roadmap
small bps on distributed volume
Nothing is for sale today. No sign-ups, no waitlist, no wallet connection on this page.
This page. The split math is real; the chain is not involved.
PDA-owned vault, distribute instruction, crank worker, tests.
USDC first, capped volumes, public ledger pages.
Monthly SHA-256 statements, CSV, invoices, nested streams.
FAQ
No. It's a concept built on the SplitwiseNow payment core. The demo on this page runs only in your browser and touches no blockchain.
The design is non-custodial: a stream's funds would sit in a token account owned by the splitter program, and the only way out is the distribute instruction that pays recipients by the stored shares. Until the program exists and has been reviewed, treat that as a design goal, not a guarantee.
All math runs in integer base units. Each recipient gets the floor of their share. The leftover base units (always fewer than the number of recipients) go one each to the recipients with the largest fractional remainder, ties broken by recipient order. It's deterministic, so anyone can re-run it and get the same numbers.
Distribution is a permissionless crank: anyone can trigger it. The plan is for a worker to crank when the balance crosses a threshold, so tiny deposits don't cost more in fees than they're worth.
Planned: share changes need approval under rules set at creation (for example, all recipients or a majority), and they only apply to funds that arrive after the change. Every change would be on the public ledger.
USDC first, then USDT, both via SPL transferChecked. Other tokens sent to a stream wouldn't be distributed automatically.
No. The planned business model is a small basis-point fee on distributed volume.