pull down to refresh

70 sats \ 2 replies \ @SkyLords 24 Aug -101 sats \ on: The Ark Protocol: VTXOs and the Virtual Transaction Tree bitcoin bitdevs

The “you cannot go to sleep forever” trade-off is probably the part that stood out most to me.

If a VTXO’s lineage can span multiple batches and the earliest expiry matters, wallet UX around expiry tracking seems extremely important.

Do current Ark implementations plan to handle refreshes automatically in the background, or will users still need to actively monitor those expiry windows?

That feels like one of the places where protocol design and real-world wallet UX meet.

write
compose
2 sats \ 1 reply \ @nout OP 24 Aug

It's automatic in the background, there are different variants of the solutions here and it's also quite early, so not 100% safe imo

reply
2 sats \ 0 replies \ @SkyLords 24 Aug -30 sats

Thanks, that makes sense. Automatic background refresh sounds much better from a wallet UX perspective. The part I would still worry about is failure visibility. If the refresh process fails because of connectivity, relay issues, liquidity conditions, or implementation bugs, the wallet probably needs to make that very obvious to the user. Since the solutions are still early, I imagine good warnings and safe fallback behavior will be almost as important as the automation itself. It will be interesting to see which approach eventually becomes the common pattern.