Separate signing service, invite tracking and Send defaults
TLDR
0 PRs merged, 7 commits across all branches, 7 PRs opened, 4 repos (the Arkade server: 5, nuri signing: 3, nuri aa: 3, the Nuri app: 3), 0 deployments, +286,172 / -754 lines of code, 2 features worked on.
Most of the day went into moving the co-signing keys for Bitcoin, Arkade and Safe accounts out of the servers into one separate signing service. On top of that, invite links that record who invited a new user, and Send on the Bitcoin card starting on Lightning. None of it is merged or live yet.
Separate signing service for co-signing
Nuri co-signs every user transaction together with the user’s passkey. Until now the servers held the key material for that themselves. I built a separate signing service with one endpoint, and both servers now ask it for every Nuri signature instead of holding a key.
For Bitcoin and Arkade the existing key is ported unchanged, so every user keeps the same keys and addresses. The signer doesn’t just trust the server. It rebuilds what it signs from the transaction itself, checks that a send actually pays where the user approved, and only signs when the user’s passkey asked for it. The passkey prompt is now a fingerprint of the exact send, so it’s still one passkey touch, same as today, but a server in between cannot swap the transaction under it. I also made a batch round survive when an answer from the signer gets lost.
The Arkade server side drops the key completely and keeps its database, chain reads and all its existing checks. Same app API, so the app doesn’t change. It is not merged on purpose, it waits until the signing service is running.
The Safe side (the accounts for Cash and Card) works the same way: the signer derives each user’s key from the passkey and only signs after that passkey approved the exact transaction. Here it’s a new key, so every Safe address changes. Right now only internal test Safes exist, and their funds have to move out before the switch. Also not merged yet.
Invite links
Someone who opens a friend’s invite link on the Nuri web app, app.nuri.com/invite/ plus the friend’s username, and signs up is now recorded as invited by that friend. Tracking only, nothing else. The visitor sees the normal welcome and signup and the address bar goes back to app.nuri.com.
In the app the inviter stays on the device until the username is claimed, the first invite opened on a device wins, and it’s sent along with the claim, so no extra passkey prompt. A failed claim keeps it for the retry.
On the Arkade server the inviter is stored once, only when the claim creates a new user, and never changed. An unknown inviter or your own name is ignored and signup works as before. Tests are green on both sides, both PRs are open, and the app part needs the server part deployed first.
Send defaults on the cards
Send on the Bitcoin card opened on Onchain as soon as Onchain had any sats, so Lightning was never the default. Now it starts on Lightning when Lightning has money and only falls back to Onchain when it’s empty. Also “Swap to my balances” from a card no longer locks the From side, the card’s balance is just preselected and any balance can be picked. Tests pass and I checked it on a web build, but the device pass on iOS and the PWA is still open. The PR is closed, not merged.
Pay page cleanup
I removed the Open in Nuri button from the pay page. It was added for a review finding, not for the product, and it sat over the keypad on a phone. A payment link only offers the handoff to the app or an external wallet. I also removed an empty 72px top bar that pushed the content down on the first screen, checked on a built page at phone size. That PR is also closed, not merged.