Documentation
Everything needed to run this engine and integrate an application against it. Start with the quickstart if you want a payout on your own machine in ten minutes; start with authentication if you are implementing the signing scheme in a language without an SDK.
The shape of it
The engine is one process (plus a worker) in front of one Postgres database. Your application talks to it over a signed HTTP API and receives signed webhooks back. It holds keys, watches chains and moves money; it does not hold your account balances, your pricing or your product logic, and it never asks about them.
Where to start
| If you are… | Start here | Then |
|---|---|---|
| Integrating an existing application | Quickstart | Deposits, Payouts, Webhooks |
| Implementing the protocol by hand | Authentication | Errors, API reference |
| Deploying and operating it | Self-hosting | Treasury, Reconciliation |
| Evaluating whether to trust it | How it works | Money, Idempotency |
All guides
Quickstart →
From an empty database to a signed payout in ten minutes.
Self-hosting →
Processes, environment, migrations, health checks, upgrades.
Authentication →
The canonical string, byte by byte, and the four ways to get it wrong.
Money and precision →
Why an amount is a decimal string and what happens when it is not.
Idempotency →
How a retry after a timeout resolves to one payout instead of two.
Errors →
One envelope, one opaque 401, and what to do with a request ID.
Deposits →
Addresses, detection, confirmations, and surviving a re-org.
Payouts →
The state machine, the broadcast reservation, and stuck payouts.
Webhooks →
Verifying a delivery and handling at-least-once properly.
Embedded widgets →
Two drop-in cashiers: deposits with an asset chooser, and withdrawals your server authorises.
Treasury →
Hot and cold tiers, float thresholds, gas-aware sweeps.
Reconciliation →
Three-way comparison, findings, and who is allowed to close one.
Reports and exports →
Projections, staleness, and streaming a CSV that never buffers.
API reference →
Every endpoint, every field, every status code.
Node SDK →
Client, webhook verification, and the reference implementation.