Euro to Lightning addresses, faster claims and support inbox
TLDR
12 PRs merged, 19 commits across all branches, 10 PRs opened, 1 PR reviewed, 6 repos (the Arkade server: 14, the swap server: 11, the Nuri app: 9, nuri support chat: 3, banking nuri com: 2, base faucet: 2), 8 deployments, +1,691 / -1,541 lines of code. I worked on 4 features.
In the Nuri app, Euro and Dollar can now pay a Lightning address, and the server claims a paid Lightning receive within about 3 seconds. I also removed the onchain payment push and kept rebuilding the support inbox.
Euro and Dollar to a Lightning address
Before, a Lightning address could only be paid from the Bitcoin balance, so someone holding only Euro or Dollar could not pay it at all. The swap server change is merged and live. It quotes and commits these orders only with the provider that resolves the address itself, and every other provider is listed as no route.
The app side is merged too. The amount screen is the Move card with the address as its fixed destination, and the wallet sends one token transfer of exactly the accepted deposit, never more. When a destination has both a Lightning and an onchain address, both are priced and Lightning comes first because it arrives at once. Lightning is only offered when the amount fits the address’s own range and the provider’s limits. Money sent to someone else’s Lightning address also no longer shows up as your own Lightning balance.
Also merged on the swap server: we now hand the provider the deposit transaction the moment the app reports it. On a test order 44 seconds passed between the deposit and the provider starting the payout. No funded order went through this path yet, so the saving is not measured.
Faster Lightning claims and tag addresses
On the Arkade server a paid Lightning receive is now claimed within about 3 seconds instead of waiting up to 15. Nuri Lightning addresses also accept a tag after a plus sign, which still pays the same user and stores the tag. A wallet can ask whether the receive under its own tag was claimed, so the app can tell which incoming payment is its order’s payout. That part is merged on the server, the app side is a separate PR.
Swap and send fixes
A swap on Base needs ETH for its whole gas limit, but the app only topped up enough for a plain token send, so wallets with a little ETH got their swap refused. It now asks the gas faucet for what the swap needs right before sending. Merged, but not tried live from a low ETH wallet.
Sending from Arkade to a Bitcoin address said no route between 6,550 and 7,000 sats. The swap server cached the provider’s minimum for 6 hours and now reads it again after a minute, and the app reads that minimum live instead of a fixed number. Both merged.
The swap server now treats the solver’s “filled” state as still in progress, which caused 113 failed status checks in 14 days on Arkade to Lightning swaps. A status read also retries once after a dropped relay connection. No funded swap was run for this.
The “Keep app open” pill now goes away after you decline the passkey on a send. I also opened an issue to let our co-signing server do the round signing on Arkade claims, so the phone only signs once.
Bitcoin activity, errors and eSIM
Bitcoin activity rows now show their Euro value on first paint after a cold start, from prices already saved on the device. Merged, not checked on a real device yet. Bitcoin activity, support chat and the swap status sheet show plain text instead of raw error messages, in all 12 languages, merged. A paid eSIM order whose pickup keeps failing offers support after 30 seconds instead of spinning for ten minutes, that PR is closed.
Server cleanup and gas faucet
I removed the onchain payment push from the Arkade server. It checked 251 addresses on every block for 20 pushes in 14 days, and the rate limits it caused also failed some deposit status reads in the app. Lightning receive pushes stay. It is merged and takes effect on the next server deploy. The Bitcoin name index also skipped three users on every run and now indexes their onchain address.
The Base gas faucet moved to another server. The PRs that point every app build at it and record the move are open, and I reviewed a PR retiring the old faucet docs.
Support inbox
The inbox now has one row per person with a status, waiting time and age, and one thread per person with the customer’s words shown first in app reports. Those two PRs are closed. The third is still open: a Needs you tab headed by day, a separate Bot answered tab, and the row time matching the sort. On a copy of live data Needs you shows 11 chats instead of one list of 53.