NFTX incident

CryptoKitties Revoke Mint Request failing

Minor Resolved View vendor source →

NFTX experienced a minor incident on June 6, 2021 affecting NFTX App, lasting 2d 1h. The incident has been resolved; the full update timeline is below.

Started
Jun 06, 2021, 01:59 PM UTC
Resolved
Jun 08, 2021, 03:51 PM UTC
Duration
2d 1h
Detected by Pingoru
Jun 06, 2021, 01:59 PM UTC

Affected components

NFTX App

Update timeline

  1. identified Jun 06, 2021, 01:59 PM UTC

    To have your Kitty approved to go into the vault a Request Mint is required. Once submitted, the team check to ensure that your Kitty is a Generation 0 for the Kitty-gen-0 vault, and that it is Generation 0 and Fast recovery on the Kitty-Gen-0-F vault. If the Kitty belongs, the request mint will be approved and you will be issued your token. If the Kitty is inelligible it will not be approved. The only way to get your Kitty back at that point is to call the Revoke Mint Request. At the moment this call against the Kitty contract is failing as the CryptoKitties contract does not follow the ERC721 standard contract. This issue has been found and a patch is being added. Once released this ticket will be updated to Monitoring and we a note added to discord.

  2. identified Jun 07, 2021, 09:38 AM UTC

    The contract update has been made and is going through the Aragon process. Vote 135: Set new contract implementation (https://etherscan.io/address/0x0C68F11ad08EF6a02C4224fA6D6585D8b3102a26#code) to fix bug in revokeRequest function when handling cryptokitty vaults.

  3. resolved Jun 08, 2021, 03:51 PM UTC

    Contract has gone through aragon and the changes are now live, revokeMinting is now available for the Kitty contract.