2026-10-05

Arkade send minimum, PWA page drag and the Safe EVM account

TLDR

3 PRs merged, 17 commits across all branches, 8 PRs opened, 3 repos (the Nuri app: 17, the Safe cosigner: 10, the swap server: 1), 7 deployments, +4,081 / -312 lines of code. I worked on 4 features.

Merged: Arkade sends under the minimum are now blocked before Confirm, Nuri users get paid at their Arkade address, and the PWA no longer drags empty screens. Most of the day went into making the EVM account a 2-of-3 Safe, and none of that is merged yet.

Arkade send minimum and paying Nuri users

In the app, you could type an amount under 330 sats to an Arkade address and press Confirm. The send then failed with a minimum error after you already confirmed. Now the send screen reads the minimum live from the Arkade server, disables Confirm and shows the minimum on the button. If the server can’t be read, the button stays enabled and the send still fails safely like before.

The second part is about the Nuri Lightning address. Lightning receive is not available right now, so a payment to it can’t arrive. The address book no longer fills it in when you look up a Nuri username, and contacts already saved with one are skipped by Pay and the send suggestions. If you type or scan a Nuri Lightning address in Bitcoin send, it now resolves to that user’s Arkade address instead. Other Lightning addresses work as before.

Tests pass. The device checks on a real phone are still open. It ships as an OTA.

Page drag in the PWA

In the PWA on iOS Safari, with the keyboard open, you could drag a screen that fits, like the username screen, and the app then snapped it back. On the simulator the page moved 160px on an iPhone SE and 140px on an iPhone 16. Now a one-finger drag is cancelled unless something under the finger can actually scroll in that direction. Both phones measure 0px, and real scrollable forms like the address book and SEPA recipient still scroll. Making the page height follow the visible area was my first try, but it did not stop the drag, so it’s not in. A pass on a real iPhone is still open.

EVM account as a Safe

This is an open PR in the app, not merged. The EVM account becomes a Safe with three owners: the wallet key, a passkey and the Nuri cosigner, and any two can sign. It has the same address on every chain. Orders started from the old account before the switch still finish there. You can also leave without Nuri, since the wallet key and passkey together can sign alone.

On the cosigner side I opened two PRs, also not merged. The first one lets Nuri co-sign without a passkey prompt as long as you stay within your per-transaction and 24h limits, and asks for the passkey above them. Without limits set, every co-sign still needs the passkey like today. A retry of the same transaction is counted once.

The second one deploys the Safe on a chain only when you actually move funds there, in one sponsored transaction, instead of deploying on all chains up front. Retries and duplicate requests pay once.

Safe swaps on the swap server

Also not merged. The swap server now checks at quote time which routes a Safe can sign, and anything it can’t sign is listed as unavailable up front instead of failing later. LI.FI and CoW come as one Safe transaction that does the approval and the swap together, because the cosigner never signs an approval alone. For CoW, I added a cosigner change that accepts only this exact batch for the Safe’s own order, checked against the full order. Proving every route with a funded Safe is still open.

Release 0.102.0 and new issues

I opened the 0.102.0 release candidate. The version bump broke a test that expected the old version number, so I fixed the test to read the current version, and that’s merged.

I also opened issues for a setting that blocks all outgoing payments until you unblock it with your passkey, paying SEPA from any balance with the exact amount, Arkade to EURC and USDC above the 50k sats cap through a cooperative exit, temporary limited cards with Wirex, and onchain privacy of balances behind a Nuri name.