2026-10-30

Lightning receive, live Lightning limits and Arkade SDK 0.5

TLDR

14 PRs merged, 21 commits across all branches, 14 PRs opened, 7 repos (nuri support chat: 15, the Nuri app: 13, the Arkade server: 10, the swap server: 6, nuri website history: 3, nuri signing: 1, server wirex aa: 1), 8 deployments, +2,066 / -498 lines. I worked on 7 features.

The Nuri app, the Arkade server and the swap server are now on the production Arkade SDK 0.5 with Lightning receive switched on, and the Lightning limits now come from the solver’s own published card instead of fixed numbers. Plus fixes for the Android keyboard, Wirex signup and the contact history.

Arkade SDK 0.5 and Lightning receive

The app, the Arkade server and the swap server all moved to Arkade’s production 0.5 release. In the app this brings back the 0.5 upgrade that was merged by accident earlier and reverted, now on the final release. A refund of a Lightning send lockup now goes out in batches, because the new version only spends a limited number of coins per refund. On the server, Lightning receive is on by default with this merge. Live, the solver created a receive invoice on the new version and the server rebuilt the identical lockup from the stored data, but nothing was paid. So a real receive and a real send on a phone, plus a small real money check in the app, are still open.

Lightning limits from the solver and Lightning address on receive

The limits for Lightning send and receive were fixed in code, so they went stale every time Arkade changed them. Receive was capped at 49,830 sats while the solver already allowed 200,000. Now the Arkade server reads the solver’s signed card from its Nostr relay every 5 minutes and only accepts a card signed by the known key and at most two hours old. The app reads the limits from the server and keeps the old numbers only as a fallback. The swap server does the same for its send bounds. Today that means send 335 to 200,000 and receive 340 to 199,380 sats. The solver can still refuse an amount it will not fill, it did at 150,000.

In the same PR the in-app Lightning invoice is fixed. It failed for everyone because the server looked for the wallet’s Arkade address in the wrong place, now it derives it from the wallet’s own keys.

Add money > Receive on the Arkade balance shows your Nuri Lightning address again, first, then Arkade, then the onchain address. It was removed in August while receive was off. This is merged but still needs a check on a phone.

Android keyboard, Wirex email and contact history

On Android 14 and older, full pages got lifted twice when the keyboard opened, so Continue jumped under the field and the home screen showed through below. Now the page reaches down to the keyboard. On the VISA & Banking email page the error goes away once you edit the email, and the keyboard opens with the page. This is not tested on a real Android device yet.

If Wirex already has your email on another account, signup now says so and lets you enter a different one. Before, every retry failed with “We could not set up your account”. The app side is merged, but the Wirex server fix that sends this error is an open PR and not deployed, so nothing changes for users until it is.

The contact page history shows Cash and Bitcoin rows at once from what the device already has, instead of waiting several seconds for every read. The “Some payments could not be loaded” line is gone.

Support cockpit and other work

Our support cockpit now tracks each user’s onchain Bitcoin wallet next to Arkade, lists the swaps paid from a user’s wallets, shows a lifetime value from every fee a user brought, and counts the original wallet of Safe users as the same account.

The old website archive deleted its build bundle after each deploy now, because two 584 MB bundles filled our shared build storage and broke the web app release. A tool to close swaps whose outcome is already proven, plus a refund for one unclaimed Arkade to Lightning lockup, is an open PR. A signing check change sits on a branch, not merged. I also opened issues for GBP, MXN, BRL, SWIFT and USD bank transfers, which mostly wait on Wirex enabling them.