top of page



We are excited to share CertiK's score and underlying report on CryptoChronic and our code. CertiK is a renowned blockchain security firm known for its comprehensive auditing procedure. Their certification ensures projects meet high standards of safety, integrity, and security. Our score is currently 68.78% and fluctuates based on social and GitHub activity. This places us solidly within the Top 20 percentile, ranked at number 2009 among the tens of thousands of Crypto projects scrutinised. With a Fundamental Health Score of 70%, Code Security of 91.93%, and Community Trust score of 73.73%, CryptoChronic stands out among pre-launch indie GameFi projects. Our operational resilience exceeds 60.09% and continues to grow. Although penalized for not being listed on a centralized exchange, we will implement a bug-bounty program after launch to improve resilience. Market Stability and Governance Strength scores are both 50% due to our unique design and freemium model, which prioritizes democratization over full decentralization. Receiving a CertiK certificate is a significant achievement, showcasing our commitment to transparency, security, and innovation in providing a trusted platform for users. Some considerations to be made:


  • CryptoChronic has received its Certificate and the certifiers are deemed satisfied.

  • CertiK indicated 8 issues of different severity levels, ranging from Informational to Major.

  • We hence have NO Critical Issues.

  • We resolved one Minor Issue regarding volatile code and an Informational issue related to coding style. Specifically, for CCK-03 (Usage Of transfer/send For Sending Ether Volatile Code), we addressed it by revising the code and using PullPayments of OpenZeppelin, which incorporates an Escrow mechanism. Furthermore, for CCK-04 (Missing Error Messages Coding Style), we resolved the issue simply by revising the code.

  • The remaining 6 issues have all been acknowledged and alleviated. Of these, 3 are Minor, 4 merely Informational, and one has been labelled a Major one, theoretically.

  • We have improved this issue, although it is inherent to our model to some extent. To alleviate it, we have implemented access control with 3 roles and 1 owner. Only the owner can set the access control, the Finance role is responsible for retrieving ETH from the contract, the Admin role handles the setup required by the game, and the Whitelister role manages whitelisting for promotions, even in the future. While we commit to further alleviating the issue, such as implementing multi-signature wallets and a time-lock with a reasonable latency (48H) to enhance awareness of privileged operations, we must maintain certain privileges to remain true to our vision. Decentralized computing doesn't necessarily require a decentralized market. Although the blockchain itself is decentralized, major operators and marketplaces are centralized. They, like us, aim to promote consensus and mass adoption of crypto but need to make compromises. We believe that current offerings prioritize decentralization at the expense of democracy due to high costs. Our Unique Value Proposition is to democratize the market through freemium pricing and a free-to-earn model. To achieve this, we operate on our private chain, sacrificing some decentralization to bring crypto closer to mass adoption.

  • As mentioned, the Minor and Informational issues have been adequately addressed by us in a way deemed satisfactory by CertiK. We have resolved all of them, utilizing interventions ranging from using PrevranDao instead of Difficulty to improve randomness (as our private chain doesn't support PrevranDao) to implementing PullPayments of OpenZeppelin, which incorporates an escrow mechanism. Regarding one of the Minor issues, there is no need to store the value in a state variable as it is already stored by the mint function itself. No changes are required, as events should be used to acknowledge the return value. In other cases, as well, only a few changes were necessary.

  • Our community has our commitment, in any case, to constantly improving and evolving, and in doing so we pledge to continue alleviating this issue as much and as soon as possible, implementing all the necessary steps to make our ecosystem as safe and as rewarding for everyone.

  • Overall, therefore, CertiK attests that our code is safe, secure, stable, and ready to be deployed for your enjoyment and profit.

bottom of page