Representing ERC-1155-Like Assets on Aptos: FA vs. DA Standard (0x4)

[garciatroisi]

Discord user ID

garcia.troisi

Describe your question in detail.

Hi! One question — to represent assets like those in ERC-1155 on EVM, would it be more appropriate to use the Aptos Fungible Asset (FA) Standard or the Aptos Digital Asset (DA) Standard?

I understand that in the legacy (0x3) version of DA it was possible to mint tokens with supply, but how is that handled now in 0x4?

What error, if any, are you getting?

No response

What have you tried or looked at? Or how can we reproduce the error?

No response

Which operating system are you using?

macOS

Which SDK or tool are you using? (if any)

TypeScript SDK

Describe your environment or tooling in detail

No response

[0xbrw]

hi @garciatroisi, can you explain your use case to use something similar to erc-1155? that would be helpful in recommended DA or FA standard. To create a fixed supply with the DA standard you can use collection::create_fixed_collection, seen in the docs here: https://aptos.dev/en/build/smart-contracts/digital-asset#fixed-maximum-supply

[garciatroisi]

hi @garciatroisi, can you explain your use case to use something similar to erc-1155? that would be helpful in recommended DA or FA standard. To create a fixed supply with the DA standard you can use collection::create_fixed_collection, seen in the docs here: https://aptos.dev/en/build/smart-contracts/digital-asset#fixed-maximum-supply

I want collections where I can have identical NFTs with limited copies and a max supply. Also, updating the metadata URI of these NFTs should be possible with a single transaction.

For example, NFT #1 could have 1000 copies and NFT #2 could have 5. But when I update the URI of #1, it should affect all 1000 copies.

I understand that the way to do this on DA is to have two separate collections — and that works for me — but I don’t have the ability to perform a mass update, or do I?

In the legacy token standard, you had to set the max supply for an NFT, right?