Skip to content
BranchesTags

Repository files navigation

Cookbook

A curated list of awesome Bitcoin resources.

Bitcoin Core:

A curated list of awesome resources for Bitcoin Core.

Bitcoin Knowledgebase:

Resources for understanding how the Bitcoin protocol works.

Lightning:

Resources for understanding how Ligthning network works.

Bitcoin mining

Resources on Bitcoin mining.

Blokchain technologies:

Stats & charts:

Statistics and charts on Bitcoin network.

Dev Blog:

Prominent blog for developers.

Bitcoin Privacy:

Resources on Bitcoin privacy.

Bitcoin Wallet:

Resources on Bitcoin wallets.

Bitcoin Meetup:

Blokchain podcast:

Bitcoin as asset:

Bitcoin app:

Bitcoin games:

  • Funny games based on Bitcoin.*

Best practices against scams:

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:

How to setup a web page in Github:

How to create a GitHub Pages site with Jekyll:

About

Trader based on google finance data and google spreadsheet

Resources

Readme
GPL-3.0 license
Activity

Stars

0 stars

Watchers

1 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages