Add details about blockchain data source / syncing

[johnsBeharry]

Describe your content request

Hello, I would like to request additions to the guide around blockchain data sync times, especially in the daily spending context.

Link to the page

• https://bitcoin.design/guide/daily-spending-wallet/

Suggestions

1. Create a list of methods of getting blockchain data
2. Discuss if it is inline with our design philosophies
3. Decide on the method of getting blockchain data for the reference design
4. Update the relevant pages and make additions where necessary
5. PROFIT!

Additional context This topic came up while discussing the Privacy section with Tor causing payment friction and UX problems. This is especially relevant in places where there might be slower, or intermittent connections.

Content guidelines If you're a contributor looking to tackle the issue, you can preview our content guidelines.

[Bosch-0]

Agree we need content around this.

This would be most suited for the first use section which is when the sync / connection UX is encountered for the first time @GBKS. For the daily spending wallet I would focus on Neutrino + SPV and we can go over Tor in the privacy page when we get around to updating that. From experience with Zeus, Tor has major UX problems and should be a more advanced thing and not pushed on the average user too hard.

Create a list of methods of getting blockchain data

We have this in the node section of the guide, we could link off to this from the reference design rather than go into technical details there: https://bitcoin.design/guide/how-it-works/nodes/