Peapods Finance

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

Peapods Finance is a permissionless suite rather than one investable product: Pods wrap single assets or indexes into pTKNs, LP staking farms volatility fees, LVF borrows a paired asset against LP collateral, isolated lenders fund those loans, and Metavaults can route capital among approved Pods. DefiLlama aggregates those unlike claims under one slug and reported approximately $1.67M of unborrowed TVL on six configured chains on 2026-08-15, plus approximately $1.29M borrowed and $3.07M tagged as staking. No single shared class accurately disposes of that mixed perimeter, and the aggregate cannot support a client allocation without selecting a named Pod, lending pair, LP or Metavault. Rejected at zero pending product-level identification, look-through, controls, loss history and executable exit evidence.

Kill criteria: the events that revoke this verdict
• A named Peapods product and contract are selected with chain, assets, oracle, fees, authorities, audits, incidents and position-level balances independently reconciled
• That exact product demonstrates an executable proposed-size exit under stressed utilization or LP conditions without relying on new deposits, and passes its product-specific comparator review

The research file

Mixed mechanism and classification scope

Peapods documents independently usable primitives. A Pod wraps one or more ERC-20 assets into a synthetic pTKN; Volatility Farming pairs pTKN with another asset and stakes the LP; LVF borrows the paired asset against LP collateral; isolated lending supplies a specific LVF market; and governance-directed Metavaults allocate lender deposits among whitelisted Pods. Those mechanisms map respectively to wrapper, AMM inventory, leveraged borrowing, direct lending and delegated allocation risks. Treating the entire protocol as only below-materiality, amm-lp, leveraged-looping or delegated-allocation would incorrectly apply one product decision to balances generated by the others.

Current observation and adapter perimeter

The DefiLlama protocol API read on 2026-08-15 classified Peapods Finance as Yield, reported approximately $1.67M of TVL, and configured Mode, Ethereum, Berachain, Sonic, Base and Arbitrum. It separately reported approximately $1.29M borrowed and $3.07M staking-tagged balances. The current adapter discovers every V2 and V3 index, unwraps index assets and LP staking tokens, includes assets held by V3 lending pairs, and calculates borrow balances from those pairs. Its stated methodology is to aggregate TVL in all Peapods indexes created. Therefore the headline is not an executable pool, vault or exit-depth measure and the stale four-chain summary is corrected.

Control, loss and exit applicability

Pod creators choose single-asset or index constituents, a paired asset, oracle, LVF or self-lending mode, wrap and unwrap fees, cooldown and AMM fees. LP participants receive spTKN positions and bear paired-inventory execution; LVF positions add utilization, interest and liquidation; isolated lenders bear oracle, collateral and socialized bad-debt risk with no recovery mechanism; Metavault users delegate allocation among whitelisted Pods. Exit therefore depends on the exact position: unwrap fees or cooldown, LP inventory and depth, lending utilization, liquidation solvency, or allocator withdrawal liquidity. Aggregate protocol TVL does not establish any one of those paths.

Security and incident evidence boundary

The reviewed primary materials disclose modular risk but do not supply one current incident ledger, audit perimeter or authority map that covers every permissionless Pod and every integrated lending, LP and Metavault path represented by the adapter. A protocol-level absence of a cited incident cannot be treated as evidence that each creator-selected oracle, constituent, pool and leveraged position has a clean record. Product-level review must identify the exact deployed contracts and versions, map audits to those contracts, reconcile any loss or bad-debt event, and distinguish immutable infrastructure from creator, governance and allocator powers before risk can be underwritten.

Decision and comparison

The coverage slug cannot be approved as an undifferentiated exposure. A fixed single-asset Pod should be compared with holding its underlying directly; a pTKN paired farm with a direct AMM LP; an isolated lender with a named reserve in an approved lending venue; an LVF position with an explicit leveraged strategy; and a Metavault with direct mandate-approved positions whose holdings and caps remain enforceable. Reopen only for a named contract-level product after its assets, chain, oracle, privileged roles, audits and incidents, debt or LP inventory, proposed-size exit and named comparison are mapped. A larger aggregate headline alone cannot cure the product-scope defect.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Peapods — protocol overview · primary · accessed 2026-08-15
  Supports: Pods, pTKN, Volatility Farming, LVF, lending, Metavaults, current product suite
• Peapods — core product distinctions · primary · accessed 2026-08-15
  Supports: single and multi-asset Pods, LP yield, leveraged borrowing, self-lending, allocator scope
• Peapods — Pod deployment parameters · primary · accessed 2026-08-15
  Supports: creator parameters, oracle, fees, cooldown, paired asset, LVF
• Peapods — isolated-lending risk disclosure · primary · accessed 2026-08-15
  Supports: isolated lending, oracle risk, bad debt, socialized lender loss, Metavault distinction
• DefiLlama adapter — Peapods aggregation logic · secondary · accessed 2026-08-15
  Supports: six-chain configuration, all indexes, LP staking, lending assets, borrowed balances, methodology
• DefiLlama — Peapods Finance survey record · secondary · accessed 2026-08-15
  Supports: current TVL, borrowed, staking, current chains, Yield 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.