Reserve security record
As of 20 Oct 2026, Reserve has 4 audit reports by 4 security firms on Trustblock; the latest is by Oak Security, dated 12 Mar 2026. Those reports list no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.
Audits4
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Reserve Updates audit | Security firm: Oak Security | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · GitHub |
| Reserve security review | Security firm: Pashov Audit Group | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · GitHub |
| Reserve | Security firm: Ackee Blockchain Security | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · GitHub |
| RToken Ethereum Contracts | Security firm: Quantstamp | Date: | Scope: Files named in the report | No open critical findings | Open · certificate.quantstamp.com |
Findings22
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 1 |
| Medium | 0 | 1 | 4 |
| Low | 4 | 7 | 5 |
LowAllowance Double-Spend ExploitRToken Ethereum Contracts · Quantstamp · 31 Oct 2019Open
As it presently is constructed, the contract is vulnerable to the [allowance double-spend exploit](https://github.com/OpenZeppelin/openzeppelin-solidity/blob/b4f87bb8fc25fb07f73099701e39e167a3d36465/contracts/token/ERC20/ERC20.sol#L71-L78), as with other ERC20 tokens.
Open the reportLowSource Account can be RecipientRToken Ethereum Contracts · Quantstamp · 31 Oct 2019Open
While the code prevents from the obvious inheritance case where the recipient is the original owner (`SELF_HAT_ID`) on `L478`, it seems that the `src` can hand craft a hat that makes him-/her-self a recipient. This way it would be automatically inherited by the recipient.
Open the reportLowUnlocked PragmaRToken Ethereum Contracts · Quantstamp · 31 Oct 2019Open
Every Solidity file specifies in the header a version number of the format `pragma solidity (^)0.5.*`. 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. Because the use of `ABIEncoderV2`, the `pragma` should be locked above `0.5.10`, as there is a known bug in array storage: [https://blog.ethereum.org/2019/06/25/solidity-storage-array-bugs/](https://blog.ethereum.org/2019/06/25/solidity-storage-array-bugs/) There are currently no signed integer arrays that are initialized in a vulnerable way, hence the low severity of this issue. However, it is best to take precautions for future updates of the code.
Open the reportLowUser can Lock Oneself OutRToken Ethereum Contracts · Quantstamp · 31 Oct 2019Open
In the functions `distributeLoans` and `recollectLoans` a user may accidentally lock oneself out if the number of `recipients` or the number of `proportions` is too high. Consequently, the for loops on lines 612, 619, 697 and 793 will require too much gas to finish and the transaction (function call) will fail for those accounts.
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="reserve"></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