Open Protocol developer guide
Integrate private funds and verifiable payments into wallets, DApps or self-hosted services. Understand assets and authority first, then complete a flow covering receiving, spending and recovery.
Start with your goal
| Goal | Reading path |
|---|---|
| First integration | Architecture → Quickstart → TypeScript |
| Build a wallet | Trust boundaries → SDKs → Sessions and recovery |
| Call contracts directly | Core → Notes / Credit → Events |
| Query state and confirm receipt | RPC → Queries → Native confirmation |
| Relay transactions | Broadcaster → Integration → Scheduling |
| Integrate native payment sessions | IPP → Facilitator → HTTP integration |
| Prove fund sources | Provenance → Integration → Evidence and recovery |
Two asset models
A Note represents funds settled into the protocol and can be transferred or withdrawn under its rules. Credit authorizes a future debit from an owner’s wallet; it is not locked funds. They share infrastructure but have distinct authority, funding, lifecycle and recovery rules.
Responsibilities
The application protects keys, presents authorization, authenticates decryption and manages inventory. Core settles on chain; RPC supplies candidates and state; Broadcaster optionally relays; Facilitator implements IPP sessions; Provenance supplies evidence for scoped source claims.
Service success, chain inclusion and business redemption are different facts. Define trust boundaries and check compatibility.
For hosted merchant collection, start with Business Payments; operating these services is not a prerequisite.