Haddies Bay Club
HBC is a collection of 7777 Haddie the 1-in-100-million Cotton Candy Lobster NFTs. On November 5, 2021, Haddie was discovered off the coast of Portland, Maine by local lobsterman Billy Coppersmith. Founder Chief Curator Mark Murrell (GetMaineLobster.com) has a partnership with Coppersmith and became Haddieâs trusted guardian. Though Mark quickly found Haddie a forever home at a local aquarium, he knew the whole world would fall in love with her amazing colors if given a chance to behold Haddieâs beautyâŠ.he was right. Haddie took over social and the newsâŠshe was an overnight sensation. Now weâre building a special â1-in-100-millionâ community around this ultra-rare lobster!
Owner privileges
Comments
Ownership Privileges
- Set fees, but not more than 25%
- Set swap back amount but it must be at least 0.05% of the total supply
- Include/Exclude multiple accounts from fees and rewards
Note - This Audit report consists of a security analysis of the Haddies Bay Club token smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the Haddies Bay Club team, other contracts associated with the project were not audited by our team. We recommend investors to do their own research before investing
Audit Scope
This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.
We will verify the following claims:- Correct implementation of Token standard
- Deployer cannot mint any new tokens
- Deployer cannot burn or lock user funds
- Deployer cannot pause the contract
- Overall checkup (Smart Contract Security)
- Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
- Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.
Functions
public
66
State variables
public
9
Total lines
of code
1643
Capabilities
Hover on items
Audit Details
Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.
Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L1074
L1445
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L1237-1243
L1245-1254
L1256-1262
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L983
Check that the address is not zero.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L494-496
L504-510
L523-529
L537-548
L583-585
L593-602
L556-558
L566-575
L441-451
L469-474
L610-630
L106-108
L376-385
L336-338
L402-411
L207-213
L249-254
L261-266
L232-242
L220-225
Remove unused functions.
Pending
#2 Issue
Unused return values (unused-return)
L1537-1550
Ensure that all the return values of the function calls are used.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L165-167
L173-176
L1044-1046
L1048-1050
L1052-1054
L1065-1072
L1074-1081
L1083-1090
L1092-1107
L1109-1120
L1122-1136
L1138-1140
L1142-1144
L1146-1156
L1158-1171
L1186-1194
L1233-1235
L1440-1442
Use the `external` attribute for functions never called from the contract.
Diagrams
Disclaimer
SolidProof.io reports are not, nor should be considered, an âendorsementâ or âdisapprovalâ of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any âproductâ or âassetâ created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etcâ...)
SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.
SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProofâs position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.