Protocols
GNT to GLM token migration, decoded
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.
Supported features
- GNT → GLM migrations are decoded into a paired event: the synthesised GNT spend (event type MIGRATE/SPEND) and the matching GLM receive (event type MIGRATE/RECEIVE), both tagged against the Golem counterparty.
- 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.
Limitations
- Golem-specific decoding is limited to the GNT → GLM migration. Other GLM activity (transfers, payments to providers/requestors on Golem Network, etc.) appears as ordinary ERC-20 events.
Setup
- 1In rotki, add the Ethereum address that performed the migration (or holds GLM).
- 2In 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.
Frequently asked questions
Are GNT → GLM migrations decoded?
Yes. Both legs (GNT spend and GLM receive) are linked and tagged as a migrate pair against the Golem counterparty.
Does rotki read Golem activity from its own servers?
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.