experimental: events

[reez]

Should think about how/where/why to use the new events api introduced in 2.2 https://github.com/bitcoindevkit/bdk_wallet/releases/tag/wallet-2.2.0

[reez]

I think the right direction here is to add events at the BDKService boundary first, not thread raw WalletEvent through the whole UI.

bdk-swift already exposes Wallet.applyUpdateEvents(update:), so the first pass should be:

• use applyUpdateEvents in the sync/full-scan paths
• map WalletEvent into an app-local event type
• process events before persisting staged changes
• keep Kyoto progress/connectivity notifications separate

I would keep the initial integration conservative and still do broad balance/tx refreshes after relevant events, rather than trying to make every view fully event-driven immediately.

Main thing to watch out for: wallet refresh/state ownership is already a bit duplicated across WalletView, WalletViewModel, and ActivityListViewModel. If we add events on top of that without care, we’ll create even more overlapping refresh paths. So I’d treat event plumbing as the feature, and any state-centralization cleanup as a separate follow-up refactor.