Acid security record
As of 3 Nov 2026, Acid has 2 audit reports by 2 security firms on Trustblock; the latest is by HashEx, dated 20 Apr 2023. Those reports list no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Audits2
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| 0xACID | Security firm: HashEx | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · hashex.org |
| Acid - DigixDAO Dissolution Contract | Security firm: Quantstamp | Date: | Scope: Files named in the report | No open critical findings | Open · certificate.quantstamp.com |
Findings25
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 2 | 1 |
| Medium | 0 | 4 | 5 |
| Low | 0 | 4 | 9 |
HighUnchecked Return ValueAcid - DigixDAO Dissolution Contract · Quantstamp · 27 Jan 2020Fixed
Most functions will return a `true` or `false` value upon success. Some functions, like `send()`, are more crucial to check than others. It's important to ensure that every necessary function is checked. Line 53 of `Acid.sol` transfers Ether using `address.call.value()`. If the transfer fails, this method does not revert the transaction. Instead, it returns `false`. The check for the return value is not present in the code.
Open the reportMediumInitialization problem0xACID · HashEx · 20 Apr 2023Fixed
The report gives no description here.
Open the reportMediumWrong imports0xACID · HashEx · 20 Apr 2023Fixed
The report gives no description here.
Open the reportMediumGas Usage / `for` Loop ConcernsAcid - DigixDAO Dissolution Contract · Quantstamp · 27 Jan 2020Fixed
Gas usage is a main concern for smart contract developers and users, since high gas costs may prevent users from wanting to use the smart contract. Even worse, some gas usage issues may prevent the contract from providing services entirely. For example, if a `for` loop requires too much gas to exit, then it may prevent the contract from functioning correctly entirely. It is best to break such loops into individual functions as possible.
Open the reportMediumInteger Overflow / UnderflowAcid - DigixDAO Dissolution Contract · Quantstamp · 27 Jan 2020Fixed
Integer overflow/underflow occur when an integer hits its bit-size limit. Every integer has a set range; when that range is passed, the value loops back around. A clock is a good analogy: at 11:59, the minute hand goes to 0, not 60, because 59 is the largest possible minute. Integer overflow and underflow may cause many unexpected kinds of behavior and was the core reason for the `batchOverflow` attack. Here's an example with `uint8` variables, meaning unsigned integers with a range of `0..255`. ``` function under_over_flow() public { uint8 num_players = 0; num_players = num_players - 1; // 0 - 1 now equals 255! if (num_players == 255) { emit LogUnderflow(); // underflow occurred } uint8 jackpot = 255; jackpot = jackpot + 1; // 255 + 1 now equals 0! if (jackpot == 0) { emit LogOverflow(); // overflow occurred } } ```
Open the reportMediumRepeatedly InitializableAcid - DigixDAO Dissolution Contract · Quantstamp · 27 Jan 2020Fixed
The contract is repeatedly initializable.
Open the reportLowGas optimizations0xACID · HashEx · 20 Apr 2023Fixed
The report gives no description here.
Open the reportLowGas optimizations0xACID · HashEx · 20 Apr 2023Fixed
The report gives no description here.
Open the reportLowGas optimizations0xACID · HashEx · 20 Apr 2023Fixed
The report gives no description here.
Open the reportLowGas optimizations0xACID · HashEx · 20 Apr 2023Fixed
The report gives no description here.
Open the reportShow 5 more
LowGas optimizations0xACID · HashEx · 20 Apr 2023Fixed
The report gives no description here.
Open the reportLowUnused parameter0xACID · HashEx · 20 Apr 2023Fixed
The report gives no description here.
Open the reportLowRace Conditions / Front-RunningAcid - DigixDAO Dissolution Contract · Quantstamp · 27 Jan 2020Fixed
A block is an ordered collection of transactions from all around the network. It's possible for the ordering of these transactions to manipulate the end result of a block. A miner attacker can take advantage of this by generating and moving transactions in a way that benefits themselves.
Open the reportLowUnchecked ParameterAcid - DigixDAO Dissolution Contract · Quantstamp · 27 Jan 2020Fixed
The address as input for the `init` function is never checked to be non-zero in `Acid.sol`.
Open the reportLowUnlocked PragmaAcid - DigixDAO Dissolution Contract · Quantstamp · 27 Jan 2020Fixed
Every Solidity file specifies in the header a version number of the format `pragma solidity (^)0.4.*`. The caret (`^`) before the version number implies an unlocked pragma, meaning that the compiler will use the specified version _and above_, hence the term "unlocked." For consistency and to prevent unexpected behavior in the future, it is recommended to remove the caret to lock the file onto a specific Solidity version.
Open the reportContracts
No deployed address is recorded for these audits.
The reports name a repository or files. Open a report to see its scope.
Show this on your site
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Content
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
Style
Format
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="0xacid"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us