2026-10-28

Separate signing service for Bitcoin, Arkade and Safe accounts

TLDR

0 PRs merged, 1 commit across all branches, 3 PRs opened, 4 repos (the Nuri app: 1, nuri signing: 1, the Arkade server: 1, nuri aa: 1), 2 deployments, +8 / -8 lines of code, 1 feature worked on.

I opened PRs that move all of Nuri’s co-signing into one separate signing service, so the Arkade server and the Safe account server no longer hold the signing key themselves. None of it is merged or live yet.

Bitcoin and Arkade co-signing in a separate signer

Every Nuri Bitcoin and Arkade wallet is 2-of-2: the user signs and Nuri co-signs. Until now the Arkade server held the Nuri key and made that second signature itself. I opened two PRs that change this.

The first adds Bitcoin and Arkade signing to the new signing service, one operation for every step the server does today: creating the account, login, sending, approving a receive, the boarding sweep and the batch rounds. The key moves over unchanged, so every user keeps the same keys and the same addresses, and nothing changes in the app.

The signer doesn’t just trust the server. It rebuilds what it is asked to sign from the transaction itself, checks that a send pays what the user approved, and only signs after the user’s passkey confirmed it. On a send the passkey now confirms a fingerprint of the exact send, so a server in between can’t swap the transaction under it. It’s still one passkey touch, same as today.

The second PR removes the key from the Arkade server completely. The server keeps only the public part, which is all it needs for addresses, plus its database, chain reads and all of its existing checks. Login challenges now come from the signer, and approvals for receives and the boarding sweep need the signer’s approval too. This PR waits until the signer is running, so it’s open and not live.

Safe accounts on the same signer

I opened an issue and a PR to do the same for the server behind Nuri’s Safe accounts. With the PR, that server holds no Nuri key anymore. The signer derives each user’s Nuri key from its own key and the user’s passkey, and signs only after that passkey approved the exact transaction. It also rebuilds the transaction and re-runs the Safe checks itself.

The Safe server keeps account setup, address prediction, the balance policy and the token check, and runs them before it asks the signer. It also refuses a signature over anything other than what it built. The app already sends what the signer needs, so there is no app change.

Because this uses a new key and a new way to derive it, every Nuri owner and Safe address changes. Only internal test Safes exist so far, and their funds have to move out before the switch. Still open per the issue: unit tests with a stand-in signer and an end-to-end test against the real running signer. The PR is not merged.

Text cleanup in the send flow

In the Nuri app I’m working on a change to the send flow, and in those changes I removed the em dashes and changed the wording to onchain. That’s one commit on a branch, not merged yet.