Coming to OnePlan
On-chain trip fund
How the planned shared USDC fund differs from recording contributions in the current app.
Availability
The planned fund lifecycle
The design assigns a shared on-chain vault to a trip. Members would contribute USDC from their own wallets. Fund spending and settlement would then follow the rules of that vault, rather than only updating a ledger entry.
A record marked “paid” in today’s group-fund screen does not represent an on-chain contribution. In a released wallet flow, an actual transaction and its confirmed status would be needed to establish that assets moved.
Bookkeeping and on-chain funds compared
| Question | Current group-fund record | Planned on-chain fund |
|---|---|---|
| Where is the money? | Wherever the group holds it outside the ledger. | In the trip’s supported on-chain vault after a confirmed contribution. |
| What does contributing do? | Creates or updates a contribution record. | Transfers supported assets into the shared fund. |
| Does marking paid prove receipt? | No. The collector must verify the real payment. | A ledger label alone is still insufficient; transaction confirmation matters. |
| Can I use it today? | Use the existing contribution workflow. | No. Not released. |
Details needed before launch
The live guide will need to specify supported networks and assets, approval thresholds, network fees, withdrawal rules and recovery/support procedures. Those details are intentionally not presented as promises here.
Merchant QR payouts are also a separate capability. A successful development demonstration must not be treated as evidence that a real bank payout is available.