Quantstamp reviewed OnRe (Nayms - OnRe Offer/Redemption Program Spec) on 3 Apr 2025: 2 findings, 0 critical; 1 marked fixed, 1 acknowledged; 1 more marked mitigated.
Report hosted on certificate.quantstamp.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed | Mitigated |
|---|---|---|---|---|
| Critical | 0 | 0 | 0 | 0 |
| High | 0 | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 | 0 |
| Low | 0 | 1 | 1 | 1 |
Marked Informational by the firm. Not counted as findings.
When calculating how many tokens the user should receive in the `calculate_buy_amount()` function, there is a potential for some small amount of precision to be lost when the sell token has more decimals than the buy token. This is important because the team has outlined their intent to use `USDC` (six decimals) in the protocol, while the `ONe` and `rONe` tokens both have nine decimals. There are two scenarios to be aware of that could cause problems: 1. The user requests to redeem an amount of `rONE` tokens with seven or more decimals. 2. The `USDC`:`ONe` ratio when calling the `take_offer_two()` function causes a normal redemption amount to lose some precision when redeeming a partial amount in `USDC`.
The `instructions::initialize::initialize()` function does not display an error if `state.boss` is already set. Not returning an error makes it harder to detect if the state was already initialized.
The `instructions::take_offer::calculate_buy_amount()` function does not return an error if the calculated buy token amount is zero because of integer truncation (rounding). Not checking the return value may lead to unexpected behavior.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (1)
240 projects reviewed · 338 reports · latest Nov 2026
See Quantstamp’s auditsSomething 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