Tags

Tags give the ability to mark specific points in history as being important

  • v0.3.0-checkpoint

    2f635c03 · chore: add checkpoint and deployment files · 
    Lightning address flow live on mainnet via matthew@vtxos.cash

Working end-to-end:
- LNURL-pay (LUD-16) returning invoices
- NIP-05 identity verification
- NWC relay communication
- Invoice creation via bark CLI
- Admin UI with VTXOs table and payment history

Federation publicly accessible at https://vtxos.cash

  • phase-2b

    3c9cbcdb · Redact mnemonic-prefix from PROGRESS.md before publishing · 
    Phase 2b checkpoint — full daemon + LNURL bridge + mainnet validated (post-redaction)

  • phase-2a

    dde1a7b9 · Add top-level README pointing at PROGRESS.md and the phase-2a tag · 
    Phase 2a: full NIP-47 send + receive on signet

Known-good checkpoint of bark-nwc. Resumable from here.

What works at this tag:
- Daemon advertises 5 methods via kind 13194 (get_info, get_balance,
  pay_invoice, make_invoice, lookup_invoice)
- Outbound: Alby Go → daemon → bark → Lightning, UI-confirmed on signet
  (94,990 → 92,986 sats across two real pays in May 2026)
- Inbound: make_invoice / lookup_invoice tested against real bark 0.1.4
  on signet; created a real lntbs1... and round-tripped it through
  receive-status by both payment_hash and BOLT11
- Relay defaulted to wss://relay.primal.net (avoid nos.lol / damus
  rate-limits on chatty wallet services)
- Duplicate-request dedup (LRU 1024) + graceful NOT_IMPLEMENTED for
  unknown methods like Zeus's list_transactions
- 102 unit tests pass, 5 ignored live tests, fmt + clippy clean

Out of scope (Phase 2b/c):
- LNURL bridge / Lightning addresses / zap-receive
- list_transactions
- bark-ffi swap (still subprocess)
- Per-client allowlist
- Systemd unit