Opensea and MetaMask will not allow signing of transactions to place items for sale that are stored in my Trezor wallet

@here

Hi @forgi - when I try to list items to sell on OpenSea, my Trezor displays “Unable to show EIP-712 data. Sign at your own risk”

Is this expected? I’m afraid to sign without seeing what I’m signing…

I have never had a problem selling single NFTs from trezor +metamask so far…

But yesterday I was trying to list a bundle of sandbox lands and after confirming on my trezor I always get “You declined to authorize your auction” on Opensea after the third confirmation step.

So could it be the update does not work when selling bundles? I´m really confused its a big important sale for me dont know what to do I am afraid to store those items anywhere else but on a hardware-linked metamask

Any solution? I cannot do collabland, transfer, sell. Everything just stuck. Regret buy this trezor

Having the same issue. Anyone have a solution?

May I know do you still have this issue?

i still cannot do collab land nor transfer

I minted an ETH NFT in my primary account in MetaMask, then I transferred the NFT to Trezor wallet connected to MetaMask. When I’m trying to send my NFT from Trezor account to my primary account in MetaMask the prosses is freezing. I’m using OpenSea platform and connected to MetaMask and the Trezor Hard Wallet connect to my laptop and I reach to the step of adding code in Trezor then the password but after that the page in OpenSea and MetaMask are freezing, and I can’t complete my transfer at all. Firmware updated to 1.10.5, the MetaMask V10.11.3.
Your help is highly appreciated

yes, I’m having the exact same issue. this has cost me losing some eth due to cannot keep up to the market. Until now, no one has reach me and help.

Stop tagging me with the metamask Trezor tweet. So many commented it’s still not working under the tweet…….

The problem persists and as a new Trezor owner it’s alarming that the needle hasn’t moved in this regard one iota in over the past 6 months.

@Zeal @IRONSAM96 this is not issue of Trezor, users have reported it from other wallets so it’s Opensea mainly and MM.

Clear cache, reconnect a few times, use different browser.

I have been able to send Polygon NFTs via Trezor-less MetaMask & OpenSea.

I am able to send Polygon NFTs via Trezor-less MetaMask # OpenSea.

Threads like this exist for a reason: https://www.reddit.com/r/TREZOR/comments/pwwnb3/polygon_nft_trapped_on_trezor/

But OK.

1 Like

A post was split to a new topic: Opeansea and MetaMask won’t allow signing of transactions

Hi,

any update on this topic?

i have the same error, when i sign the transactions nothing happens.

need help , need some liquity plzZzz

06ba217174e54f7b16d4386c5218fdf
My trezor stuck in this page, I click accept and sign in metamask, It had no response. I have a NFT in trezor and I want to sell it in opensea. help me plz

Hi @xincctnn,

If you’re from China, I guess this is not an Opensea or Metamask issue, but rather that the Chinese government block the Trezor connect API which both of these third party sites use. See more here about this issue.

1 Like

Great solution…

I’m being sarcastic. This is really not optimal.

Why can’t you provide support for NFTs in Trezor?

@Perogi,

Note the date of the message you are replying to. Things have changed since then. :slight_smile:

Trezor can’t connect to OpenSea through Metamask. I tried in multiple browsers.

When you try to sign the transaction to connect it displays the binary data on the Trezor One device but the “confirm” option won’t work. It just refreshes the binary data and stays on that screen.

Since you cannot send NFTs inside the Trezor Suite and can’t connect through Metamask to OpenSea there is no way to move your NFTs from the Trezor One. They are stuck there.

The only other possible way to resolve this would be by sending them out from inside the Metamask browser extension but their dev team still hasn’t built out this functionality. Trezor One can’t connect to mobile to do it from Metamask mobile.

So for now thanks to both the dev teams on Trezor and Metamask, anybody who decided to safeguard their NFTs on the Trezor One is stuck with them and no ability to send. I guesss at least they are secure LOL.

But seriously this is a big fuck up from both of the developer teams.

  1. Why the hell would you not include NFT support in Trezor Suite? Planning on staying in 2017 forever?

  2. Metamask team needs to get the ability to send NFTs from the browser extension up and running. Then at least you could do a bulk transfer back over to Metamask (although it’s a big security risk and user error risk of screwing up the transfer). That way you could at least manage them through OpenSea.

Ledger is pulling ahead here. Devs do something. Thanks.

2 Likes