Adam Hollander

@HollanderAdam

Oct 7

AJT

@ajt

Sep 28

The ME/Limitbreak hack affected a lot of NFTs across the @truth ecosystem, including some of our biggest and most active community members.

Outside of a handful that @0xQuit was able to save, a lot of those stolen NFTs are now flagged on OpenSea and realistically aren’t recoverable.

So we’ve been thinking about what we *can* do.

Here’s the tentative plan:

For stolen Goblins, we change the art/metadata on those NFTs to basically say “stolen” / FU to the hackers, making the stolen versions worthless from an art and metadata perspective.

Then we’ll take Goblins from the Truth treasury, change their art and metadata to match the stolen Goblins, and send those replacement Goblins back to the people who were affected.

So effectively:

Stolen Goblin → art/metadata gets nuked.

Treasury Goblin → becomes the original Goblin and goes back to the affected holder.

There are some downsides. We’ll probably end up giving away a large part, if not all, of the Goblins in our treasury. And anyone who legitimately bought one of the stolen Goblins after the hack could end up holding an NFT with changed metadata. Most appear to be hackers or WETH offers, but if there are legitimate buyers, we’ll work with them to trade it back to the original holder in exchange for one in our treasury.

But I think the upside is worth it.

This was a terrible hack. The people affected didn’t do anything wrong, and many of them are some of the most passionate people in our community and in crypto generally.

We can’t recover everything they lost. But in this case, we actually have the ability to do something.

We’re going to start with @goblintown. If it works well, we’ll look at doing the same for @secretsociety, @the187, Grumpls, and others.

We may also try to buy back the stolen NFTs after their metadata has been changed, burn them, or potentially restore them later depending on what makes the most sense.

We’ll start rolling this out over the next few days. It is going to be a very manual process so bear with me.

If you were affected, DM me here or on Discord with all the details so I can verify everything end to end.

AJT

@ajt

Oct 5

AJT

@ajt

Sep 28

The ME/Limitbreak hack affected a lot of NFTs across the @truth ecosystem, including some of our biggest and most active community members.

Outside of a handful that @0xQuit was able to save, a lot of those stolen NFTs are now flagged on OpenSea and realistically aren’t recoverable.

So we’ve been thinking about what we *can* do.

Here’s the tentative plan:

For stolen Goblins, we change the art/metadata on those NFTs to basically say “stolen” / FU to the hackers, making the stolen versions worthless from an art and metadata perspective.

Then we’ll take Goblins from the Truth treasury, change their art and metadata to match the stolen Goblins, and send those replacement Goblins back to the people who were affected.

So effectively:

Stolen Goblin → art/metadata gets nuked.

Treasury Goblin → becomes the original Goblin and goes back to the affected holder.

There are some downsides. We’ll probably end up giving away a large part, if not all, of the Goblins in our treasury. And anyone who legitimately bought one of the stolen Goblins after the hack could end up holding an NFT with changed metadata. Most appear to be hackers or WETH offers, but if there are legitimate buyers, we’ll work with them to trade it back to the original holder in exchange for one in our treasury.

But I think the upside is worth it.

This was a terrible hack. The people affected didn’t do anything wrong, and many of them are some of the most passionate people in our community and in crypto generally.

We can’t recover everything they lost. But in this case, we actually have the ability to do something.

We’re going to start with @goblintown. If it works well, we’ll look at doing the same for @secretsociety, @the187, Grumpls, and others.

We may also try to buy back the stolen NFTs after their metadata has been changed, burn them, or potentially restore them later depending on what makes the most sense.

We’ll start rolling this out over the next few days. It is going to be a very manual process so bear with me.

If you were affected, DM me here or on Discord with all the details so I can verify everything end to end.

△ T R i P L Ξ ❂ P T i C S △

@tripleoptics_

Oct 6

AJT

@ajt

Oct 5

We just did our first theef swap with @tripleoptics_ (thanks for being our guinea pig 🫡)

Quick clarification on how this will work going forward:

This is going to be a rolling, case-by-case process. The “theef” metadata is temporary, the goal is to punish the hackers, not innocent people who may end up with one of these NFTs.

If a good-faith buyer ends up with a theef, we can restore the metadata from the swapped one in our treasury (that turned into the replacement) and will do our best to work with OpenSea on getting the flag removed.

We’re also not automatically swapping every affected NFT. Each situation will be handled individually, and ultimately the biggest hit here is to our own goblin treasury.

We will be doing the same with Illuminati and Grumpls soon. The 187 is a little tricker but we will figure something out.

If you were affected by the hack, DM me here or on Discord and I’ll help get you sorted. And seriously, pester me if I miss your message.

goblintown

@goblintown

Sep 28

goblintown

@goblintown

Sep 28

To those affected by last weeks hack...

AJT

@ajt

Sep 28

AJT

@ajt

Sep 28

The ME/Limitbreak hack affected a lot of NFTs across the @truth ecosystem, including some of our biggest and most active community members.

Outside of a handful that @0xQuit was able to save, a lot of those stolen NFTs are now flagged on OpenSea and realistically aren’t recoverable.

So we’ve been thinking about what we *can* do.

Here’s the tentative plan:

For stolen Goblins, we change the art/metadata on those NFTs to basically say “stolen” / FU to the hackers, making the stolen versions worthless from an art and metadata perspective.

Then we’ll take Goblins from the Truth treasury, change their art and metadata to match the stolen Goblins, and send those replacement Goblins back to the people who were affected.

So effectively:

Stolen Goblin → art/metadata gets nuked.

Treasury Goblin → becomes the original Goblin and goes back to the affected holder.

There are some downsides. We’ll probably end up giving away a large part, if not all, of the Goblins in our treasury. And anyone who legitimately bought one of the stolen Goblins after the hack could end up holding an NFT with changed metadata. Most appear to be hackers or WETH offers, but if there are legitimate buyers, we’ll work with them to trade it back to the original holder in exchange for one in our treasury.

But I think the upside is worth it.

This was a terrible hack. The people affected didn’t do anything wrong, and many of them are some of the most passionate people in our community and in crypto generally.

We can’t recover everything they lost. But in this case, we actually have the ability to do something.

We’re going to start with @goblintown. If it works well, we’ll look at doing the same for @secretsociety, @the187, Grumpls, and others.

We may also try to buy back the stolen NFTs after their metadata has been changed, burn them, or potentially restore them later depending on what makes the most sense.

We’ll start rolling this out over the next few days. It is going to be a very manual process so bear with me.

If you were affected, DM me here or on Discord with all the details so I can verify everything end to end.

goblintown

@goblintown

Sep 28

AJT

@ajt

Sep 28

The ME/Limitbreak hack affected a lot of NFTs across the @truth ecosystem, including some of our biggest and most active community members.

Outside of a handful that @0xQuit was able to save, a lot of those stolen NFTs are now flagged on OpenSea and realistically aren’t recoverable.

So we’ve been thinking about what we *can* do.

Here’s the tentative plan:

For stolen Goblins, we change the art/metadata on those NFTs to basically say “stolen” / FU to the hackers, making the stolen versions worthless from an art and metadata perspective.

Then we’ll take Goblins from the Truth treasury, change their art and metadata to match the stolen Goblins, and send those replacement Goblins back to the people who were affected.

So effectively:

Stolen Goblin → art/metadata gets nuked.

Treasury Goblin → becomes the original Goblin and goes back to the affected holder.

There are some downsides. We’ll probably end up giving away a large part, if not all, of the Goblins in our treasury. And anyone who legitimately bought one of the stolen Goblins after the hack could end up holding an NFT with changed metadata. Most appear to be hackers or WETH offers, but if there are legitimate buyers, we’ll work with them to trade it back to the original holder in exchange for one in our treasury.

But I think the upside is worth it.

This was a terrible hack. The people affected didn’t do anything wrong, and many of them are some of the most passionate people in our community and in crypto generally.

We can’t recover everything they lost. But in this case, we actually have the ability to do something.

We’re going to start with @goblintown. If it works well, we’ll look at doing the same for @secretsociety, @the187, Grumpls, and others.

We may also try to buy back the stolen NFTs after their metadata has been changed, burn them, or potentially restore them later depending on what makes the most sense.

We’ll start rolling this out over the next few days. It is going to be a very manual process so bear with me.

If you were affected, DM me here or on Discord with all the details so I can verify everything end to end.

goblintown

@goblintown

Sep 25

AJT

@ajt

Sep 25

Still digesting the Magic Eden / Limit Break hack but formulating a few ideas to counter it with and for the community.

Quit

@0xQuit

Sep 25

Quit

@0xQuit

Sep 25

REVOKE APPROVALS TO THESE ASAP:

Payment Processor V2 on Ethereum: 0x9A1D00bEd7CD04BCDA516d721A596eb22Aac6834
Payment Processor V3 on ApeChain: 0x9a1D00000000fC540e2000560054812452eB5366

use revoke.cash or similar.