When to use arrays vs mappings in Solidity?
Arrays are useful when you know the size of the collection in advance, and you need to be able to iterate over the elements in a specific order. Mappings are useful when you don't know the size of the collection in advance, and you need to be able to quickly lookup values. Here are a few specific scenarios where you might choose to use one over the other: 1. Use an array when you need to store a collection of items that need to be accessed by index. 2. Use a mapping when you need to asso...
Ethereum vanity addresses
Ethereum vanity address is a one-of-a-kind customized address that has portions of it chosen rather than being created at random. Why would you create a vanity address? First of all, it looks cool. The second thing it can help you with is to reinforce your brand and make you more noticeable. How to generate your own vanity address? Creating a vanity address is a straightforward trial-and-error process. When performing high-risk cryptographic operations, such as private key creation, it is imp...
Bored Ape Yacht Club: Smart Contract Breakdown
Bored Ape Yacht Club (BAYC) is a popular NFT collection created by Yuga Labs. In this post, we’ll go over BAYC smart contract code. The source code is available on EtherScan.ERC721BAYC is implemented as an ERC721 token, a standard that defines a set of functions that a smart contract must implement in order to be considered a compliant ERC721 token. These functions include the ability to transfer tokens, approve other addresses to manage your tokens, and check token ownership.ERC721 interface...
Co-founder & CTO of Blank. Building software and helping companies enter web3.
When to use arrays vs mappings in Solidity?
Arrays are useful when you know the size of the collection in advance, and you need to be able to iterate over the elements in a specific order. Mappings are useful when you don't know the size of the collection in advance, and you need to be able to quickly lookup values. Here are a few specific scenarios where you might choose to use one over the other: 1. Use an array when you need to store a collection of items that need to be accessed by index. 2. Use a mapping when you need to asso...
Ethereum vanity addresses
Ethereum vanity address is a one-of-a-kind customized address that has portions of it chosen rather than being created at random. Why would you create a vanity address? First of all, it looks cool. The second thing it can help you with is to reinforce your brand and make you more noticeable. How to generate your own vanity address? Creating a vanity address is a straightforward trial-and-error process. When performing high-risk cryptographic operations, such as private key creation, it is imp...
Bored Ape Yacht Club: Smart Contract Breakdown
Bored Ape Yacht Club (BAYC) is a popular NFT collection created by Yuga Labs. In this post, we’ll go over BAYC smart contract code. The source code is available on EtherScan.ERC721BAYC is implemented as an ERC721 token, a standard that defines a set of functions that a smart contract must implement in order to be considered a compliant ERC721 token. These functions include the ability to transfer tokens, approve other addresses to manage your tokens, and check token ownership.ERC721 interface...
Co-founder & CTO of Blank. Building software and helping companies enter web3.

Subscribe to 0xMarko

Subscribe to 0xMarko
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
Are you familiar with the concept of NFT provenance hash?
Without a provenance hash, projects have the ability to manipulate the metadata of an NFT to their advantage once the minting process has been completed.
The sequence in which NFT tokens are assigned to the metadata is important. If the order of assignment is undisclosed before the mint, buyers of the NFTs have no assurance that the project team will not modify the assignment after the mint to benefit themselves.
To address this issue, projects require a way to demonstrate that the metadata order was established before the mint and was not modified afterward.
The provenance hash provides an elegant solution to this problem.
The provenance hash is created in a few steps:
Create a hash for each image in the collection.
Concatenate the hashes in the order in which the images will be minted to create a large combined string.
Hash the combined string to obtain a provenance hash.
The best way to share the provenance hash with the community is by storing it in the collection's smart contract. This should only be done once before the mint. Updating it after the mint can be interpreted as a sign of potential manipulation.
The Bored Ape Yacht Club is a prime illustration of a project that utilizes a provenance hash. Anyone can go to Etherscan and read the BAYC provenance hash that is stored in the smart contract.
BAYC also created a UI to showcase how the provenance hash is calculated - https://boredapeyachtclub.com/#/provenance
So the question is, do you care about the provenance hash?
Does it concern you whether the metadata has been modified after the minting process or not?
Are you familiar with the concept of NFT provenance hash?
Without a provenance hash, projects have the ability to manipulate the metadata of an NFT to their advantage once the minting process has been completed.
The sequence in which NFT tokens are assigned to the metadata is important. If the order of assignment is undisclosed before the mint, buyers of the NFTs have no assurance that the project team will not modify the assignment after the mint to benefit themselves.
To address this issue, projects require a way to demonstrate that the metadata order was established before the mint and was not modified afterward.
The provenance hash provides an elegant solution to this problem.
The provenance hash is created in a few steps:
Create a hash for each image in the collection.
Concatenate the hashes in the order in which the images will be minted to create a large combined string.
Hash the combined string to obtain a provenance hash.
The best way to share the provenance hash with the community is by storing it in the collection's smart contract. This should only be done once before the mint. Updating it after the mint can be interpreted as a sign of potential manipulation.
The Bored Ape Yacht Club is a prime illustration of a project that utilizes a provenance hash. Anyone can go to Etherscan and read the BAYC provenance hash that is stored in the smart contract.
BAYC also created a UI to showcase how the provenance hash is calculated - https://boredapeyachtclub.com/#/provenance
So the question is, do you care about the provenance hash?
Does it concern you whether the metadata has been modified after the minting process or not?
No activity yet