Protocols
FPIS airdrop claim, decoded
rotki tags the FPIS (Frax Price Index Share) airdrop claim against the Frax counterparty on Ethereum so the claim shows up as a Frax-attributed receive in your history.
Supported features
- FPIS airdrop claim is decoded as an airdrop receive event tagged against the Frax counterparty.
Limitations
- Frax-specific decoding is currently limited to the FPIS airdrop claim. sFRAX, frxETH and sfrxETH liquid staking, veFXS locking, and Frax gauge rewards are not decoded as Frax-counterparty events; the underlying token movements still appear in your history.
- FRAX and other Frax-issued tokens are tracked as ordinary ERC-20s on whatever chain they appear, but rotki has no Frax-aware decoder for their stablecoin minting/redemption flows.
Setup
- 1In rotki, add the Ethereum address that claimed FPIS.
- 2In rotki, open History and let the initial sync run. The FPIS airdrop claim is decoded automatically; other Frax-related token movements appear as ordinary ERC-20 events.
Frequently asked questions
Are sFRAX, frxETH, sfrxETH, and veFXS decoded as Frax events?
Not currently. Their token movements (deposits, withdrawals, transfers) show up as ordinary ERC-20 events without a Frax counterparty tag.
Does rotki read Frax 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.