Skip to content

Releases: GlacierProtocol/GlacierProtocol

v0.94-beta

22 Apr 23:19
f851536
Compare
Choose a tag to compare

Release Notes:

Upgrade Guidance

  • v0.94 includes usage of new APIs introduced in Bitcoin Core v0.17, removing deprecated ones (signrawtransaction and getaddressesbyaccount) that were necessary for compatibility with v0.16.
  • This version is compatible with Bitcoin Core v0.18. Earlier versions are not.

Detailed Changes

  • Minor change to xor_hex_strings #45
  • Use new Bitcoin Core v0.17 APIs #50
  • Consolidate all bitcoin-cli and bitcoind calls into dedicated function #56
  • Add verbose flag -v to GlacierScript #58
  • Improve developer tests #60

v0.93-beta

19 Oct 01:53
d20454e
Compare
Choose a tag to compare

Release notes

Upgrade Guidance

  • v0.93 now creates Segwit (p2wsh-in-p2sh) addresses in the Deposit Protocol. This will make future withdrawals less expensive in terms of network fees.

    • New Glacier users do not need to do anything to take advantage of the cost savings.
    • Glacier users with deposits made to earlier versions of Glacier addresses may choose to upgrade to Segwit. With transaction fees so low right now, this would be a great opportunity to move to Segwit so that you are better prepared for higher fees in the future. In order to take advantage of the cost savings, the user needs to (1) purchase two new USB keys of two different brands; (2) construct new App USB keys with the new GlacierScript and Bitcoin Core; (3) execute the Deposit Protocol to create a new cold storage address; then (4) execute the Withdrawal Protocol on their previous cold-storage address to transfer their bitcoins to the new Segwit address.
  • v0.93 includes a fix for compatibility with Bitcoin Core v0.17.0. If you are creating new App USBs, you should use v0.93.

Detailed Changes

  • v0.93 adds support for Bitcoin Core 0.17. Any new App USBs created on or after October 16, 2018 (when the Ubuntu Bitcoin PPA was updated with v0.17.0) using an older version of Glacier will fail with GlacierScript errors during the Withdrawal Protocol and Deposit Protocol. Any App USBs created before that date will still work and are safe to continue using (excepting other errata).
  • Fixes a security false alarm (issue #36) that could occasionally occur during the Withdrawal Protocol.
  • Enables Segwit (p2wsh-in-p2sh) for lower-cost withdrawals

v0.92-beta

27 Feb 02:58
d833ea9
Compare
Choose a tag to compare

Errata

  • The cover page of the PDF is still titled version 0.91.
  • Deposit Protocol, Section III, step 2.a: The recommended size of the test deposit ($6) might be too small for today's transaction fees. We recommend a deposit sufficient to fund 1000 bytes of transactions; as of January 17, 2018, with a fee rate of 510 sat/B and $11185 USD/BTC this is a deposit of approximately $57. Fees have since declined, but the user is advised to check the current fee rate before making the test deposit.

Upgrade Guidance

  • v0.92 includes a fix for some withdrawal errors encountered in v0.91. If you encounter errors withdrawing in v0.91, you should upgrade to v0.92. You'll need to recreate your Quarantined App USBs with v0.92.
  • v0.92 includes a fix for compatibility with Bitcoin Core v0.16.0. If you are creating new App USBs, you should use v0.92.
  • v0.92 has no security improvements. Funds stored with earlier Deposit Protocols are perfectly secure.

Note that the PDF document did not change from v0.91, and is still titled v0.91 on the cover page.

Detailed Changes

  • v0.92 adds support for Bitcoin Core 0.16. Any new App USBs created on or after March 5, 2018 (when the Ubuntu Bitcoin PPA was updated with v0.16.0) using an older version of Glacier will fail with GlacierScript errors during the Withdrawal Protocol and Deposit Protocol. Any App USBs created before that date will still work and are safe to continue using (excepting other errata).
  • Fixes crash when unspent xact has native segwit outputs. If your Glacier wallet was funded using a transaction containing native Segwit outputs (such as the change output from an Electrum 3 Segwit wallet), previous versions of GlacierScript would crash when trying to withdraw.
  • Forces re-entry of fee rate when user declines fee confirmation prompt. Previous versions of GlacierScript erroneously recalculated using the same fee rate instead of prompting the user for a corrected rate.

v0.91-beta

30 Apr 21:12
Compare
Choose a tag to compare

Errata

  • Deposit Protocol, Section III, step 2.a: The recommended size of the test deposit ($6) might be too small for today's transaction fees. We recommend a deposit sufficient to fund 1000 bytes of transactions; as of January 17, 2018, with a fee rate of 510 sat/B and $11185 USD/BTC this is a deposit of approximately $57. Fees have since declined, but the user is advised to check the current fee rate before making the test deposit.
  • Funding your Glacier cold-storage address from a segwit-enabled wallet (e.g. Electrum 3) may result in unspendable funds. (Your funds are safe; Glacier v0.92 Beta fixes this and enables your funds to be spent.) To avoid this problem:
    • Create or recreate your App USBs using Glacier v0.92 Beta; or
    • Fund your Glacier address using a wallet that is not Segwit compatible; or
    • Send 100% of your wallet's funds to your Glacier address in a single transaction (so that no change output is created)

Upgrade Guidance

  • v0.91 includes workarounds for some withdrawal errors encountered in v0.90. If you encounter errors withdrawing in v0.90, you should upgrade to v0.91. You'll need to recreate your Quarantined App USBs with v0.91.
  • v0.91 has no security improvements. Funds stored with earlier Deposit Protocols are perfectly secure.

Detailed Changes

  • The protocol was incapable of properly handling raw unspent transactions past a certain length (workarounds are now in place for both issues):
  • QR codes cannot handle large raw unspent transactions; such transactions must be manually split into multiple QR codes and re-spliced.
  • With extremely large raw unspent transactions (over 4000 bytes), GlacierScript was incapable of processing them in v0.90.
  • Fixed minor errors in Setup Protocol for Windows machines
  • Updated Ubuntu release link (old link broke when it became not-the-latest Ubuntu release)
  • Added Errata section to website (for issues / fixes which haven't yet made it into an official release), and included protocol steps to check the Errata section.
  • Fixed various typos (thanks /u/dooglus)

v0.9-beta

30 Apr 21:13
Compare
Choose a tag to compare

Errata

  • Ubuntu 16.04.2 has been released, and the link to 16.04.1 in the protocol document has broken. Use http://old-releases.ubuntu.com/releases/xenial/ubuntu-16.04.1-desktop-amd64.iso instead of http://releases.ubuntu.com/xenial/ubuntu-16.04.1-desktop-amd64.iso.
  • Windows: Setup Protocol step IV.5.b.i is missing a space in the terminal command after "sha256".
  • Windows: Setup Protocol Section IV requires Windows Powershell, not a regular terminal/command line window
  • Windows: Instructions for opening Windows Powershell were incorrect. (Correct: Win-R, type "powershell", press Enter)
  • Some information (e.g. raw unspent transactions) are too long to be converted into a single QR code -- or the QR code may be such high resolution that some QR code readers may struggle to read it. In these cases, you will need to split the data into multiple QR codes, and splice them back together after decoding the QR codes. Be careful not to encode trailing spaces or newlines when splitting the data.

Changelog

  • Enabled HTTPS on website for improved security of protocol distribution
  • Added Windows support to Setup Protocol
  • Required the second Setup Computer to be “distinct” (e.g. preferably one not previously owned by the Glacier user) to minimize the chance of identical malware on both Setup Computers propagating to the quarantined environments (and generating an identical flawed key in both environments)
  • Revised online wallet section to describe a wider variety of market options