The @opensea digest this week says POAP collectors "will be able to keep their tokens regardless of what happens to POAP's company." opensea.io/blog/articles/ope… That is true, but it is the smaller half of the story. You keep the token. You do not keep the badge. Here is what the POAP contract returns today, on Gnosis: tokenURI(7000000) -> api.poap.tech/metadata/15124… That URL returns JSON, and the image inside it points at assets.poap.xyz. Both hops are ordinary web addresses that POAP pays to keep online. I checked the metadata for an IPFS or Arweave pointer. There is none. No CID, no mirror, no redirect, no fallback of any kind. api.poap.xyz is already NXDOMAIN. When the rest lapses, nearly 7.6 million badges become a token ID and a broken image. POAP's metadata also uses image_url instead of the ERC-721 standard image field, so anything following the spec rather than special-casing POAP gets nothing back even today. Now the part I did not expect. The POAP contract is an upgradeable proxy. implementation 0xa178b166bea52449d56895231bb1194f20c2f102 proxy admin 0xdd3c426fa842f890bcb793da6ccd749edb09c44b admin owner 0xa7c257324b69406964622cdd981db832d6370082 @poapxyz can still fix this permanently. One implementation upgrade, so that tokenURI returns an IPFS URI, and every one of those badges describes itself forever. It needs no migration, no action from collectors, and no per-token gas. One transaction, and the art outlives the company. You would not have to rebuild anything either. I archived the corpus before it went dark - 190,153 events, 174,498 artworks, 157 GB, every file verified against its own hash. It is pinned on IPFS with a public registry mapping event to hash to CID. @poapxyz @worthalter @izonline - the archive is done and the roots are yours to point at. Happy to help however is useful. If you run an IPFS node, one recursive pin of each root mirrors the whole thing - instructions in the repo: github.com/mdws-org/poap-sav…