Trezor model T Binance smart chain: "unsupported chain id" - can't sign transactions #1451.
Upgraded to Trezor Model T and imported Trezor 1 seed. Using Trezor via metamask.
I can sign transactions on the ETH network on newest firmware but getting "transaction failed unsupported chain ID" on Binance smart chain. Getting this error on 2.3.3 and 2.3.4.
Downgraded to 2.3.0 which solves it and I can sign transactions with no problems.
Trezor 1 works as intended on newest firmware with no issues, problem is only with newer firmwares ModelT.
Is this a known issue and will this be fixed in an upcoming firmware?
Should I rather continue using my Trezor 1 on newest firmware or the model T on 2.3.0 until the issue is fixed?
thanks alot in advance.
The text was updated successfully, but these errors were encountered:
matejcik commented Feb 8, 2021.
that is correct.
hfray commented Feb 20, 2021.
Describe the bug Very similar issue to: #1327 Upgraded to Trezor Model T and imported Trezor 1 seed. Using Trezor via metamask. I can sign transactions on the ETH network on newest firmware but getting "transaction failed unsupported chain ID" on Binance smart chain. Getting this error on 2.3.3 and 2.3.4 Downgraded to 2.3.0 which solves it and I can sign transactions with no problems Trezor 1 works as intended on newest firmware with no issues, problem is only with newer firmwares ModelT Is this a known issue and will this be fixed in an upcoming firmware? Should I rather continue using my Trezor 1 on newest firmware or the model T on 2.3.0 until the issue is fixed? thanks alot in advance.
how did you downgrad your firmware. IM having this issue right now.
TimStone84 commented Feb 20, 2021 •
Describe the bug Very similar issue to: #1327 Upgraded to Trezor Model T and imported Trezor 1 seed. Using Trezor via metamask. I can sign transactions on the ETH network on newest firmware but getting "transaction failed unsupported chain ID" on Binance smart chain. Getting this error binary options trading signals nadex demo on 2.3.3 and 2.3.4 Downgraded to 2.3.0 which solves it and I can sign transactions with no problems Trezor 1 works as intended on newest firmware with no issues, problem is only with newer firmwares ModelT Is this a known issue and will this be fixed in an upcoming firmware? Should I rather continue using my Trezor 1 on newest firmware or the model T on 2.3.0 until the issue is fixed? thanks alot in advance.
how did you downgrad your firmware. IM having this issue right now.
it should work if you are on the newer versions. at least it does for me. they solved it with 2.3.5.
alternatively you just download the old firmware and install it on your device. google is your friend.