SushiSwap · Ethereum
USDC-QUARTZ
Current APY
0.00%
base 0.00% · reward 0.00%
TVL
$486.0K
APY -0.01% 7d
Risk signals
Overview
The SushiSwap USDC-QUARTZ pool on Ethereum is an LP token for a liquidity provision pair, generating yield through trading fees earned by participants who supply both USDC and QUARTZ tokens to the decentralized exchange. Total APY stands at 0.81%, with no additional reward component. The 7-day trend shows an increase of 0.81% while the 30-day trend is up 0.66%, placing the current rate below the 30-day mean of 1.62%. TVL in this pool is $485K, with no reported change over the past week; primary exposure includes impermanent loss risk due to the multi-asset composition. This liquidity depth supports trading activity on SushiSwap, contributing to stable fee generation for LP token holders.
Composed 2026-05-20 from the structured data above. See methodology for the full pipeline.
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.00%. 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 USDC-QUARTZ 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 $486.0K 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-07-06. See methodology for how we collect and refresh this data.