Ethereum Commonwealth Security Department conducted over 400 security audits since 2018. Not even a single contract that we audited was hacked. You can access our audit reports in the ISSUES of this repo. We are accepting new audit requests.
This Audit provides due-diligence project audits for various BSC projects. Dessert Finance in no way guarantees that a project will not remove liquidity, sell off team supply, or otherwise exit scam.
This Audit does the legwork and provides public information about the project in an easy-to-understand format for the common person.
his disclosure policy defines the rules by which the Security Department will publish the results of its work during audits of open-source smart-contracts.
If no errors are found in the contract, the head of the security department may notify the customer about the completion of the audit and publish the report immediately after the completion of the audit.
If there is not enough information provided to contact the developer of the contract or the requester of the security audit, then the head of the security department should publish the report immediately after the audit is completed without notifying any parties about the completion of the audit.
If errors of medium, high or critical severity were found in the contract, then the head of the Security Department must contact the developer of the smart contract and report any errors found during the audit. The head of the Security Department must not publish the results within 15 days after the completion of the audit and finding errors.
If the contract contains errors of medium, high or critical severity, but there is not enough information provided for the head of the Security Department to contact the developer of the smart contract, then the Callisto Network announces the completion of the audit using its media resources to attract the attention of the contract developers within 15 days since the completion of the audit.
After 15 days from the date of the completion of the audit, the head of the Security Department must publish the results regardless of the severity of the findings and a reaction of the developers of the smart-contract.
Agreeing to a project audit can be seen as a sign of confidence and is generally the first sign of trust for a project, but in no way guarantees that a team will not remove all liquidity (“Rug Pull”), sell off tokens, or completely exit scam. It is ultimately your responsibility to read through all documentation, social media posts, and contract code of each individual project to draw your own conclusions and set your own risk tolerance.
This audit in no way takes responsibility for any losses, nor does Dessert Finance encourage any speculative investments. The information provided in this audit is for information purposes only and should not be considered investment advice.
Common vulnerabilities were not found in the token’s Smart Contract as shown above.
Social Media
This audit is able to locate a variety of Social Media networks for the project including Twitter,Telegram and official website,All links have been conveniently placed below.
This Audit provides due-diligence project audits for various BSC projects. Dessert Finance in no way guarantees that a project will not remove liquidity, sell off team supply, or otherwise exit scam.
This Audit does the legwork and provides public information about the project in an easy-to-understand format for the common person.
Source code
https://bscscan.com/address/0xf47b6915023de9b464e7f9522ba400c48f579d45#code
Disclosure policy
his disclosure policy defines the rules by which the Security Department will publish the results of its work during audits of open-source smart-contracts.
If no errors are found in the contract, the head of the security department may notify the customer about the completion of the audit and publish the report immediately after the completion of the audit.
If there is not enough information provided to contact the developer of the contract or the requester of the security audit, then the head of the security department should publish the report immediately after the audit is completed without notifying any parties about the completion of the audit.
If errors of medium, high or critical severity were found in the contract, then the head of the Security Department must contact the developer of the smart contract and report any errors found during the audit. The head of the Security Department must not publish the results within 15 days after the completion of the audit and finding errors.
If the contract contains errors of medium, high or critical severity, but there is not enough information provided for the head of the Security Department to contact the developer of the smart contract, then the Callisto Network announces the completion of the audit using its media resources to attract the attention of the contract developers within 15 days since the completion of the audit.
After 15 days from the date of the completion of the audit, the head of the Security Department must publish the results regardless of the severity of the findings and a reaction of the developers of the smart-contract.
Agreeing to a project audit can be seen as a sign of confidence and is generally the first sign of trust for a project, but in no way guarantees that a team will not remove all liquidity (“Rug Pull”), sell off tokens, or completely exit scam. It is ultimately your responsibility to read through all documentation, social media posts, and contract code of each individual project to draw your own conclusions and set your own risk tolerance.
This audit in no way takes responsibility for any losses, nor does Dessert Finance encourage any speculative investments. The information provided in this audit is for information purposes only and should not be considered investment advice.
Table of Contents:
Website Part 1 – Overview
www.tigercoin.cc
BEP-20 Contract Audit – Common Vulnerabilities
✓ Integer Underflow ✓ Integer Overflow ✓ Callstack Depth Attack ✓ Timestamp Dependency ✓ Parity Multisig Bug ✓ Dependency
Code is truncated to fit the constraints of this document.
https://bscscan.com/address/0xf47b6915023de9b464e7f9522ba400c48f579d45#code
✓The contract code is verified on BSCScan.
Common vulnerabilities were not found in the token’s Smart Contract as shown above.
Social Media
This audit is able to locate a variety of Social Media networks for the project including Twitter,Telegram and official website,All links have been conveniently placed below.
The social ways to contact $TIGER:
Twitter:https://www.twitter.com/tigercoindao Telegram:https://t.me/tigercoindaogroup Official website:http://www.tigercoin.cc
Top Token Holders
The top token holders at the time of the audit are shown below.
1,[0x448fd77ce84f49156afa4bf60c5081d9274cb26c] 69.9417%, DODO MINE V3 2,[0xf884e7368d5e4950e9d93622b6ddf6346ec18eea] 10% DODO Vending machine 3,[0x525f41d62fa8c878cfb15db7337d1f88d4a771be] 5.0583% Crowd pooling 4,[0x8262dbe5069be42bd536a70543ceeb119afce33e] 5% Team 5,[0x436d70e0ee993985f2565bbd76550704b1ae7c82] 5% Marketing wallet 6,[0xa8a7c509fca290e79ba84b7fcb0d6b58ef07ccbb] 2.5% Governance wallet
Location Audit
We were unable to identify a primary location for the project at this time or a location has not been declared.
Tiger coin is published on DODOEX. Add the liquidity on DODOEX.
THANK YOU.