Issue bonds.Raise capital.
Issue revenue bonds to raise capital for your onchain business. Investors fund the bonds, and a share of business revenue is routed toward repayment.
[–]
Revenue routed
[–]
Payments booked
[–]
Collected for investors
[–]
Live bonds
Live from Monad testnet via Envio. Dollar totals use the deployment’s USDC; counts include all indexed accounts. Collected means revenue sent to bond pools, not holder redemptions. Demo businesses and traffic are run by the Bondrail team.
(01) How it works
From revenue to a funded bond.
Record revenue, set the terms, and let investors assess the business behind the bond.
(01)
Open an account
Create a revenue account in the token you earn. It is your revenue address from day one.
(02)
Build history
Native fees and account settlements prove a payer on-chain. Plain transfers are booked by sweep without a proven payer.
(03)
Issue a bond
Set the bond terms against your revenue history. Investors fund it; 25% or 50% is released, the rest at a milestone.
(04)
Route revenue to repayment
The current revenue share goes toward repayment, up to the cap. Native fees and x402 payments settled through BondrailAccount.settle via the Bondrail facilitator split in the same transaction. Plain transfers still need sweep.
(02) Two tiers
Routing enforced in code, or monitored.
Built on Bondrail
A reviewed template or individually reviewed project routes fees through its bound account using BondrailEarner. Review covers the disclosed code path; it does not guarantee future business revenue.
- · collect() for money in, settleOut() for money out
- · payer proven by the transfer itself
- · optional fee floor while a bond is live
Paid APIs over x402
Your API pays its account. Chainlink CRE checks every paid endpoint every 30 minutes; a confirmed diversion defaults the bond and slashes your stake.
- · /.well-known/bondrail.json manifest
- · every payment option must pay the account
- · guarded buyers verify payTo before paying
(03) For builders
Start the record today.
Route revenue through an account. Build history, then set terms investors can assess.
Build with the npm packages @bondrail/sdk and @bondrail/contracts.
(04) For investors
Underwrite evidence, not promises.
Assess attributed revenue, payer concentration and coverage. Buy claims on Kuru where listed, or fund a raise. Early redemption burns claims for current backing and gives up future receipts.
Pool capital in the credit vault, inspect credit profiles, and check performance triggers that can raise the investor share when revenue falls.
(05) Trust
Every assumption, disclosed.
Read the full trust model in the docs.
Native fees and x402 payments settled through BondrailAccount.settle via the Bondrail facilitator split in the same transaction. Plain transfers split when anyone calls sweep. Revoking Native project or template approval blocks new deposits and releases unless another approval still applies; repayment of a live bond continues.
A disclosed Native reviewer approves projects or templates; a milestone signer approves signed milestones where selected; observer reports arrive through Chainlink CRE. Signed credit assessments rely on the attester, and vault allocations rely on the curator within contract limits.
Revenue stops too. Holders retain the collected pool and undrawn capital when it is recovered. Watched stake goes to investors only on a recorded default. Coverage and any available Kuru price help assess risk; neither guarantees repayment.
Self-payments still pay the investor share while a bond collects revenue. Indexer attribution excludes detected issuer-linked payers and plain transfers, but cannot prove customer independence. Performance triggers use all booked revenue, including self-payments.
On Monad testnet, with team-run demo businesses and traffic. The contracts are not audited.
Built with