Redemption CSV Workflow

Manifold Support Questions
1

Redemption Workflow Questions - Before CSV Minting

Context: CSV and assets ready, need guidance on redemption flow and NPM package

Hello!

We were able to upload a CSV and have our assets to submit, but we have some questions before we finalize the minting configuration.

Context:

  • “1 OF 1 TOKEN BATCH” with 8 ERC721 assets

  • Planning redemption: users redeem ERC20 coins for ERC721 NFTs

  • Currently at “Select a recipient” step

  • Keeping everything in DRAFTS until we clarify

Questions:

  1. Redemption Capability - Timing and CSV Structure

Question: Do we need to set redemption capability (ERC20 → NFT) BEFORE minting, or can it be configured after?

Follow-up: Can a single CSV contain both:

  • NFTs redeemable with ERC20 coins (redemption payment method)

  • NFTs with other payment methods (ETH, USDC, etc. - not redeemable)

Or must redeemable NFTs (ERC20 payment) and non-redeemable NFTs (ETH/USDC payment) be in separate CSV uploads?

  1. Recipient for Redemption

Question: For ERC20 → NFT redemption, what’s the recommended recipient setup?

Options:

  • “Self” - Mint to our wallet, then transfer via redemption

  • “SAFE” - Mint to SAFE wallet, hold for redemption

  • Redemption Contract - Can redemption contract mint directly to users?

  1. NPM Package Timeline

Question: When will the NPM package be available for testing? We’d like to test it with our redemption flow before finalizing our csv test.

Current Status:

  • :white_check_mark: CSV created with ArDrive URLs

  • :white_check_mark: 8 assets configured in DRAFTS

  • :pause_button: Waiting on recipient decision pending your guidance

We’re happy to be early testers of the NPM package and would appreciate any guidance on how it fits into redemption flows.

Thank you!