2026-11-09

v0.111.0, signed swap changes and send safety fixes

TLDR

11 PRs merged, 5 commits across all branches, 1 PR opened, 4 repos (the Nuri app: 10, nuri origin infra: 3, the swap server: 2, the banking server: 2), 1 deployment, +642 / -68 lines of code. I worked on 3 features.

v0.111.0 is merged as the first iOS build from the new Apple team, with the key backup prompt and paying Nuri contacts from the address book. On the swap server, changing an older swap now needs a signature from the wallet that sent it, but that PR is still open and not live.

Release v0.111.0 and the new Apple team

The release candidate collects everything since v0.110.0: the key backup prompt sheet on home, paying a contact in Bitcoin or Cash from the address book, and a list of fixes. The production app ID is unchanged, so the current store app keeps getting updates until users install the new build. The TestFlight check, where one passkey sign-in has to restore the wallet over the current App Store app, is still open.

The dev and preview apps could not be built on the new team because the old team still holds their IDs, so I moved them to new IDs. For passkeys to work in those builds, nuri.com has to list them, so I added them there too and kept the old entries. Testers have to reinstall the dev and preview apps once. Android is unchanged.

Signed changes to older swaps

On the swap server I opened a PR so that every change to an older swap needs a signature from the swap’s own sending wallet over that exact change, with a short expiry. Plain reads stay the same. It is not merged.

The app has exactly one place that changes such a swap: the old Arkade refund that runs on app open. Without a signature the refund still lands onchain, but the server never records it and the order stays open. That app side is merged. The signature only happens if the wallet active at that moment is the one that started the refund, otherwise nothing is sent until that wallet is active again. A test pins the signed message byte for byte to the server’s, and a cross-check passed the real refund report to the server, which accepted it. The server PR waits until this app release is out.

Send and card safety

When you scan an address that belongs to a Nuri user, the app pays their current address instead. The send sheet only showed the name, so now there is a muted line like “Paying 0x1234…abcd, their address on Nuri now (not 0x5678…ef01)”, only when the two differ. It is in all 12 languages but not checked on a device yet.

For wallet to card top-ups the app now derives the card deposit address itself and compares it with what the server sends. For now it only logs a mismatch and money still goes to the same address as before, because older accounts might not match. Refusing a mismatch comes only after a release with zero mismatches.

The Bitcoin send fee rate is now capped at 500 sat/vB, so a wrong value from the fee feed can’t spend most of a balance as miner fee. Above that a send just confirms later. A counter for swap secrets now survives logout, so the app does not reuse old ones after signing in again. Neither was tested on a device.

For one LI.FI bridge type from stablecoins to Bitcoin, the Bitcoin payout address in the bridge call must now match the address the order committed to, otherwise the app refuses before signing. No live order was run. I also fixed a note in the app update pipeline: a failing test does block an update from going out.

Base node failover

If our paid node key died or got throttled, Base sends, card top-ups, sweeps and swap legs stopped completely. Now they fall back to a public node and stay on it for that session, so one transaction never reads from one node and broadcasts to the other. A short hiccup is still retried on the paid node first. This was only tested against a stubbed network, not live.

UK bank transfers

On the banking server, in the UK Faster Payments work, a failure nested deep in the bank’s server response is now treated as a server error instead of the bank refusing the payment. This is on two branches and not merged yet.