The problem PolyLiquid solves

What problem does PolyLiquid solve?

Liquid staking is powerful, but today it’s messy, risky, and labour-intensive:

1. Fragmented tokens & diverging prices – Leading LSTs (stETH, rETH, sAVAX) often trade at different premia or discounts, forcing users to juggle multiple assets and dashboards.
2. Dangerous, complex cross-chain hops – Traditional bridges remain the #1 attack vector in Web3, and bridging requires a tedious wrap → bridge → unwrap flow.
3. Manual yield chasing – Staking APRs shift constantly; harvesting and re-compounding by hand wastes gas and leaves yield on the table.
4. Opaque reserve backing – Users can’t easily verify that liquid-staking derivatives are fully collateralised.

What users can do with PolyLiquid

• Deposit once, earn everywhere – Hold one PLY token and let the protocol hunt the best staking yields across Ethereum, Avalanche, Base and more.
• Forget manual upkeep – Compounding, migrations, and hedges all run automatically.
• Travel safely – Move PLY cross-chain without touching risky third-party bridges.
• Verify backing on-chain – Anyone can check that every vault share is 100 % collateralised.
• Join the fun – Predict weekly APR outcomes or enter the no-loss lottery without risking principal.

PolyLiquid turns fragmented, hands-on liquid staking into a single, portable, self-optimising asset—making DeFi yield safer, simpler, and more engaging.

Challenges I ran into

Challenges & quick fixes

• CCIP decimals bug
  Issue: PLY (18 dec) mis-scaled when minted on Fuji (8 dec test token).
  Fix: Added a shim router that normalises decimals before mint.

• Functions timeout
  Issue: Polymarket API sometimes exceeded 20 s limit.
  Fix: Cached last good result and used exponential back-off.

• Gas spikes on rebalance
  Issue: Harvest + swap + CCIP in one tx hit block gas cap.
  Fix: Split into two upkeeps and packed calldata, saving ~40 % gas.

• UI chain desync
  Issue: Wallet network change mid-tx showed stale balances.
  Fix: Network guard blocks actions until chain IDs match and prompts user.