{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "nft-burning",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/nft-burning/",
  "collection": "ethereum",
  "title": "Burning an NFT: which record disappears and what can remain?",
  "description": "Distinguish an NFT burn function from sending a token away and understand which ownership and media records remain.",
  "aliases": [
    "burn NFT meaning",
    "NFT burn versus dead address"
  ],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T19:27:58.939Z",
    "dataAsOf": "2026-10-02"
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "Burning an NFT removes the token or quantity from the contract’s live ownership accounting under that contract’s rules. A transfer to an inaccessible address is not necessarily the same operation. ERC-721 does not require a public burn function; some implementations allow owners or approved operators to burn, while others do not expose burning at all.",
    "claimId": "nft-burning-quick-answer",
    "sourceIds": [
      "x425-eth-erc721",
      "x425-eth-erc1155",
      "x425-eth-oz-burn"
    ]
  },
  "keyFacts": [
    {
      "label": "Implementation",
      "value": "A burn entry point is not mandatory in ERC-721.",
      "sourceIds": [
        "x425-eth-erc721"
      ],
      "id": "implementation",
      "claimId": "nft-burning-fact-implementation"
    },
    {
      "label": "Authorization",
      "value": "OpenZeppelin Contracts v5.4.0’s ERC721Burnable checks ownership or approval.",
      "sourceIds": [
        "x425-eth-oz-burn"
      ],
      "id": "authorization",
      "claimId": "nft-burning-fact-authorization"
    },
    {
      "label": "History",
      "value": "Burning is represented by events rather than deleting previous chain history.",
      "sourceIds": [
        "x425-eth-erc721",
        "x425-eth-erc1155"
      ],
      "id": "history",
      "claimId": "nft-burning-fact-history"
    }
  ],
  "prerequisites": [
    "erc-721-nfts"
  ],
  "sections": [
    {
      "id": "operation",
      "heading": "Check the collection’s actual burn method",
      "sourceIds": [
        "x425-eth-erc721",
        "x425-eth-oz-burn"
      ],
      "paragraphs": [
        "A collection may expose an authorized burn function, restrict it or omit it. The versioned OpenZeppelin ERC721Burnable example permits an owner or approved operator to perform a burn; another contract can impose different rules.",
        "Do not assume an NFT can be destroyed by invoking a function found in an unrelated collection’s interface."
      ]
    },
    {
      "id": "example",
      "heading": "An ERC-1155 burn can affect only a quantity",
      "sourceIds": [
        "x425-eth-erc1155"
      ],
      "paragraphs": [
        "Suppose an address holds five units of one ERC-1155 token ID and the contract authorizes a burn of two. The resulting balance is three units. This is different from removing the token ID everywhere or erasing every holder’s balance.",
        "For an ERC-721 token, a burn concerns the unique token’s live ownership record. Neither operation erases the transactions that led up to it."
      ]
    },
    {
      "id": "media",
      "heading": "Destroyed ownership is not deleted content",
      "sourceIds": [
        "x425-eth-erc721",
        "x425-eth-ipfs-content",
        "x425-eth-ipfs-persistence"
      ],
      "paragraphs": [
        "An NFT can point to offchain metadata and images. Burning the token does not instruct every web server or IPFS node to delete those files. Other people may retain the same content independently.",
        "Likewise, sending a token to an address thought to be inaccessible may leave the contract counting it as owned there. Use the contract’s documented semantics when discussing burned supply."
      ]
    }
  ],
  "faq": [
    {
      "question": "Can an approved operator burn an NFT?",
      "answer": "It depends on the implementation. OpenZeppelin Contracts v5.4.0 ERC721Burnable permits owners or approved operators, so approval scope can matter beyond a marketplace transfer.",
      "sourceIds": [
        "x425-eth-oz-burn"
      ]
    },
    {
      "question": "Does burning remove the NFT’s image from the internet?",
      "answer": "No. Token accounting and offchain storage are separate. Existing media copies can remain available after a burn.",
      "sourceIds": [
        "x425-eth-erc721",
        "x425-eth-ipfs-persistence"
      ]
    }
  ],
  "claims": [
    {
      "id": "nft-burning-quick-answer",
      "articleSlug": "nft-burning",
      "statement": "Burning an NFT removes the token or quantity from the contract’s live ownership accounting under that contract’s rules. A transfer to an inaccessible address is not necessarily the same operation. ERC-721 does not require a public burn function; some implementations allow owners or approved operators to burn, while others do not expose burning at all.",
      "sourceIds": [
        "source-b08b9aae11ea4085",
        "source-a8902fec2ff6f520",
        "source-6afc89f384bcfbe0"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-b08b9aae11ea4085",
          "locator": "safeTransferFrom; approve; setApprovalForAll; Transfer; metadata"
        },
        {
          "sourceId": "source-a8902fec2ff6f520",
          "locator": "Safe transfer rules; operator approvals; minting and burning"
        },
        {
          "sourceId": "source-6afc89f384bcfbe0",
          "locator": "burn"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read version-pinned OZERC721Burnable burn->_update(0,id,msgSender),authorizedcallercomment; standardmintburn optional. ERC1155burnquantity/event conventions support5-2=3. Transfers to inaccessibleaccountnotidenticalburn; chainhistory/offchainmediaremainseparate."
        ]
      }
    },
    {
      "id": "nft-burning-fact-implementation",
      "articleSlug": "nft-burning",
      "statement": "Implementation: A burn entry point is not mandatory in ERC-721.",
      "sourceIds": [
        "source-b08b9aae11ea4085"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-b08b9aae11ea4085",
          "locator": "safeTransferFrom; approve; setApprovalForAll; Transfer; metadata"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read version-pinned OZERC721Burnable burn->_update(0,id,msgSender),authorizedcallercomment; standardmintburn optional. ERC1155burnquantity/event conventions support5-2=3. Transfers to inaccessibleaccountnotidenticalburn; chainhistory/offchainmediaremainseparate."
        ]
      }
    },
    {
      "id": "nft-burning-fact-authorization",
      "articleSlug": "nft-burning",
      "statement": "Authorization: OpenZeppelin Contracts v5.4.0’s ERC721Burnable checks ownership or approval.",
      "sourceIds": [
        "source-6afc89f384bcfbe0"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-6afc89f384bcfbe0",
          "locator": "burn"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read version-pinned OZERC721Burnable burn->_update(0,id,msgSender),authorizedcallercomment; standardmintburn optional. ERC1155burnquantity/event conventions support5-2=3. Transfers to inaccessibleaccountnotidenticalburn; chainhistory/offchainmediaremainseparate."
        ]
      }
    },
    {
      "id": "nft-burning-fact-history",
      "articleSlug": "nft-burning",
      "statement": "History: Burning is represented by events rather than deleting previous chain history.",
      "sourceIds": [
        "source-b08b9aae11ea4085",
        "source-a8902fec2ff6f520"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-b08b9aae11ea4085",
          "locator": "safeTransferFrom; approve; setApprovalForAll; Transfer; metadata"
        },
        {
          "sourceId": "source-a8902fec2ff6f520",
          "locator": "Safe transfer rules; operator approvals; minting and burning"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read version-pinned OZERC721Burnable burn->_update(0,id,msgSender),authorizedcallercomment; standardmintburn optional. ERC1155burnquantity/event conventions support5-2=3. Transfers to inaccessibleaccountnotidenticalburn; chainhistory/offchainmediaremainseparate."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "x425-eth-erc721",
      "label": "ERC-721 NFT standard",
      "publisher": "Ethereum Improvement Proposals",
      "url": "https://eips.ethereum.org/EIPS/eip-721",
      "locator": "safeTransferFrom; approve; setApprovalForAll; Transfer; metadata",
      "note": "Ownership, receiver checks, token-level and operator approvals, mint/burn event semantics.",
      "version": "ERC-721",
      "checkedAt": "2026-10-02T18:55:25.399Z",
      "contentSha256": "bedd672103f3ebb6803ce2bddb33a9ff3d23b08e8e3ae3173b6a5b016f65e2a1",
      "recordId": "source-b08b9aae11ea4085"
    },
    {
      "id": "x425-eth-erc1155",
      "label": "ERC-1155 multi-token standard",
      "publisher": "Ethereum Improvement Proposals",
      "url": "https://eips.ethereum.org/EIPS/eip-1155",
      "locator": "Safe transfer rules; operator approvals; minting and burning",
      "note": "Receiver acceptance, collection-wide operators, balance accounting and burn events.",
      "version": "ERC-1155",
      "checkedAt": "2026-10-02T18:55:25.400Z",
      "contentSha256": "50eece6ce1ad417b39ae7183a5626c6f9e3b11fc16a00ba5f630bc6fed01cfd2",
      "recordId": "source-a8902fec2ff6f520"
    },
    {
      "id": "x425-eth-oz-burn",
      "label": "OpenZeppelin ERC721Burnable",
      "publisher": "OpenZeppelin",
      "url": "https://raw.githubusercontent.com/OpenZeppelin/openzeppelin-contracts/v5.4.0/contracts/token/ERC721/extensions/ERC721Burnable.sol",
      "locator": "burn",
      "note": "A versioned example of authorized NFT token destruction, distinct from moving to an inaccessible address.",
      "version": "OpenZeppelin Contracts v5.4.0",
      "checkedAt": "2026-10-02T18:55:25.609Z",
      "contentSha256": "7b212ebdf844128dd2b3f02f824d7e855983495a75eea9c23852301c3887e861",
      "recordId": "source-6afc89f384bcfbe0"
    },
    {
      "id": "x425-eth-ipfs-content",
      "label": "IPFS content addressing",
      "publisher": "IPFS contributors",
      "url": "https://docs.ipfs.tech/concepts/content-addressing/",
      "locator": "Content identifiers; content addressing",
      "note": "A CID identifies content rather than promising a continuously available server.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:25.788Z",
      "contentSha256": "6b5f2f1fd6e1e2605f34ee5e63618a2239ed27666148d82a4931a6959cd0fc5d",
      "recordId": "source-d6c57c6845e6d6cf"
    },
    {
      "id": "x425-eth-ipfs-persistence",
      "label": "IPFS persistence and pinning",
      "publisher": "IPFS contributors",
      "url": "https://docs.ipfs.tech/how-to/pin-files/",
      "locator": "Pinning; garbage collection; remote pinning",
      "note": "Availability depends on nodes retaining and serving content; pinning prevents local garbage collection.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:25.704Z",
      "contentSha256": "3fd4a0313f1c5af3309da80188b6ea14f3ea178d73f769a35b97d72d06690b76",
      "recordId": "source-37c1413248e9760f"
    }
  ],
  "related": {
    "articles": [
      "erc-721-nfts",
      "erc-1155-multi-tokens",
      "nft-metadata",
      "nft-royalties",
      "nfts-not-showing-in-wallet"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "First publication after primary-source research and separate automated verification."
    }
  ],
  "citation": "Degrees of Satoshi editorial project. “Burning an NFT: which record disappears and what can remain?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/nft-burning/"
}