Audit · firm’s term: smart contract audit
Resonance Security reviewed Meta Pool (MetaPool) on 8 Aug 2025: 4 findings, 0 critical; all marked fixed.
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 | 0 |
| Low | 0 | 0 | 4 |
Marked Info by the firm. Not counted as findings.
The function get_number_of_accounts() makes use of intput parameters of type u64. This type is longer than 52 bits and, as such, is not serializable by JSON, therefore making it impossible to retrieve a properly decoded value when calling this function through an external integrated interface.
The state variable staking_pools makes use of Vec as a collection from Rust's std library. This collection, as opposed to NEAR SDK's Vector collection, is not as efficient in term of gas usage when dealing with large amounts of data that do not need to be accessed altogether.
Throughout the source code there are multiple instances that lead to a dead end as unimplemented features and functionalities are explicitly reverted. These should be cleaned up to increase the quality of the code and decrease the bytecode stored on the blockchain.It should be noted that while some code might be used to maintain interoperability between other contracts on the blockchain, it may still increase smart contract size while not being entirely necessary, since the blockchain may revert nonetheless.
It was observed that throughout the protocol there are multiple instances of redundant code on several accounts:Variables and values related to testing environments;Deprecated variables and values;Reimplemented standard trait implementations;Redundant functions, e.g. withdraw_all() and withdraw_unstaked();These design patterns increase code complexity and do not maximize transaction gas and storage efficiency on the blockchain.
The function ft_metadata_set() is marked as read-only, however, it mutates the storage of the smart contract, specifically the LazyOption with storage key ftmd. This fact may create inconsistencies in the usage of the protocol by its users.
The following functions and modifiers were found to be unused within the system:RewardMeter::reset()assert_min_balance()apply_multiplier()Unused functions increase the complexity and readability of the smart contract's code and their inclusion should be discouraged whenever possible.
The following Rust crates are used as dependencies of the project and contain known vulnerabilities:paste (1.0.15). paste is unmaintained. For more information: [RUSTSEC-2024-0436](https://rustsec.org/advisories/RUSTSEC-2024-0436)wee_alloc (0.4.5). wee_alloc is unmaintained. For more information: [RUSTSEC-2022-0054](https://rustsec.org/advisories/RUSTSEC-2022-0054)borsh (0.7.2). Parsing borsh messages with ZST which are not-copy/clone is unsound. For more information: [RUSTSEC-2023-0033](https://rustsec.org/advisories/RUSTSEC-2023-0033)borsh (0.8.2). Parsing borsh messages with ZST which are not-copy/clone is unsound. For more information: [RUSTSEC-2023-0033](https://rustsec.org/advisories/RUSTSEC-2023-0033)It should also be noted that the NEAR SDK version 3.1.0 is also outdated and should be bumped to more recent versions to include the latest logical, performance, and security fixes.
The report names a repository or files. Open the report to see its scope.
27 projects reviewed · 57 reports · latest Dec 2025
See Resonance Security’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