- Home
- Security Audits
- Bitcoin.com
Web3 · Smart Contract Audit
Bitcoin.com Security Audits
softstack has completed 2 smart contract audits for Bitcoin.com between June 2023 and October 2024, reporting 10 findings in total (6 low and 4 informational), of which 1 were resolved or mitigated before the final reports. Every report is published in the softstack public audit archive.
Key facts
- Client
- Bitcoin.com
- Audits completed
- 2
- First audited
- Latest audit
- Chains
- Ethereum
- Languages
- Solidity
- Market cap
- $202,643 as of 2026-09-30
About the project
Bitcoin.com is a cryptocurrency platform that has operated since 2015, providing tools to buy, sell, trade, store and earn Bitcoin and other digital assets. It publishes the self-custodial Bitcoin.com Wallet app, a news portal and educational material for newcomers. Its ecosystem includes VERSE, an Ethereum-based rewards and utility token earned through platform activity.
Case study
Findings
Combined across all 2 reviews softstack has completed for Bitcoin.com. Each report is broken out below.
1 of 10 findings resolved before the final reports.
Reports
Newest first. Every report covers its own scope and commit.
Verse Dynamic Rewards Farming smart contract audit
0Critical0High0Medium4Low3Informational1 of 7 resolved
Scope
Source repositorygithub.com/bitcoin-portal/sol-farmsComponents reviewed
1 module- See the published report for the file list
All 7 findings
ID Title Severity Status 6.2.1Missing SafeApprove Pattern in the approve Function While the increaseAllowance and decreaseAllowance functions are already implemented in the contract, the approve function lacks the necessary validation to prevent potential race conditions or re-entrancy issues.
Low acknowledged 6.2.2Insufficient Validation of Reward Token Addresses The _validateRewardToken function only checks if the token address is non-zero and not already added. It doesn't verify if the address actually represents a valid ERC20 token contract.
Low acknowledged 6.2.3Inflexible Reward Token Management Due to Fixed Token Limit The DynamicRewardFarm contract has a hardcoded limit of 10 reward tokens (MAX_TOKENS = 10). Once this limit is reached, no new reward tokens can be added, and there is no mechanism to remove existing tokens.
Low acknowledged 6.2.4Insufficient Token Validation in setRewardRates Function The setRewardRates function in the DynamicRewardFarm contract lacks proper validation of the reward tokens passed as parameters.
Low fixed 6.2.5Duplicate Token Validation Logic in DynamicRewardFarm Contract The DynamicRewardFarm contract contains two separate functions, _validateRewardToken and _onlyExistingToken, which perform similar token validation checks. This duplication of functionality
Informational acknowledged 6.2.6Incorrect Import of SafeERC20 in TokenWrapper Contract The TokenWrapper contract currently imports a non-standard version of SafeERC20.sol. It should import the well-established and widely-used version provided by OpenZeppelin for security and best practices in handling ERC-20 tokens.
Informational acknowledged 6.2.7Missing Event Emission for New Reward Token Addition The addRewardToken function in the DynamicRewardFarm contract adds a new reward token to the farm but fails to emit an event to signal this significant state change.
Informational acknowledged Liquidity Maker smart contract audit
0Critical0High0Medium2Low1Informational0 of 3 resolved
All 3 findings
ID Title Severity Status 6.2.1Redundant References In LiquidityMaker.sol, references to router and WETH are stored twice: once as an address and once as an interface. This redundancy could lead to higher gas costs and bytecode size.
Low acknowledged 6.2.2Over-Approval of Tokens By calling the makeLiquidity or makeLiquidityDual function, the contract first swaps the given token and adds afterwards the two tokens to a liquidity pool.
Low acknowledged 6.2.3Floating Compiler Version The current pragma Solidity directive is floating. It is recommended to specify a fixed compiler version to ensure that the bytecode produced does not vary between builds.
Informational acknowledged
About this engagement
A smart contract audit reviews on-chain code for flaws an attacker could exploit. Engineers trace how assets move through the contracts, check who can call privileged functions, and test the arithmetic, external calls and upgrade paths. Each finding is rated by severity, and fixes are re-checked before the final report.
How softstack runs smart contract auditsMethodology
Review process
Scoping and threat modelling
The commit hash is frozen and the attack surface is mapped: asset flows, trust assumptions, privileged roles and the external systems the code depends on.
Automated analysis
Static analysers sweep the full codebase to surface known weakness patterns, unreachable states and deviations from established conventions.
Manual code review
Independent engineers read the code line by line, concentrating on business logic, access control, arithmetic and the handling of external calls.
Adversarial testing
Property-based fuzzing and invariant tests attack the assumptions the protocol relies on, targeting states that ordinary unit tests never reach.
Reporting
Every finding is documented with a severity rating, its impact, the steps to reproduce it and a concrete remediation the team can act on.
Remediation verification
Submitted fixes are re-reviewed against the original finding, and the final report records the resolved state of each one.
Standards and references
- SWC RegistrySmart Contract Weakness Classification
- CWECommon Weakness Enumeration
FAQ
Bitcoin.com was audited by softstack GmbH, a German Web3 security and software company based in Flensburg and certified to ISO/IEC 27001 by TÜV SÜD. softstack has completed 2 smart contract audits for Bitcoin.com between June 2023 and October 2024. The published reports are linked on this page and in the softstack public audit archive.
2 separate reviews, the first in June 2023 and the most recent in October 2024. Each one covers its own scope and commit, and is listed individually on this page.
10 findings across all 2 reviews: 6 low and 4 informational. 1 of 10 were resolved or mitigated before the final reports.
Each report covers the code as it stood at the commit it names, the most recent in October 2024. Any code changed after that point is outside the reviewed scope.
Related audits
Browse all security auditsDisclaimer
This audit represents a point-in-time security assessment of the reviewed codebase and is intended for informational purposes only. While Softstack applies industry-standard security review methodologies, no audit can guarantee the absence of vulnerabilities, bugs, or other security risks. This report does not constitute financial, legal, regulatory, or investment advice, nor does it endorse the project, its business model, products, or services. Security is an ongoing process, and we strongly recommend conducting a new assessment following any material code changes or at least every 6 months to address newly emerging threats, vulnerabilities, and ecosystem developments.