Parallel Protocol V3
Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.
Parallel V3 issues USDp through onchain Parallelizer contracts that accept reserve assets at oracle value and permit proportional basket redemption. This is a stablecoin reserve claim, not user recursive borrowing, so the leveraged-looping dossier does not apply. Parallelizer can expose individual collateral to external strategies, but current primary documents do not establish that every measured reserve is manager-routed; that must be read from getManagerData per live collateral before applying delegated allocation. With no better evidenced class, the 2026-08-16 survey value of about $2.01M across Ethereum, Avalanche, HyperEVM and Base supports the version-1 below-materiality disposition.
- TVL sustained above $100M for 30 days
- Every live collateral manager, external strategy, whitelist and reserve exposure is reconciled onchain before product-level underwriting
The research file
Mechanism and class boundary
Users mint USDp by exchanging supported collateral through a Parallelizer and can burn for an individual reserve asset or redeem for a proportional basket. sUSDp is a separate ERC-4626 savings receipt over deposited USDp. There is no required borrow-and-resupply loop or user liquidation path in this surveyed reserve mechanism, so leveraged looping is inapplicable. The protocol’s automated reserve bands also differ from a vault manager freely selecting venues.
External strategy ambiguity
Parallel’s developer interface exposes getManagerData because a collateral may be invested externally and redemption can return sub-collaterals from those strategies. That feature could make delegated allocation fundamental for a particular live reserve. The reviewed documents do not identify which current collateral has a manager, its venue allowlist or active allocation. Without onchain per-collateral manager reads, it would be speculative to classify the entire measured Parallelizer balance as delegated allocation.
Current perimeter, controls and solvency
The DefiLlama adapter reads collateral lists and balances held by Parallelizer contracts. On 2026-08-16 the API reported about $2.01M: roughly $0.82M Ethereum, $0.54M Hyperliquid L1, $0.40M Avalanche and $0.25M Base; Sonic was configured but had no nonzero sample. Parallel states that backing is held onchain without contributor access, while DAO-approved parameters, oracle configuration, whitelists, pause state and upgradeable modules still shape issuance and exits.
Exit, access and comparison
Redemption returns a proportional collateral basket and may apply a penalty below full collateralization. Whitelisted reserve assets can prevent an ineligible address from receiving its full proportional backing, while burn liquidity depends on the chosen asset. Compared with holding an eligible reserve asset directly, USDp and sUSDp add basket, oracle, module, whitelist and possible strategy look-through. Reopen after materiality and then verify every live collateral’s manager data, access status and proposed-size burn and redemption output.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Parallel — USDp and sUSDp product scope · primary · accessed 2026-08-16
Supports: USDp, sUSDp, reserve basket, ERC-4626 savings, deployments - Parallel — Parallelizer reserve mechanism · primary · accessed 2026-08-16
Supports: mint, burn, proportional redemption, oracle pricing, whitelisted collateral, penalty - Parallel — manager and redemption interface · primary · accessed 2026-08-16
Supports: getManagerData, external strategies, sub-collateral, pause, whitelist, redemption quote - Parallel — onchain proof of solvency · primary · accessed 2026-08-16
Supports: Parallelizer addresses, onchain backing, no contributor custody, Ethereum, Base, Avalanche, HyperEVM - DefiLlama adapter — Parallel V3 collateral accounting · secondary · accessed 2026-08-16
Supports: Parallelizer contracts, collateral list, reserve balances, chain perimeter - DefiLlama — Parallel V3 survey record · secondary · accessed 2026-08-16
Supports: current TVL, Ethereum, Avalanche, Hyperliquid L1, Base, CDP category
Inherited controls
The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.
| Chain | Verdict | Grade | Control constraint |
|---|---|---|---|
| Ethereum | Approved | sovereign | No sequencer, no upgrade key, no operator who can be compelled — rule changes require social consensus. |
| Avalanche | Approved · limits | crypto-backed | no party can freeze or seize C-Chain funds, but one vendor writes the only production client and Messari measured over a third of stake hosted on AWS. |
| Hyperliquid / HyperEVM | Rejected | freezable | a 21-validator permissioned set operates both the chain and its bridge — one compromise reaches both. |
| Base | Approved · limits | hybrid | Coinbase — one regulated US company — operates the only sequencer, and admin keys can upgrade bridge contracts within ~7 days. |