Pay links, Bitcoin send details and remit price holds
TLDR
3 PRs merged, 1 commit across all branches, 3 PRs opened, 1 PR reviewed, 2 repos (the Nuri app: 5, nuri infra: 2), 0 deployments, +439 / -1 lines of code. I worked on 3 features.
Shipped shorter pay links and Bitcoin send details that show where the money went. Also fixed the app paying a remit invoice after its price had already expired.
Pay links without the @
In the Nuri app, the links it makes and shares now read app.nuri.com/pay/name instead of app.nuri.com/pay/@name. Same for the handoff into the native app, into the installed web app and back to the browser. Links already shared with the @ keep opening the same page. Released app versions already read links without the @, so the handoff from the new page also reaches older installs. Merged, full unit suite passed.
Recipient address and explorer link in Bitcoin send details
The details screen used to hide the address as soon as a row was named after a contact or Nuri user. Now the name stays as the title and the address shows under it, with Copy. This is the shared details screen, so Cash and bank rows also show their address or IBAN under a known name. Swaps still show their two sides.
Instant Arkade sends now show the recipient too. The app already read that address to look up a name but never showed it. It only shows when the payment has exactly one other address, otherwise nothing, so it never guesses.
Every Arkade row that has one now gets an explorer link: payments inside Arkade open the Arkade explorer (only on the default Arkade server, because that explorer only reads that server), and sends out of Arkade to a Bitcoin address open mempool.space on the onchain transaction that paid it. A send out of Arkade shows the link but no address, because that onchain transaction pays many users at once and the history does not say which output was ours. Older cached rows without a payment id get no link. Merged.
Remit payouts and the price hold
The send screen paid a remit invoice after the provider’s price hold had ended. The Lightning payment went through, the payout failed, and the sats came back by manual refund. The screen only checked the invoice expiry of one hour, never the price hold of about 44 seconds.
Now the app keeps the last moment a press can still pay in time, which is the hold minus 40 seconds for passkey, Arkade and the Lightning swap. A press after that fetches a new price. A new price with under 15 seconds left is not shown, and the screen says the rate is unavailable. The deadline is checked again right before the wallet sends, and if it fails nothing is sent. Because the provider’s hold is shorter than that budget today, these payouts show “Rate unavailable right now” until they make the hold longer. Merged, tests include a replay of the failed order’s timeline.
One-tap passkey for incoming Bitcoin
Open, not merged. Incoming Bitcoin should work like a Lightning claim: one tap on the passkey button opens the system prompt right away, without the extra confirm screen that showed up about 8 seconds later. A retry after a cancel gets a fresh challenge, and if the screen stays open for a long time the challenge gets refreshed so it does not expire.
Card withdrawal fallback, log runbook and a review
I opened a PR so that when the Wirex route is down, the card withdrawal to the wallet goes straight onchain with the same two approvals, only if nothing was signed yet. That PR is closed, not merged.
On the infra side I opened a PR with a runbook and the live configs for our central log system, so the team can run and redeploy it without asking me. The configs were checked against the live servers and match. No secrets are in it and nothing on the servers changed. Not merged yet.
I also reviewed one PR on the signing side about a test setup and recovery.