2026-11-11

Payment pushes, Arkade claims and Lightning addresses

TLDR

6 PRs merged, 6 opened, 1 reviewed, 12 commits across all branches in 5 repos (nuri support chat 10, the Nuri app 6, the Arkade server 5, the swap server 2, nuri agent ready website 1), 4 deployments, +2,237 / -369 lines. I worked on 4 features.

Onchain “Payment received” pushes work again with far fewer lookups, and Arkade claims reconnect after a cut connection. The swap server can now pay a Lightning address from EURC or USDC, and the support inbox shows one row and one thread per person.

Onchain payment pushes

Since Nov 10 the onchain payment watch on the Nuri Arkade server failed for up to 149 of 249 addresses on every sweep, so those users got no “Payment received” push. The server read every subscribed address every 30 seconds, about 720k lookups a day, and the data service started refusing most of them. A push only fires on confirmation, and that needs a new block. So now each tick reads the block height and only reads the addresses when it moved, about 36k requests a day.

New subscribers, failed lookups and failed pushes are still read on the next tick, so a payment in the next block is not missed. When the service refuses, the sweep pauses for 30 seconds, doubling up to 10 minutes. Every read, including the deposit status the app shows, now falls back to Blockstream when the primary cannot answer. This is merged. The new checks pass, and it was tested live. Stuck pushes catch up on the first sweep after deploy.

Arkade claims

Claiming received Bitcoin failed on iOS with a confusing engine error. A claim follows its round over one long connection to Arkade. When the network cut it, the claim just ended, and our logging wrapper hid the real error. The app now reopens a connection that was up and got cut, and passes the real error through. I reproduced the exact error on the engine the app ships, and the fix works in that same setup. No funded claim was run on a device yet. A cut in the middle of signing can still fail that round, but now with the real reason. Merged.

I also opened an issue for a suggestion from the Arkade team. Our co-signing server would do the round signing, so the phone only signs once. Arkade needs no change, our server needs new work.

Euro or Dollar to a Lightning address

A Lightning address can only be paid from the Bitcoin balance today. BitcoinVN swaps EURC or USDC and pays the address itself, so I opened issues for the app and the swap server.

The swap server part is merged. A quote to a Lightning address now only asks BitcoinVN, and the commit works. The quote stays bound to that one address. Checked live without funding: orders get created, and an unknown address is refused before any deposit address exists. No funded order end to end yet.

The app PR is open and not live. Euro or Dollar pays the address through the Move card. When a recipient has both a Lightning and an onchain address, both are priced, with Lightning first because it arrives at once.

Support inbox

Merged: one row per person with a status (Needs reply, Bot only, Answered, Done), how long the customer has waited and who wrote last. Tabs come with counts, and opening a chat marks it read and jumps to the newest message. An open chat is now one thread per person in time order. App reports show the customer’s words first, and each message says Customer, Team or Bot.

Still open: the time on each row matches the sort, and a Needs you tab is headed by day. A separate Bot answered tab is in there too, and a lone “ok” or “thanks” does not reopen a chat. On a copy of the data that list goes from 53 to 11.

Smaller fixes

Merged: a paid eSIM order whose pickup keeps failing now offers support after 30 seconds instead of spinning for ten minutes. Why the pickups failed in the two orders that day is not proven.

Open, not merged: Base swaps get gas topped up for the swap’s own gas limit, because a wallet holding a little ETH got no top-up and the swap was refused. Screens that showed raw error text get plain copy in all 12 languages. Bitcoin activity shows cached fiat values right after a cold start.

A PR adding Liberland to the nuri.com country pickers was closed, not merged. I also reviewed a build pipeline change for our signing setup.