Keep Ark state per ASP, not just per wallet

Switching providers showed the previous server's balance and tried to resume
its in-flight board ("1 deposit confirming" against a server that had never
heard of it). A vtxo is only meaningful against the ASP that cosigned it, so
state must be scoped to both the wallet and the server.

- ark state keys gain a namespace derived from the ASP endpoint, so switching
  providers switches state and switching back restores it
- state is stamped with the server pubkey; on connect a mismatch is discarded
  rather than displayed. This also self-corrects the one-time adoption of
  pre-namespacing state, which can only guess which ASP it belonged to
- mergeArkStates refuses to fuse two servers' states, and the nostr sync
  snapshot carries (and filters on) the ASP it came from, so a device on a
  different provider can't inject foreign vtxos

Nothing is deleted: each ASP's state lives under its own key, and the legacy
key is left in place for whichever server rightfully claims it.

Co-Authored-By: Claude Fable 5 <[email protected]>

0 files changed, 0 insertions, 0 deletions