Create a page about node connection options

[GBKS]

Every (well, almost every) Bitcoin application at some point needs to connect to the Bitcoin network to retrieve data or publish transactions. This can happen in different ways, each one with advantages and disadvantages. I think it would be helpful to lay these out, so designers and developers can choose the one that is most appropriate for their product.

This stems from a Twitter/Slack conversation a few days ago that led me to create this image (Figma):

[GBKS]

Existing content to tie in is on the software overview and hardware overview pages, as well as the upcoming glossary.

Some additional thoughts:

• Differentiate trusted and untrusted (white and black respectively in the image)
• "Multiple third-party nodes" is for mobile use via BIP 157/158 for low data usage and decent privacy
• Consider Lightning
• Consider implementation effort as well as user effort
• Consider appropriate use cases for each option

[Bosch-0]

Keen to take this on, I was thinking this would be suitable within the Onboarding section of the Guide @ConorOkus @pavlenex

[Bosch-0]

I think there is enough content for there to be a Nodes chapter. Below is a rough outline of the content it would cover:

This section covers best design practices for setting up, using and managing a Bitcoin Full node

• Node types
  • Full nodes
  • Light nodes
    • SPV
    • API ?
    • Neutrino
• Setting up a node
  • Desktop node
  • Hardware node
  • Hosted (cloud) node
• Node management
  • Bootstrapping
  • Archive
  • Pruned
  • Storage
  • Bandwidth
  • Privacy
  • Mining mode
• Connecting wallets
• Applications

Misc

• Add details about ‘Connecting to the Bitcoin Network’ somewhere in onboarding section.

Eventually lightning node content would also fit in here.