Project overview - GNOX
Gnox has one of the fastest-growing communities within reflection projects due to its unique DeFi treasury feature, which allows the treasury to create a higher reward return from other protocols while airdropping returns in $GNOX. We are a decentralized platform whose main goal is to connect the gap between the crypto and fiat worlds while showing the benefits and ease of use of the Gnox Protocol to everyday users. Gnox is built on the Binance Smart Chain (BSC). Binance offers quick transfer speeds, low fees, and high scalability compared to Ethereum and other competitors. The Gnox Protocol is proud to be the worldâs first reflection project which uses our treasury to invest in DeFi yield earning protocols for its users! We are establishing a new standard in tokenomics and marketing techniques within the DeFi space. Gnox believes in rewarding long-term holders/users by generating a passive income for users proportionate to what the treasury makes within the timeframe. The nature of paying rewards in $GNOX means that once we claim our rewards to pay our Gnox holders, there will always be buying pressure to support our underlying price.
Price Chart
Audit Summary
0x132f6f1743e45880aF91D25257e02DB1839bb5Ed
Comment
There can be multiple admins of these contracts and they will have control over the fee rate and the fee receiver address.
If the Owner wants he/she can assign 'n' number of admins. There is no maximum limit to adding admins.
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.
| Public functions | Public state variables | Total lines of code | Capabilities |
|---|---|---|---|
| 68 | 27 | 788 |
| Public functions | Public state variables | Total lines of code | Capabilities |
|---|---|---|---|
| 68 | 27 | 788 |
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.
#2 | Missing events
| Severity | Location | Status |
|---|---|---|
| Low | Gnox.sol: 439,761, 749, 742 | Pending |
Emit events in critical parameter changes
#3 | Floating pragma
| Severity | Location | Status |
|---|---|---|
| Low | Gnox.sol: 2 | Pending |
The current pragma Solidity directive is â^0.8.0". Contracts should be deployed with the same compiler version and flags that they have been tested with thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions.
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.