Burn

Builds a transaction that permanently destroys an asset and reclaims its rent to authority, which must be the current owner and is the only signer.

Supported tokenStandard values are nft, pnft, core and core-collection. Collection membership and printed-edition parentage are resolved on-chain, so neither needs to be supplied — but printed-edition burns work for nft only, not pnft. The cnft, objkt, native, erc20, erc721 and erc1155 standards are rejected with a 400.

Burning is irreversible and there is no on-chain confirmation step beyond your signature.

Authorization

ApiKeyAuth

x-api-key<token>

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Permanently destroys an asset and reclaims its rent. Accepts nft, pnft, core and core-collection only.

authority*string

Wallet burning the asset (base58). Must be its current owner and is the only signer.

asset*string

Mint/asset address to burn (base58).

tokenStandard*TokenStandard

Asset standard, which selects the program the transaction is built against. Solana: nft (Token Metadata), pnft (programmable NFT), cnft (compressed), core / core-collection (Metaplex Core). objkt is a Tezos asset. EVM: native, erc20, erc721, erc1155. Individual endpoints accept only a subset — an unsupported standard is rejected with a 400.

Value in

"nft"
"core"
"core-collection"
"pnft"
"cnft"
"objkt"
"native"
"erc20"
"erc721"
"erc1155"

targetPriorityFeeLamports?integer

Total priority fee to target for this transaction, in lamports. The builder derives the compute-unit price from it and the transaction's compute budget. Omit to let mallow pick a fee from current network conditions.

Formatuint64

blockhash?string

Recent blockhash to stamp onto the transaction, base58. Omit to let mallow supply one — mallow's is cached for up to 10 seconds, so two identical requests inside that window compile the same transaction, with the same signature once signed. Supply your own to control the expiry window, or when otherwise-identical requests must produce distinct transactions. Rejected with a 400 if it is not valid base58; a blockhash the cluster has already aged out builds fine and fails at send time.

Response Body

`application/json`

curl -X POST "https://example.com/v2/tx/assets/burn" \  -H "Content-Type: application/json" \  -d '{    "authority": "string",    "asset": "string",    "tokenStandard": "nft"  }'

{  "result": {    "tx": "string"  }}

Authorization

Request Body

Response Body

200application/json

400application/json

401application/json

429application/json

500application/json

`application/json`

`application/json`

`application/json`

`application/json`

`application/json`