Product
From “we owe them” to “here is the proof”.
Orynt is a layer between the decision to pay and the wallet that sends the money. This is the whole flow, in plain language.
How to read the status labels. “Verified” follows the project’s execution register: a command was run and its result recorded. “Real regtest” means it ran against real bitcoind and LND nodes on a test network; “simulator + tests” means automated tests with the labelled practice wallet. Nothing has been audited, and mainnet is disabled.
The six steps
Obligation Verified · real regtest
Write down the payout before anything moves: who, how much, and which invoice.
- What happens
- An operator creates or imports a payout with the payee, the exact amount (whole millisatoshis, never decimals) and a Lightning invoice. Orynt decodes the invoice, checks its signature, and binds its network, amount, expiry and payee node key to the record. Any edit creates a new immutable revision and cancels earlier approvals.
- What it prevents
- Paying a different amount, network or node than was agreed. Approving something that has since changed.
- Limits
- Orynt checks that the invoice is well formed and matches the record. To catch a swapped invoice, bind the payee to their node key.
Approval Verified · simulator + tests
The right people approve the exact payout, and their approval is signed.
- What happens
- A policy decides how many approvers are needed (for example maker-checker, thresholds, limits). Each approver signs the exact payout fingerprint (the “intent digest”) with an Ed25519 key held on their own device. Roles are checked when approving and checked again at execution.
- What it prevents
- “I thought you meant a different amount.” One person creating and approving their own payout. Approvals that quietly survive an edit.
- Limits
- Operators and API keys cannot approve. What a signature means legally is a question for counsel, not something we claim.
Execution Verified · real regtest
An approved payout is reserved exactly once, then sent through your wallet.
- What happens
- A single-use, durable execution record is reserved in PostgreSQL inside a transaction, before the wallet is called. The wallet adapter is chosen per workspace: a real LND node (REST) on regtest, or a simulator that is always clearly labelled.
- What it prevents
- Double sends from a double click, a retry or two operators acting at once.
- Limits
- Only an LND REST adapter and the simulator exist. Mainnet execution is not enabled by default.
Truthful state Verified · real regtest
If the wallet’s answer is lost, the payout says so, and waits.
- What happens
- States only move forward and are based on evidence. A lost response becomes Unknown, then Reconciling, never Failed. A second send is refused until the wallet’s own record, looked up by payment hash, says what happened. An expired invoice is not proof of failure.
- What it prevents
- Paying twice because a timeout looked like a failure. Leaving a payee unpaid because nobody was sure.
- Limits
- Orynt can only be as truthful as the wallet’s record. If the wallet cannot answer, a person resolves the case with fresh evidence, and that action is logged.
Evidence Verified · real regtest
A receipt anyone can check, without asking us.
- What happens
- A versioned receipt binds the agreement, the approvals (with their signatures), the payee, amount and invoice, and the wallet’s payment result including the payment preimage. Hashing the preimage gives the payment hash, which is cryptographic proof of payment independent of Orynt. A standalone command-line verifier checks it offline and rejects tampered, replayed, stale or forged receipts.
- What it prevents
- Disputes that rest on screenshots. Needing to trust Orynt’s database to prove a payment happened.
- Limits
- A receipt cannot prove that work was delivered or good, that an agreement is legally enforceable, that no other payments exist, or that funds were held in trustless escrow. You obtain the issuer’s public key out-of-band; the verifier tells you when it is missing.
Developer platform Built · SDK not on npm
Everything above is available to your own code.
- What happens
- A REST API described by OpenAPI, a typed TypeScript SDK, signed webhooks and the verifier CLI. See the developer page for real samples.
- What it prevents
- Rebuilding payout safety logic inside every internal script.
- Limits
- Early and unstable. The SDK lives in the repository and is not published to a package registry.
Payment states, and why Unknown is not red.
States only move forward, and each move needs evidence. The colour carries meaning: green is proven paid, indigo is not yet proven either way, red is proven not paid.
Every state, in words
| State | Meaning | Money may have moved? |
|---|---|---|
DRAFT | Being prepared. Can be edited. | No |
AWAITING_APPROVAL | Frozen and waiting for the required approvers. | No |
APPROVED | Enough valid signed approvals. | No |
EXECUTION_RESERVED | The single send has been reserved; the wallet has not been called yet. | No |
DISPATCHING | The wallet is being asked to pay. | Possibly |
PENDING | The wallet says the payment is in flight. | Possibly |
UNKNOWN | No reliable answer. Sending again is refused. | Possibly |
RECONCILING | Asking the wallet for its authoritative record. | Possibly |
SETTLED | The wallet’s record shows it paid, with the preimage. | Yes |
SIMULATED_SETTLED | Settled in the simulator only. Not a real payment. | No (simulated) |
DEFINITIVELY_FAILED | The wallet’s record proves it did not pay. Only now can a new attempt start. | No |
REJECTED | An approver declined it. Only possible before any send. | No |
CANCELLED | Stopped before any send. | No |
Works in front of a wallet you control.
Orynt does not hold funds. An operator connects a Lightning wallet they control, and Orynt discovers what that connection is allowed to do rather than assuming. The credentials you hand over decide what Orynt could do with your money, so give the least permission that works.
Today that means an LND node over REST on Bitcoin regtest, or a simulator that is always labelled and can never produce a real receipt. Other wallet types are not built; see the wallet capability matrix.
Where the limits live.
Approval rules, roles and limits are enforced inside Orynt. They are not enforced by the wallet. If someone holds your wallet credentials directly, they can bypass Orynt entirely. Read the security page for the full picture.
Want to see it on regtest with your own workflow?
Tell us how you pay people today. We will walk through the flow on test funds and tell you honestly where it does not fit.