Hop Protocol · Polygon
ETH
Current APY
0.02%
base 0.02% · reward 0.00%
TVL
$170.3K
APY +0.00% 7d
Risk signals
Overview
The Hop Protocol ETH on Polygon is a single-asset liquidity position where users hold ETH tokens that the protocol uses for cross-chain bridging activities between Ethereum and Polygon networks. The protocol generates yield by facilitating transfers of ETH across chains, earning fees from bridge transactions.
Total APY stands at 2.10%, with no additional reward component. Both the 7-day and 30-day trend percentages are unavailable, leaving the current rate in line with the 30-day mean of 2.10%.
TVL is $203K, with no reported 7-day change; primary exposure lies in smart-contract risk due to the cross-chain bridge operations involved. The liquidity depth supports efficient bridging transactions for users moving ETH between chains.
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.
-
Yield variability
Current APY is 0.02%; 30-day mean is 0.02%. Yields can change as TVL and incentive emissions change.
-
DefiLlama yield prediction
DefiLlama's model classifies this pool's yield as "Stable/Up" with 88% confidence based on historical patterns.
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 Hop Protocol ETH on Polygon?
The current total APY is 0.02%. Base yield: 0.02%. Reward yield: 0.00%.
› What is the TVL of this pool?
Total value locked is $170.3K as of the last data refresh.
› Is there impermanent loss risk?
No. This pool is single-asset and has no impermanent loss exposure.
› 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.