[{"data":1,"prerenderedAt":109},["ShallowReactive",2],{"\u002Fintegrations\u002Fli-fi":3},{"id":4,"title":5,"body":6,"ctaPlan":85,"description":15,"extension":86,"faq":87,"features":91,"image":92,"intro":15,"isExchangeWithKey":93,"keywords":94,"label":5,"limitations":95,"meta":96,"metaDescription":97,"navigation":98,"path":99,"screenshots":100,"seo":101,"setup":102,"sitemap":103,"slug":104,"stem":105,"tagline":106,"type":107,"__hash__":108},"integrations\u002Fintegrations\u002Fli-fi.md","LI.FI",{"type":7,"value":8,"toc":81},"minimark",[9,12,16,20,36,39,47,50,59,62,66,69,72,75,78],[10,11,5],"h1",{},[13,14,15],"p",{},"rotki decodes activity routed through the LI.FI diamond - same-chain swaps and cross-chain bridge transfers - into readable events tagged with LI.FI, and matches the two legs of a bridge transfer when you track both chains.",[17,18,19],"h2",{},"Features",[21,22,23,27,30,33],"ul",{},[24,25,26],"li",{},"Swaps executed through the LI.FI diamond decoded as paired spend\u002Freceive trades rather than loose transfers.",[24,28,29],{},"Cross-chain transfers started through LI.FI decoded as bridge events, including routes that hand off to underlying bridges such as Relay, Squid, and Glacis.",[24,31,32],{},"Source and destination legs matched into a single bridge transfer when both chains are tracked in rotki.",[24,34,35],{},"The decoder runs on every EVM chain rotki supports, so LI.FI routes are recognised wherever they touch a tracked address.",[17,37,38],{},"Limitations",[21,40,41,44],{},[24,42,43],{},"Only the legs that touch an address you track can be decoded. If the destination chain is not added in rotki, the transfer shows as a one-sided bridge event.",[24,45,46],{},"LI.FI is an aggregator: the underlying liquidity source of a route is not always identifiable on-chain, so some routes are tagged with LI.FI rather than the venue that ultimately filled them.",[17,48,49],{},"Setup",[51,52,53,56],"ol",{},[24,54,55],{},"In rotki, open Blockchain Balances and add the addresses you use with LI.FI on both the source and destination chains.",[24,57,58],{},"Open History and let the transaction sync run. LI.FI swaps and bridge transfers are decoded automatically.",[17,60,61],{},"FAQ",[63,64,65],"h3",{},"Which chains does the LI.FI integration cover?",[13,67,68],{},"The LI.FI decoder is part of rotki's shared EVM decoding layer, so it runs on every EVM chain rotki supports rather than a fixed subset.",[63,70,71],{},"Why is my cross-chain transfer only showing one side?",[13,73,74],{},"rotki can only decode what happened to an address it tracks. Add the destination address under Blockchain Balances and re-run the sync, and the two legs are matched into one bridge transfer.",[63,76,77],{},"Does using LI.FI through rotki expose my addresses?",[13,79,80],{},"No. rotki reads the transactions from the chain through the RPC endpoint you configure. It does not call LI.FI's API on your behalf and nothing passes through a rotki-operated server.",{"title":82,"searchDepth":83,"depth":83,"links":84},"",2,[],"free","md",[88,89,90],{"q":65,"a":68},{"q":71,"a":74},{"q":77,"a":80},[26,29,32,35],"\u002Fimg\u002Fintegrations\u002Flifi.svg",false,"LI.FI portfolio tracker, LiFi bridge tracker, LI.FI accounting, LI.FI tax, cross-chain swap tracker",[43,46],{},"rotki decodes LI.FI swaps and cross-chain bridge transfers into readable events and matches both legs of a transfer when both chains are tracked.",true,"\u002Fintegrations\u002Fli-fi",[],{"description":82},[55,58],{"loc":99},"li-fi","integrations\u002Fli-fi","LI.FI swaps and cross-chain transfers, decoded","protocol","gpSwpaetnoM5Kzkw5-LFsp_U52fQ2SaV4-VPuFdtW6g",1787584947149]