Can a Claim Page work alongside a custom extension that binds ERC-6551 accounts and ERC-8004 agents?

Manifold Support Questions
1

Hi Manifold team,

I have a 333-piece ERC-721 collection on a Creator Core contract with a custom registered extension. My extension’s mint() creates the NFT, deploys an ERC-6551 token-bound account, binds it to the token, and assigns a sequential seed. A second call, awakenAgent(), registers an ERC-8004 agent identity and transfers it into that token-bound account. This all works — I’ve verified it end to end.

What I don’t have is a collector-facing mint page. I’d much rather use your Claim Page than build my own. Four questions:

  1. Can a Claim Page or Editions campaign be configured to call a custom registered extension’s mint() function instead of ERC721LazyPayableClaim? My reading of the architecture says no, but I’d like to confirm before I build an alternative.

  2. If tokens are minted by ERC721LazyPayableClaim, can a separately registered extension act on those tokens afterward — specifically create an ERC-6551 account for them and write token data? Or are extensions limited to tokens they minted themselves?

  3. When ERC721LazyPayableClaim mints, it controls tokenURI through the claim’s location and storageProtocol. I have 333 unique metadata files in a single IPFS folder as 1.json through 333.json. Can a claim be configured to resolve each token to its own file in that folder, or does the identical flag mean all tokens in a claim share one URI?

  4. I noticed you ship a 6551 Display Widget. Is there a recommended pattern for combining Claim Pages with token-bound accounts? If there’s a supported path I’m missing, I’d rather follow it than invent one.

Happy to share contract addresses if that helps. Thanks — the Creator Core architecture has been a pleasure to build on says me trying to control Claude AI. Cheers Manifold Team!

1 Like
2

Hello bullymeow,

  1. Can a Claim Page or Editions campaign be configured to call a custom registered extension’s mint() function instead of ERC721LazyPayableClaim ?
    Unfortunately no, we don’t have a way to call a custom mint function on our claim page currently.

    1. If tokens are minted by ERC721LazyPayableClaim, can a separately registered extension act on those tokens afterward — specifically create an ERC-6551 account for them and write token data? Or are extensions limited to tokens they minted themselves?
      The current design bounds tokens to the extension that minted them. This is part of the permissioning model to prevent bad actors from tampering with the tokens once they are minted.

  3. When ERC721LazyPayableClaim mints, it controls tokenURI through the claim’s location and storageProtocol. I have 333 unique metadata files in a single IPFS folder as 1.json through 333.json. Can a claim be configured to resolve each token to its own file in that folder, or does the identical flag mean all tokens in a claim share one URI?
    A claim can be configured by setting the identical flag to false, each token metadata will then be rendered based on the order they are minted.
    Example, if you set the location to be https://arweave.net/<hash> and identical to be false. The first minted token will have tokenURI of https://arweave.net/<hash>/1, the second minted token will have tokenURI of https://arweave.net/<hash>/2 etc.

  4. Is there a recommended pattern for combining Claim Pages with token-bound accounts?
    We currently don’t have documentations for this since we haven’t seen a lot of use cases for 6551 token bound accounts.

With all that said, do you have a one-pager that describes the project? It would also be helpful if you could share the relevant contract addresses. That would help us better understand your use case and see how we might be able to help.

3

Thank you @ dongqtm you rock!
Ahh a one sheet. Or I can email you the url for the testnet view? I got version 1 up on testnet. I was viewing on Opensea then only days later they brought the testbnet down. I do have both contract addresses - not safe to post here. Can I please have your email? I am trying to make a claim page that 1) mints NFT 2) awakens agent. Similar to the FREAKS 1 drop. THanks so much I think I this is my 8th time minting a collection on Manifold?