Rara security record
As of 3 Nov 2026, Rara has 1 audit report on Trustblock, by Quantstamp, dated 21 Apr 2022. That report lists no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Audits1
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Rara | Security firm: Quantstamp | Date: | Scope: Files named in the report | No open critical findings | Open · certificate.quantstamp.com |
Findings13
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 1 |
| Low | 1 | 4 | 7 |
LowPossible Wrong Taker Amount ValueRara · Quantstamp · 21 Apr 2022Acknowledged
Executing `info.totalCuratorLiability -= info.referrerCut` in `ReactionVault._spendReaction()` before computing `takerAmount` reduces the taker value.
Open the reportLowRe-registering NFTs Transfers Taker RewardsRara · Quantstamp · 21 Apr 2022Acknowledged
The rewards for `takers` whenever reactions are spent are stored in the `nftOwnerRewards` mapping. This is a mapping from `rewardsIndex` to the rewards. Since the `rewardsIndex` does not include any information about the address owner, the address that is currently registered as the owner of the NFT will be able to claim the rewards.
Open the reportLowRe-registering NFTs Without De-registering Is PossibleRara · Quantstamp · 21 Apr 2022Acknowledged
The design plan document states: > If an NFT is already registered, trying to re-register will fail. The owner will need to de-register before the register call can be made again. However, the `_registerForOwner` function in `MakerRegistrar` does not check if the NFT is already registered. It simply overwrites the `sourceToDetailsLookup` mapping with the new information.
Open the reportLowUpgradeable ContractsRara · Quantstamp · 21 Apr 2022Acknowledged
Many contracts are implemented using the proxy pattern to be upgradeable. As a result, some address that owns the proxy is able to upgrade the contract and completely change its code. Since the new code could be anything, it is important to implement good security practices around the address that is capable of upgrading the contracts.
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="rara"></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