AprScope

SushiSwap · Ethereum

WBTC-ROBO

Current APY

0.00%

base 0.00% · reward 0.00%

TVL

$599.1K

APY +0.00% 7d

Risk signals

0.00% - multi asset IL risk

Overview

The SushiSwap WBTC-ROBO pool on Ethereum is a liquidity position for the WBTC and ROBO token pair, generating yield through trading fees collected by the protocol. Total APY stands at 0%, with no reward component. The 7-day trend shows a decline of -10.93% and the 30-day trend indicates a drop of -11.11%, placing the current rate below the 30-day mean of 7.9%. TVL is $526K, with no reported change over the past week; primary exposure includes impermanent loss risk due to multi-asset holdings. Depth in liquidity pools like this one affects fee generation and slippage for traders.

Composed 2026-05-20 from the structured data above. See methodology for the full pipeline.

APY history
TVL history

Risk profile

  • Smart contract risk

    Funds are deposited into a smart contract. A bug or exploit in the contract could lead to total loss. Audits reduce, but do not eliminate, this risk. Check the protocol page for audit history.

  • Impermanent loss

    This pool holds multiple assets, so price divergence between them can reduce your USD value below what holding the assets separately would yield.

  • Yield variability

    Current APY is 0.00%; 30-day mean is 0.13%. Yields can change as TVL and incentive emissions change.

These notes are derived from the pool's structured data, not editorial advice. See our methodology.

Similar pools

FAQ

› What is the current APY for SushiSwap WBTC-ROBO on Ethereum?

The current total APY is 0.00%. Base yield: 0.00%. Reward yield: 0.00%.

› What is the TVL of this pool?

Total value locked is $599.1K as of the last data refresh.

› Is there impermanent loss risk?

Yes. This pool holds multiple assets and is exposed to impermanent loss.

› How often is this APY updated?

We refresh APY and TVL hourly from DefiLlama. Daily snapshots are stored to power the historical chart on this page.

Last updated 2026-10-04. See methodology for how we collect and refresh this data.