2026-10-21

Faster Arkade payments, Nuri contacts and Safe balance

TLDR

13 PRs merged, 24 commits across all branches, 20 PRs opened, 5 repos (the swap server 31, the Nuri app 14, the banking server 8, Nuri support chat 3, the Arkade server 1), 9 deployments, +3,682 / -386 lines of code. I worked on 6 features.

Most of the day went into making Arkade payments in Nuri reach the passkey faster and not get stuck. Nuri users now land in the address book by themselves and are always paid by username, and a Safe account’s balance counts its old address too.

Faster Arkade payments

On the swap server, our own share of the wait before the passkey was about 1.15 s, almost all of it storage calls running one after another. That is merged now: ending a lock is one call, a journal entry is one call, adding an order to the wallet’s order lists is one call, and the refund step saves the order once instead of twice. Expected about 0.4 s less, measured live after deploy.

One wallet (mine, served from Berlin) spent 138 to 175 ms on every storage call while every other wallet spent 17 to 60 ms. Its storage was created far away and never moves, and that cost about 3 s of the 8 s from tap to passkey. New payments now use new wallet storage created by the wallet’s own request, so it sits near the user. Older orders stay where they are and are still listed. The new numbers still get measured on the next payments.

The server can also take the refund material with the commit, so the phone saves one round trip. The app side is an open PR, not merged yet: it sends the refund material with the commit, quotes early and cuts the phone’s own prep before the passkey from 4.4 s to 2.1 s.

Stuck Arkade payments

All merged on the swap server. About one in five FixedFloat orders failed because FixedFloat’s rate moves a little between quote and create. Now they settle at FixedFloat’s final amount, and what the wallet pays stays capped at the accepted amount.

When the solver’s answer never reached us, a retry of that payment failed every time. Now the retry asks again under a new request, and only an answer that actually arrived is ever offered for funding.

A paid Lightning send could stay in flight forever when the solver gave no status, and that open order blocked every new send from the wallet. The server now reads the payment on the Arkade chain itself. Verified on a live order: it reads as settled, 1,231 sats.

Since about 16:00 UTC FixedFloat was missing from every quote and nothing logged why. Refused calls are now logged with the reason, with amounts, addresses and keys cut out. The reason itself is not known yet.

Nuri users in the address book

Merged in the app, ships as an OTA. Anyone you pay or get paid by who is a Nuri user is saved as a contact by username, with every address seen for them, so old payments read as that person. Those addresses are only used for naming. A send always looks the username up fresh and stops if the lookup fails. The device test is still open.

Safe balance and card withdrawals

In the app, a Safe account’s balance is now the Safe plus its old address, so money does not look gone during the migration. A send that needs money still on the old address moves it into the Safe first. The migration’s passkey prompt now says what it signs, in all 12 languages. This is merged into the Safe migration work, which is not live yet. Still open: if the move is pending when the send runs, the user has to retry.

An open PR, from Android and iPhone recordings, cuts the migration to one explained prompt, runs it once per user and sends card money straight to the Safe.

On the banking server, merged: a card withdrawal can pay any Base address, and only the signed-in owner can choose it. The money goes straight from Wirex to that address. No live withdrawal to another address has happened yet.

Paying a link with a wallet token failed with “That price expired” when the payer was also signed into Nuri. Fixed and merged, the device test is open.

Open PR, not merged: one send flow for Cash and Bitcoin that starts on the recipient, where the balance you pay from decides the route.

The support chat’s revenue page has an MRR card now, projected from the days since fees started on 2026-10-15.

Several earlier PRs, including Safe native coin sweeps and username rules, were closed today without merging.