Cookbook

Bitcoin Core:

• Jon Atack - How to compile Bitcoin Core and run the unit and functional tests
• Jon Atack - How to Contribute Pull Requests to Bitcoin Core
• Jon Atack - How to review pull requests
• Jon Atack - Stoic thoughts from Marcus Aurelius
• Bitcoin Core on Ubuntu with Extras
• BlocSoc IITR - All about Bitcoin Core
• Bitcoin.org - Running a full node
• Stadicus - Beginner’s Guide to ️Lightning️ on a Raspberry Pi
• Luke Dahjr - How to securely install Bitcoin
• StopAndDecrypt - A Complete Beginners Guide to Installing a Bitcoin Full Node on Linux (2021 Edition)
• StopAndDecrypt - Running Bitcoin & Lightning Nodes Over The Tor Network (2021 Edition)
• StopAndDecrypt - A Complete Beginners Guide to Installing a Lightning Node on Linux (2021 Edition)
• Chaincode Labs - Study guide
• Onboarding to Bitcoin Core
• Andreas Antonopolous - Mastering Bitcoin
• Darthcoin - How to get started with a Umbrel Bitcoin / LN Node
• Configurazione Electrs per accesso remoto su TOR
• Restore a Bitcoin blockchain backup copy to a new installation
• TOR support
• Raspibolt 3 - Bitcoin and lightning node
• MiniBolt - A DIY Bitcoin & Lightning node

Bitcoin Knowledgbase:

• Learn me a bitcoin
• Bitcoin Wiki
• Bitcoin Talk
• Learning Bitcoin from the Command Line
• Bitcoin subreddit
• ArmantheParman’s FREE Guides
• Alberto De Luigi - Debunking delle più comuni critiche a Bitcoin
• Alberto De Luigi - 101 cose che non sapevi su Bitcoin

Lightning:

• Managing lightning node
• Zeus LN Node - Advanced Usage
• The Lightning channels recap
• Alberto De Luigi - Guida completa al wallet Bitcoin, con Lightning Network
• Alberto De Luigi - Lightning network
• Alberto De Luigi - Bitcoin e adozione di massa: cosa (e quanto tempo) manca a Lightning Network
• Lightning labs - Loop

Blokchain technologies:

• James D'Angelo - Bitcoin 101 - Elliptic Curve Cryptography

Stats & charts:

• Protocol statistics
• checkonchain charts

Dev Blog:

• Bitcoin Stack Exchange
• Delving Bitcoin
• Bitcoin Optech
• bitcoindev mailing list
• Blog Loïc Morel

Bitcoin Privacy:

• KYCP.org - Knowing Your Coin Privacy
• Coin control

Bitcoin Wallet:

• Wallet recovery
• Ian Coleman Mnemonic Code Converter
• Vanity address
• How to Design Schnorr Signatures
• Transaction Size Calculator
• Manually Creating and Signing a Bitcoin Transaction

Bitcoin Meetup:

• Bitcoin lighthouse

Blokchain podcast:

• Nodesignal Podcast

Bitcoin as asset:

• Jesse Myers - Asset DNA: The Diverging Performance of Store-of-Value Assets
• Jesse Myers - Increasing Scarcity: Bitcoin's Value Appreciation Engine

Bitcoin app:

• Timechain Calendar

Bitcoin games:

• BTC treasure hunt
• BTC Puzzle

Bitcoin Wallet:

HD wallet key identifier (path)

HD wallet key identifier (path) Keys in an hardware wallet are identified using a "path" convention, with each level of the tree separated by a slash (/) character. Private keys derived from the master private key start with "m." Public keys derived from the master public key start with "M." Therefore, the first child private key of the master private key is m/0. The first child public key is M/0. The second grandchild of the first child is m/0/1, and so on. The "genealogical tree" of a key is read from right to left, until you reach the master key from which it was derived. For example, identifier m/x/y/z describes the private key that is the z-th child of the parent private key m/x/y, which is the y-th child of the parent private key m/x, which is the x-th child of the parent master private key m.

Hardware wallet path examples

HD path	Key described
m/0	The first (0) child private key from the master private key (m)
m/0/0	The first (0) child private key from the first child (m/0)
m/0'/0	The first (0) normal child from the first hardened child (m/0')
m/1/0	The first (0) child private key from the second child (m/1)
M/23/17/0/0	The first (0) child public key from the first child (M/23/17/0) from the 18th child (M/23/17) from the 24th child (M/23)

BIP-44 specifies the derivation path structure as consisting of five predefined tree levels:

m / purpose' / coin_type' / account' / change / address_index

• The second-level coin_type specifies the type of cryptocurrency coin, allowing for multicurrency HD wallets where each currency has its own subtree under the second level. For example, for Bitcoin it is m/44'/0'.
• The third level of the tree is account which allows users to subdivide their wallets into separate logical subaccounts, for accounting or organizational purposes. For example, an hardware wallet might contain two bitcoin accounts: m/44'/0'/0' and m/44'/0'/1'. Each account is the root of its own subtree. Changing the value for account you can generate as many wallets as you wish, for example:

m/84'/0'/0'/0
m/84'/0'/1'/0
m/84'/0'/2'/0
m/84'/0'/94982'/0

• On the fourth level, change, an hardware wallet has two subtrees, one for creating receiving addresses and one for creating change addresses. Note that whereas the previous levels used hardened derivation, this level uses normal derivation. This is to allow this level of the tree to export extended public keys for use in a nonsecured environment. Usable addresses are derived by the hardware wallet as children of the fourth level, making the fifth level of the tree the "address_index." For example, the third receiving address for bitcoin payments in the primary account would be M/44'/0'/0'/0/2.

Markdown & Readme file in Github and beyond

Hot to setup a readme file in Github:

• https://guides.github.com/features/mastering-markdown/
• https://guides.github.com/features/wikis/#creating-a-readme

How to setup a web page in Github:

• https://pages.github.com/

How to create a GitHub Pages site with Jekyll:

• https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll