Co-founder & CTO of Blank. Building software and helping companies enter web3.
Co-founder & CTO of Blank. Building software and helping companies enter web3.
Subscribe to 0xMarko
Subscribe to 0xMarko
Share Dialog
Share Dialog
0xMarkoWhen 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...
0xMarkoEthereum 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...
0xMarkoWhen 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...
0xMarkoEthereum 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...
<100 subscribers
<100 subscribers
Good code is self-documenting. However, adding documentation to the code is well worth it, especially for smart contracts.
Let’s see what is NatSpec is and how to utilize it for smart contract documentation.
NatSpec is a special documentation format for Solidity smart contracts. While good contracts can be self-documenting, including NatSpec enables developers to easily share and export documentation.
The NatSpec format consists of specially formatted comments within the Solidity code. NatSpec comments start with `///` for single or `/**` ending with `*/` for multi-line comments. You are probably familiar with this syntax if you read contracts on Etherscan.
NatSpec supports different optional tags that indicate what type of information is provided. Functions usually have multiple tags attached to them, like notice, dev, params, and return.
Here is an example contract from the official Solidity documentation.
Here is a cheat sheet from the official Solidity docs that explains the purpose of each tag and where it may be used.
Once you've written tags a few times, they become familiar and you won't need to consult the cheat sheet anymore.
If no tags are used, then the Solidity compiler will interpret `///` or `/**` comments in the same way as if they were tagged with the notice tag. Nice default right there.
If you are using HardHat, then NatSpec documentation can be easily exported and updated on each compile. You'll have to add and configure `hardhat-docgen` plugin that does the magic. Plugin has different options so set it up as you like.
A good rule of thumb is to always add NatSpec for all public interfaces (everything in the ABI). Exported documentation can be easily understood by your frontend & backend teams that have to integrate smart contracts in the app.
Thanks for reading.
Follow me on Twitter for more!
Good code is self-documenting. However, adding documentation to the code is well worth it, especially for smart contracts.
Let’s see what is NatSpec is and how to utilize it for smart contract documentation.
NatSpec is a special documentation format for Solidity smart contracts. While good contracts can be self-documenting, including NatSpec enables developers to easily share and export documentation.
The NatSpec format consists of specially formatted comments within the Solidity code. NatSpec comments start with `///` for single or `/**` ending with `*/` for multi-line comments. You are probably familiar with this syntax if you read contracts on Etherscan.
NatSpec supports different optional tags that indicate what type of information is provided. Functions usually have multiple tags attached to them, like notice, dev, params, and return.
Here is an example contract from the official Solidity documentation.
Here is a cheat sheet from the official Solidity docs that explains the purpose of each tag and where it may be used.
Once you've written tags a few times, they become familiar and you won't need to consult the cheat sheet anymore.
If no tags are used, then the Solidity compiler will interpret `///` or `/**` comments in the same way as if they were tagged with the notice tag. Nice default right there.
If you are using HardHat, then NatSpec documentation can be easily exported and updated on each compile. You'll have to add and configure `hardhat-docgen` plugin that does the magic. Plugin has different options so set it up as you like.
A good rule of thumb is to always add NatSpec for all public interfaces (everything in the ABI). Exported documentation can be easily understood by your frontend & backend teams that have to integrate smart contracts in the app.
Thanks for reading.
Follow me on Twitter for more!
No activity yet