[{"data":1,"prerenderedAt":93},["ShallowReactive",2],{"\u002Fintegrations\u002Fgolem":3},{"id":4,"title":5,"body":6,"ctaPlan":70,"description":15,"extension":71,"faq":72,"features":75,"image":76,"intro":15,"isExchangeWithKey":77,"keywords":78,"label":5,"limitations":79,"meta":80,"metaDescription":81,"navigation":82,"path":83,"screenshots":84,"seo":85,"setup":86,"sitemap":87,"slug":88,"stem":89,"tagline":90,"type":91,"__hash__":92},"integrations\u002Fintegrations\u002Fgolem.md","Golem",{"type":7,"value":8,"toc":66},"minimark",[9,12,16,20,30,33,38,41,50,53,57,60,63],[10,11,5],"h1",{},[13,14,15],"p",{},"rotki decodes the legacy Golem GNT → GLM migration on Ethereum. The migration contract doesn't emit a GNT transfer event, so rotki synthesises the GNT spend, links it to the GLM receive, and tags both as a single migrate pair against the Golem counterparty.",[17,18,19],"h2",{},"Features",[21,22,23,27],"ul",{},[24,25,26],"li",{},"GNT → GLM migrations are decoded into a paired event: the synthesised GNT spend (event type MIGRATE\u002FSPEND) and the matching GLM receive (event type MIGRATE\u002FRECEIVE), both tagged against the Golem counterparty.",[24,28,29],{},"Because the migration contract emits no GNT transfer event, the GNT spend wouldn't otherwise show up in your history; rotki adds it so the swap is visible and not just a one-sided GLM receive.",[17,31,32],{},"Limitations",[21,34,35],{},[24,36,37],{},"Golem-specific decoding is limited to the GNT → GLM migration. Other GLM activity (transfers, payments to providers\u002Frequestors on Golem Network, etc.) appears as ordinary ERC-20 events.",[17,39,40],{},"Setup",[42,43,44,47],"ol",{},[24,45,46],{},"In rotki, add the Ethereum address that performed the migration (or holds GLM).",[24,48,49],{},"In rotki, open History and let the initial sync run. The GNT → GLM migration pair is decoded automatically; ordinary GLM transfers appear as standard ERC-20 events.",[17,51,52],{},"FAQ",[54,55,56],"h3",{},"Are GNT → GLM migrations decoded?",[13,58,59],{},"Yes. Both legs (GNT spend and GLM receive) are linked and tagged as a migrate pair against the Golem counterparty.",[54,61,62],{},"Does rotki read Golem activity from its own servers?",[13,64,65],{},"No. rotki is a local application that talks directly to the Ethereum RPC endpoint you configure - the public default, a third-party provider, or your own node. The query goes from your computer to that endpoint without passing through any rotki-operated server.",{"title":67,"searchDepth":68,"depth":68,"links":69},"",2,[],"free","md",[73,74],{"q":56,"a":59},{"q":62,"a":65},[26,29],"\u002Fimg\u002Fintegrations\u002Fgolem.svg",false,"golem portfolio tracker, glm token, gnt to glm migration, golem network",[37],{},"rotki decodes the legacy Golem GNT → GLM migration on Ethereum.",true,"\u002Fintegrations\u002Fgolem",[],{"description":67},[46,49],{"loc":83},"golem","integrations\u002Fgolem","GNT to GLM token migration, decoded","protocol","bMWk99pB0eq9ObpAiWqD_G4WVVmu7P6jDcmt_Yi9-EQ",1781774867392]