Live Lightning limits, Wirex email fix and cockpit wallets
TLDR
1 PR merged, 7 commits across all branches, 8 PRs opened, 7 repos (this site: 6, Nuri support chat: 4, server Wirex AA: 2, the Nuri app: 1, the swap server: 1, the Arkade server: 1, Nuri website history: 1), 0 deployments, +1,263 / -97 lines. I worked on 6 features.
The main things: Lightning limits in Nuri now come from the solver’s live card instead of fixed numbers, the Lightning address is back on the receive screen, and Wirex onboarding now says when an email is already used by another account. Only the Wirex fix is merged, and it is not deployed yet.
Lightning limits from the live card
Arkade changes the Lightning solver’s limits, but we had them fixed in code. Production capped Lightning receive at 49,830 sats while the solver actually served up to 200,000. The solver publishes a signed card with its limits on Nostr, so now we read it from there.
On the Arkade server, it reads the card at start and every 5 minutes, only accepts one signed by the known key and at most two hours old, and keeps the last card if a read fails. Receive bounds follow the card with the same margins as before, and the server gives the app the current send and receive limits. I also removed the old fixed cap from the production settings, but nothing changed live, that happens with the deploy of this PR.
In the app, the send screen and the invoice sheet load those limits, at most every 5 minutes. The old numbers are only a fallback until the first answer. The keypad, the button and the checks behind it now all use the same range. Today’s card is send 335 to 200,000 and receive 340 to 199,380.
The swap server does the same for Arkade sends, gated on the card’s bounds. I checked it reads the real card live. The solver still refuses an amount it will not fill, on Oct 30 it said no at 150,000 because of its exposure cap.
All three PRs are open, none merged or deployed.
Lightning address on receive and invoice fix
Add money > Receive on the Arkade balance only showed the Arkade and onchain addresses, because the Lightning row was removed in August while receive was off. Now the user’s Lightning address shows first, then Arkade, then onchain, and the invoice sheet shows it too. This is JS only, so it can go out as an OTA once merged.
Also in the Arkade server PR: creating a Lightning invoice in the app failed for everyone with “registered wallet has no Arkade address to receive into”, because it read a field the wallet record never has. Not merged yet.
Wirex onboarding with a used email
If the email someone enters already belongs to another Wirex user, onboarding treated it as if this wallet’s user existed and ran every later step against nothing. The app waited and then showed “We could not set up your account”. 4 wallets hit this in 3 days. Now onboarding stops and tells the app the email is already in use. I confirmed the error shape against the live Wirex API. This is merged but not deployed.
Support cockpit wallets and lifetime value
Four PRs for our internal support cockpit, all open. It now tracks each user’s own onchain Bitcoin wallet next to the Arkade boarding address, in the users list, user page, totals and daily snapshot. One user’s onchain wallet holds about 0.21 BTC and showed nowhere before.
For users with a Safe, the original wallet now counts as the same account, so their Wirex account, swaps and fees land on them instead of an unnamed row. For one user that moved swaps from 12 to 264.
The user page shows a lifetime value, every fee Nuri got from their swaps in EUR, with pending fees named as pending and never counted as 0. The swap list on the user page also read the wrong field and always said “Swap data not loaded yet”, that is fixed. Tests pass, 226 on the last PR.
Local AI analysis page
I added a German page to this site comparing running your own AI against a subscription or leasing, with a configurator, model choice, common objections and buying as the default. It is noindex.
Website archive deploys
Every deploy of the old Nuri website archive left a 584 MB bundle in our shared GitHub storage. Two deploys on Oct 29 filled the quota and broke the app’s web release. The PR deletes the bundle once the deploy succeeds. Open, not merged.