aboutsummaryrefslogtreecommitdiffstats
path: root/src/features/names.js
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-08-02 18:17:27 -0700
committerAdam Soltys <[email protected]>2026-08-02 18:17:27 -0700
commit8da44392be513929802a5f4329b29bfa125aaa04 (patch)
treead147686220f5a64b7c8bc9c3287f9ba0bb12020 /src/features/names.js
parentdf01e3fb245c3e8d75a335d94e95df5f76a3b30a (diff)
downloadcoinosv3-8da44392be513929802a5f4329b29bfa125aaa04.tar.gz
coinosv3-8da44392be513929802a5f4329b29bfa125aaa04.zip
Pay an npub: ark > lightning > on-chain, and fix the orphaned LN seams
Picking a search result (or pasting an npub) now resolves every way the person can be paid and takes the best: their kind-10037 ark advert; an ark= instruction in BIP-353 via their coinos name (registrar /pubkey returns the URI directly) or their nip05 name's own DNS record (a bare domain is the BIP-353 "_" user); then Lightning from profile lud16/ lud06 through the zap flow; then a BIP-353 on-chain address as last resort. Search results no longer put the nip05 identifier in the fill value — that's how fiatjaf.com ended up as a dead recipient. Along the way: the zaps feature's canLnPay/startLnPay seams had no provider since the swaps feature retired, so the whole Lightning-zap path was unreachable. Ark provides both now (the ASP pays invoices natively), which also revives zapping any LN-only npub. Co-Authored-By: Claude Fable 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Wvj4aoeMZwA7VUGdJP9Swi
Diffstat (limited to 'src/features/names.js')
0 files changed, 0 insertions, 0 deletions