You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well, I was not able to find resources for knowing more about this, so I guess this is the best place.
I've encountered two high severity warnings on a specific contract I am developing for production. The warning is about integer underflow, even though it seems this issue is gone on versions of Solidity that are higher than and including 0.8.0.
So, I do not know if this is an issue with the code itself or if it is some issue related to solidity versioning on KARL.
Any guidance on that would be really helpful. Also, I have not found documentation for interpreting the errors - and I love that they are shown in the terminal, but some of them seem very abstract. For example, in one of the images below, there is a warning about an integer underflow in a string public name variable that receives a value in the constructor of the contract and does nothing else rather than being a view function so that NFT marketplaces can call on it to know the name of the collection. The other function with an issue is the setApprovalForAll - with no changes from the ERC1155 standard.
Thank you guys for this amazing masterpiece and wait on your response.
The text was updated successfully, but these errors were encountered:
Well, I was not able to find resources for knowing more about this, so I guess this is the best place.
I've encountered two high severity warnings on a specific contract I am developing for production. The warning is about integer underflow, even though it seems this issue is gone on versions of Solidity that are higher than and including 0.8.0.
So, I do not know if this is an issue with the code itself or if it is some issue related to solidity versioning on KARL.
Any guidance on that would be really helpful. Also, I have not found documentation for interpreting the errors - and I love that they are shown in the terminal, but some of them seem very abstract. For example, in one of the images below, there is a warning about an integer underflow in a string public name variable that receives a value in the constructor of the contract and does nothing else rather than being a view function so that NFT marketplaces can call on it to know the name of the collection. The other function with an issue is the setApprovalForAll - with no changes from the ERC1155 standard.
Thank you guys for this amazing masterpiece and wait on your response.
The text was updated successfully, but these errors were encountered: