Inspiration

Bitcoin-native teams can have payment obligations in one place, approvals in another, and settlement records in a third. When a Lightning wallet's response is interrupted after payment dispatch, an operator may not know if money moved. Retrying blindly is unsafe. Orynt explores a safer financial-operations workflow for teams paying contributors, contractors, and grant recipients. Demand is a hypothesis, not yet validated through customer interviews.

What it does

Orynt (working title) is payout-authorization and reconciliation software that connects to a customer-controlled LND Lightning wallet; it is not itself a wallet, exchange, or custodian.

  • Bind a BOLT11 payout to an exact amount, recipient node, network, invoice expiration, wallet connection, and immutable revision.
  • Apply role- and amount-based approval policies; approvers sign the exact intent using Ed25519.
  • Reserve execution durably in PostgreSQL, so concurrent requests do not create duplicate dispatches.
  • Treat an interrupted wallet response as UNKNOWN, not automatically failed. Block unsafe second execution while checking the node's payment record.
  • Issue signed receipts with preimage/payment-hash checks and an audit-chain segment; verify them independently using the orynt-verify CLI, including negative tests for tampering.
  • Provide an operations console with onboarding, recipients, incidents, reports, and support. Additional SaaS workflows use controlled test services; no paid launch is claimed.

What we actually verified

On regtest, with valueless Bitcoin Core 29.5 and two LND v0.20.1 nodes, the repository records 15 real-node tests, an end-to-end payment, an injected lost-response recovery, API SIGKILL recovery, duplicate prevention, receipt verification, and rejection of altered receipts. The latest CI pipeline also passed six jobs at commit c103031c (November 11). Real Lightning has not been tested on mainnet; mainnet is disabled. The UI and subscription infrastructure are not evidence of production payments, customers, or provider approval.

Technology

TypeScript, Node.js, Fastify, PostgreSQL, React, Vite, Zod/OpenAPI, LND REST, Bitcoin Core regtest, Ed25519/SHA-256, Vitest, Playwright, Docker, GitHub Actions.

Challenges

Payment responses can be lost after funds move. The most important design decision is refusing to interpret transport uncertainty as definitive failure. Real LND tests exposed issues that simulation did not, including encoded payment-hash lookup and permission-check differences.

What's next

Human security assessment, operational wallet adapter verification beyond LND, customer interviews, approved billing and email providers, and production commissioning. NWC and BTCPay adapters are currently contract-tested but not connected to the application's execution path.

Open-source evidence

Source: https://github.com/VictorCyberDev/orynt/tree/claude/busy-goodall-ajeb0p

Architecture and evidence: https://github.com/VictorCyberDev/orynt/tree/claude/busy-goodall-ajeb0p/docs/evidence

Presentation (PDF): https://github.com/VictorCyberDev/orynt/blob/claude/busy-goodall-ajeb0p/docs/hackathon/deck/orynt-deck.pdf

Rendered video file (not a YouTube/Vimeo public video): https://github.com/VictorCyberDev/orynt/blob/claude/busy-goodall-ajeb0p/docs/hackathon/video/orynt-demo-silent-captioned.mp4

AI-assisted development disclosed. Orynt is a working brand name pending clearance.

Built With

Share this project:

Updates