Thread by @punk6529

1/ The last 24 hours in NFT UX

✅New @opensea contract does not work with @Trezor @MetaMask combo
✅PANIC! Revoke your OpenSea NFT permissions due to possible phishing
✅I think(?) latest MM build breaks Trezor T compatibility completely (but not sure)

2/ I am easily in the top 0.1% of NFT/crypto sophistication, I have wasted several weekend hours on this and I am still not 100% about some things.

This is an inconceivably bad UX for any normal person.

We CANNOT mainstream this way.

3/ These are not obscure edge case outcomes with obscure firms.

These are three of the five main infrastructure firms in the NFT space who are not coordinating with each other at all

Each of the teams needs to do better on comms, better on coordinating their release cycles

4/ I fully appreciate that everyone is buried in work, but also the amount of capital available to major crypto/NFT firms is basically "infinity" right now.

They need to staff up.

Comms, for example, in NFTs is a 24/7/365 function but it is not staffed this way by anyone

5/ I will give a simple example.
The reason the MM/Trezor combo breaks on the new OpenSea release is because MM does not yet support a certain type of signature for Trezor. The details are unimportant, the important thing is that this issue has been known for 1.5 months now.

6/ The correct answer is for MM to work it into a release cycle before the opensea new contract launch.

The slightly less correct answer is for OS to say "MM is not ready, we need to release to solve the old listings issue, giving you 48 hours warning of this"

7/ The least correct answer of all that the release happens, there is a perfectly predictable bug on one of the most common infrastructure combos, and then it is left to the community to discover what has broken.

I mean this is "worst practices" in release management

8/ This is not OK for the level of volume that OS is doing.

It does not impact me because I am not an active trader, but for an active trader this is a nightmare.

You are stuck in your position (listings, buys, etc) with no warning.

9/ This particularly punishes anyone who is taking security seriously and is working with a hardware wallet with seeds offsite.

It should not be fast/easy to swap into a different hardware wallet if your security is setup correctly

10/ In summary:

✅@opensea @Trezor @MetaMask @Ledger and possibly others need a permanent working group to coordinate on releases

✅Communication should happen ahead of releases, in a timely manner and 24/7

✅Workarounds should be officially communicated by all stakeholders