Glacier is a protocol for secure cold storage of bitcoins. https://glacierprotocol.org
Good question. That comes from GlacierScript itself, specifically this code here: https://github.com/GlacierProtocol/GlacierProtocol/blob/bda9582eda7280f6b154d63eb1c5359ab76fe369/glacierscript.py#L635
Which, if compromised, could generate keys known to the attacker.
But in your view, have even the latest releases Of Glacier been reviewed thoroughly enough to support the idea that the code remains well-reviewed? I know many people reviewed and commented on earlier versions, but that enthusiasm from some of the other contributors dropped off over time. What would keep someone from slipping something malicious into the code now that not as many people are looking? Are all modifications to the code, however small, closely monitored?
You can look at the history of PRs to confirm this: https://github.com/GlacierProtocol/GlacierProtocol/pulls?q=is%3Apr+is%3Aclosed
For anyone who might have private keys stored in bank safe deposit boxes as part of their Glacier Protocol, here's something to consider - I was granted access to my safe deposit box yesterday while wearing a medical mask. I was never asked to remove the mask so that they could verify my identity. Granted, I did still have to show my ID and had to have the key to my box, but it was still a bit shocking. Any person with similar physical characteristics to me could have pulled this off if they had my ID and safe key. This helped me understand that bank safe deposit boxes aren't as secure as I once believed them to be.
I have tested GlacierScript with Bitcoin Core v0.20.0rc2 (upcoming release). No changes needed. (Although, thanks to bug #38, Glacier is broken anyway, and nobody seems to care.)
Guess I have to go through updating to the latest Bitcoin Core. Thanks for this https://gist.github.com/bitcoinhodler/8be823fae7b46e924caa594abdde3bd0 @bitcoinhodler you contribution is very much appreciated.
And thanks for pointing out issue #14, must be this. I'll test it later this week.
I've added a warning to my gist to be careful and do your own research. Don't blindly trust those instructions. They have not been reviewed by the wider Glacier community (if there is such a thing) and if I wanted to be malicious I could direct you to download a hacked Bitcoin Core that sends all your coins to me.
@hellosa-sa Not with its current release because this still uses Bitcoin Core 0.13.x. If you update the app USB following @bitcoinhodler‘s gist you‘ll be able to send to bech32 addresses. I tested this. https://gist.github.com/bitcoinhodler/8be823fae7b46e924caa594abdde3bd0
I've tested Glacier with the upcoming Bitcoin Core 0.21 release. We require changes to be compatible. I opened a new PR: GlacierProtocol/GlacierProtocol#80
This only affects creating new App USBs. If you already have App USBs, or if you use my gist (which installs Bitcoin Core v0.19.0.1) to create new App USBs, this does not affect you, and I know of no advantage to upgrading.
My glacier-psbt repo https://github.com/bitcoinhodler/glacier-psbt explains how to import a Glacier address into Bitcoin Core as a watch-only wallet. (It assumes you're comfortable with bitcoin-cli.)
Is it 'bitcoin-cli getrawtransaction "tx id"'
has anyone used more recent versions of ubuntu? alternatively, what about trying to get a specific update onto the permanently air-gapped hardware? My particular issue is I've got an inspiron 11 3000, and the trackpad driver doesn't work... it works for a second or two and then quits. luckily it's got 3 usb ports, so I could get a new wired usb mouse, but I hate the idea of having to use that and not being able to use the trackpad.
but that leads me to the second question of what if one were to need to load a newer version of bitcoin-core onto the air-gapped machine?
has anyone used more recent versions of ubuntu?
@SmeethRoger_twitter years ago I tried to update Glacier to use Ubuntu 18.04 (instead of 16.04) and found that the setup process required significant changes. On the setup PC, we download the Ubuntu ISO into ramdisk, then write it to the Q1 BOOT usb. Ubuntu got bigger between 16.04 and 18.04 and the 18.04 download wouldn't fit in the ramdisk anymore (on a 4GB laptop). I abandoned the project after realizing that.
You could conceivably copy any extra drivers needed onto the Q1 APP usb when you first create them, and add an extra step to the "Prepare Quarantined Workspaces" process to install that driver.
If you want a newer version of Bitcoin Core, you'd have to go back to the setup process and create new APP USBs. (No need to create new BOOT USBs.) But keep in mind that GlacierScript uses APIs in bitcoin-cli that sometimes change between versions, so changing the Bitcoin Core version might break GlacierScript. That's why I opened this issue: GlacierProtocol/GlacierProtocol#38
Also: Glacier Protocol is abandoned and broken. I wouldn't recommend anyone use it anymore.
@bitcoinhodler: So unfortunate that Glacier Protocol has been abandoned. I already bought all the hardware to use it before I dug a little deeper and saw that some steps need to be updated. Thank you so much for keep it updated for the past couple of years. I saw you've done the majority of the work 🙏 If I have a programming/technical background, I could probably still make it work using your steps, no?
:point_up: Edit: @bitcoinhodler: So unfortunate that Glacier Protocol has been abandoned. I already bought all the hardware to use it before I dug a little deeper and saw that some steps need to be updated. Thank you so much for keeping it updated! I saw you've done the majority of the work in past couple of years 🙏 If I have a programming/technical background, I could probably still make it work using your steps, no?
Yes, Glacier still works, if you use Bitcoin Core 0.19.0.1 via my gist (https://gist.github.com/bitcoinhodler/8be823fae7b46e924caa594abdde3bd0), the latest Glacier release for the GlacierScript software, and the older 0.91 PDF before the doc reformat screwed it all up in the newer releases.
I still use Glacier because I haven't found an HD multisig solution that's as hard-core on security.
In my fork that I use, I've added support for sequential signing using PSBTs. But this hasn't received any security review so I'd not recommend it to anyone else.