[{"data":1,"prerenderedAt":107},["ShallowReactive",2],{"\u002Fintegrations\u002Fhop-protocol":3},{"id":4,"title":5,"body":6,"ctaPlan":83,"description":15,"extension":84,"faq":85,"features":89,"image":90,"intro":15,"isExchangeWithKey":91,"keywords":92,"label":5,"limitations":93,"meta":94,"metaDescription":95,"navigation":96,"path":97,"screenshots":98,"seo":99,"setup":100,"sitemap":101,"slug":102,"stem":103,"tagline":104,"type":105,"__hash__":106},"integrations\u002Fintegrations\u002Fhop-protocol.md","Hop Protocol",{"type":7,"value":8,"toc":79},"minimark",[9,12,16,20,45,48,57,60,64,67,70,73,76],[10,11,5],"h1",{},[13,14,15],"p",{},"rotki decodes the full Hop Protocol lifecycle across Ethereum and the L2s Hop runs on: bridge sends and receives (with bridge fees split out), AMM swaps via Hop pools, liquidity adds\u002Fremoves, staking and unstaking of LP positions, ongoing HOP reward claims, and Merkle HOP airdrop claims.",[17,18,19],"h2",{},"Features",[21,22,23,27,30,33,36,39,42],"ul",{},[24,25,26],"li",{},"Bridge sends are tagged as bridge deposits, with the bonder\u002Frelayer fee split out as a separate fee-subtype event so the bridged amount stays clean.",[24,28,29],{},"Bridge receives on the destination chain (including L1→L2 transfers and bonded withdrawals) are tagged as bridge withdrawals against the Hop counterparty.",[24,31,32],{},"Hop AMM swaps between the canonical asset and its hToken are decoded as trade events.",[24,34,35],{},"Add-liquidity and remove-liquidity calls against Hop pools are decoded, with the LP token cached so the pool position is recognised.",[24,37,38],{},"Staking, unstaking, and ongoing reward claims from Hop reward contracts are decoded; reward-paid receives are tagged as reward-subtype events.",[24,40,41],{},"Merkle HOP airdrop claims are decoded as reward-subtype receives against the Hop counterparty.",[24,43,44],{},"Decoded on every chain Hop currently runs on: Ethereum, Arbitrum One, Optimism, Polygon PoS, Base, and Gnosis Chain.",[17,46,47],{},"Setup",[49,50,51,54],"ol",{},[24,52,53],{},"In rotki, add the addresses you use with Hop on the relevant chains so both sides of each bridge transfer are captured.",[24,55,56],{},"In rotki, open History and let the initial sync run. Bridges, AMM swaps, LP adds\u002Fremoves, staking, reward claims, and HOP airdrop claims are decoded automatically.",[17,58,59],{},"FAQ",[61,62,63],"h3",{},"Will a Hop bridge transfer create a fake gain or loss?",[13,65,66],{},"No. Both legs are tagged as bridge events (with the relayer fee split out), which rotki treats as non-taxable transfers rather than a spend\u002Freceive pair.",[61,68,69],{},"Are Hop LP and reward claims captured?",[13,71,72],{},"Yes. Liquidity adds\u002Fremoves, stake\u002Funstake events, ongoing reward claims, and the Merkle HOP airdrop are all decoded against the Hop counterparty.",[61,74,75],{},"Does rotki read Hop activity from its own servers?",[13,77,78],{},"No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server.",{"title":80,"searchDepth":81,"depth":81,"links":82},"",2,[],"free","md",[86,87,88],{"q":63,"a":66},{"q":69,"a":72},{"q":75,"a":78},[26,29,32,35,38,41,44],"\u002Fimg\u002Fintegrations\u002Fhop_protocol.png",false,"hop protocol bridge tracker, hop l2 bridge, hop lp tracker, hop staking, hop airdrop",[],{},"rotki decodes the full Hop Protocol lifecycle across Ethereum and the L2s Hop runs on: bridge sends and receives (with bridge fees split out), AMM swaps via",true,"\u002Fintegrations\u002Fhop-protocol",[],{"description":80},[53,56],{"loc":97},"hop-protocol","integrations\u002Fhop-protocol","Hop bridge, AMM, liquidity, staking, and HOP rewards, decoded","protocol","8x3NCxr2jyvvdIq4leuvGnGt0A7_X2OQzdfi339ViTw",1781774867406]