Exact token and amount to burn.
Burn to Redeem
Trade exact works for a new artwork.
Create a reward, choose exactly what collectors must burn, and review everything before paying for deployment.
Private beta: connect the platform owner wallet to open Burn to Redeem.
True burn only
Requirements are permanent after deployment.
Collectors must burn every listed token to receive one reward. Burns cannot be undone. This version supports exact token IDs on compatible Manifold Creator Cores and calls their native burn functions.
Step 1 · Reward Core
Create a new Core or use one you already own.
The collection contract mints the reward. Its owner controls extension registration and collection administration. No deployment is required until the review step.
You will deploy this collection after reviewing the complete setup. Your connected wallet will own it.
Paste an existing Manifold Creator Core. It must match the reward standard selected above and be owned by the connected wallet.
Connect the wallet to deploy or verify the reward Creator Core.
Step 2 · Reward
What will collectors receive?
One artwork is minted for each successful redemption. An ERC-1155 reward uses one token ID; ERC-721 rewards are individually minted tokens.
Use an existing public metadata JSON URI that includes the artwork and its details. Uploading artwork or generating reward metadata is not yet available in this flow.
Times use your device’s local time. Supply, wallet limits and dates cannot be changed after deployment; you can pause or disable the reward.
Enter the reward details.
Step 3 · Burn requirements
Add every token required for one redemption.
Example: token #12 × 1 and token #4 × 3. Each row names an exact token ID from a compatible Manifold collection. ERC-721 amount is always 1; ERC-1155 amounts can be greater. An exact ERC-721 can only be burned once, so a rule containing one can only ever be redeemed once.
Add the complete burn requirement before reviewing deployment.
Step 4 · Review and launch
Confirm the immutable rule before it goes onchain.
Review carefully: burn requirements, supply, limits and schedule cannot be edited later. Launch needs separate wallet transactions for a new collection (if needed), the burn rule, and extension registration. Gas and any storage costs are paid by your wallet.
Your draft and submitted transaction hashes are saved in this browser for the connected wallet. If a confirmation is slow, refresh its status before retrying; do not start a duplicate deployment.
Connect your wallet to begin.
Step 4 · Manage
Manage an existing redemption.
Load a BurnRedeem contract you own to pause it, turn one reward on or off, or change metadata for output tokens minted by this extension. Burn requirements, supply, times, and wallet limits are immutable. For ERC-721 rewards, updating an already-minted token does not change the metadata URI used for future mints.
Connect the drop owner wallet, then load a BurnRedeem contract.