Quantstamp reviewed Chromia (Chromia FT4 (token library)) on 21 Jun 2024: 10 findings, 0 critical; 8 marked fixed, 2 acknowledged.
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 |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 2 |
| Low | 0 | 2 | 6 |
While not an issue in and of itself, the FT4 library may have some default behaviors that will be unexpected for users/developers from other ecosystems. When integrating the library, developers should confirm whether this is the desired behavior for their dapp and make any necessary adjustments. Additionally, users should be aware of the possibility of these behaviors before interacting with a dapp. A non-exhaustive list of these behaviors includes: * `rell/src/lib/ft4/external/admin/operations::mint()`: The admin can mint any amount of an asset without restriction. * `rell/src/lib/ft4/external/assets/operations::burn()`: Unlike the ERC-20 standard in which burning is a custom extension, the FT4 library has burning enabled as a default. More specifically, a user can decide to burn their own assets.
`get_first_allowed_auth_descriptor()` makes a call to `get_auth_handler(op_name).resolver()`. The resolver will go through the list of auth descriptors and return the first allowed one. However, there is no validation that the auth descriptor isn't violating any rules. This can result in valid auth descriptors being ignored.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (130)
236 projects reviewed · 332 reports · latest Oct 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