Prism payment splits on Rootstock
Geyser is an open-source crowdfunding platform for Bitcoin, Lightning, and Nostr. Geyser Prism is its payment architecture for routing one incoming payment to multiple recipients.
Prism accepts Lightning or on-chain Bitcoin payments and applies your split rules. Rootstock, the EVM-compatible Bitcoin sidechain, settles each payout on chain. Geyser does not hold project funds in a central custodial wallet.
Get started
Choose the path that matches your role.
Run a project on Geyser
- Open geyser.fund and follow the Geyser guide to configure your project wallet and withdrawals.
- Save your wallet password offline. Geyser cannot recover it if you lose it.
Build or fork a Bitcoin payment app
- Visit the geyser repo on GitHub.
- For custom settlement on Rootstock, use Hardhat or Foundry with a Rootstock RPC endpoint on testnet first.
Prism ships on Geyser first. APIs and reuse outside Geyser may change. Check geyser-app release notes before you ship.
What problem Prism solves
Lightning is strong for single payments. Platforms often need one checkout to pay a seller, a fee, affiliates, or collaborators at once. Prism defines split rules for that case and runs payout distribution through Rootstock contracts after the incoming payment is accepted.
How it works
One payment enters your app. Prism applies your split rules. Rootstock confirms each recipient’s share on chain.
- The payer uses Lightning or an on-chain path your app supports.
- Prism maps the payment to your split rules (fees, shares, royalties).
- Rootstock executes the split so each recipient gets the correct amount.
Wallet setup, withdrawals, and operator UI are documented on guide.geyser.fund, not on this page.
Rootstock gives you EVM smart contracts secured by Bitcoin merge-mining. Prism uses that layer to enforce split rules on chain instead of trusting a single platform balance.
When you launch a Geyser project with Prism, you set a wallet password that encrypts your project key. Geyser does not store that password. If you lose it, you cannot withdraw project funds.
Example products
You are responsible for compliance, UX, and wallet policy in your jurisdiction. The table shows common fits for split payments.
| Product type | Split behavior |
|---|---|
| Multi-vendor marketplace | One payment to sellers, platform fee, royalties, affiliates |
| Agencies and freelancers | Client payment to lead, subcontractors, platform |
| Creator tips and subs | Share between creator, collaborators, platform |
| Affiliates and referrals | Commissions to referrers, seller, platform |
| Royalties | Fixed shares for artist, label, platform |
| DAOs and treasuries | Revenue to contributors, treasury, or governance rules |
| Charity | One donation across multiple causes plus overhead |
| Bounties and grants | Sponsor funds to winners when your rules are met |
| Bundled subscriptions | One charge split across providers in the bundle |
Other payment guides on Rootstock
| Use case | Solution |
|---|---|
| Pay-per-request APIs for agents | x402 on Rootstock |
| Gas paid in ERC-20 | RIF Relay |
| BTC ↔ rBTC | PowPeg App |
| Rootstock vs Lightning | FAQs |
Resources
- Geyser and Geyser guide
- geyser-app (open source)
- Prism announcement
Have a unique idea or need a comprehensive integration guide? Submit an idea on the Hacktivator Marketplace.