MetaPool

Resonance Security8 Aug 20258 addresses on Ethereum and Solana

Audit · firm’s term: smart contract audit

Resonance Security reviewed Meta Pool (MetaPool) on 8 Aug 2025: 11 findings, 0 critical; 9 marked fixed, 2 open.

No open critical findings

Open the report Open Meta Pool’s security record

Report stored on IPFS. Content hash QmeGnaTjX5NXYH7GHVLUfG6yKkKFMnA9EP4PTvfMjaLFqE

Trustblock does not review code.

Findings11

Statuses are the security firm’s own, from its report.

Severity	Open	Fixed
Critical	0	0
High	0	0
Medium	0	0
Low	2	9

LowMissing Usage Of NEAR SDK Integer Types For Input And OutputOpen

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.

LowUsage Of std Vec Not Gas EfficientOpen

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.