mirror of
https://github.com/openoms/bitcoin-tutorials.git
synced 2025-12-19 04:54:18 +01:00
backup: formatting
This commit is contained in:
@@ -9,8 +9,8 @@ Can be thought of as a physical 2-of-3 multisig solution.
|
||||
## [JoinMarket](joinmarket.md)
|
||||
## [LND](lnd.md)
|
||||
|
||||
---
|
||||
### Electrum Wallet seed as a passphrase
|
||||
|
||||
A well proven way to generate a random 12 word is to create a new wallet seed in [Electrum Wallet](https://electrum.org/#download).
|
||||
To use Electrum boot [Tails](https://tails.boum.org/) (ideally offline) or [download and verify the wallet](https://electrum.org/#download) on an existing system.
|
||||
|
||||
|
||||
@@ -8,8 +8,8 @@ but needs to be written in the CC every time the wallet is opened.
|
||||
|
||||
The ColdCards should be stored uninitialized, best to be freshly acquired in the tamper resistant package from the manufacturer (<https://coldcardwallet.com>) to minimize the risk or evil-maid and supply-chain attacks.
|
||||
|
||||
---
|
||||
### Components grouped together by the requirement for a full restore
|
||||
|
||||
#### Full backup 1
|
||||
* Seed mnemonic (12/18/24 words)
|
||||
* Passphrase
|
||||
@@ -18,8 +18,8 @@ The ColdCards should be stored uninitialized, best to be freshly acquired in the
|
||||
* Backup password (12 words)
|
||||
* Passphrase
|
||||
|
||||
---
|
||||
### Packages for a 2-of-3 setup
|
||||
|
||||
#### Location 1
|
||||
- Seed mnemonic (12/18/24 words)
|
||||
- Backup password (12 words)
|
||||
@@ -31,4 +31,4 @@ The ColdCards should be stored uninitialized, best to be freshly acquired in the
|
||||
|
||||
#### Location 3
|
||||
- Passphrase (BIP39)
|
||||
- Backup password (12 words)
|
||||
- Backup password (12 words)
|
||||
@@ -2,8 +2,8 @@
|
||||
Documentation on JoinMarket wallet recovery: <https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/master/docs/USAGE.md#recover>
|
||||
When the wallet is restored connected to a bitcoin node with which it was not previously used, will need to rescan the blockhain to register the transactions and look up the wallet balance. Having the wallet birthday helps to do the rescan only from when the wallet was created, but it is not absolutely necessary.
|
||||
|
||||
---
|
||||
### Components grouped together by the requirement for a full restore
|
||||
|
||||
#### Full backup 1
|
||||
* Seed (12 words)
|
||||
* Passphrase (BIP39)
|
||||
@@ -11,8 +11,8 @@ When the wallet is restored connected to a bitcoin node with which it was not pr
|
||||
* Wallet file (.jmdat)
|
||||
* Encryption passphrase
|
||||
|
||||
---
|
||||
### Packages for a 2-of-3 setup
|
||||
|
||||
#### Location 1
|
||||
- Seed (12 words)
|
||||
- Wallet file (.jmdat)
|
||||
@@ -26,4 +26,4 @@ When the wallet is restored connected to a bitcoin node with which it was not pr
|
||||
#### Location 3
|
||||
- Seed (12 words)
|
||||
- Encryption passphrase
|
||||
- First tx blockheight (optional)
|
||||
- First tx blockheight (optional)
|
||||
@@ -2,8 +2,8 @@
|
||||
Notes on LND wallet recovery: <https://github.com/lightningnetwork/lnd/blob/master/docs/recovery.md>
|
||||
Notes on LND seed format (different from Bip39 or Electrum): <https://github.com/lightningnetwork/lnd/tree/master/aezeed>
|
||||
|
||||
---
|
||||
### Components grouped together by the requirement for a full restore
|
||||
|
||||
#### Full backup 1
|
||||
* Seed (24 words)
|
||||
* Cypher Phrase (passphrase)
|
||||
@@ -16,8 +16,8 @@ Notes on LND seed format (different from Bip39 or Electrum): <https://github.com
|
||||
* Wallet Unlock Password
|
||||
* include logins and/or the SSH password to allow access to the node
|
||||
|
||||
---
|
||||
### Packages for a 2-of-3 setup
|
||||
|
||||
#### Location 1
|
||||
* Seed (24 word)
|
||||
* Static Channel Backup (channel.backup)
|
||||
@@ -30,4 +30,4 @@ Notes on LND seed format (different from Bip39 or Electrum): <https://github.com
|
||||
#### Location 3
|
||||
* Seed (24 words)
|
||||
* Static Channel Backup (channel.backup)
|
||||
* Wallet Unlock Password
|
||||
* Wallet Unlock Password
|
||||
Reference in New Issue
Block a user