0% found this document useful (0 votes)
14 views16 pages

Mechanics Completely Changing Soon!

Descriptive Anonymously

Uploaded by

hollandyogh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
14 views16 pages

Mechanics Completely Changing Soon!

Descriptive Anonymously

Uploaded by

hollandyogh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

Security Assessment

Fluffy Coin
Jan 4th, 2022
Fluffy Coin Security Assessment

Table of Contents
Summary

Overview
Project Summary
Audit Summary
Vulnerability Summary
Audit Scope

Findings
TOK-01 : `allowance` Not Updated in `transferFrom()`
TOK-02 : Initial token distribution
TOK-03 : Declare Variable As `constant`
TOK-04 : Missing Emit Events
TOK-05 : Unlocked Compiler Version

Appendix

Disclaimer

About
Fluffy Coin Security Assessment

Summary
This report has been prepared for Fluffy Coin to discover issues and vulnerabilities in the source code of
the Fluffy Coin project as well as any contract dependencies that were not part of an officially recognized
library. A comprehensive examination has been performed, utilizing Static Analysis and Manual Review
techniques.

The auditing process pays special attention to the following considerations:

Testing the smart contracts against both common and uncommon attack vectors.
Assessing the codebase to ensure compliance with current best practices and industry standards.
Ensuring contract logic meets the specifications and intentions of the client.
Cross referencing contract structure and implementation against similar smart contracts produced
by industry leaders.
Thorough line-by-line manual review of the entire codebase by industry experts.

The security assessment resulted in findings that ranged from critical to informational. We recommend
addressing these findings to ensure a high level of security standards and industry practices. We suggest
recommendations that could better serve the project from the security perspective:

Enhance general coding practices for better structures of source codes;


Add enough unit tests to cover the possible use cases;
Provide more comments per each function for readability, especially contracts that are verified in
public;
Provide more transparency on privileged activities once the protocol is live.
Fluffy Coin Security Assessment

Overview
Project Summary

Project Name Fluffy Coin

Description ERC20

Platform bsc

Language Solidity

Codebase https://bscscan.com/address/0xa3abe68db1b8467b44715eb94542b20dc134f005

Commit

Audit Summary

Delivery Date Jan 04, 2022

Audit Methodology Static Analysis, Manual Review

Key Components

Vulnerability Summary

Vulnerability Level Total Pending Declined Acknowledged Partially Resolved Resolved

Critical 1 0 0 1 0 0

Major 1 0 0 1 0 0

Medium 0 0 0 0 0 0

Minor 0 0 0 0 0 0

Informational 3 0 0 3 0 0

Discussion 0 0 0 0 0 0
Fluffy Coin Security Assessment

Audit Scope

ID File SHA256 Checksum

TOK Token.sol 313a1af47fc4f7665b0b79761e26d3f6a479aeb4c857e60800399d4dee9c7266


Fluffy Coin Security Assessment

Findings

Critical 1 (20.00%)

Major 1 (20.00%)

5 Medium
Minor
0 (0.00%)
0 (0.00%)
Total Issues
Informational 3 (60.00%)

Discussion 0 (0.00%)

ID Title Category Severity Status

allowance Not Updated in


TOK-01 Volatile Code Critical Acknowledged
transferFrom()

Centralization /
TOK-02 Initial token distribution Major Acknowledged
Privilege

TOK-03 Declare Variable As constant Gas Optimization Informational Acknowledged

TOK-04 Missing Emit Events Coding Style Informational Acknowledged

TOK-05 Unlocked Compiler Version Language Specific Informational Acknowledged


Fluffy Coin Security Assessment

TOK-01 | allowance Not Updated in transferFrom()

Category Severity Location Status

Volatile Code Critical Token.sol (0xa3abe): 30 Acknowledged

Description
The function transferFrom() does not update the allowance of the msg.sender after a successful
transfer. User A could drain User B's token balance by repeatedly calling transferFrom() should User B
approve User A for any non-zero amount.

Recommendation
We recommend updating a msg.sender 's allowance when calling transferFrom() .

Alleviation
[Fluffy coin team]: Hello Certik team, I am Chris or Godsfavourcrypto, representing the Fluffy Coin
community and development team. In terms of the vulnerability, the issue has been looked into and the
community has been notified about all issues.

They have been made aware of the critical vulnerability ID TOK-01 as well, the community has been
notified not to trust any unvetted link, only using official pancakeswap, 1 inch or other reputed dex links
and not to approve any transaction from anyone you do not trust. Also we have notified them all to never
click on shady links, always to disconnect your wallet and for added security always have transaction
signing on as well as if there is any dapps feature to disable and clear the cache when not making buys or
sells.All of these announcements have been made known as standard practice to make the community
aware of the vulnerability.

I have also run through the code myself to ensure the contract is not renounced and thankfully it is not.
Should we need to make any dire changes, these can be addressed and changed by the owner and
creator of the contract, the youtuber Biaheza.
Fluffy Coin Security Assessment

TOK-02 | Initial token distribution

Category Severity Location Status

Centralization / Privilege Major Token.sol (0xa3abe): 15 Acknowledged

Description
All of the FLUF tokens are sent to the contract deployer when deploying the contract. This could be a
centralization risk as the deployer can distribute FLUF tokens without obtaining the consensus of the
community.

Recommendation
We recommend the team to be transparent regarding the initial token distribution process, and the team
shall make enough efforts to restrict the access of the private key.

Alleviation
[Fluffy coin team]: Hello Certik team, I am Chris or Godsfavourcrypto, representing the Fluffy Coin
community and development team. In terms of the vulnerability, the issue has been looked into and the
community has been notified about all issues.

They have been made aware of the critical vulnerability ID TOK-01 as well, the community has been
notified not to trust any unvetted link, only using official pancakeswap, 1 inch or other reputed dex links
and not to approve any transaction from anyone you do not trust. Also we have notified them all to never
click on shady links, always to disconnect your wallet and for added security always have transaction
signing on as well as if there is any dapps feature to disable and clear the cache when not making buys or
sells.All of these announcements have been made known as standard practice to make the community
aware of the vulnerability.

I have also run through the code myself to ensure the contract is not renounced and thankfully it is not.
Should we need to make any dire changes, these can be addressed and changed by the owner and
creator of the contract, the youtuber Biaheza.
Fluffy Coin Security Assessment

TOK-03 | Declare Variable As constant

Category Severity Location Status

Gas Optimization Informational Token.sol (0xa3abe): 6, 7, 8, 9 Acknowledged

Description
Variables totalSupply , name , symbol , and decimals could be declared as constant since these state
variables are never to be changed.

Recommendation
We recommend that those state variables should be declared constant to save gas.
Fluffy Coin Security Assessment

TOK-04 | Missing Emit Events

Category Severity Location Status

Coding Style Informational Token.sol (0xa3abe): 15 Acknowledged

Description
When assigning the initial token balance, no Transfer() event is emitted.

Recommendation
Consider adding events for sensitive actions, and emit them in the function.
Fluffy Coin Security Assessment

TOK-05 | Unlocked Compiler Version

Category Severity Location Status

Language Specific Informational Token.sol (0xa3abe): 1 Acknowledged

Description
The contract has unlocked compiler version. An unlocked compiler version in the source code of the
contract permits the user to compile it at or above a particular version. This, in turn, leads to differences in
the generated bytecode between compilations due to differing compiler version numbers. This can lead to
an ambiguity when debugging as compiler specific bugs may occur in the codebase that would be hard to
identify over a span of multiple compiler versions rather than a specific one.

Recommendation
We advise that the compiler version is instead locked at the lowest version possible that the contract can
be compiled at. For example, for version v0.8.4 the contract should contain the following line:

pragma solidity 0.8.4;


Fluffy Coin Security Assessment

Appendix
Finding Categories

Centralization / Privilege
Centralization / Privilege findings refer to either feature logic or implementation of components that act
against the nature of decentralization, such as explicit ownership or specialized access roles in
combination with a mechanism to relocate funds.

Gas Optimization
Gas Optimization findings do not affect the functionality of the code but generate different, more optimal
EVM opcodes resulting in a reduction on the total gas cost of a transaction.

Volatile Code
Volatile Code findings refer to segments of code that behave unexpectedly on certain edge cases that may
result in a vulnerability.

Language Specific
Language Specific findings are issues that would only arise within Solidity, i.e. incorrect usage of private or
delete.

Coding Style
Coding Style findings usually do not affect the generated byte-code but rather comment on how to make
the codebase more legible and, as a result, easily maintainable.

Checksum Calculation Method


The "Checksum" field in the "Audit Scope" section is calculated as the SHA-256 (Secure Hash Algorithm 2
with digest size of 256 bits) digest of the content of each file hosted in the listed source repository under
the specified commit.

The result is hexadecimal encoded and is the same as the output of the Linux "sha256sum" command
against the target file.
Fluffy Coin Security Assessment

Disclaimer
This report is subject to the terms and conditions (including without limitation, description of services,
confidentiality, disclaimer and limitation of liability) set forth in the Services Agreement, or the scope of
services, and terms and conditions provided to you (“Customer” or the “Company”) in connection with the
Agreement. This report provided in connection with the Services set forth in the Agreement shall be used
by the Company only to the extent permitted under the terms and conditions set forth in the Agreement.
This report may not be transmitted, disclosed, referred to or relied upon by any person for any purposes,
nor may copies be delivered to any other person other than the Company, without CertiK’s prior written
consent in each instance.

This report is not, nor should be considered, an “endorsement” or “disapproval” of any particular project or
team. This report is not, nor should be considered, an indication of the economics or value of any
“product” or “asset” created by any team or project that contracts CertiK to perform a security
assessment. This report does not provide any warranty or guarantee regarding the absolute bug-free
nature of the technology analyzed, nor do they provide any indication of the technologies proprietors,
business, business model or legal compliance.

This report should not be used in any way to make decisions around investment or involvement with any
particular project. This report in no way provides investment advice, nor should be leveraged as investment
advice of any sort. This report represents an extensive assessing 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. CertiK’s position is
that each company and individual are responsible for their own due diligence and continuous security.
CertiK’s goal is to help reduce the attack vectors and the high level of variance associated with utilizing
new and consistently changing technologies, and in no way claims any guarantee of security or
functionality of the technology we agree to analyze.

The assessment services provided by CertiK is subject to dependencies and under continuing
development. You agree that your access and/or use, including but not limited to any services, reports,
and materials, will be at your sole risk on an as-is, where-is, and as-available basis. Cryptographic tokens
are emergent technologies and carry with them high levels of technical risk and uncertainty. The
assessment reports could include false positives, false negatives, and other unpredictable results. The
services may access, and depend upon, multiple layers of third-parties.

ALL SERVICES, THE LABELS, THE ASSESSMENT REPORT, WORK PRODUCT, OR OTHER MATERIALS,
OR ANY PRODUCTS OR RESULTS OF THE USE THEREOF ARE PROVIDED “AS IS” AND “AS
Fluffy Coin Security Assessment

AVAILABLE” AND WITH ALL FAULTS AND DEFECTS WITHOUT WARRANTY OF ANY KIND. TO THE
MAXIMUM EXTENT PERMITTED UNDER APPLICABLE LAW, CERTIK HEREBY DISCLAIMS ALL
WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE
SERVICES, ASSESSMENT REPORT, OR OTHER MATERIALS. WITHOUT LIMITING THE FOREGOING,
CERTIK SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AND ALL WARRANTIES ARISING FROM
COURSE OF DEALING, USAGE, OR TRADE PRACTICE. WITHOUT LIMITING THE FOREGOING, CERTIK
MAKES NO WARRANTY OF ANY KIND THAT THE SERVICES, THE LABELS, THE ASSESSMENT REPORT,
WORK PRODUCT, OR OTHER MATERIALS, OR ANY PRODUCTS OR RESULTS OF THE USE THEREOF,
WILL MEET CUSTOMER’S OR ANY OTHER PERSON’S REQUIREMENTS, ACHIEVE ANY INTENDED
RESULT, BE COMPATIBLE OR WORK WITH ANY SOFTWARE, SYSTEM, OR OTHER SERVICES, OR BE
SECURE, ACCURATE, COMPLETE, FREE OF HARMFUL CODE, OR ERROR-FREE. WITHOUT LIMITATION
TO THE FOREGOING, CERTIK PROVIDES NO WARRANTY OR UNDERTAKING, AND MAKES NO
REPRESENTATION OF ANY KIND THAT THE SERVICE WILL MEET CUSTOMER’S REQUIREMENTS,
ACHIEVE ANY INTENDED RESULTS, BE COMPATIBLE OR WORK WITH ANY OTHER SOFTWARE,
APPLICATIONS, SYSTEMS OR SERVICES, OPERATE WITHOUT INTERRUPTION, MEET ANY
PERFORMANCE OR RELIABILITY STANDARDS OR BE ERROR FREE OR THAT ANY ERRORS OR
DEFECTS CAN OR WILL BE CORRECTED.

WITHOUT LIMITING THE FOREGOING, NEITHER CERTIK NOR ANY OF CERTIK’S AGENTS MAKES ANY
REPRESENTATION OR WARRANTY OF ANY KIND, EXPRESS OR IMPLIED AS TO THE ACCURACY,
RELIABILITY, OR CURRENCY OF ANY INFORMATION OR CONTENT PROVIDED THROUGH THE
SERVICE. CERTIK WILL ASSUME NO LIABILITY OR RESPONSIBILITY FOR (I) ANY ERRORS, MISTAKES,
OR INACCURACIES OF CONTENT AND MATERIALS OR FOR ANY LOSS OR DAMAGE OF ANY KIND
INCURRED AS A RESULT OF THE USE OF ANY CONTENT, OR (II) ANY PERSONAL INJURY OR
PROPERTY DAMAGE, OF ANY NATURE WHATSOEVER, RESULTING FROM CUSTOMER’S ACCESS TO
OR USE OF THE SERVICES, ASSESSMENT REPORT, OR OTHER MATERIALS.

ALL THIRD-PARTY MATERIALS ARE PROVIDED “AS IS” AND ANY REPRESENTATION OR WARRANTY
OF OR CONCERNING ANY THIRD-PARTY MATERIALS IS STRICTLY BETWEEN CUSTOMER AND THE
THIRD-PARTY OWNER OR DISTRIBUTOR OF THE THIRD-PARTY MATERIALS.

THE SERVICES, ASSESSMENT REPORT, AND ANY OTHER MATERIALS HEREUNDER ARE SOLELY
PROVIDED TO CUSTOMER AND MAY NOT BE RELIED ON BY ANY OTHER PERSON OR FOR ANY
PURPOSE NOT SPECIFICALLY IDENTIFIED IN THIS AGREEMENT, NOR MAY COPIES BE DELIVERED TO,
ANY OTHER PERSON WITHOUT CERTIK’S PRIOR WRITTEN CONSENT IN EACH INSTANCE.

NO THIRD PARTY OR ANYONE ACTING ON BEHALF OF ANY THEREOF, SHALL BE A THIRD PARTY OR
OTHER BENEFICIARY OF SUCH SERVICES, ASSESSMENT REPORT, AND ANY ACCOMPANYING
Fluffy Coin Security Assessment

MATERIALS AND NO SUCH THIRD PARTY SHALL HAVE ANY RIGHTS OF CONTRIBUTION AGAINST
CERTIK WITH RESPECT TO SUCH SERVICES, ASSESSMENT REPORT, AND ANY ACCOMPANYING
MATERIALS.

THE REPRESENTATIONS AND WARRANTIES OF CERTIK CONTAINED IN THIS AGREEMENT ARE


SOLELY FOR THE BENEFIT OF CUSTOMER. ACCORDINGLY, NO THIRD PARTY OR ANYONE ACTING
ON BEHALF OF ANY THEREOF, SHALL BE A THIRD PARTY OR OTHER BENEFICIARY OF SUCH
REPRESENTATIONS AND WARRANTIES AND NO SUCH THIRD PARTY SHALL HAVE ANY RIGHTS OF
CONTRIBUTION AGAINST CERTIK WITH RESPECT TO SUCH REPRESENTATIONS OR WARRANTIES OR
ANY MATTER SUBJECT TO OR RESULTING IN INDEMNIFICATION UNDER THIS AGREEMENT OR
OTHERWISE.

FOR AVOIDANCE OF DOUBT, THE SERVICES, INCLUDING ANY ASSOCIATED ASSESSMENT REPORTS
OR MATERIALS, SHALL NOT BE CONSIDERED OR RELIED UPON AS ANY FORM OF FINANCIAL, TAX,
LEGAL, REGULATORY, OR OTHER ADVICE.
Fluffy Coin Security Assessment

About
Founded in 2017 by leading academics in the field of Computer Science from both Yale and Columbia
University, CertiK is a leading blockchain security company that serves to verify the security and
correctness of smart contracts and blockchain-based protocols. Through the utilization of our world-class
technical expertise, alongside our proprietary, innovative tech, we’re able to support the success of our
clients with best-in-class security, all whilst realizing our overarching vision; provable trust for all
throughout all facets of blockchain.

You might also like