1/ Meebits exploit summary - @0xNietzsche posted a hint they were up to something
https://twitter.com/0xNietzsche/status/1390886307438731270?s=20
2/ Then people spotted a bunch of strange transactions on the meebit contract
etherscan.io/address/0x270f…
etherscan.io/address/0x270f…
3/ Lo and behold, a rare visitor got minted - but only after a lot of reverted transactions. Clearly an exploit.
The person themselves reveals what they've done on the Meebits Discord, as well as via their OpenSea identity.
The person themselves reveals what they've done on the Meebits Discord, as well as via their OpenSea identity.
4/ Then they offer it for sale for 300 Eth on Opensea, dropping to 200 Eth minutes later, pinging @pranksyNFT who then buys it seemingly without knowing it's from an exploit.
5/ The exploit continues in the search for the final dissected, but @larvalabs pause the sales and (their) trading functions in the contract to prevent further hacks. Trading may be locked for a couple more days, after which the expoit is no longer valid.
6/ Should Meebit owners be worried?
No, it wasn't possible to mint arbitrarily, this was a way to select the final rare meebits, of which they got one.
This is now just part of the Meebit story. Embrace it.
No, it wasn't possible to mint arbitrarily, this was a way to select the final rare meebits, of which they got one.
This is now just part of the Meebit story. Embrace it.
9/ The exploit was not the smart contract per se but because the IDs got known due to being on IPFS. The contract is fine.
10/ Apparently the data wasn't meant to be on ipfs until all were sold, only the hash.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
