TREZOR: Bitcoin Gold’s codebase is incomplete

Trezor wallet makes a statement concerning Bitcoin Gold, claiming it will not support it yet
23 October 2017   1654

Days (or rather hours?) away from the Bitcoin hardfork, the crypto community is getting more and more concerned about Bitcoin Gold.

Now, Satoshi Labs, the makers of the hardware wallet TREZOR, make a statement about the upcoming Bitcoin Gold fork. The company claims that it will not support Bitcoin Gold yet.

Still, Trezor team highlights that if there are any Bitcoins held on TREZOR before the block, the customers will have the same Bitcoin Gold balance as their Bitcoin balance. 

In other words, Bitcoin Gold is an altcoin, using Bitcoin’s history similarly to the case of Bitcoin Cash. However, Bitcoin Gold does not launch immediately at the point when the chains diverge.


As for TREZOR (the device), it, in fact, supports Bitcoin Gold. According to the company, with TREZOR, you own your private keys (in form of the seed), therefore you have control over all of your coins, including forked coins. Yet, there are some obstacles.

Bitcoin Gold’s codebase is, at the moment of the writing, incomplete. Most importantly, it lacks replay protection. For this reason, TREZOR Wallet will not support Bitcoin Gold yet, as it would endanger your Bitcoins.


The TREZOR team, as well as Hong Kong Gatecoin team earlir today, stresses out that replay protection, that prevents you from “double spending” your coins after the hardfork, is crucial. 

Talking about supporting Bitcoin Gold if it implements replay protection, the company detailes that they "will make all efforts to develop support for Bitcoin Gold, but will not do so if it will risk your coins". 

What the future has in stock for Bitcoin and Bitcoin Gold, remains to be seen. Just wait for a little while. 

Trezor to Promise Hardware Update

The update is expected in January; it's going to fix the Wallet Fail vulnerability
29 December 2018   577

As reported earlier, Wallet Fail team was able to hack Trezor's and Ledger's hardware wallets at the  35C3 Refreshing Memories conference.

CTO of SatoshiLabs, creator of Trezor, have finally commented on the situation.

With regards to 35c3 findings about Trezor: we were not informed via our Reponsible Disclosure program beforehands, so we learned about them from the stage. We need to take some time to fix these and we'll be addressing them via a firmware update at the end of January.

Pavol Rusnak

CTO, SatoshiLabs

Same group of researchers also claimed during the talk that they were able to install any firmware on a Ledger Nano S, another hardware wallet.

We can send malicious transactions to the ST31 [the secure chip] and even confirm it ourselves [via software,] or we can even go and show a different transaction [not the one that is actually being sent] on the screen.

Team Member, Wallet Fail

Additionally, Wallet Fail demonstrated a vulnerability in the Ledger Blue, the most expensive hardware wallet produced by the company, with a color touchscreen. The signals are transported to the screen by an unusually long trace on the motherboard, which is why it leaks those signals as radio waves.