💾 TECHNICAL THREAD OF NFTs HACK 💾

First of all we need to understand the difference between CALL and DELEGATECALL EVM Opcodes

In a simple way; when you call a contract with delegatecall, it is as if you embed the called function inside the contract itself

🧵 1/8 Opensea uses Wyvern Protocol, which is the most optimal fees-wise peer-to-peer exchange protocol

But it has also a disadvantage: when you sign a malicious message, the counter-part can execute that signed message for you

🧵 2/8

🏴‍☠️ OPENSEA NFT HACK EXPLAINED THREAD 🏴‍☠️

28 days ago the hacker uploads a new smart contract, he already knows well that his goal is to get as many signatures as possible

🧵 1/4 He starts sending emails with phising websites. They tell you to sign a message to login/migrate to the new Opensea smart contract

Instead you are signing a private sale (0 eth) of your NFTs to the hacker

🧵 2/4

Did you know we are developing a Furniture Builder for @isotile ecosystem?

We are also finalizing our Sprite Rendering Engine so that complex furniture can be created by users

Best of all, it works on the browser, you don't have to download any executable The Furniture Builder will follow the Virtual Reality standard, so they could be placed in any metaverse

For this we are improving the existing standards on the interoperability of objects in the metaverse (ERC-721 & stateful VR files)