Protocols
Fluence FLT-DROP and FLT claim flow, decoded
rotki decodes the Fluence developer rewards flow on Ethereum: claiming FLT-DROP from the distributor, and the second step where FLT-DROP is burned to mint real FLT.
Supported features
- FLT-DROP claims from the Fluence dev rewards distributor are tagged against the Fluence counterparty with the claimed amount in the notes.
- FLT-DROP burn / FLT mint: when you convert FLT-DROP into FLT, the burn of FLT-DROP and the matching FLT receive (tagged as an airdrop subtype) are linked into a single event pair.
Limitations
- Fluence decoding is currently scoped to the FLT-DROP claim and the FLT-DROP-to-FLT conversion only. Fluence staking, peer/provider rewards, and other on-chain Fluence activity are not decoded as Fluence-counterparty events.
Setup
- 1In rotki, add the Ethereum address that holds FLT-DROP or claims FLT.
- 2In rotki, open History and let the initial sync run. The FLT-DROP claim and the FLT-DROP-to-FLT conversion are decoded automatically.
Frequently asked questions
Is Fluence staking decoded?
No. Only the FLT-DROP claim and the FLT-DROP-to-FLT conversion are tagged against the Fluence counterparty.
Does rotki read Fluence 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.