Skip to content

Let a store turn on Monero, Lightning, and Zcash - #153

Merged
hoffmabc merged 1 commit into
mainfrom
fix/store-own-rails
Nov 17, 2026
Merged

hoffmabc merged 1 commit into
mainfrom
fix/store-own-rails

Conversation

@hoffmabc

Copy link
Copy Markdown
Member

Summary

  • The store payment list always painted Bitcoin as the only selected rail, and Zcash was hard-coded off, so a seller could not opt Monero, Lightning, or Zcash in from store settings. Each of those rails is now a switch that signs the own store record. Escrow stays on bitcoin.
  • A rail the node cannot take stays on the list with the node's reason (no daemon, no indexer, Lightning off or blocked, wallet not open yet) instead of disappearing. The first Lightning opt-in still shows the LSP notice.
  • The letter badges are original filled marks: Bitcoin ₿, Monero M, a Lightning bolt, and the Zcash Z. Escrow stays a balance, not a coin.

Test plan

  • node --experimental-strip-types --test src/paymentRails.test.ts (7 passed)
  • npx tsc --noEmit in apps/mobile
  • On a testnet4 desktop build, open Store settings and turn on Monero, Lightning, and Zcash for the own store. Lightning asks for the LSP notice once. A locked wallet shows the node's refusal.

The payment list only painted Bitcoin as selected, and Zcash was hard-coded off, so a seller on testnet4 could not opt the other rails in from the store. The switches sign the store record and keep a refused rail visible with the node's reason.
@hoffmabc
hoffmabc merged commit 173747c into main Nov 17, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant