

It also does some bookkeeping so it can actually be queried for assets and has functionality so the owner of the Collection’s own NFT (the actual owner of the Collection itself) and full control over those assets, including functions to safely transfer those away again or even call functions on other contracts in the name of the Collection (similar to what you would see on e.g. Now this Collection contract is the account that receives ERC-721 and ERC-1155 assets, and becomes their owner. On that new contract, we set the requested ENS name for easier addressing of the Collection. Additionally, every time a new NFT for a collection is created, this core contract acts a “factory” and creates a new separate contract for the collection itself, connecting this new “ Collection” contract with the newly created NFT. To achieve all that, we came up with a system that we think could be a model for future similar project as well and would ideally form the basis of a future standard itself.Īt its core, a common “ Collections” ERC-721 contract acts as the “registry” for all Crypto stamp collections, every individual collection is represented as an NFT in this “registry”. That said, to be NFTs themselves, the collections need to be “indexed” by what we could call a “registry of Collections”.

Also, we wanted to be able to give names to collections (via ENS) so it would be easier to work with them for normal users – and that also requires every collection to have a distinct Ethereum account address (which the before-mentioned EIP-998 is unable to do, for example). The Ethereum account should not be shared with other collections so ownership of an asset is as transparent as people and (distributed) apps expect. So, for the former (being the owner of assets), it needs to be an Ethereum account (in this case, a contract) and for the latter (being owned and traded) be a single ERC-721 NFT as well. We wanted a collection (a stamp album) to actually be the owner of those NFTs or “assets” but at the same time being owned by an Ethereum account and able to be transferred (or traded) as an NFT by itself. We set off to find existing standards on Ethereum contracts for grouping NFTs ( ERC-721 and potentially ERC-1155 tokens) together and we found that there are a few possibilities (like EIP-998) but those ares getting complicated very fast.

After a successful release of Crypto stamp 1, one of our core ideas for a second edition was to represent stamp albums (or stamp collections) in the digital world as well – and not just the stamps themselves. As mentioned in a previous post, I’ve been working with the Capacity team on the Crypto stamp project, the first physical postage stamp with a unique digital twin, issued by the Austrian Postal Service (Österreichische Post AG).
