coinos-ui.git/src/lib, branch master

nostr: fetch the encrypted key with the password when there's no session key

2026-10-13T23:23:39Z

Without the sk cookie from a password login (nostr logins, older sessions) the reveal button was hidden and signing failed. Ask for the password and get the key from /nsec instead. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01UjHzoBmW1iPpEe5qC2LDYB

nostr: sign with the session key instead of the encrypted key from /me

2026-10-08T19:15:17Z

Co-Authored-By: Claude Opus 5.5

ecash: carry pasted tokens in the URL instead of storing them server-side

2026-09-27T21:46:30Z

The server no longer accepts anonymous token uploads. A pasted token now redirects straight to /ecash/, and the page asks the server for the token's status statelessly. Ids from previously shared links still resolve. Co-Authored-By: Claude Fable 5.1

invoice: a reusable bolt12 offer has no terminal paid state

2026-09-22T18:27:15Z

A bolt12 offer is a standing payment code. CLN derives the same offer_id from the same (amount, description), so re-creating one hands back the original record, whose `received` has accumulated over the offer's whole lifetime. The invoice layout read that as "this invoice was paid" and redirected to the success screen, so reopening a long-lived offer never showed the QR and left no way to copy the lno. Treat a payment as celebratory only when it arrives while the page is open: the socket handler now passes the amount of that payment as `?paid=`, and the layout uses it in place of the lifetime total for reusable offers. Single-use invoices keep the existing logic, so a partly-paid invoice still stays on the QR rather than celebrating early. The success screen showed lifetime `received` for the same reason, which misreported a single payment to a long-lived offer; it now renders the amount the socket reported, which is already net of tip. Co-Authored-By: Claude Opus 5 (1M context)

send: quote the lightning routing fee up front and add Max to lightning sends

2026-09-22T02:21:43Z

The lightning send page now asks the server what the payment will cost before showing the Send button: the exact routing fee from the route query, the platform fee, and the total. The quoted fee is submitted as the maxfee, so what the user sees is what gets debited; advanced settings still let them override it, and if the quote fails the page falls back to the old 2% reserve. Max on the amount step asks the server for the largest amount whose amount + routing fee + platform fee lands exactly on the balance, and for an offer picks up the invoice fetched for that exact amount. LNURL-pay gets a Max button too. The invoice only exists once we name an amount, so the action fetches a probe invoice at the ceiling, lets the server solve for the amount, then fetches the real invoice for it. Co-Authored-By: Claude Fable 5.1

ecash: drop the mint account special-case and the mint route

2026-09-16T11:53:22Z

The server no longer keeps a house ecash pool, so there is no mint account to skip when parsing a payment and no /ecash/mint endpoint. Co-Authored-By: Claude Fable 5.1

register: start the session from the register response

2026-09-14T19:54:23Z

/register now verifies the recaptcha token itself, and Google tokens are single-use — so the follow-up /login that reused the same token came back "failed captcha" for an account that had just been created. The register response already carries the JWT; set the session cookies from it and only fall back to /login when registration itself failed. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_0166Ci2XdCair1B9ych7w8dq

Only pay internally when the name is really a local account

2026-08-02T15:50:15Z

Addresses at our own domain used to have the domain stripped and get paid internally on the assumption that every one of them was ours. v3 payment addresses live at the same domain, so check the account exists first and otherwise leave the address intact — it then flows through the normal lightning-address path. Co-Authored-By: Claude Fable 5

bolt12 zaps: accept offers in send flow, show/publish user offer

2026-07-30T15:51:45Z

- parse lno= from BIP-321 bitcoin: URIs; send page parses offers for preview now that /parse handles them - settings/nostr shows the user's standing lno1 offer with copy/QR and a button to publish it as a kind 10058 offer list for NIP-177 zaps - new locale strings translated Co-Authored-By: Claude Fable 5

Fix parse matching subdomain addresses as local users

2026-02-25T20:13:18Z

Co-Authored-By: Claude Opus 4.6