USPD

Resonance SecurityRepository, no commit named

Audit · firm’s term: audit report

Resonance Security reviewed USPD on 4 Aug 2025: 22 findings, 1 critical; 17 marked fixed, 5 open.

1 critical finding, fixed
Open the reportOpen USPD’s security record
Report stored on IPFS. Content hash QmYXemLMTZe8icNTeZRnvha2HDETAidjzBw2XK2aKJJyzP

Trustblock does not review code.

Findings22

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

SeverityOpenAcknowledgedFixed
Critical001
High000
Medium003
Low5013
LowCentrallization Risk On cUSPDOpen

The smart contract contains several functions access controlled by administrative users with privileged rights in charge of performing admin tasks such as minting and burning tokens. These users need to be trusted not to perform malicious updates on the contract.

LowChainlink Sequencer Status Is Not CheckedOpen

The Chainlink network uses a technology called Sequencers in their Off-Chain Reporting protocol. Sequencers help in improving data transmission efficiency by enabling transaction aggregation and submitting data on-chain in batches.It is crucial for the protocol to verify the status of the Chainlink sequencer involved. Not checking the sequencer's status might lead to scenarios where the protocol is working with outdated, inaccurate, or even completely missing data. This could potentially lead to incorrect operation of the contracts or even financial loss, depending on the role of the oracle data.

LowMinting stabilizerNFT Tokens Could Be FrontrunOpen

The protocol provides first minter a 125% threshold to liquidate other positions and then this benefit decreases by a 5% until the default 110%. As there is no access control on the minting process, this function can be frontrun by other users to obtain an advantageous position.

LowMissing Zero Address ValidationsOpen

Throughout the protocol there are multiple instances where input parameters are not being validated against the Zero Address, most of which are used to perform external calls, allowing for undefined behavior within the protocol.It should be noted that although this occurs mostly in the constructor, mistakes can be made by the deployer of the smart contracts, allowing for unwanted transactions to take place in the future.

LowRedundant Code Throughout The ProtocolOpen

It was observed that throughout the protocol there are multiple instances of redundant code on several accounts:Invariant testing within the source code. Invariant testing should be done mostly within test files;Variables and values related to testing environments;Redundant functions, e.g. mint() and mintShares();These design patterns increase code complexity and do not maximize transaction gas and storage efficiency on the blockchain.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Part of USPD’s security record

USPD
Audits1 audit by 1 firmLast audit Aug 2025, by Resonance Security.
Critical findingsNo open critical findingsIn that report, 1 critical finding was reported. It is marked fixed by the firm that reported it.
Open USPD’s security record

Security firm

Resonance Security

18 projects reviewed · 25 reports · latest Aug 2025

See Resonance Security’s audits

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