Lately I've been looking into re-staking / shared security again, basically it's about repeatedly using the same collateral to "endorse," stacking yields very smoothly, but the risks also stack up—don't just stack illusions. On the contract side, I usually check three things first: whether permissions can arbitrarily change parameters, whether callback chains can be clogged with strange external calls, and whether upgrades are just a master key that can be swapped at will. Many people only focus on APY, forgetting that they're actually acting as guarantors for a series of contracts. Recently, new L1/L2 projects are offering incentives to attract TVL, and old users complain about "mining, dumping," which I can empathize with: liquidity comes quickly and leaves quickly, and the ones left in the pool are actually at the tail risk. Anyway, I now prefer to earn a little less and first understand the exit paths, penalty conditions, and slash trigger logic before taking action.

View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments
  • Pin