Thingies
This commit is contained in:
parent
ac14d36f3e
commit
9a3c5403a5
7 changed files with 289 additions and 0 deletions
28
Drama Upgrade Umbrel to 5.md
Normal file
28
Drama Upgrade Umbrel to 5.md
Normal file
|
|
@ -0,0 +1,28 @@
|
|||
|
||||
I'm upgrading from Umbrel 0.4.18 to Umbrel 5.
|
||||
|
||||
# Steps
|
||||
|
||||
|
||||
## Backing things up
|
||||
|
||||
I'm scared shitless about this one, so I'll back pretty much everything except the Bitcoin and Electrum large databases.
|
||||
|
||||
Data sizes:
|
||||
- Total umbrel folder: 614GB
|
||||
- Bitcoin dir: 570GB
|
||||
- electrs dir: 40GB
|
||||
|
||||
`rsync -avh --info=progress2 --exclude bitcoin --exclude electrs /media/data_disk/umbrel/ /media/backup20230206`
|
||||
|
||||
Okay, that was fast, nice and easy. I should probably start doing that more often.
|
||||
|
||||
## Venturing into the update
|
||||
|
||||
I'm simply gonna try to let Umbrel update and pray.
|
||||
|
||||
Okay, it took a while and it ends up in the exact same version after restarting. What the fuck. Classic umbrel.
|
||||
|
||||
I've found this guide: https://github.com/getumbrel/umbrel/issues/1516
|
||||
|
||||
That didn't do the trick either. It says successful on the console but then when it starts it's still in 0.4.18.
|
||||
4
Installing BOS.md
Normal file
4
Installing BOS.md
Normal file
|
|
@ -0,0 +1,4 @@
|
|||
I'm going to try to install balance of satoshis.
|
||||
|
||||
I'm following the instructions here: https://plebnet.wiki/wiki/Umbrel_-_Installing_BoS
|
||||
|
||||
14
Textos para usuarios de Banky.md
Normal file
14
Textos para usuarios de Banky.md
Normal file
|
|
@ -0,0 +1,14 @@
|
|||
|
||||
- Como montar la wallet
|
||||
- Descargar bluewallet
|
||||
- Crear una nueva wallet
|
||||
- En el menu de crear wallet, seleccionar la opcion de importar
|
||||
- Escanear el QR
|
||||
- Listo para usar
|
||||
|
||||
- Algunos disclaimers
|
||||
- Yo custodio la pasta. Si la lio, los fondos se podrian perder. Pero yo perdere mas, asi que puedes contar con que me esforzare en que no pase. Pero puede pasar.
|
||||
- No hace falta que hagas ningun backup ni guardes nada. Si borras bluewallet o pierdes el movil, avisame y volveremos a montar la cartera. El dinero seguira alli.
|
||||
- Esta pensado para transacciones "pequeñas". Si intentas mandar cantidades mayores de 200€, no siempre funcionara. Si intentas mandar cantidades mayores de 100€, algunas que otra vez fallará. Por debajo de 100€, funcionará el 99,9% de las veces.
|
||||
- Si alguna vez preves recibir mucho dinero (>1000€) avisame porque puede necesitar alguna accion por mi parte.
|
||||
- A nivel de privacidad: yo puedo ver en cualquier momento tu balance y tus transacciones. No tengo intencion de hacerlo, pero puedo.
|
||||
36
bitbox unboxing.md
Normal file
36
bitbox unboxing.md
Normal file
|
|
@ -0,0 +1,36 @@
|
|||
|
||||
I'm unboxing the Bitbox02 Bitcoin-only edition.
|
||||
|
||||
I have plugged it into the USB-C port of Oli and I am downloading the bitbox app v4.35.0 from their webpage.
|
||||
|
||||
The app is sleek. The first thing it tells me to do is to install some firmware. Done.
|
||||
|
||||
I was placing the Bitbox upside down in the USB-C. Modern problems, this stuff didn't happen with USB-A
|
||||
|
||||
I get a code shown in both the bitbox and the app and get asked to confirm they match. They do. I tap on the bitbox to proceed. The hidden buttons thing is funny.
|
||||
|
||||
Now I can choose if I want to create a wallet or import an existing one. I'll create a new set of keys.
|
||||
|
||||
I need to give the bitbox a name.
|
||||
|
||||
I'm now going to set a password on the bitbox. Wow, I love the buttons thingy. Never seen an interface like this.
|
||||
|
||||
I get a few warning messages on how the backup is important as hell. Yep yep yep.
|
||||
|
||||
I must confirm the date. Now the backup is created.
|
||||
|
||||
And done. I guess my seedwords are the in the backup? I guess these guys would rather trust people storing the SD card than the words in plain sight. I'll have to read the SD card to check what is inside.
|
||||
|
||||
|
||||
---
|
||||
|
||||
Now I'm going to try and create a Wallet with Sparrow.
|
||||
|
||||
Okay, this is important. To ensure that Sparrow can read the wallet, you must:
|
||||
- Connect the Bitbox.
|
||||
- Open Sparrow.
|
||||
- Unlock the Bitbox with the password.
|
||||
|
||||
Okay, creating the wallet was easy. I can also see that both the Bitbox app and Sparrow use the same derivation path by default (m/84'/0'/0'), so the same addresses show up in both apps.
|
||||
|
||||
Now I just need to receive and send some sats to test it out.
|
||||
206
ideas_on_multisig.md
Normal file
206
ideas_on_multisig.md
Normal file
|
|
@ -0,0 +1,206 @@
|
|||
# Ideas on multisig
|
||||
|
||||
After accumulating for months (and years) during the current winter market, I have progressively felt more and more the responsibility of successful self-custody on my shoulders. As of today, with our current holdings, if a few or all the important wallets were compromised or lost, we would experience a complete and utter financial catastrophe. And I can't allow that to happen.
|
||||
|
||||
I have know for some time now that the next level of security would be a multisignature wallet, but I have avoided tackling it out of laziness and because I thought it would be terribly complicated. The other day I watched a video from BTC sessions on the Sparrow wallet, mainly due to having heard a lot of people talking about this wallet lately. As the video passed, I kept thinking that the wallet is just as good as any other. But then, when I reached the multisig section, I was amazed. It was so damned simple, clean and obvious. After watching this, I decided it was time to get responsible and implement a multisig scheme to store our funds.
|
||||
|
||||
## What I have today
|
||||
|
||||
Right now I have a mess of wallets. This is the current inventory:
|
||||
|
||||
1. Saylor
|
||||
2. Palanca
|
||||
3. Bisq cold
|
||||
4. Umbrel
|
||||
5. Bisq hot
|
||||
6. Tainted
|
||||
7. Saylor bait
|
||||
8. Futurible Antonio MC
|
||||
9. Futurible Ana y Scot
|
||||
10. Arya y Unai
|
||||
11. Gala Wisselink
|
||||
|
||||
Wallets 4, 5, 6 and 8 will remain untouched.
|
||||
Wallet 7 will be outdated, I'll mix the coins back with the main saylor because I'm happy with the bait experiment and I don't want to have to keep a separate wallet anymore.
|
||||
Wallets 9, 10 and 11 should be moved to an alternative version that does not require using colki so I don't have to go fucking around with different seeds constantly since that is most definitely a bad idea.
|
||||
Wallets 1, 2 and 3 should be merged into the arctic.
|
||||
|
||||
|
||||
## A draft on how I could clean up the mess
|
||||
|
||||
Let's assume I had 3HW wallets. My Coldcard MK3, a BitBox02 and a Trezor One.
|
||||
|
||||
That allows me to have:
|
||||
- One wallet associated with each HW seed.
|
||||
- Three possible 2-of-2 multisigs.
|
||||
- One 2-of-3 multisig.
|
||||
|
||||
So, how to store safely? The devices themselves are not that dangerous. They all use some pin based security that makes them useless if they fall in the hands of adversaries. As long as this is not coupled with a physical attack on me to force me to give the pin away, I shouldn't be worried.
|
||||
|
||||
Now, for the seed backups: this needs more thought. Effectively, 2 of the seeds plus the 3 master public keys are the required to spend from the wallet. Thus, to enjoy the benefits of multisig to the fullest, no single storage location should contain everything that is necessary to spend from the multisig wallet.
|
||||
|
||||
Besides this, I can always have a single seed holding several "virtual" wallets just by keeping a separate accounting in gnucash. This simplifies management a lot, but also puts all the eggs in one basket. But then again, it's sort of a titanium basket...
|
||||
|
||||
### Temperature Policy
|
||||
|
||||
- Hot wallets are hot and used to play around. No fucks given.
|
||||
- Snow wallets are Umbrel and Bisq. They have a good chunk of money to reduce the need to go to the arctic.
|
||||
- The arctic is the long-term, no touchy vault.
|
||||
|
||||
### Keys and Locations
|
||||
|
||||
There are three keys: colki, biti and trevor.
|
||||
There are four physical locations: Tibidabo, Argentina, Matagalls and Maestrazgo.
|
||||
There are two virtual locations: Mitre and Redmond.
|
||||
|
||||
|
||||
| Location | Coldcard (Malasaña) | Coldcard Seed | Bitbox02 (Daoiz) | Bitbox02 Seed | Trezor (Velarde) | Trezor seed | Sparrow Backup |
|
||||
| ---------- | ----- | ---------- | ---- | --------- | ------ | ----------- | -------------- |
|
||||
| Tibidabo | X | X | | | | | |
|
||||
| Argentina | | | X | X | | | |
|
||||
| Matagalls | | X | | | X | X | |
|
||||
| Maestrazgo | | | | X | | X | |
|
||||
| Mitre | | | | 1 | | 2 | |
|
||||
| Redmond | | | | 2 | | 1 | |
|
||||
| Poco | | | | | | | X |
|
||||
|
||||
|
||||
The Tibidabo package contains:
|
||||
- Open use Coldcard
|
||||
- Tamper proof bag with:
|
||||
- Coldcard seed
|
||||
- USB with Sparrow wallet export, including all XPUBS
|
||||
|
||||
The Argentina package contains:
|
||||
- Open use Bitbox02
|
||||
- Tamper proof bag with:
|
||||
- Bitbox02 seed
|
||||
- USB with Sparrow wallet export, including all XPUBS
|
||||
|
||||
The Matagalls package contains:
|
||||
- Tamper proof bag with:
|
||||
- Trezor one
|
||||
- Trezor one seed
|
||||
- Coldcard seed
|
||||
- USB with tails
|
||||
- Instructions in case of friendly opening
|
||||
|
||||
The Maestrazgo package contains:
|
||||
- Tamper proof bag with:
|
||||
- Bitbox02 seed
|
||||
- Trezor one seed
|
||||
- USB with tails
|
||||
- Instructions in case of friendly opening
|
||||
|
||||
|
||||
|
||||
Migration plan:
|
||||
|
||||
- Create multisig
|
||||
- ~~Create malasana key set~~
|
||||
- ~~Create wallet in sparrow~~
|
||||
- ~~Backup wallet skeleton~~
|
||||
- Back it up partly
|
||||
- ~~Create Tibidabo package and store~~
|
||||
- ~~Create Argentina package and store~~
|
||||
- Test ride with some money
|
||||
- ~~Create changes in accounting~~
|
||||
- ~~Play around with a couple of transactions~~
|
||||
- Load bisq cold
|
||||
- Load
|
||||
- Remove backup from home
|
||||
- Remove backup from argentina
|
||||
- Send monthly DCA
|
||||
- ~~Retrieve part of it ~~
|
||||
- Back it up fully
|
||||
- ~~Create Maestrazgo package~~ and store
|
||||
- ~~Create Matagalls package and store~~
|
||||
- Finish the transfer
|
||||
- Move saylor
|
||||
- Load
|
||||
- Remove backup from home
|
||||
- Remove backup from argentina
|
||||
- Remove border backup
|
||||
- Move palanca
|
||||
- Load
|
||||
- Remove backup from home
|
||||
- Remove backup from argentina
|
||||
- Remove border backup
|
||||
- Remove old stuff
|
||||
- Remove bisq cold keys
|
||||
- Remove palanca keys
|
||||
- Remove saylor keys
|
||||
- Train the team
|
||||
- Hold session 1
|
||||
- Hold session 2
|
||||
- Perform transfer simulation 1
|
||||
- Perform transfer simulation 2
|
||||
|
||||
|
||||
## Status check on September 2023
|
||||
|
||||
The full plan for the multisig was not completed and we are in a shaky half-assed state that I don't like. I'm going to:
|
||||
- Describe how I would like the end state to be.
|
||||
- Assess how things are now.
|
||||
- Define the steps to go from as-is to to-be.
|
||||
|
||||
### Target state
|
||||
|
||||
- Three locations with the following contents:
|
||||
- Tibidabo Package
|
||||
- Accessible coldcard
|
||||
- Coldcard seed
|
||||
- Sparrow file backup
|
||||
- Argentina Package
|
||||
- Accessible bitbox
|
||||
- Bitbox seed
|
||||
- Sparrow file backup
|
||||
- Fren Package
|
||||
- Trezor
|
||||
- Trezor seed
|
||||
- Sparrow file backup
|
||||
- Digital copies
|
||||
- Keychain
|
||||
- Stored in Onedrive
|
||||
- Encryption key in Bitwarden
|
||||
- Descriptor
|
||||
- Stored in Onedrive
|
||||
- Encryption key in Bitwarden
|
||||
|
||||
Additional assets
|
||||
- Written description + instructions in case of death
|
||||
|
||||
Operating procedures
|
||||
- Smoke test transaction once every quarter
|
||||
- Training session once every six months
|
||||
- Check on fren once a year
|
||||
|
||||
|
||||
### How things are now
|
||||
|
||||
- Tibidabo package exists
|
||||
- Argentina package exists
|
||||
- Fren package exists but is stored at tibidabo.
|
||||
- Digital copies do not exist
|
||||
- Written description + instructions do not exist
|
||||
|
||||
### Steps
|
||||
|
||||
1. ~~Write description and instructions~~
|
||||
1. ~~Prepare a Tails USB with persistence~~
|
||||
2. ~~Write and encrypt~~
|
||||
3. ~~Store a digital copy of instructions in onedrive~~
|
||||
4. ~~Store in two thumbdrives for heirs~~
|
||||
5. ~~Deliver to heirs and train them~~
|
||||
2. ~~Assemble all packages in one location~~
|
||||
3. ~~Create digital copies and store them~~
|
||||
1. ~~Write the seeds in different files~~
|
||||
2. ~~Encrypt them with PGP key~~
|
||||
3. ~~Upload to onedrive~~
|
||||
4. ~~Review contents of all packages~~
|
||||
5. ~~Store Tibidabo package~~
|
||||
6. ~~Store Argentina package~~
|
||||
7. ~~Store Fren package~~
|
||||
8. ~~Inform confidants and share description and instruction files~~
|
||||
9. ~~Set operating procedure calendar reminders~~
|
||||
10. Store mystery package
|
||||
BIN
matagalls_storage.jpg
Normal file
BIN
matagalls_storage.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 4.5 MiB |
1
millennium_vault_backup
Normal file
1
millennium_vault_backup
Normal file
|
|
@ -0,0 +1 @@
|
|||
U1BSVzEz5Hv6tZ4PPzc0YH905+xtQklFMQJbN0qbaUEE2JvIOoZzGWOnwDENLVBxF4S7LmXrakpBusd8iWClNOJBzjtfCvSRAx9g2i496MSX/lF8JwWJ52OGUh2f3DPgZGfSUdNhpOMAfysmBS4l90a6ha1ylNVOG2KL6EY+/B0HBwbG1wv7AnFHPFYmaCaPPzaROFtb+3KJ5v9iukLLV5Y88247xUdCGUwuMauxeZsfY2ljPtQFzDf2U9CxzdEpIKUKCTry3tulSFaIWhd1yEilPPaVezXnoEu8Dbfgos2D+yXk+r4Oupi+UwNHP2ABQTSnFy+Z4F/OkZbkKeZEFmPEtACob/O5SBpEIEgGbaOFZNh6WQYAVdnA+PbLciZMyO+OjnGEtpypUPO0Nfw1pBj4gXmXIfh5O5g5MfcjWJR0kl0fzQM8xHUaESMWzsTS3aof5yaP724N6WSN0lx0yniYxQ3RL2nXbMyoblyr412b+Eb2LEGS5PRAMBtYRChXMelAMdENoI4cfEJ3mJ/6X5AZOAIhfFSPu66jCXWYrMLNXpJvesFN3bkaChx/5T6tR+c7poRAovldkGZm1UUiHqI0aB1WYz0l27fYqDvEdRRxGpIqHfLQAuoldB7f4D4JkTMLRg5wCcRLtA1TaeH4fdll/jvjzw1osYgRFlFZvo/Dn8uju1//oyMUGDf95TE7VJ33wEqB7n57rE3eRewF2T89vJjL1t0VG16JNQedNYN9diQagUzcMcz7d8KRmTxVg0PqH5HvvSgksGW2mCiHWNjdIX/AZLazorc7kRlH6TavnCWyrE2B2cIheHbKbk+k0tI0pXrlq+lYvjfWwP8Q2spK5DOQjHg3hjygpDnovgCTyQzo2O2GCzUaGuJKtDLQ6Y6Zc6ttG6DUKF2BgZ98epi9kSpzUbT6ZJm6zU7VMDzp+kBmTeP7wluL7JT5GZPF0n/llmfGJe47ZOfQplS44x6zVOwNP9B1gPw4qNDEz2auIv3G1xJeY4E+ErukuJ0l3I1Gk8nA1lIKA39RX9xVX3/lmK4GN8d3ry2gQFH/DxqpabcKGrJ4aaKUjyucd2mF/9NbXy8yUQMNqNuJXUlZ11v/XhDZ03yxs8g=
|
||||
Loading…
Add table
Add a link
Reference in a new issue