Glacier is a protocol for secure cold storage of bitcoins. https://glacierprotocol.org
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.
Thank you. I also plan to use Glacier and I find it superior to everything else in terms to security, but given that the current version is unusable, I have been doing my own cleanup + refactoring so I can actually use it. I am keeping my version here: https://bitcoinfacts.github.io/glacierprotocol.github.io/ It also includes some of your changes. I will consider adding your PSBT changes next. Any reason for the specific Bitcoin Core version 0.19.0.1 (instead of version 22.0) ?
1 reply
Yes, you found #80 which is needed for 0.21 due to API changes. 22.0 makes another change that breaks GlacierScript, which I haven't tried to fix yet.
Glacier uses Bitcoin Core only for offline signing on the quarantined laptops. It won't see any blockchain, or be connected to the Internet, so I don't know of any reason that continuing to use Glacier with an older version of Bitcoin Core would cause any problems or security weaknesses.
I think I know the issue you're referring to. After version 22.0, we have to replace the "addresses" field with "address" in the "get_utxos()" function because of this change: bitcoin/bitcoin#20286. Correct?
Hi all - (if anyone sees this!) I've been working to keep Glacier alive. I've made some updates and fixes to both the documentation and script. The result is hosted here: http://www.glacierbf.org/ If anyone is interested, I can share a list of all the changes. Hopefully, someday we can merge some of these changes back into the main repo which is currently outdated/not working. Any feedback is of course welcome. Thanks!
Thank you for your efforts to keep Glacier working.
I assume you're aware of my fork (though I haven't done any work on the document): https://github.com/bitcoinhodler/GlacierProtocol
@bitcoinhodler Yes, a lot of my changes are based on your fork, except for the PSBT part. Thank you for leaving a comment! I replied: https://github.com/bitcoinfacts/GlacierProtocol/commit/d58992f6789438297c9248b5a367b4474b502fdf#commitcomment-64458524
I didn't change to use descriptor wallets (yet); I just changed the call to createwallet so it will still create a legacy wallet
1 reply
I've made some more changes to my Glacier fork for compatibility with the upcoming Bitcoin Core 24. Most have to do with test system changes, but at least this change is critical: bitcoinhodler/GlacierProtocol@5406c9f
I've also started porting the wallet usage to use the new descriptor wallets, since legacy wallets will be unsupported within a year or two.