# 0x rotki decodes 0x protocol swaps (including those routed through Matcha) across Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain, and Monad. Processing is local; your addresses and trades stay on your computer. ## Features - 0x protocol swaps decoded as clean trade events. - Matcha swaps decoded as standard 0x swap events (Matcha is built on 0x). - Multi-chain - Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Chain, and Monad. ## Setup 1. In rotki, add your address under the chain where you've used 0x or Matcha. 2. Open History → wait for the initial sync to complete. 0x swap events appear once your transactions are decoded. ## FAQ ### Do my 0x trades leave my machine? No. rotki reads activity from the RPC nodes you configure directly from your computer. # 1inch rotki decodes 1inch aggregator swaps (v4, v5, and v6, including Fusion-routed) across Ethereum, Arbitrum, Optimism, Polygon, and Gnosis, including swaps that settle through a Balancer pool. ## Features - 1inch v4, v5, and v6 aggregator swaps decoded as clean swap events. - Pool-routed swaps - 1inch trades settling via Balancer V2/V3 (including v6 Fusion routing) are folded into a single swap event instead of a separate Balancer trade. - Multi-chain - Ethereum, Arbitrum, Optimism, Polygon, and Gnosis. ## Setup 1. In rotki, add your address under the chain where you've used 1inch. 2. Activity is decoded automatically. 3. Open History → wait for the initial sync to complete. Protocol events appear once your transactions are decoded. ## FAQ ### Do my 1inch trades leave my machine? No. rotki reads activity from the RPC nodes you configure directly from your computer. # Aave rotki decodes your Aave v1, v2, and v3 activity - supplies, borrows, repayments, liquidations, GHO, and AAVE rewards - across Ethereum, Arbitrum, Optimism, Polygon, Base, Gnosis, Scroll, and BNB Chain. ## Features - Supplies and withdrawals - including v3 ETH gateway and native+wrapped-token same-transaction flows. - Borrows and repayments - interest accrual events tied to your position. - AAVE rewards - claim and immediate-restake patterns recognised. - Liquidations - both the debt repayment and the collateral seizure are tagged as liquidation events, so realised PnL flows into your tax report. - GHO - Aave's stablecoin decoded with its own dedicated handling. - Multi-chain - Aave v3 across Ethereum, Arbitrum, Optimism, Polygon, Base, Gnosis, Scroll, and BNB Chain. - v2 → v3 migrations - transactions routed through Aave's migration helper on Ethereum and Polygon are decoded as migrations rather than separate v2 exits and v3 entries. ## Setup 1. In rotki, add your address under the chain where your Aave position lives (Blockchain & Accounts → Ethereum / Arbitrum / etc.). 2. rotki will detect your Aave positions automatically; no Aave-specific configuration needed. 3. Open History → wait for the initial sync to complete. Protocol events appear once your transactions are decoded. ## FAQ ### Do my Aave positions or addresses leave my machine? No. rotki reads your activity from the RPC nodes you configure directly from your computer. ### Does rotki support both Aave v2 and v3? Yes. Both versions are decoded, including the v2 → v3 migration flows. ### Are Aave liquidations handled for tax purposes? Yes. The debt repayment and collateral seizure are decoded as paired liquidation events, so realised PnL flows into your tax report. # Account Delegation (EIP-7702) rotki decodes EIP-7702 account-delegation events - when an EOA delegates its code to a smart-contract implementation - so your wallet's set-code state and its consequences are visible in your event history. Processing is local; your addresses and delegations stay on your computer. ## Features - EIP-7702 set-code (delegation) events decoded as protocol events. - Delegation revocations recognised. ## Setup 1. In rotki, add your address under any EVM chain where you've authorised an EIP-7702 delegation (Ethereum and any other chain that supports type-4 transactions). 2. Open History → wait for the initial sync to complete. Delegation events appear once your transactions are decoded. ## FAQ ### What is EIP-7702? EIP-7702 lets a regular EOA (externally-owned account) authorise its address to behave like a smart contract for a single transaction. rotki decodes those authorisations so the resulting behaviour is interpretable. ### Do my delegations leave my machine? No. rotki reads activity from the EVM RPCs you configure directly from your computer. # Aerodrome Finance rotki decodes Aerodrome swaps, LP positions, gauge rewards, and veAERO voting on Base, including fee claims via Aerodrome's fee addresses. ## Features - Swaps and LP positions on Base. - Gauge deposits, withdrawals, and reward claims decoded as discrete events. - Gauge fee and bribe claims tracked via Aerodrome's fee and bribe distributor addresses. - veAERO - vote-escrow lock creation, increases, voting, and unlocks decoded as their own events. ## Setup 1. In rotki, add your Base address. Aerodrome activity is decoded automatically. 2. Optional: refresh Aerodrome's pool/gauge data under Settings → Manage Data → Refresh protocol data. 3. Open History → wait for the initial sync to complete. Protocol events appear once your transactions are decoded. ## FAQ ### Do my Aerodrome positions or addresses leave my machine? No. rotki reads activity from the Base RPC you configure directly from your computer. ### Are Aerodrome fee claims captured? Yes. rotki tracks Aerodrome's gauge fee and bribe distributor addresses so claim events are decoded as separate income events. # Arbitrum One Add your Arbitrum One addresses to rotki to track ARB and token balances, decoded transactions, bridge events, and DeFi activity. ## Features - Address balances - ARB, ETH, and ERC-20 tokens on Arbitrum One. - Transaction decoding - swaps, bridges, deposits, withdrawals, and DeFi events become readable. - DeFi protocols on Arbitrum - GMX, Aave, Curve, Uniswap, Balancer, Compound, Yearn, Gearbox, and more. - Bridge events - Arbitrum bridge deposits and withdrawals are linked with their L1 counterparts. - Monerium activity on Arbitrum is decoded as Monerium events rather than bare ERC-20 transfers. ## Setup 1. In rotki, open Blockchain & Accounts → Arbitrum One → Add address. 2. Paste your address (often the same as your Ethereum address). 3. Optional: in Settings → RPC, set your preferred Arbitrum RPC endpoint. ## FAQ ### Do my Arbitrum addresses leave my machine? No. rotki queries the Arbitrum RPC you configure directly from your computer. ### Can I track the same address on Ethereum and Arbitrum? Yes. Add it on both chains; rotki tracks balances and history separately and shows a unified portfolio view. ### Are Arbitrum airdrops decoded? Yes. ARB and other airdrop claims are decoded into income events for tax reporting. # Aura Finance rotki decodes Aura Finance deposits, gauge withdrawals, AURA/BAL reward claims, vlAURA locking, and auraBAL vault activity across Ethereum, Arbitrum, Optimism, Polygon, Base, and Gnosis. ## Features - Booster deposits and gauge withdrawals decoded as paired position events without double-counting the underlying BPT. - AURA and BAL reward claims decoded as income events, including extra-reward and L2 booster-lite claim paths. - vlAURA - locking AURA in auraLocker decoded as its own lock event (Ethereum and Base). - auraBAL - vault deposits and withdrawals decoded as auraBAL events. - Multi-chain - Ethereum, Arbitrum, Optimism, Polygon, Base, and Gnosis. ## Setup 1. In rotki, add your address on any chain where you've used Aura (Ethereum, Arbitrum, Optimism, Polygon, Base, or Gnosis). Aura positions are detected automatically. 2. Open History → wait for the initial sync to complete. Protocol events appear once your transactions are decoded. ## FAQ ### Do my Aura positions or addresses leave my machine? No. rotki reads activity from the EVM RPCs you configure directly from your computer. ### Are all Aura reward claims captured? Yes. AURA, BAL, extra rewards, and L2 booster-lite claim paths are all decoded as income events. # Avalanche Add your Avalanche C-Chain addresses to rotki to track your AVAX balances locally. ## Features - AVAX native balance tracking on Avalanche C-Chain. - Multi-account - track multiple Avalanche addresses in one place. ## Limitations - Avalanche support is balance-only - token balances, transaction decoding, and DeFi protocol modules are not currently available on this chain. - X-Chain (UTXO) and P-Chain (staking) are not tracked. ## Setup 1. In rotki, open Blockchain & Accounts → Avalanche → Add address. 2. Paste your C-Chain address. 3. Optional: configure your preferred Avalanche RPC endpoint in Settings → RPC. ## FAQ ### Do my Avalanche addresses leave my machine? No. rotki queries the Avalanche RPC you configure directly from your computer. ### Does rotki decode my Avalanche transactions or DeFi activity? Not currently. The Avalanche integration tracks AVAX balances only; transaction decoding and DeFi protocol modules are not yet implemented on this chain. ### Does rotki track X-Chain or P-Chain? No. Only the EVM-compatible C-Chain is supported. X-Chain (UTXO) and P-Chain (staking) are not tracked. # Badger DAO rotki decodes the BADGER airdrop (BadgerHunt) claim on Ethereum as an income event for tax reporting. ## Features - BADGER airdrop (BadgerHunt) claim on Ethereum decoded as an income event. ## Limitations - Sett vaults, DIGG, and Badger staking/rewards are not currently decoded - only the BADGER airdrop claim is recognised. ## Setup 1. In rotki, add your Ethereum address. 2. Open History → wait for the initial sync to complete. The BADGER claim appears once your transactions are decoded. ## FAQ ### Do my addresses leave my machine? No. rotki reads activity from the Ethereum RPC you configure directly from your computer. ### Does rotki decode Badger sett vaults or DIGG rewards? Not currently. Only the BADGER airdrop (BadgerHunt) claim is decoded; sett vault deposits/withdrawals and DIGG rewards are not yet supported. # Balancer rotki decodes Balancer v1, v2, and v3 swaps, LP positions, and v3 gauge rewards across Ethereum, Arbitrum, Optimism, Polygon, Base, and Gnosis. ## Features - Balancer v1 - pool swaps on Ethereum decoded as trades. - Balancer v2 - multi-hop swaps and swaps that involve the native chain token decoded as single trade events. - Balancer v3 - swaps, LP deposits/withdrawals, and LP balances tracked. - Balancer v3 gauges - reward claims decoded as income events. - Multi-chain - Ethereum, Arbitrum, Optimism, Polygon, Base, and Gnosis. ## Setup 1. In rotki, add your address under the chain where you use Balancer. 2. Balancer activity is decoded automatically; LP balances appear in your portfolio. 3. Open History → wait for the initial sync to complete. Protocol events appear once your transactions are decoded. ## FAQ ### Do my Balancer positions or addresses leave my machine? No. rotki reads activity from the RPC nodes you configure directly from your computer. ### Which Balancer versions does rotki support? v1 (Ethereum), v2, and v3 are all decoded. v3 includes LP balance tracking and gauge reward claims. ### Are Balancer gauge rewards captured? Yes. v3 gauge reward claims are decoded as income events. # Base Add your Base addresses to rotki to track ETH and ERC-20 balances, decoded transactions, bridge events, and DeFi activity on Coinbase's L2. ## Features - Address balances - ETH and ERC-20 tokens on Base. - Transaction decoding - swaps, bridges, deposits, and DeFi interactions decoded. - DeFi protocols on Base - Aerodrome, Aave, Compound, Uniswap, Balancer, Morpho, Yearn, Spark, and more. - Basenames - Base's ENS-style name service is resolved alongside ENS. - Bridge events - Base ↔ Ethereum bridges linked across chains. ## Setup 1. In rotki, open Blockchain & Accounts → Base → Add address. 2. Paste your address. 3. Optional: configure your preferred Base RPC endpoint in Settings → RPC. ## FAQ ### Do my Base addresses leave my machine? No. rotki queries the Base RPC you configure directly from your computer. ### Are Basenames resolved? Yes. rotki resolves Basenames alongside ENS so your addresses display with their human-readable names. ### Can I track the same address on Ethereum and Base? Yes. Add it on both chains for a unified view. # Basenames rotki decodes Basenames registrations and name transfers on Base, and resolves Basenames alongside ENS so your addresses display with human-readable names. ## Features - Basenames registration events decoded. - Basenames transfers decoded as name-transfer events. - Basenames resolution - addresses display their Basenames alongside ENS. ## Setup 1. In rotki, add your Base address. Basenames activity and resolution are automatic. 2. Open History → wait for the initial sync to complete. Protocol events appear once your transactions are decoded. ## FAQ ### How does rotki resolve Basenames? rotki is a local application that resolves Basenames by talking directly to the Base RPC endpoint you configure - the public default, a third-party provider, or your own node. The lookup goes from your computer to that endpoint without passing through any rotki-operated server or centralised name service. ### Are Basenames renewals tracked? Not currently. rotki decodes Basenames registrations and name transfers today; renewal events are not yet recognised on Base. # Beefy Finance rotki decodes Beefy Finance vault deposits and withdrawals, reward-pool staking, harvest rewards, and legacy boost exits across Ethereum, Arbitrum, Optimism, Polygon, Base, Gnosis, Scroll, and BNB Chain. ## Features - Vault deposits and withdrawals decoded as deposit/withdraw events with the underlying token resolved. - Reward-pool staking - depositing the moo/cow vault token for the rmoo/rcow reward-pool token (and the reverse) decoded as staking/unstaking events. - Beefy staking rewards decoded as separate reward income events. - Legacy boost exits - unstake-and-claim from old boost contracts decoded as a single unstake event. - Vault and reward-pool tokens are auto-registered on first sight so they appear in your portfolio with correct pricing. - Multi-chain - Ethereum, Arbitrum, Optimism, Polygon, Base, Gnosis, Scroll, and BNB Chain. ## Setup 1. In rotki, add your address under the chain where you use Beefy. 2. Vault positions are detected automatically. 3. Optional: refresh Beefy's cached vault data under Settings → Manage Data → Refresh protocol data. 4. Open History → wait for the initial sync to complete. Protocol events appear once your transactions are decoded. ## FAQ ### How does rotki query my Beefy activity? rotki is a local application that talks directly to the EVM RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server or Beefy's API. ### Are Beefy boost rewards captured? Yes. Reward-pool staking rewards and legacy boost exits are both decoded as income/unstake events. # Binance Connect your Binance account to rotki and import spot trades, deposits and withdrawals, Convert swaps, margin and futures positions, and Simple Earn interest. Use a read-only API key or import Binance's CSV exports. ## Features - Spot trades - full trade history once you select your market pairs. - Deposits and withdrawals - reconciled against your balance history. - Binance Convert - quick swaps imported as trades. - Cross-collateral and margin futures - balances and positions for COIN-M (dapi) and USD-M (fapi). - Simple Earn - flexible and locked interest history. - CSV import - load Binance's exported trade and history CSVs for periods before your API key existed. ## Limitations - Binance does not return trades for delisted markets via API; CSV import is the workaround. - You must paste your market pairs into rotki - Binance's API requires the pair to query its trades. - Binance Convert history is limited by Binance to a 30-day window per request, so deep history takes longer to sync. ## Setup 1. In Binance, open Account → API Management and click "Create API". 2. Restrict permissions to "Enable Reading" only. Leave trading, withdrawals, and futures-trading permissions off. 3. Optionally enable IP whitelist for extra safety. 4. In rotki, open API Keys → Exchanges → Add Binance, paste the API key and secret. 5. Paste your active market pairs (e.g. BTCUSDT, ETHUSDT) so rotki knows which markets to query. ## FAQ ### Does rotki support Binance Futures? Yes. rotki queries USD-M and COIN-M margined futures balances. Make sure the API key has "Enable Reading" for futures. ### Why does rotki ask for market pairs? Binance's API only returns trades when you specify a pair. rotki asks you to paste your active pairs so it can query each one. You can paste multiple pairs at once. ### Can I track Binance.US and global Binance in the same rotki instance? Yes. Binance.US is a separate integration in rotki - add both with their own API keys. ### Where are my Binance API keys sent? rotki is a local application: your Binance API key is stored on your computer and used to sign each request, which goes directly from your machine to Binance's API. No rotki-operated server ever sees the key or the request. # BNB Smart Chain Add your BNB Smart Chain (BSC) addresses to rotki to track BNB and BEP-20 balances, decoded transactions, and DeFi activity. ## Features - Address balances - BNB and BEP-20 tokens on BNB Smart Chain. - Transaction decoding - swaps and DeFi events become readable. - DeFi protocols on BSC - Aave, Curve, Uniswap, SushiSwap, Morpho, Pendle, Beefy, CowSwap, Paraswap, WooFi, and more. - Multi-account - track multiple BSC addresses in one rotki instance. ## Setup 1. In rotki, open Blockchain & Accounts → BNB Smart Chain → Add address. 2. Paste your address (the same address you use on Ethereum works on BSC too). 3. Optional: configure your preferred BSC RPC endpoint in Settings → RPC. ## FAQ ### How does rotki query my BSC activity? rotki is a local application that talks directly to the BSC 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. ### Is this the same as Binance the exchange? No. BNB Smart Chain is a public blockchain. The Binance exchange is a separate centralised service, tracked through a different integration in rotki. # Binance.US Connect Binance.US to rotki to import spot trades, deposits, and withdrawals via the API, with CSV import to fill the gaps Binance.US doesn't expose. ## Features - Spot trades - full Binance.US trade history once you select your market pairs. - Deposits and withdrawals - reconciled against your balance history. - CSV import - load Binance.US exported trade and history CSVs, including Convert history. ## Limitations - Binance.US does not expose the Convert API that Binance.com offers - Convert trades must be imported via CSV. - Binance.US does not expose Simple Earn history via API. - You must paste your market pairs into rotki - the API requires the pair to query trades. ## Setup 1. In Binance.US, open Account → API Management and click "Create API". 2. Restrict permissions to "Enable Reading" only. Leave trading and withdrawal permissions off. 3. Optionally whitelist your IP. 4. In rotki, open API Keys → Exchanges → Add Binance.US and paste the API key and secret. 5. Paste your active market pairs (e.g. BTCUSD, ETHUSD). ## FAQ ### Can I track Binance and Binance.US in the same rotki instance? Yes. They are separate integrations - add both with their own API keys. ### Where are my Binance.US API keys sent? rotki is a local application: your Binance.US API key is stored on your computer and used to sign each request, which goes directly from your machine to Binance.US's API. No rotki-operated server ever sees the key or the request. ### Can rotki trade or withdraw on Binance.US? No. rotki only requests read scopes and never sends trade or withdrawal calls. # Bisq Bisq is a decentralised, peer-to-peer Bitcoin exchange that runs on your machine, a natural fit for rotki's local-first approach. Import your Bisq trade history via CSV; everything is processed on your computer. ## Features - CSV import for Bisq trade history exports. - Peer-to-peer trades imported as swap events with buy/sell sides and trade fees preserved. - Imported trades sit alongside the rest of your portfolio for unified PnL. ## Setup 1. In Bisq, export your trade history as CSV from your trade history view. 2. In rotki, open Import Data and select the Bisq trades file. ## FAQ ### Why is Bisq CSV-only? Bisq is a desktop application without a remote API, it runs entirely on your computer. CSV export is the canonical way to share data with other tools. ### Does my Bisq data leave my machine? No. Both Bisq and rotki are local applications, and the CSV import is read straight from disk. Nothing about your trades is sent to any rotki-operated server. # Bitcoin Track multiple Bitcoin addresses or whole wallets via xpub/ypub/zpub keys, including Taproot. ## Features - Single addresses: legacy (P2PKH), SegWit (P2WPKH/Bech32), and Taproot (Bech32m/P2TR). - xpub / ypub / zpub support: rotki auto-detects the type from the prefix and derives addresses. - Taproot (P2TR) xpubs: supported as a dedicated derivation type when adding a Bitcoin account. - Address-level filtering: slice your Bitcoin event history by individual address even when adding via xpub. - Multi-wallet: combine multiple xpubs and standalone addresses in one rotki instance. ## Setup 1. In rotki, open Blockchain & Accounts → Bitcoin → Add. 2. Paste either a single Bitcoin address or your extended public key (xpub, ypub, or zpub). For Taproot xpubs, select the P2TR derivation type since Taproot xpubs share the same \`xpub\` prefix as legacy P2PKH. 3. Optional: in Settings → RPC, open the Bitcoin Mempool tab to point rotki at a custom mempool.space / Esplora-compatible API (public block explorers are used by default). 4. rotki will derive addresses, fetch balances, and pull transaction history. ## FAQ ### Where do my xpubs and addresses go? Only to the Bitcoin API you query. By default rotki uses public block explorers (blockchain.info, blockstream.info, mempool.space); you can instead set a custom mempool.space / Esplora-compatible endpoint in Settings → RPC. Either way the request goes from your computer to that endpoint without passing through any rotki-operated server. ### Is an xpub safe to share with rotki? An xpub only allows watching balances; it cannot spend funds. rotki stores it locally and uses it from your machine to derive addresses and query balances. Avoid pasting xpubs into remote services in general. ### Can I run rotki against my own Bitcoin node? rotki queries Bitcoin through a mempool.space / Esplora-style REST API, not the Electrum protocol or Bitcoin Core's RPC. You can self-host mempool.space or an Esplora (electrs) instance and point rotki at it via Settings → RPC → Bitcoin Mempool. ### Does rotki support Taproot? Yes. rotki supports Taproot (P2TR) xpubs and Bech32m Taproot addresses natively when adding Bitcoin accounts. ### Is testnet supported? No. rotki tracks mainnet Bitcoin only; testnet prefixes such as vpub are not accepted. # Bitcoin Cash Track Bitcoin Cash addresses or whole wallets via xpub keys. ## Features - Single BCH addresses (CashAddr or legacy format) or whole wallets via xpub keys. - Automatic address derivation from your extended public keys. - CashAddr ↔ legacy conversion: paste either format; rotki normalises addresses internally. - Multi-wallet: combine multiple xpubs and standalone BCH addresses in one rotki instance. - Same xpub on Bitcoin and Bitcoin Cash: each chain stores its own entry, so there is no collision when sharing keys across both. ## Setup 1. In rotki, open Blockchain & Accounts → Bitcoin Cash → Add. 2. Paste a BCH address (CashAddr or legacy) or an xpub. rotki derives sub-addresses automatically. 3. Optional: in Settings → RPC, point at your preferred BCH endpoint. ## FAQ ### Where do my BCH addresses and xpubs go? Only to the BCH endpoint you configure. rotki does not proxy through its own servers. ### Can I add the same xpub to both Bitcoin and Bitcoin Cash? Yes. rotki treats the two chains as separate xpub entries (uniqueness is xpub + derivation path + chain), so a single seed can be tracked on both without conflict. ### Does rotki accept legacy BCH addresses? Yes. Both legacy and CashAddr formats are accepted on input, and rotki converts between them as needed when querying balances. # Bitcoin.de Connect Bitcoin.de, Germany's peer-to-peer Bitcoin marketplace, to rotki to import your trades and account history with a read-only API key. ## Features - Bitcoin.de marketplace trades imported as swap events. - Balance reconciliation against your Bitcoin.de account. ## Setup 1. In Bitcoin.de, open API → Create API Key. 2. Set permissions to read-only (account, trades). Disable trade-creation and withdrawal permissions. 3. In rotki, open API Keys → Exchanges → Add Bitcoin.de and paste the key and secret. ## FAQ ### Where are my Bitcoin.de API keys sent? rotki is a local application: your Bitcoin.de API key is stored on your computer and used to sign each request, which goes directly from your machine to Bitcoin.de's API. No rotki-operated server ever sees the key or the request. ### Can rotki trade or withdraw on Bitcoin.de? No. rotki only requests read scopes and never sends trade or withdrawal calls. # Bitfinex Connect Bitfinex to rotki to import trades, deposits, and withdrawals, with balances tracked separately across exchange, margin, and funding wallets. Authenticate with a read-only API key; rotki processes everything locally on your machine. ## Features - Spot trades: full trade history including legacy pairs. - Deposits and withdrawals with fees preserved. - Balance reconciliation across all three Bitfinex wallet types (exchange, margin, funding). ## Limitations - Margin position history (funding fees, P/L, interest events) is not currently fetched - only balances on the margin and funding wallets are reported. ## Setup 1. In Bitfinex, open API → Create New Key. 2. Grant read permissions for Account History and Wallets. Leave Orders and Withdrawals disabled. 3. Optionally restrict the key to your IP. 4. In rotki, open API Keys → Exchanges → Add Bitfinex and paste the key and secret. ## FAQ ### Does rotki separate exchange, margin, and funding wallets? Yes. Bitfinex returns wallet type per balance, and rotki preserves that distinction in your portfolio view. ### Where are my Bitfinex API keys sent? rotki is a local application: your Bitfinex API key is stored on your computer and used to sign each request, which goes directly from your machine to Bitfinex's API. No rotki-operated server ever sees the key or the request. ### Can rotki place trades or withdraw from Bitfinex? No. rotki only requests read scopes and never sends order or withdrawal calls. # BitMEX Connect BitMEX to rotki to import your margin trading history, deposits, withdrawals, and balances. ## Features - Margin trades imported as margin position records with realised P/L and fees. - Deposits and withdrawals imported as asset movements. - Balance reconciliation: BitMEX returns balances in satoshi-style integer units; rotki normalises them to real amounts using the asset's decimals. ## Setup 1. In BitMEX, open Account → API Keys → Create API Key. 2. Leave only read access; do not grant the "Order" or "Withdraw" permissions. 3. In rotki, open API Keys → Exchanges → Add BitMEX and paste the key and secret. ## FAQ ### Where are my BitMEX API keys sent? rotki is a local application: your BitMEX API key is stored on your computer and used to sign each request, which goes directly from your machine to BitMEX's API. No rotki-operated server ever sees the key or the request. ### Can rotki place trades or withdraw on BitMEX? No. rotki only requests read access and never sends order or withdrawal calls. # Bitpanda Connect Bitpanda to rotki to import trades, deposits, withdrawals, and balances. ## Features - Spot trades imported as swap events with fees. - Crypto deposits and withdrawals from your Bitpanda wallets. - Fiat deposits and withdrawals from your Bitpanda fiat wallets. - Balance reconciliation against your Bitpanda wallet view. ## Setup 1. In Bitpanda, open Settings → API key → Generate API key. 2. Select the read scopes you want rotki to use (balances, trades, transactions). Bitpanda API keys grant no trading or withdrawal capability. 3. Save the key. Bitpanda shows it only once. 4. In rotki, open API Keys → Exchanges → Add Bitpanda and paste the key. ## FAQ ### Can rotki place trades or withdraw on Bitpanda? No. Bitpanda API keys are read-only by design and rotki only issues read calls. ### Where is my Bitpanda API key sent? rotki is a local application: your Bitpanda API key is stored on your computer and sent in the request header to authenticate each call, which goes directly from your machine to Bitpanda's API. No rotki-operated server ever sees the key or the request. # Bitstamp Connect Bitstamp to rotki to import trades, deposits, and withdrawals. Authenticate with a read-only API key, or import Bitstamp's transaction CSV export. Everything is processed on your machine. ## Features - Spot trades imported as swap events with fees in the settlement currency. - Deposits and withdrawals with on-chain addresses and transaction IDs where Bitstamp returns them. - CSV import for Bitstamp transaction exports, useful for backfilling old history. - Balance reconciliation against your Bitstamp account. ## Setup 1. In Bitstamp, open Account → Security → API Access and create a new API key. 2. Grant only read permissions (account balance, user transactions). Leave trading and withdrawal permissions off. 3. Approve the key by email. 4. In rotki, open API Keys → Exchanges → Add Bitstamp and paste the key and secret. 5. Alternatively, in rotki open Import Data and select Bitstamp to import a transaction CSV. ## FAQ ### Can I import Bitstamp data via CSV? Yes. rotki accepts Bitstamp's transaction CSV export, which is useful if you'd rather not generate an API key or want very old history. ### Where are my Bitstamp API keys sent? rotki is a local application: your Bitstamp API key is stored on your computer and used to sign each request, which goes directly from your machine to Bitstamp's API. No rotki-operated server ever sees the key or the request. ### Can rotki withdraw from Bitstamp? No. rotki only requests read scopes and never sends withdrawal calls. # Bittrex Bittrex US wound down in 2023 and Bittrex Global ceased operations later that year. If you traded there, rotki can ingest your historical Bittrex trades and transfers from CSV exports so they appear in your portfolio history and tax reports. ## Features - CSV import of Bittrex trade history and deposit/withdrawal exports. - Historical Bittrex trades feed into the same cost basis and tax report as the rest of your portfolio. ## Limitations - Bittrex is no longer operational. There is no live API; rotki supports CSV imports only. ## Setup 1. Locate your saved Bittrex CSV exports (trades and/or transactions). 2. In rotki, open Import Data and select the Bittrex file. ## FAQ ### Is Bittrex still operating? No. Bittrex US shut down in 2023 and Bittrex Global ceased operations later that year. rotki supports it for historical accounting only. ### Where is my Bittrex CSV processed? Entirely on your computer. CSV imports never leave your machine. # BlockFi BlockFi filed for bankruptcy in November 2022 and ceased operations. If you held assets there, rotki can ingest your historical BlockFi trades, interest, deposits, and withdrawals from CSV exports so they appear in your portfolio history and tax reports. ## Features - CSV import for BlockFi trading activity (trades export). - CSV import for BlockFi transactions (deposits, withdrawals, interest payments, bonuses, referrals). - Interest, bonus, and referral payments imported as receive events that flow into your portfolio and tax report. ## Limitations - BlockFi is no longer operational. There is no live API; rotki supports historical CSV imports only. ## Setup 1. Locate your saved BlockFi trading activity and transaction CSVs. 2. In rotki, open Import Data and select the BlockFi file (trades and transactions are imported separately). ## FAQ ### Is BlockFi still active? No. BlockFi filed for bankruptcy in November 2022. rotki supports it for historical accounting only. ### Are BlockFi interest payments included in my tax report? Yes. Imported interest, bonus, and referral payments are treated as receive events and flow through to your PnL and tax exports. ### Where is my BlockFi CSV processed? Entirely on your computer. CSV imports never leave your machine. # Blur rotki decodes Blur staking and airdrop claims on Ethereum, and reports your staked BLUR balance alongside the rest of your portfolio. ## Features - Stake and unstake of BLUR in the Blur staking contract decoded as staking events. - BLUR airdrop claims (airdrop 2 distributor) decoded as airdrop receive events. - Staked BLUR balance queried on demand and included in your portfolio. ## Limitations - Marketplace activity (sales, listings, bids) and Blend NFT loans are not currently decoded as Blur-counterparty events. ## Setup 1. In rotki, add the Ethereum address that holds your BLUR or interacts with the Blur staking contract. 2. In rotki, open History and let the initial sync run. Staking and airdrop events are decoded automatically. ## FAQ ### Does rotki read Blur 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. ### Was the BLUR airdrop captured? Yes. Claims from the Blur airdrop 2 distributor are decoded as airdrop receive events. # Bybit Connect Bybit to rotki to pull spot trades, deposits, withdrawals, and balances. ## Features - Spot trades imported from Bybit's order history. - Deposits and withdrawals walked in 30-day windows over your full history. - Balance reconciliation across your Bybit wallet (unified or classic) and funding account. ## Limitations - Bybit's deposit/withdrawal API enforces a maximum 30-day window per request, so the first sync over a long history takes some time. - Trade fees from the execution-list endpoint are not yet imported; trades are sourced from the order history. - Bybit's API does not expose balances locked in bots, so those are not included. - Margin/derivatives history is not imported. ## Setup 1. In Bybit, open Account → API → Create New Key. 2. Choose System-generated API Keys and set permissions to Read-Only. Leave trading and withdrawal scopes off. 3. Optionally whitelist your IP for additional safety. 4. In rotki, open API Keys → Exchanges → Add Bybit and paste the key and secret. ## FAQ ### Where are my Bybit API keys sent? rotki is a local application: your Bybit API key is stored on your computer and used to sign each request, which goes directly from your machine to Bybit's API. No rotki-operated server ever sees the key or the request. ### Why does the first sync take a while? Bybit limits its deposit and withdrawal endpoints to a 30-day window per request. rotki walks through your history in chunks since the account's earliest activity. ### Can rotki place trades or withdraw funds? No. rotki only asks for read-only scopes and never sends trade or withdrawal calls. # Circle CCTP rotki decodes Circle's Cross-Chain Transfer Protocol (CCTP v1 and v2) on both source and destination chains, tagging the USDC burn and mint as bridge events so they don't flow through your PnL as ordinary spends and receives. ## Features - CCTP v1 burn-and-mint events decoded on both sides of the bridge. - CCTP v2 burn-and-mint events decoded on both sides of the bridge. - USDC moved via CCTP is tagged as a bridge deposit on the source chain and a bridge withdrawal on the destination chain, so cost basis isn't disturbed. - Decoded across all CCTP-enabled chains rotki currently supports: Ethereum, Arbitrum, Base, Optimism, Polygon PoS, Monad, and Hyperliquid. ## Setup 1. In rotki, add your addresses on both the source and destination chains you use with CCTP. 2. In rotki, open History and let the initial sync run. CCTP transfers on both sides are decoded automatically. ## FAQ ### Does rotki read CCTP transfers from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. ### Will my CCTP bridge create a fake gain or loss? No. The burn and the mint are both tagged as bridge events, which rotki treats as non-taxable transfers rather than spends or receives. # clr.fund rotki decodes clr.fund quadratic-funding activity on Arbitrum One so contributors, voters, and grant recipients have clean records. Donations, votes, project applications, and matching-pool claims are all recognised. ## Features - Contributions to a clr.fund round are tagged as donations against the clr.fund counterparty. - Votes are recorded as informational events tied to the round. - Project applications to a round's recipient registry are recognised (with the application fee, if any). - Matching-pool claims are decoded as funds-claimed events on the recipient address. ## Limitations - clr.fund decoding currently ships with Arbitrum One rounds only. The decoder is chain-agnostic, but no Gnosis Chain round addresses are registered. ## Setup 1. In rotki, add the Arbitrum One address you used for clr.fund. 2. In rotki, open History and let the initial sync run. Donations, votes, applications, and matching claims for that address are decoded automatically. ## FAQ ### Does rotki read clr.fund activity from its own servers? No. rotki is a local application that talks directly to the Arbitrum 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. ### Are matching-pool payouts captured? Yes. Funds claimed from a clr.fund funding round are decoded against the recipient address. # Coinbase Connect your Coinbase account to rotki and import trades, conversions, deposits, withdrawals, and staking rewards. rotki talks to Coinbase directly from your computer with a read-only API key. ## Features - Simple buys and sells imported as swap events. - Coinbase Advanced Trade order fills imported (multiple fills under one order are folded into the single trade). - Coin-to-coin conversions imported as a sell of the source asset and a buy of the destination, with the Coinbase conversion fee captured. - External transfers (deposits/withdrawals) and internal Coinbase transfers (exchange\_deposit / exchange\_withdrawal) imported as asset movements. - Staking rewards, inflation rewards, interest, cardbuyback, and staking/unstaking transfers recognised. - Balance reconciliation across all account portfolios. ## Setup 1. In Coinbase, create an API key from the API keys section of your settings (newer keys are created in the Coinbase Developer Platform). 2. Grant View (read-only) permission only, and restrict the key to the accounts/portfolio you want rotki to see. 3. Save the key and secret. Coinbase shows the secret (or downloadable key file) only once; copy it now. 4. In rotki, open API Keys → Exchanges → Add Coinbase and paste the key and secret. ## FAQ ### Does rotki support Coinbase Advanced Trade? Yes. Advanced Trade order fills are picked up alongside simple buys/sells through the same API key. ### Are Coinbase staking rewards included in tax reports? Yes. Staking rewards, inflation rewards, and interest are recognised as income events and flow into PnL and tax exports. ### Where are my Coinbase API keys sent? rotki is a local application: your Coinbase API key is stored on your computer and used to sign each request, which goes directly from your machine to Coinbase's API. No rotki-operated server ever sees the key or the request. ### Can rotki move my coins or place trades? No. rotki only requests view scopes and never sends trade or withdrawal calls. ### What about Coinbase Pro / Coinbase Prime? Coinbase Pro and Coinbase Prime are separate integrations in rotki. Coinbase Pro was shut down by Coinbase in late 2022; rotki retains its historical support. # Coinbase Prime Connect Coinbase Prime to rotki to import institutional trades, conversions, deposits, withdrawals, and rewards. Authenticate with a read-only API key; rotki processes everything on your own machine. ## Features - Coinbase Prime orders (FILLED status) imported as swap events with commission as the trade fee. - Conversions imported with the Coinbase Prime conversion fee captured. - Deposits, withdrawals, and internal Coinbase deposits (COINBASE\_DEPOSIT) imported as asset movements. - Rewards imported as receive events. - Balance reconciliation across every portfolio linked to the API key (portfolios are auto-discovered). ## Limitations - Margin/derivatives history is not imported. ## Setup 1. In Coinbase Prime, create an API key under Settings → API with read-only scopes. 2. Note the API key, secret, and passphrase. Coinbase Prime requires all three; portfolio IDs are discovered automatically. 3. In rotki, open API Keys → Exchanges → Add Coinbase Prime and paste the credentials. ## FAQ ### How is Coinbase Prime different from Coinbase? Coinbase Prime is Coinbase's institutional offering with multi-portfolio accounts. Add it as a separate integration; consumer Coinbase uses its own integration entry. ### Do I need to enter each portfolio ID? No. rotki lists all portfolios linked to the API key and queries each one automatically. ### Are Coinbase Prime rewards included in tax reports? Yes. Rewards are imported as receive events and flow through to your PnL and tax exports. ### Where are my Coinbase Prime API credentials sent? rotki is a local application: your Coinbase Prime credentials are stored on your computer and used to sign each request, which goes directly from your machine to Coinbase Prime's API. No rotki-operated server ever sees the credentials or the request. # Coinbase Pro Coinbase Pro was retired by Coinbase in late 2022. If you traded there, rotki can ingest your historical trades and transfers from the Coinbase Pro CSV export and feed them into your portfolio history and tax reports. ## Features - CSV import of Coinbase Pro account statements: trades, deposits, and withdrawals. - Trade rows are grouped by Trade ID so each fill becomes a single swap event. - Historical Coinbase Pro activity feeds into the same cost basis and tax report as the rest of your portfolio. ## Limitations - Coinbase Pro was retired by Coinbase; for trades after the shutdown, use the Coinbase integration with Advanced Trade. - There is no live Coinbase Pro API; rotki supports CSV imports only. ## Setup 1. Export your Coinbase Pro account statement from the Coinbase reports archive (or use a copy you saved before the shutdown). 2. In rotki, open Import Data and select the Coinbase Pro file. ## FAQ ### Is Coinbase Pro still active? No. Coinbase retired Coinbase Pro in late 2022 and merged trading into Coinbase Advanced Trade. rotki supports it for historical accounting only. ### Should I use the Coinbase integration instead? For activity after the shutdown, yes. Use the Coinbase integration for current trades and keep your historical Coinbase Pro data in this separate entry. ### Where is my Coinbase Pro CSV processed? Entirely on your computer. CSV imports never leave your machine. # Compound rotki decodes your Compound v2 activity on Ethereum and your Compound v3 (Comet) activity on Ethereum, Arbitrum, Optimism, Base, Polygon PoS, and Scroll: supplies, withdrawals, borrows, repayments, and COMP claims. ## Features - Compound v2 on Ethereum: cToken mint/redeem and borrow/repay events are decoded against the Compound counterparty. - Compound v3 (Comet) deposits, withdrawals, borrows, and repays decoded across each Comet deployment. - Compound v3 bulker contract decoded so the underlying ETH/WETH movement is captured rather than being attributed to the bulker. - COMP rewards claims (Compound rewards contract) decoded as receive events. - Compound v3 balances queried on demand and included in your portfolio. ## Limitations - Compound v2 is only deployed on Ethereum; v2 activity on other chains is not decoded. ## Setup 1. In rotki, add the addresses you use on the chains where your Compound positions live (Ethereum for v2, plus any of Arbitrum, Optimism, Base, Polygon PoS, or Scroll for v3). 2. In rotki, open History and let the initial sync run. Compound v2 and v3 events are decoded automatically. ## FAQ ### Which chains does Compound v3 cover? Compound v3 (Comet) is decoded on Ethereum, Arbitrum, Optimism, Base, Polygon PoS, and Scroll. ### Are Compound bulker transactions handled? Yes. Compound v3 bulker calls are decoded so the underlying ETH/WETH movement is recorded against your address rather than the bulker contract. ### Does rotki read Compound positions from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Convex rotki decodes your Convex Finance activity on Ethereum: Curve LP deposits and withdrawals, vlCVX locks and unlocks, and CRV/CVX/extra reward claims. ## Features - Convex deposits and withdrawals of Curve LP tokens against the matching Convex pool. - vlCVX locks and unlocks decoded, with relocked withdrawals distinguished from genuine unlocks. - CRV, CVX, and pool reward claims tagged as reward subtype events against the Convex counterparty. - Virtual-rewards contracts (extra incentive rewards distributed alongside CRV/CVX) recognised. - Convex balances (staked LPs, staked CVX, locked CVX) queried on demand and included in your portfolio. ## Limitations - Convex decoding is currently Ethereum-only; there is no per-chain Convex module. ## Setup 1. In rotki, add the Ethereum address you use with Convex. 2. In rotki, open History and let the initial sync run. Deposits, withdrawals, locks, unlocks, and reward claims are decoded automatically. ## FAQ ### Are CRV and CVX rewards tracked? Yes. Pool reward claims are tagged as reward events against the Convex counterparty, including extra rewards distributed via the virtual-rewards contracts. ### Is vlCVX tracked? Yes. Vote-locked CVX deposits and unlocks are decoded; relocked withdrawals are not mistaken for an unlock. ### Does rotki read Convex positions 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. # CoW Swap rotki decodes CoW Swap trades on Ethereum and Gnosis Chain, including native-ETH orders via the ethflow contracts and vCOW claim/vesting flows. ## Features - GPv2 settlement trades decoded as swap events (spend/receive) with fees attributed to CoW Swap. - ETH-native orders via the CoW ethflow contracts decoded: place, refund, and invalidate events recognised. - vCOW claim and vesting decoded; vCOW returned and COW received are linked through the CoW counterparty. ## Limitations - CoW Swap decoding currently ships only for Ethereum and Gnosis Chain; other CoW deployments are not yet covered. ## Setup 1. In rotki, add the Ethereum and/or Gnosis Chain address you use with CoW Swap. 2. In rotki, open History and let the initial sync run. Trades, ethflow orders, and vCOW claims are decoded automatically. ## FAQ ### Are native-ETH (ethflow) trades supported? Yes. Orders placed through the CoW ethflow contracts are decoded as CoW Swap trades, with placement, refund, and invalidation events recognised. ### Does rotki read CoW Swap trades from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # CrossCurve CrossCurve lets you send a token on one chain and receive a (potentially different) token on another, often by routing through Curve stableswap pools and CrossCurve's own messaging layer. rotki decodes both legs of that flow so a cross-chain swap shows up as a single bridge movement instead of an unrelated spend and receive. ## Features - Source chain: the token you send through CrossCurve is labelled as a CrossCurve bridge deposit against your address. - The native-token fee you pay to the CrossCurve router for cross-chain messaging is captured separately as a CrossCurve bridge fee, so it doesn't inflate the bridged amount. - Destination chain: the token you receive is labelled as a CrossCurve bridge withdrawal, even when CrossCurve fulfils the swap by pulling liquidity from a Curve pool (the underlying Curve withdrawal is re-tagged to CrossCurve so it isn't double-counted). - Decoded on every EVM chain CrossCurve currently runs on: Ethereum, Arbitrum, Optimism, Base, Polygon PoS, Gnosis Chain, and BNB Smart Chain. ## Setup 1. In rotki, add the addresses on the chains you use with CrossCurve. 2. In rotki, open History and let the initial sync run. Bridge send (fee + deposit) and bridge receive events are decoded automatically. ## FAQ ### Will a CrossCurve swap create a fake gain or loss? No. The send is tagged as a bridge deposit and the receive as a bridge withdrawal, which rotki treats as non-taxable transfers rather than a spend/receive pair. ### What if CrossCurve completes the swap via a Curve pool on the destination chain? rotki re-tags the underlying Curve REDEEM\_WRAPPED event to the CrossCurve counterparty, so the receive is correctly attributed to your bridge instead of a Curve withdrawal. ### Does rotki read CrossCurve activity from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Crypto.com Connect Crypto.com to rotki to import trades, deposits, and withdrawals from the Crypto.com Exchange API, and bring in your mobile-app history (recurring buys, swaps, supercharger, earn, and rewards) via CSV import. ## Features - Crypto.com Exchange API: spot trades imported as swap events with fees. - Crypto.com Exchange API: deposits and withdrawals imported as asset movements. - Mobile-app CSV: recurring buys imported as swap events. - Mobile-app CSV: dynamic coin swaps, wallet swaps, lockup swaps, and interest swaps each recognised and converted to swap events. - Mobile-app CSV: rewards (Crypto.com Visa rebates, MCO stake reward, pay checkout reward, supercharger reward, crypto earn interest, etc.) imported as receive events. - Mobile-app CSV: supercharger and crypto earn deposits/withdrawals tracked separately from spot transfers. ## Limitations - Crypto.com Exchange API only returns the last 6 months of trades, deposits, and withdrawals. For older history, use the mobile-app CSV export. ## Setup 1. Crypto.com Exchange: open Settings → API → Create New API Key and set permissions to read-only. 2. In rotki, open API Keys → Exchanges → Add Crypto.com and paste the key and secret. 3. Mobile app: in the Crypto.com app, export your transaction history as CSV. 4. In rotki, open Import Data and select the Crypto.com CSV. ## FAQ ### Does rotki support both the Crypto.com Exchange and the mobile app? Yes. The Exchange uses the API key path; the mobile app uses CSV import. Combine both for a complete history. ### Why is my older Exchange history missing? Crypto.com's Exchange API only returns the most recent 6 months. For older trades and transfers, fall back to the mobile-app CSV export. ### Where are my Crypto.com API keys sent? rotki is a local application: your Crypto.com API key is stored on your computer and used to sign each request, which goes directly from your machine to Crypto.com's API. No rotki-operated server ever sees the key or the request. ### Can rotki trade or withdraw on Crypto.com? No. rotki only requests read scopes and never sends trade or withdrawal calls. # Curve rotki decodes your Curve activity across the EVM chains where Curve is deployed: pool swaps, deposits and withdrawals, gauge interactions, voting bribes, and the newer crvUSD and Llama Lend submodules. Locked CRV in the veCRV contract is shown in your balances. ## Features - Pool swaps (including routes via the Curve router) decoded as swap events. - Deposits decoded for single-asset, dynamic-asset, and intermediate-pool flows, including add-liquidity-and-stake combinations. - Withdrawals decoded for dynamic-amount and single-token withdrawals, with the source pool surfaced in the event notes. - Gauge deposits, withdrawals, and reward claims tagged against the Curve counterparty. - veCRV locks, increases, and lock-time extensions recognised; locked CRV balance is queried and surfaced in your portfolio. - veCRV voting bribes claimed via Curve are decoded as bribe receive events. - crvUSD borrow/repay activity decoded via the Curve crvUSD submodule. - Llama Lend (Curve Lend) deposits, withdrawals, borrows, and repayments decoded across supported chains. - Decoded on all chains Curve currently runs on: Ethereum, Arbitrum, Optimism, Base, Polygon PoS, Gnosis Chain, BNB Smart Chain, Monad, and Hyperliquid. ## Setup 1. In rotki, add the addresses you use on the chains where you interact with Curve. 2. In rotki, open History and let the initial sync run. Pool, gauge, veCRV, crvUSD, and Llama Lend events are decoded automatically. 3. If you've just opened a brand-new Curve position, you can refresh the Curve cache via Settings → Manage Data → Refresh protocol data (select Curve). ## FAQ ### Is locked CRV (veCRV) tracked? Yes. Lock events are decoded and the current locked CRV balance is queried from the veCRV contract. ### Are gauge rewards captured? Yes. Gauge claims are decoded against the Curve counterparty as reward receive events. ### Are crvUSD and Llama Lend supported? Yes. crvUSD borrow/repay flows and Llama Lend deposit/withdraw/borrow/repay flows are decoded. ### Does rotki read Curve activity from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # DeFi Saver rotki recognises DeFi Saver automation subscription events on Ethereum, so subscribing to or deactivating an automation strategy shows up as a DeFi Saver event in your history. ## Features - Subscribe-to-automation events on the DeFi Saver SubStorage contract decoded as informational DeFi Saver events with the subscription ID and proxy address noted. - Deactivate-automation events decoded as informational DeFi Saver events with the subscription ID noted. - DeFi Saver positions held via a DSProxy benefit from rotki's generic DSProxy resolution: when you add the owner address, rotki also resolves the proxy so its on-chain activity is included. ## Limitations - DeFi Saver-specific decoding is currently limited to automation subscribe/deactivate events. The underlying actions performed by an automation run (e.g. on MakerDAO, Liquity, Aave, or Compound) are decoded by each protocol's own decoder, not by a DeFi Saver-aware composite. ## Setup 1. In rotki, add the Ethereum owner address you use with DeFi Saver. Any DSProxy it owns is resolved automatically. 2. In rotki, open History and let the initial sync run. Subscribe/deactivate events on the DeFi Saver SubStorage contract are decoded automatically; the underlying MakerDAO/Liquity/Aave/Compound activity is decoded by those protocols' integrations. ## FAQ ### Does rotki recognise DeFi Saver-created DSProxies? Yes, but not as DeFi Saver-specific. DSProxies are resolved generically from your owner address, so any positions held via a DSProxy (DeFi Saver-created or not) flow into your portfolio. ### Are automation runs labelled as DeFi Saver activity? Only the subscribe and deactivate calls are tagged against DeFi Saver. The on-chain actions performed by an automation run are decoded by the underlying protocol's integration (MakerDAO, Liquity, Aave, etc.). ### Does rotki read DeFi Saver 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. # Degen rotki decodes DEGEN airdrop claims on Base so each season's claim shows up against the Degen counterparty in your history. ## Features - Degen airdrop 1 claims decoded as airdrop receive events against the Degen counterparty. - Degen airdrop 2 (Season 1) claims decoded as airdrop receive events against the Degen counterparty. - Degen airdrop 3 (Season 3) claims decoded as airdrop receive events against the Degen counterparty. ## Limitations - Only the three known Merkle-claim airdrop contracts are decoded. Farcaster tip transfers and DEGEN swaps appear as ordinary token movements, not Degen-counterparty events. ## Setup 1. In rotki, add the Base address you used to claim DEGEN. 2. In rotki, open History and let the initial sync run. Claims from the registered airdrop contracts are decoded automatically. ## FAQ ### Are Farcaster DEGEN tips decoded as Degen events? No. Tip transfers appear as ordinary ERC-20 receives in your history; only the official airdrop-claim contracts are tagged against the Degen counterparty. ### Does rotki read DEGEN activity from its own servers? No. rotki is a local application that talks directly to the Base 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. # DigixDAO DigixDAO voted to dissolve in 2020 and refunded its treasury to DGD holders. rotki decodes the DGD burn and the paired ETH refund from the dissolution contract so the wind-down shows up cleanly in your history. ## Features - DGD sent to the DigixDAO refund contract is tagged as a burn against the DigixDAO counterparty. - ETH received from the refund contract is tagged as a refund against the DigixDAO counterparty. - The burn and the refund are linked in your history so the wind-down reads as a single event pair. ## Limitations - DigixDAO is dissolved; rotki supports it for historical accounting of the refund only. No new DigixDAO events exist. ## Setup 1. In rotki, add the Ethereum address that held DGD when you redeemed against the refund contract. 2. In rotki, open History and let the initial sync run. The DGD burn and ETH refund pair is decoded automatically. ## FAQ ### Is DigixDAO still active? No. The DAO voted to dissolve in 2020 and DGD holders were refunded in ETH. rotki supports it for historical accounting only. ### Does rotki read DigixDAO 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. # Diva rotki decodes activity around the DIVA governance token on Ethereum: airdrop claims, delegate changes, and votes on the Diva Governor contract. ## Features - DIVA airdrop claims (Merkle distributor) decoded as airdrop receive events against the Diva counterparty. - Delegate-changed events on the DIVA token recorded as governance informational events with the old and new delegate noted. - Diva Governor proposals and votes decoded via rotki's generic governance interface, with links to Tally proposal pages. ## Limitations - Only DIVA governance-token activity is decoded. The Diva Staking product (liquid staking deposits/withdrawals/rewards) is not covered by a Diva-specific decoder. ## Setup 1. In rotki, add the Ethereum address that held or claimed DIVA. 2. In rotki, open History and let the initial sync run. Airdrop claims, delegate changes, and governor events are decoded automatically. ## FAQ ### Are Diva Staking deposits and rewards decoded? No. Only DIVA governance-token events (airdrop, delegation, governor proposals/votes) are tagged against the Diva counterparty. ### Does rotki read DIVA 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. # Drips rotki decodes Drips v1 activity on Ethereum and Polygon PoS: outgoing gifts (Give) and ongoing streams (Drip) you send, splits you configure, and funds you collect from incoming drips. ## Features - Outgoing Give calls labelled as donations against the Drips counterparty. - Ongoing Dripping configurations recorded as informational events with the stream parameters, and the corresponding spends tagged as donations. - Splits and SplitsUpdated configurations recorded as informational Drips events. - Collected receives (funds drawn from an incoming Drip) tagged as donate-subtype receives against the Drips counterparty. ## Limitations - Only Drips v1 (the original DAI-centric streaming contracts) is decoded. Drips v2 (the newer Radicle Drips deployment) is not yet covered. - Drips v1 is decoded on Ethereum and Polygon PoS only. ## Setup 1. In rotki, add the addresses you use with Drips on Ethereum and/or Polygon PoS. 2. In rotki, open History and let the initial sync run. Give, Drip, Split, and Collected events are decoded automatically. ## FAQ ### Are incoming Drips income? rotki labels Collected receives as donate-subtype events against the Drips counterparty. Whether they are taxable income is jurisdiction-specific; consult a tax professional. ### Does rotki read Drips activity from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # DXdao rotki decodes interactions with the DXdao Mesa exchange contract on Ethereum: deposits, withdrawals, withdraw requests, and order placements from the batch-auction era. ## Features - Deposits into the DXdao Mesa exchange contract tagged as deposit-to-protocol events against the DXdao counterparty. - Withdrawals from the DXdao Mesa exchange contract tagged as withdraw-from-protocol events. - Withdraw-request events (the two-step Mesa withdrawal flow) recorded as informational DXdao events with the requested asset and amount. - Order placements on Mesa recorded as informational events showing the sell amount, buy amount, and tokens. ## Limitations - Only DXdao Mesa exchange contract activity is decoded. DXD redemptions, the DXdao Reputation token, and other DXdao products are not covered by a DXdao-specific decoder. ## Setup 1. In rotki, add the Ethereum address you used with the DXdao Mesa exchange. 2. In rotki, open History and let the initial sync run. Mesa deposits, withdrawals, withdraw requests, and order placements are decoded automatically. ## FAQ ### Is DXdao still active? DXdao voted to dissolve in 2024. rotki's DXdao decoder covers historical Mesa exchange activity rather than the dissolution itself. ### Are DXD redemptions decoded? Not as DXdao-specific events. The DXdao decoder is scoped to the Mesa exchange contract. ### Does rotki read DXdao 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. # Echo Echo is the on-chain investment platform where members follow a group lead into individual deals, with everyone's USDC commitment pooled into a single on-chain entity that invests in the target project. rotki decodes the on-chain side of that flow on Base: your commitment into a deal pool, Echo's platform fee, and full refunds if you're deregistered before the pool closes. ## Features - Deal commitment: the USDC (or other deal-currency token) you send to follow a group lead into a deal is tagged as a deposit-to-protocol event against the Echo counterparty, with the deal pool address recorded in the notes. - Platform fee: the on-chain fee Echo charges on top of your commitment is broken out as a fee-subtype event, so your committed capital and the fee are accounted for separately rather than as one inflated spend. - Pool refund: if you're deregistered from a deal pool (full refund), the USDC you get back is tagged as a withdraw-from-protocol event against Echo and linked to the deal pool address. ## Limitations - Echo decoding currently ships on Base only. - Only full refunds (a member being deregistered from a pool) are decoded. Partial refunds don't emit the deregistration event, so they appear as ordinary token receives; reconcile them manually if you have one. - Token or equity distributions that arrive after a deal closes (project tokens, vested receivables, group-lead carry) appear as ordinary receives, not as Echo-counterparty events. ## Setup 1. In rotki, add the Base address you used to commit to Echo deals. 2. In rotki, open History and let the initial sync run. Deal commitments, Echo platform fees, and full pool refunds are decoded automatically. ## FAQ ### Are Echo platform fees separated from my commitment? Yes. The platform fee is split out as a fee-subtype event against the Echo counterparty, so the amount you actually committed to the deal pool stays clean for cost-basis purposes. ### Does rotki read Echo activity from its own servers? No. rotki is a local application that talks directly to the Base 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. # Ethereum Follow Protocol rotki decodes Ethereum Follow Protocol (EFP) list operations - follow, unfollow, tag, and untag - on Ethereum, Optimism, and Base, so your on-chain social activity appears in your history with the target address (and tag) recorded. ## Features - Follow operations: a List Op against your EFP list is decoded as an informational EFP event noting the address you followed. - Unfollow operations: recognised as informational EFP events noting the address you unfollowed. - Tag and untag operations: recognised as informational EFP events with the tag label and the target address. - Decoded on every chain EFP currently runs on: Ethereum, Optimism, and Base. ## Limitations - Only address-type list records (RecordVersion 1, RecordType 1) are decoded. Future record types and op versions will be silently skipped until the decoder is updated. - List creation/minting and list-registry changes are not specifically decoded as EFP events; only operations on the list-records contract are. ## Setup 1. In rotki, add the address whose EFP list is controlled by you (the slot owner). 2. In rotki, open History and let the initial sync run. Follow, unfollow, tag, and untag operations are decoded automatically. ## FAQ ### Are EFP tags captured? Yes. Both tag and untag operations are decoded with the tag label and target address in the event notes. ### Does rotki read EFP activity from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # EigenLayer rotki decodes your EigenLayer activity on Ethereum: LST deposits into strategies, operator delegation, queued and completed withdrawals, native restaking via EigenPods, AVS reward claims, and EIGEN airdrop claims. ## Features - LST deposits into EigenLayer strategies tagged against the EigenLayer counterparty. - Operator delegation and undelegation events recorded with operator addresses in the notes. - Withdrawals queued and withdrawals completed decoded as separate events so the in-flight balance is visible until completion. - Native restaking via EigenPods: start-checkpoint, finalize-checkpoint, and validator-balance-updated events decoded. - AVS reward claims via the EigenLayer Rewards Coordinator tagged as reward receive events. - EIGEN airdrop claims decoded for Season 1 Phase 1, Season 1 Phase 2, and Season 2 distributors. - EigenLayer balance query covers strategy deposits, queued withdrawals, and EigenPod-held ETH. ## Limitations - EigenLayer decoding is currently Ethereum-only; other-chain deployments are not yet covered. - If an operator forcibly undelegates a staker, rotki only sees that event if the staker's address is tracked when the transaction is queried. ## Setup 1. In rotki, add the Ethereum address you use with EigenLayer (the staker address, not the EigenPod proxy). 2. In rotki, open History and let the initial sync run. Deposits, delegations, withdrawals, checkpoints, AVS reward claims, and EIGEN airdrop claims are decoded automatically. ## FAQ ### Are AVS rewards tracked? Yes. Claims via the EigenLayer Rewards Coordinator are tagged as reward subtype receives against the EigenLayer counterparty. ### Was the EIGEN airdrop captured? Yes. Season 1 Phase 1, Season 1 Phase 2, and Season 2 EIGEN airdrop claims are decoded against the EigenLayer counterparty. ### Does rotki read EigenLayer 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. # Element Finance rotki decodes ELFI airdrop claims on Ethereum: when you claim and delegate your ELFI through Element's Council vote/locking flow, the receive is tagged as an airdrop against the Element Finance counterparty. ## Features - ELFI airdrop claims via the Element Council vote/locking contract are decoded as airdrop receive events against the Element Finance counterparty. - The delegation choice made when claiming (self-delegate or delegate to another address) is recorded in the event notes. ## Limitations - Element Finance decoding is currently scoped to the ELFI airdrop claim only. Principal Token and Yield Token activity, pool LP positions, and ongoing Council governance proposals/votes are not decoded as Element-counterparty events. ## Setup 1. In rotki, add the Ethereum address you used to claim ELFI. 2. In rotki, open History and let the initial sync run. The ELFI airdrop claim is decoded automatically. ## FAQ ### Are Element Principal Tokens and Yield Tokens decoded? Not currently. The Element Finance decoder is limited to the ELFI airdrop claim; PT/YT positions appear as ordinary token movements rather than Element-tagged events. ### Does rotki read Element Finance 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. # ENS rotki decodes the full lifecycle of an ENS name on Ethereum: registration and renewal (with the ETH cost), .eth name transfers, resolver and owner changes, addr/content-hash/text-record updates on the public resolver, and the original ENS governance-token airdrop claim. Tracked addresses also display their primary ENS name across the app, and ENS expirations show up as reminders in rotki's calendar. ## Features - Name registration: the NameRegistered event is decoded with the ETH paid, and the ETH spend is linked to the ENS counterparty. - Name renewal: the NameRenewed event is decoded with the ETH paid for the renewal. - .eth name transfers (ERC-721) are recognised against the ENS counterparty. - Resolver changes (NewResolver), owner changes / subnode creation (NewOwner), and addr-changed records on the public resolver are decoded. - Content-hash updates on the public resolver decoded with the codec (ipfs, swarm, etc.) and value. - TextChanged records on the public resolver decoded for both key-only and key+value event variants. - ENS airdrop claims decoded as airdrop receive events against the ENS counterparty. - Primary ENS name resolution: tracked Ethereum addresses display their primary ENS name across the app. - ENS expiration reminders are added to rotki's calendar so you can renew before names lapse. ## Limitations - ENS registry/registrar/resolver decoding ships for Ethereum mainnet. ENS L2 deployments are not yet covered by the ENS-counterparty decoder, though the generic ENS resolver code is shared between mainnet and other chain implementations like Basenames. ## Setup 1. In rotki, add the Ethereum address you used to register, renew, or claim ENS. 2. In rotki, open History and let the initial sync run. Registrations, renewals, resolver changes, and the airdrop claim are decoded automatically; primary-name resolution and calendar reminders update in the background. ## FAQ ### Are ENS renewal costs reflected in my history? Yes. The NameRenewed event is decoded with the ETH paid, so the renewal cost is captured. ### Are ENS expirations surfaced anywhere? Yes. rotki adds an ENS-expiration entry to its calendar so you get a reminder before the name lapses. ### Was the ENS airdrop captured? Yes. ENS airdrop claims are decoded as airdrop receive events against the ENS counterparty. ### Does rotki resolve ENS through its own servers? No. rotki is a local application: ENS resolution and event decoding go directly from your computer to the Ethereum RPC endpoint you configure (the public default, a third-party provider, or your own node), without passing through any rotki-operated server. # Ethereum Validators rotki tracks your Ethereum validators directly against the beacon chain and execution layer: balances over time, consensus PnL, withdrawals to your execution address, and execution-layer rewards split between block proposal payments and MEV. Validator data is queried from the beacon endpoint you configure; withdrawals are reconstructed from Etherscan with a Blockscout fallback. ## Features - Add validators by index or public key; balance and status are queried from the beacon endpoint. - Consensus-layer PnL computed from balance snapshots and validator exits. - Beacon chain withdrawals to the execution address decoded and credited to the right validator. - Execution-layer rewards split into block proposal payments and MEV payments, reported separately. - Exited validators continue to display in your history with their final state, so historical PnL stays correct. - Validator-related events feed the rest of rotki: tax reports, history filters, and PnL summaries treat them like any other history events. ## Limitations - Tracking Ethereum validators is not available on the free tier. A Basic or Advanced subscription is required, and the ETH-staking limit applied to your account scales with your tier. If the Basic and Advanced limits don't fit your setup, contact us to arrange a custom plan with a higher limit. ## Setup 1. In rotki, open Blockchain Balances → Ethereum Validators and add a validator by index or public key. 2. Optional: configure a beacon-node endpoint in Settings if you don't want to rely on the default. 3. In rotki, open History and let the initial sync run. Withdrawals, block proposals, MEV payments, and balance updates are populated automatically. ## FAQ ### Are MEV/block rewards captured separately? Yes. Execution-layer rewards are split into block proposal payments and MEV payments, so they are reported as two separate streams alongside consensus PnL. ### Can I track validators without tracking the withdrawal address? Yes. rotki resolves validators by index/public key and queries their withdrawals against the execution address even if you haven't added that address as a tracked account. ### Does rotki query the beacon chain through its own servers? No. rotki is a local application that talks directly to the beacon-chain endpoint you configure, plus Etherscan/Blockscout for execution-layer data. Each query goes from your computer to those endpoints without passing through any rotki-operated server. # Ethereum Add your Ethereum addresses (or ENS names, or read-only watch addresses) to rotki and you get balances, full transaction history, ERC-20 holdings, NFTs, and decoded DeFi activity for every protocol rotki ships a decoder for - all queried directly from the RPC endpoint you choose. ## Features - ETH and ERC-20 balances queried per tracked address against the RPC you configure. - Transaction history decoded into readable events: transfers, swaps, approvals, deposits, withdrawals, protocol interactions. - Dedicated decoders for a wide range of Ethereum protocols (Aave, Curve, Uniswap, MakerDAO, Lido, Morpho, Yearn, Pendle, and many more), so activity is tagged with the right counterparty instead of appearing as raw calls. - NFT tracking for ERC-721 and ERC-1155 holdings, including ENS names. - Primary ENS name resolution: tracked addresses display their primary ENS name across rotki. - Free-tier tracking has no address-count limit; track as many Ethereum addresses as you like. ## Limitations - Ethereum-validator tracking (beacon chain balances, withdrawals, MEV, block-proposal rewards) is a separate, paid feature. See the Ethereum Validators integration page for details. ## Setup 1. In rotki, open Blockchain Balances → Ethereum → Add address. Paste your address or ENS name, optionally with a label. 2. Optional: configure your preferred Ethereum RPC endpoint in Settings (a public default is provided). Pointing rotki at your own geth/reth/erigon node is the most private and reliable setup. 3. In rotki, open History and let the initial sync run. The first sync of a long-history wallet can take a few minutes; subsequent syncs are incremental. ## FAQ ### Do my Ethereum addresses leave my machine? No. rotki is a local application that talks directly to the Ethereum RPC endpoint you configure - the public default, your own node, or a provider like Infura/Alchemy. The query goes from your computer to that endpoint without passing through any rotki-operated server. ### Do I need to give rotki a private key or seed phrase? No. rotki is read-only. You only ever add public addresses or ENS names. ### Can I run rotki against my own Ethereum node? Yes. Point rotki at your own RPC endpoint (geth, reth, erigon, nethermind, etc.) in Settings. ### Does rotki decode my DeFi activity automatically? Yes. rotki ships dedicated decoders for the major Ethereum DeFi protocols, so transactions show up as readable, counterparty-tagged events instead of raw call data. # Ethereum Attestation Service rotki decodes Ethereum Attestation Service (EAS) Attested events as informational attest events tied to your address, with a direct link to the attestation page on easscan for the chain it was made on. ## Features - Attested events from the EAS attestation service contract are decoded as informational attest events against the EAS counterparty. - The event notes include a direct easscan.org link to view the attestation by UID (with the correct chain-specific subdomain). - Both attester and recipient sides are matched: if either the attester or the recipient address is tracked, the event is attached to that address. - Decoded on Ethereum, Arbitrum One, Optimism, and Base. ## Limitations - Only Attested (attestation creation) events are decoded. Revocation events are not currently decoded as EAS-counterparty events. ## Setup 1. In rotki, add the Ethereum, Arbitrum, Optimism, or Base address that attests via EAS or receives attestations. 2. In rotki, open History and let the initial sync run. Attested events are decoded automatically with an easscan link in the notes. ## FAQ ### Are attestation revocations captured? Not as EAS-counterparty events. Only attestation creations (Attested events) are decoded. ### Does rotki read EAS activity from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Extrafi rotki decodes Extrafi activity on Optimism and Base: lending pool deposits and withdrawals, pool reward claims, and leveraged farm positions (where Extrafi borrows on your behalf to amplify the LP). ## Features - Lending pool deposits and withdrawals tagged against the Extrafi counterparty with the pool surfaced in the notes. - Pool reward claims (REWARD\_PAID events) tagged as reward-subtype receives against Extrafi. - Farm position openings decoded into separate borrow and deposit events when Extrafi takes leverage on your behalf, so the borrowed portion is visible in your history. - Partial farm-position closes decoded with the farm pair (token0-token1) named in the notes. - Extrafi balances (open lending-pool positions and farm positions) queried on demand and included in your portfolio. ## Limitations - Extrafi decoding currently ships on Optimism and Base only. ## Setup 1. In rotki, add the Optimism and/or Base address you use with Extrafi. 2. In rotki, open History and let the initial sync run. Pool deposits, withdrawals, reward claims, and farm open/close events are decoded automatically. ## FAQ ### Are Extrafi reward claims tagged? Yes. REWARD\_PAID events on Extrafi pools are tagged as reward-subtype receives against the Extrafi counterparty, so they don't appear as anonymous token receives. ### Are leveraged farm borrows visible? Yes. When you open a leveraged farm position, the borrowed amount is decoded as a separate borrow event in the same transaction as the deposit, so your borrowed exposure is visible. ### Does rotki read Extrafi activity from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Farcaster rotki decodes Farcaster Pro tier purchases on Base, tagging the USDC payment as a Farcaster subscription so the spend shows up in your history with the tier and duration in the notes. ## Features - Farcaster Pro tier purchases on Base are decoded: the USDC spend is tagged as a payment-subtype event against the Farcaster counterparty. - Event notes record which tier was purchased and the duration in days, so subscription renewals are easy to identify in your history. ## Limitations - Farcaster decoding covers Pro tier purchases only. Other Farcaster on-chain actions (FID registration, storage rent, key registrations, etc.) are not yet decoded as Farcaster-counterparty events. ## Setup 1. In rotki, add the Base address you used to pay for Farcaster Pro. 2. In rotki, open History and let the initial sync run. Pro tier purchases are decoded automatically. ## FAQ ### Does rotki decode FID registrations or storage rent? Not currently. The Farcaster decoder is scoped to Pro tier purchases on Base; other on-chain Farcaster actions appear as ordinary token movements. ### Does rotki read Farcaster activity from its own servers? No. rotki is a local application that talks directly to the Base 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. # Firebird Finance rotki decodes Firebird Finance aggregator swaps by re-tagging the spend and receive transfers around the Firebird router as a clean trade pair against the Firebird counterparty. ## Features - Swap-out and swap-in legs through the Firebird router are paired into a single trade event so the input and output of each swap are linked. - Each leg is tagged against the Firebird Finance counterparty, so aggregator activity is distinguishable from direct DEX trades in your history. - Decoded on every chain Firebird currently runs on: Ethereum, Arbitrum One, Optimism, Polygon PoS, and BNB Smart Chain. ## Setup 1. In rotki, add the addresses you use with Firebird on Ethereum, Arbitrum, Optimism, Polygon PoS, and/or BNB Smart Chain. 2. In rotki, open History and let the initial sync run. Firebird router swaps are decoded automatically into trade pairs. ## FAQ ### Are Firebird trades distinguishable from direct DEX swaps? Yes. Both legs of a Firebird swap are tagged against the Firebird Finance counterparty, so aggregator routing is visible in your history rather than being attributed to the underlying pools. ### Does rotki read Firebird trades from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Fluence 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. ## 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 1. In rotki, add the Ethereum address that holds FLT-DROP or claims FLT. 2. In rotki, open History and let the initial sync run. The FLT-DROP claim and the FLT-DROP-to-FLT conversion are decoded automatically. ## FAQ ### 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. # Frax 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. ## 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 1. In rotki, add the Ethereum address that claimed FPIS. 2. In 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. ## FAQ ### 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. # FTX FTX collapsed in November 2022 and rotki no longer ships an FTX API connector or a dedicated FTX CSV importer. FTX is still recognised as a historical location enum, so events can be tagged against it, but you need to bring those events into rotki yourself. ## Features - FTX is preserved as a historical location. History events you add manually (or import via rotki's generic CSV) can be tagged as FTX so they group with the rest of your FTX activity. ## Limitations - There is no FTX exchange connector; the FTX API is unreachable and rotki has removed it. - There is no dedicated FTX CSV importer. If you have FTX history saved from before the shutdown, format it into rotki's own generic CSV import (generic trades or generic events) or add the events manually. ## Setup 1. Recover or export your FTX history (from records saved before the shutdown, or via the bankruptcy claim portal). 2. Format those records into rotki's generic CSV import, or add the events manually as FTX-tagged history events. 3. In rotki, open Import Data and select the rotki generic trades or generic events importer. ## FAQ ### Can I add my FTX API key to rotki? No. The FTX API is unreachable. FTX appears only as a historical location. ### Does rotki have a direct FTX CSV importer? No. Format your FTX history into rotki's generic CSV import (generic trades or generic events), or add the events manually. # FTX US FTX US wound down in November 2022 alongside its parent. rotki no longer ships an FTX US API connector or a dedicated FTX US CSV importer; FTX US is still recognised as a historical location, so events can be tagged against it, but you need to bring those events into rotki yourself. ## Features - FTX US is preserved as a historical location. History events you add manually (or import via rotki's generic CSV) can be tagged as FTX US so they group with the rest of your FTX US activity. ## Limitations - There is no FTX US exchange connector; the FTX US API is unreachable and rotki has removed it. - There is no dedicated FTX US CSV importer. If you have FTX US history saved from before the shutdown, format it into rotki's own generic CSV import (generic trades or generic events) or add the events manually. ## Setup 1. Recover or export your FTX US history (from records saved before the shutdown, or via the bankruptcy claim portal). 2. Format those records into rotki's generic CSV import, or add the events manually as FTX-US-tagged history events. 3. In rotki, open Import Data and select the rotki generic trades or generic events importer. ## FAQ ### Can I add my FTX US API key to rotki? No. The FTX US API is unreachable. FTX US appears only as a historical location. ### Does rotki have a direct FTX US CSV importer? No. Format your FTX US history into rotki's generic CSV import (generic trades or generic events), or add the events manually. # Gearbox rotki decodes the passive side of Gearbox: pool deposits and withdrawals (with the matching pool/farming token recognised as the wrapped position) and Gearbox reward claims. ## Features - Pool deposits decoded as deposit-for-wrapped events with the matching pool LP or farming token tagged as the received wrapped position. - Pool withdrawals decoded as redeem-wrapped events, including pools where there is no separate farming token (just the pool token and the underlying asset). - Reward claims from Gearbox farming/staking contracts tagged as reward receive events against the Gearbox counterparty. - Decoded on every chain Gearbox currently runs on: Ethereum, Arbitrum One, and Optimism. - Gearbox balances (open passive pool and farming positions) queried on demand and included in your portfolio. ## Limitations - Gearbox decoding covers the passive side (pool deposits/withdrawals and rewards). Credit account / leveraged-credit-line interactions are not decoded as Gearbox-counterparty events. ## Setup 1. In rotki, add the addresses you use with Gearbox on Ethereum, Arbitrum One, and/or Optimism. 2. In rotki, open History and let the initial sync run. Gearbox pool deposits, withdrawals, and reward claims are decoded automatically. 3. If you've just opened a brand-new Gearbox position, you can refresh the Gearbox cache via Settings → Manage Data → Refresh protocol data (select Gearbox). ## FAQ ### Are Gearbox reward claims tagged? Yes. Reward claims via Gearbox farming/staking contracts are tagged as reward receives against the Gearbox counterparty on every supported chain. ### Are Gearbox credit accounts decoded? Not currently. Only the passive side (pool deposits, withdrawals, and rewards) is decoded as Gearbox-counterparty activity; credit-account interactions appear as ordinary token movements. ### Does rotki read Gearbox activity from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Gemini Connect Gemini to rotki to import spot trades, transfers, and balances - including Gemini Earn balances added on top of your spot wallet. rotki uses a read-only (Auditor) API key signed from your computer. ## Features - Spot trades imported from the mytrades endpoint as swap events with fees. - Deposits and withdrawals imported from the transfers endpoint as asset movements. - Spot balances and Gemini Earn balances combined into a single portfolio view. - API key permission is validated against the roles endpoint at setup: rotki refuses to proceed if the key isn't Auditor (read-only). ## Limitations - Margin/derivatives history is not imported (Gemini's older retail margin product is not exposed via the connector). ## Setup 1. In Gemini, open Settings → API → Create a new API key. 2. Set the scope to Auditor (read-only). Leave trading and withdrawal scopes disabled. 3. Save the key. Gemini shows the secret only once. 4. In rotki, open API Keys → Exchanges → Add Gemini and paste the key and secret. ## FAQ ### Are Gemini Earn balances included? Yes. rotki queries the balances/earn endpoint in addition to the spot balances endpoint and combines them, so your portfolio total reflects both. ### Where are my Gemini API keys sent? rotki is a local application: your Gemini API key is stored on your computer and used to sign each request, which goes directly from your machine to Gemini's API. No rotki-operated server ever sees the key or the request. ### Can rotki place trades on Gemini? No. rotki insists on an Auditor (read-only) key and refuses to proceed otherwise, so it has no permission to send trade or withdrawal calls. # GHO rotki decodes the GHO safety-module (stkGHO) staking flow on Ethereum: staking GHO, activating the unstaking cooldown, and redeeming stkGHO back to GHO. The paired events are linked into a stake/wrap-and-unstake/unwrap pair against the GHO counterparty. ## Features - Stake GHO: the GHO spend is tagged as a staking deposit and the matching stkGHO receive is tagged as a receive-wrapped event, both against the GHO counterparty. - Cooldown activation: starting the stkGHO unstaking cooldown is recorded as an informational event with the cooldown amount in the notes. - Unstake (redeem) stkGHO: the stkGHO spend is tagged as return-wrapped and the matching GHO receive as a staking-remove-asset event. ## Limitations - Only the stkGHO safety-module flow on Ethereum is decoded against the GHO counterparty. GHO borrow/repay flows on Aave are decoded by the Aave integration, not under the GHO counterparty. ## Setup 1. In rotki, add the Ethereum address you use with the GHO safety module. 2. In rotki, open History and let the initial sync run. Stake, cooldown, and unstake events are decoded automatically and paired. ## FAQ ### Are GHO borrow/repay events covered here? No - those are part of Aave's GHO facility and are decoded under the Aave counterparty by rotki's Aave integration. ### Does rotki read GHO 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. # Gitcoin rotki decodes Gitcoin Grants activity for both the legacy bulk-checkout flow and the Allo Protocol v2 rounds: donations you send (as a donate-subtype spend) and donations you receive (matched payouts, direct grants, retro funding) all flow into your history tagged against the Gitcoin counterparty. ## Features - Gitcoin v1 (bulk checkout) donations decoded on Ethereum, Arbitrum One, Optimism, and Polygon PoS. - Gitcoin v2 (Allo Protocol) donations, voted donations, and direct-grant payouts decoded on Ethereum and Polygon PoS. - Outgoing donations: matching token spends are re-tagged as donate-subtype events against the Gitcoin counterparty. - Incoming donations and matching payouts: token receives are tagged as donate-subtype receives so grantee income is identifiable in your history. - Allo v2 round registration, profile creation, and allocation/payout events are decoded so the lifecycle of your grant or round is captured. - Allo retro-funding strategy payouts (Optimism RetroPGF-style rounds) decoded as donate-subtype receives. ## Setup 1. In rotki, add the addresses you use with Gitcoin on Ethereum, Arbitrum One, Optimism, and/or Polygon PoS. 2. In rotki, open History and let the initial sync run. Donations, payouts, and Allo round events are decoded automatically. ## FAQ ### Are matched-funding payouts captured? Yes. Matching pool payouts to grantees in both v1 (bulk checkout) and v2 (Allo) rounds are decoded as donate-subtype receives against the Gitcoin counterparty. ### Are retro funding distributions captured? Yes. Allo v2 retro-funding-strategy payouts are decoded as donate-subtype receives against the Gitcoin counterparty. ### Does rotki read Gitcoin activity from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Giveth rotki decodes Giveth activity across the chains Giveth is deployed on: donations you send (split per recipient for multi-donations), donations you receive as a project, GIV locks into GIVpower rounds, and GIV reward claims from the distributor. ## Features - Outgoing donations through Giveth tagged as donate-subtype spends against the Giveth counterparty. Native-token multi-donations to several recipients in one transaction are split into per-recipient donation events instead of collapsing into one aggregate spend. - Incoming donations (when you're the project receiving) tagged as donate-subtype receives so grantee income is identifiable in your history. - GIV locking for GIVpower: the GIV lock is recorded against the Giveth counterparty with the number of rounds locked, and the matching POW receive is linked. - GIV reward claims from the Giveth distributor are tagged as reward-subtype receives against the Giveth counterparty. - Decoded on every chain Giveth currently runs on: Ethereum, Gnosis Chain, Polygon PoS, Arbitrum One, Optimism, and Base. ## Setup 1. In rotki, add the addresses you use with Giveth on Ethereum, Gnosis, Polygon PoS, Arbitrum, Optimism, and/or Base. 2. In rotki, open History and let the initial sync run. Donations, GIVpower locks, and GIV reward claims are decoded automatically. ## FAQ ### Are GIV rewards tracked as income? Yes. GIV reward claims from the Giveth distributor are tagged as reward-subtype receives against the Giveth counterparty. ### What happens with a multi-recipient native-token donation? rotki splits the single aggregate spend into one donation event per recipient, so each grantee shows up correctly in your history with their share. ### Does rotki read Giveth activity from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # GMX rotki decodes GMX v1 activity on Arbitrum One: swaps through the GMX vault, long/short position increases and decreases (with the GMX execution fee captured separately), GMX staking, and the staked GMX + GLP + esGMX balances that follow from it. ## Features - GMX vault swaps decoded as trade events (spend/receive) tagged against the GMX counterparty. - Long and short position increases and decreases decoded with the direction, asset, and collateral amount in the notes. - GMX execution fees on position changes are split out as a separate ETH spend tagged against GMX, so the fee doesn't get folded into the position size. - GMX staking: the GMX spend is tagged as a staking deposit and the bookkeeping receive (sGMX/sbGMX/sbfGMX) as a receive-wrapped event, both against the GMX counterparty. - Staked GMX balances are queried on demand; staked GLP (fsGLP), sbGMX, and esGMX (non-transferable) are recognised as tokens and surface in the portfolio. ## Limitations - GMX decoding currently covers GMX v1 on Arbitrum One only. GMX v2 (GM tokens, the new market system) and GMX on Avalanche are not yet decoded. ## Setup 1. In rotki, add the Arbitrum One address you use with GMX. 2. In rotki, open History and let the initial sync run. Swaps, position changes, execution fees, and staking events are decoded automatically; staked balances are queried on demand. ## FAQ ### Is GMX v2 supported? Not currently. The GMX decoder covers GMX v1 (vault swaps, perp positions, GMX/GLP staking) on Arbitrum One. GMX v2 GM tokens and markets are not yet decoded as GMX-counterparty events. ### Does rotki read GMX activity from its own servers? No. rotki is a local application that talks directly to the Arbitrum 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. # Gnosis Add your Gnosis Chain addresses to rotki and get balances, decoded transactions, and counterparty-tagged DeFi activity. rotki is a local application that talks directly to the Gnosis RPC endpoint you configure, with no rotki-operated server in the middle. ## Features - xDAI (native gas), GNO, and ERC-20 token balances per tracked address. - Transaction history decoded into readable events: transfers, swaps, deposits, withdrawals, protocol interactions. - Counterparty-tagged Gnosis Chain decoders include Aave, Aura Finance, Balancer, CoW Swap, CrossCurve, Curve, Giveth, Hop, Magpie, 1inch, Paraswap, Safe, Spark, Sushiswap, WXDAI, and Yearn. - Both official Ethereum ↔ Gnosis bridges decoded: xDai bridge (DAI ↔ xDAI) and Omnibridge (ERC-20). See the \[Gnosis bridges]\(/integrations/gnosis-chain) page for the cross-chain decoding details. - Gnosis Pay and Monerium activity on Gnosis Chain decoded against their own counterparties. ## Setup 1. In rotki, open Blockchain Balances → Gnosis → Add address. Paste your address, optionally with a label. 2. Optional: configure your preferred Gnosis RPC endpoint in Settings (a public default is provided). 3. In rotki, open History and let the initial sync run. Balances and decoded events populate automatically. ## FAQ ### Are Gnosis bridges decoded? Yes. Both the xDai bridge (DAI ↔ xDAI) and the Omnibridge (ERC-20) are decoded, with source and destination legs tagged as bridge events. See the \[Gnosis bridges]\(/integrations/gnosis-chain) page. ### Where do my Gnosis address queries go? rotki is a local application that talks directly to the Gnosis 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. ### Can I run rotki against my own Gnosis node? Yes. Point rotki at your own RPC endpoint in Settings. # Gnosis bridges rotki decodes both official Gnosis bridges between Ethereum and Gnosis Chain: the xDai bridge (for DAI ↔ xDAI, Gnosis Chain's native gas token) and the Omnibridge (for ERC-20s). Both legs of each transfer are tagged as bridge events so the same asset isn't double-counted as a spend and an unrelated receive. For Gnosis Chain balances and account activity see the \[Gnosis]\(/integrations/gnosis) blockchain integration. ## Features - xDai bridge: deposits of DAI on Ethereum and the matching xDAI receive on Gnosis Chain are tagged as bridge events against the bridge counterparty, so the cross-chain transfer reads as one operation rather than a DAI spend plus an xDAI receive. - Omnibridge: ERC-20 deposits on either side are tagged as bridge deposits, and the matching receives on the destination chain are tagged as bridge withdrawals. - Both bridges decoded symmetrically: rotki picks up the source side when run against the source chain and the destination side when run against the destination chain. ## Setup 1. In rotki, add the address you use with the bridges on both Ethereum and Gnosis Chain so each leg is captured. 2. In rotki, open History and let the initial sync run. xDai bridge and Omnibridge events are decoded automatically on whichever chain you queried. ## FAQ ### How is this different from the Gnosis integration? The Gnosis integration covers balances and account activity on Gnosis Chain itself. This page covers the two official bridges between Ethereum and Gnosis Chain (xDai bridge and Omnibridge). ### Will a Gnosis bridge transfer create a fake gain or loss? No. Both legs are tagged as bridge events, which rotki treats as non-taxable transfers rather than a spend/receive pair. ### Does rotki read bridge activity from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Gnosis Pay rotki decodes your Gnosis Pay activity on Gnosis Chain - card spends, refunds, cashback, and referral rewards - through your Safe. Connecting your Gnosis Pay account to enrich spends with merchant details is a Basic (or higher) feature. You choose which Gnosis RPC endpoint handles the queries. ## Features - Card spends decoded as payment events on the free tier. - Refunds from Gnosis Pay decoded. - Cashback (paid in GNO) and referral rewards recognised as income. - With a Basic subscription: connect your Gnosis Pay account to enrich each spend with the merchant name, location, and category. ## Setup 1. In rotki, add the Gnosis Chain Safe address you use for Gnosis Pay. Spends, refunds, and cashback are decoded automatically. 2. Optional (Basic or higher): connect your Gnosis Pay account so rotki can add merchant details to your spends. 3. Open History and let the initial sync run. ## FAQ ### Which Gnosis RPC does rotki use for Gnosis Pay activity? rotki is a local application that talks directly to the Gnosis 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. ### What works on the free tier and what needs a subscription? Decoding your Gnosis Pay spends, refunds, cashback, and referral rewards works on the free tier. Connecting your Gnosis Pay account to enrich spends with merchant name, location, and category requires a Basic (or higher) subscription. # Golem 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. ## 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 1. In rotki, add the Ethereum address that performed the migration (or holds GLM). 2. 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. ## FAQ ### 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. # Harvest Finance rotki decodes the GRAIN airdrop on Ethereum (the post-incident compensation distribution from the October 2020 Harvest exploit) as an airdrop receive against the Harvest Finance counterparty. ## Features - GRAIN airdrop claims from the Harvest Merkle distributor are tagged as airdrop-subtype receives against the Harvest Finance counterparty. ## Limitations - Harvest Finance-specific decoding is limited to the GRAIN compensation airdrop claim. Vault deposits/withdrawals and FARM/iFARM reward claims are not decoded as Harvest-counterparty events; their token movements appear as ordinary ERC-20 events. ## Setup 1. In rotki, add the Ethereum address that claimed GRAIN from the Harvest compensation distributor. 2. In rotki, open History and let the initial sync run. The GRAIN airdrop claim is decoded automatically. ## FAQ ### Are Harvest vault deposits and FARM rewards decoded? Not currently. Only the GRAIN compensation airdrop is tagged against the Harvest Finance counterparty; vault and reward token movements appear as ordinary ERC-20 events. ### Does rotki read Harvest 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. # Hedgey rotki decodes the Hedgey voting-token-lockups flow on Ethereum: when you create a voting vault for a lockup, when you (re)delegate the locked voting power, and when you redeem unlocked tokens out of a plan. Outstanding Hedgey lockup balances are also queried so they show up in your portfolio. ## Features - Voting Vault creation: when a lockup creates its voting vault, the matching delegate-changed event is decoded as a governance-subtype event against the Hedgey counterparty, with the plan ID in the notes. - Direct delegate calls to the voting-token-lockups contract are decoded as governance events, including the case where you re-delegate multiple plans in one call (the plan IDs are listed in the notes). - Plan redemption: when you redeem unlocked tokens, the token receive is tagged as a reward-subtype receive against the Hedgey counterparty, with the redeemed amount, token, and plan ID in the notes. - Outstanding Hedgey voting-token lockup balances are queried on demand and included in your portfolio. ## Limitations - Hedgey decoding currently covers the voting-token-lockups contract on Ethereum (vault creation, delegate changes, and plan redemption). Other Hedgey products (non-voting plans, OTC, token claims) are not decoded as Hedgey-counterparty events. ## Setup 1. In rotki, add the Ethereum address that owns the Hedgey plan. 2. In rotki, open History and let the initial sync run. Vault creation, delegate changes, and plan redemptions are decoded automatically; outstanding lockup balances are queried on demand. ## FAQ ### Are Hedgey vesting redemptions captured? Yes. PlanRedeemed events from the voting-token-lockups contract are decoded as reward-subtype receives against the Hedgey counterparty, with the plan ID recorded. ### Does rotki read Hedgey 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. # Hop Protocol rotki decodes the full Hop Protocol lifecycle across Ethereum and the L2s Hop runs on: bridge sends and receives (with bridge fees split out), AMM swaps via Hop pools, liquidity adds/removes, staking and unstaking of LP positions, ongoing HOP reward claims, and Merkle HOP airdrop claims. ## Features - Bridge sends are tagged as bridge deposits, with the bonder/relayer fee split out as a separate fee-subtype event so the bridged amount stays clean. - Bridge receives on the destination chain (including L1→L2 transfers and bonded withdrawals) are tagged as bridge withdrawals against the Hop counterparty. - Hop AMM swaps between the canonical asset and its hToken are decoded as trade events. - Add-liquidity and remove-liquidity calls against Hop pools are decoded, with the LP token cached so the pool position is recognised. - Staking, unstaking, and ongoing reward claims from Hop reward contracts are decoded; reward-paid receives are tagged as reward-subtype events. - Merkle HOP airdrop claims are decoded as reward-subtype receives against the Hop counterparty. - Decoded on every chain Hop currently runs on: Ethereum, Arbitrum One, Optimism, Polygon PoS, Base, and Gnosis Chain. ## Setup 1. In rotki, add the addresses you use with Hop on the relevant chains so both sides of each bridge transfer are captured. 2. In rotki, open History and let the initial sync run. Bridges, AMM swaps, LP adds/removes, staking, reward claims, and HOP airdrop claims are decoded automatically. ## FAQ ### Will a Hop bridge transfer create a fake gain or loss? No. Both legs are tagged as bridge events (with the relayer fee split out), which rotki treats as non-taxable transfers rather than a spend/receive pair. ### Are Hop LP and reward claims captured? Yes. Liquidity adds/removes, stake/unstake events, ongoing reward claims, and the Merkle HOP airdrop are all decoded against the Hop counterparty. ### Does rotki read Hop activity from its own servers? No. rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # HTX Connect HTX (formerly Huobi) to rotki to import spot trades, deposits, withdrawals, and balances. rotki uses a read-only API key signed from your machine. ## Features - Spot trades imported as swap events from the HTX match-results endpoint. - Deposits and withdrawals imported from the deposit-withdraw endpoint as asset movements. - Balance reconciliation against your HTX spot, OTC, and point account types. ## Limitations - HTX's spot trade-history endpoint exposes roughly the last 120 days of trades; older history is not retrievable via the connector. If you need older history, fall back to manual entry or rotki's generic CSV import. - Margin/derivatives history is not imported. ## Setup 1. In HTX, open Account → API Management → Create. 2. Set permissions to Read Only. Leave trading and withdrawal scopes off. 3. Optionally whitelist your IP for additional safety. 4. In rotki, open API Keys → Exchanges → Add HTX and paste the key and secret. ## FAQ ### Is HTX the same as Huobi? Yes. HTX is Huobi's rebranded name (renamed in 2023). The API and account structure are unchanged. ### Why is my older trade history missing? HTX's spot trade-history endpoint only returns roughly the last 120 days. For older history, supplement with rotki's generic CSV import or manual entry. ### Where are my HTX API keys sent? rotki is a local application: your HTX API key is stored on your computer and used to sign each request, which goes directly from your machine to HTX's API. No rotki-operated server ever sees the key or the request. ### Can rotki trade or withdraw on HTX? No. rotki only requests Read Only scopes and never sends trade or withdrawal calls. # Hyperliquid rotki tracks Hyperliquid (HyperEVM) addresses as an EVM chain: HYPE and ERC-20 balances per address, transaction decoding, and counterparty-tagged DeFi events for the protocols rotki ships with on Hyperliquid. ## Features - HYPE (native gas) and ERC-20 token balances per tracked Hyperliquid address. - Transaction history decoded into readable events using the Hyperliquid RPC you configure. - Counterparty-tagged decoders on Hyperliquid include Curve, Sushiswap, KyberSwap, Morpho, Morpho Blue, WOOFi, and Circle CCTP. ## Limitations - Hyperliquid's perpetuals DEX and the HYPE genesis distribution are not currently decoded as Hyperliquid-counterparty events. Token movements appear as ordinary ERC-20 events. ## Setup 1. In rotki, open Blockchain Balances → Hyperliquid → Add address. 2. Optional: configure your preferred Hyperliquid RPC endpoint in Settings. 3. In rotki, open History and let the initial sync run. Balances and decoded events populate automatically. ## FAQ ### Are Hyperliquid perpetual positions tracked? Not as Hyperliquid-counterparty events. The current Hyperliquid integration covers on-chain HyperEVM activity (balances and decoded DeFi events). The off-chain perpetual order book is not pulled into rotki. ### Was the HYPE genesis distribution decoded? Not as a Hyperliquid-counterparty event. The HYPE you received appears as an ordinary token receive on the address. ### Where do my Hyperliquid address queries go? rotki is a local application that talks directly to the Hyperliquid 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. # ICONOMI Connect ICONOMI to rotki to import your strategy trades and balances. rotki uses a read-only API key signed from your machine. ## Features - Strategy buys and sells imported as swap events from your ICONOMI activity. - Balance reconciliation across your ICONOMI strategies and free assets. ## Limitations - Only buy and sell activity is imported as trades; plain deposits and withdrawals are not retrieved. - Margin and derivatives history is not imported. ## Setup 1. In ICONOMI, open Settings → API Keys → Generate new key. 2. Set the scope to read-only and leave trade-creation permissions off. 3. In rotki, open API Keys → Exchanges → Add ICONOMI and paste the key and secret. ## FAQ ### Where are my ICONOMI API keys sent? rotki is a local application: your ICONOMI API key is stored on your computer and used to sign each request, which goes directly from your machine to ICONOMI's API. No rotki-operated server ever sees the key or the request. ### Can rotki place trades on ICONOMI? No. rotki only requests read-only scopes and never sends trade calls. # Independent Reserve Connect Independent Reserve, Australia's longest-running regulated crypto exchange, to rotki to import trades, deposits, withdrawals, and balances. rotki uses a read-only API key signed from your machine. ## Features - Spot trades imported as swap events with matched spend and receive sides. - Deposits and withdrawals imported as asset movements. - Balance reconciliation across your Independent Reserve accounts. ## Limitations - Margin and derivatives history is not imported. ## Setup 1. In Independent Reserve, open Settings → API Keys → Create new key. 2. Grant read-only scopes only and leave trade and withdrawal permissions off. 3. In rotki, open API Keys → Exchanges → Add Independent Reserve and paste the key and secret. ## FAQ ### Where are my Independent Reserve API keys sent? rotki is a local application: your Independent Reserve API key is stored on your computer and used to sign each request, which goes directly from your machine to Independent Reserve's API. No rotki-operated server ever sees the key or the request. ### Can rotki place trades or withdraw funds? No. rotki only requests read-only scopes and never sends trade or withdrawal calls. # Jito rotki recognises the Jito tips you pay on Solana and labels them as fee events, alongside the rest of your portfolio. Processing is local; you choose which Solana RPC endpoint handles the queries. ## Features - Jito tip payments on Solana recognised as fee events with the Jito counterparty. ## Limitations - Only Jito tip payments are decoded. JitoSOL staking and restaking balances are not tracked separately. ## Setup 1. In rotki, add your Solana address. 2. Open History and let the initial sync run. Jito tips in your transactions are labelled automatically. ## FAQ ### Which Solana RPC does rotki use for Jito activity? rotki is a local application that talks directly to the Solana 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. # Juicebox rotki decodes the payments you make to Juicebox projects on Ethereum and recognises the reward NFT you receive in return. Processing is local; you choose which Ethereum RPC endpoint handles the queries. ## Features - Payments to Juicebox projects decoded as outgoing ETH events with the Juicebox counterparty. - Reward NFTs received for paying a Juicebox project recognised. ## Limitations - Only payments and their reward NFTs are decoded; redemptions and reserved-token distributions are not yet covered. ## Setup 1. In rotki, add your Ethereum address. 2. Open History and let the initial sync run. Juicebox payments are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for Juicebox activity? 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. # Jupiter rotki decodes Jupiter aggregator swaps and Jupiter Lend activity on Solana. Processing is local; you choose which Solana RPC endpoint handles the queries. ## Features - Jupiter aggregator swaps, including RFQ fills, decoded as swap events on Solana. - Jupiter Lend deposits, withdrawals, borrows, and repays decoded as events. - Jito tips paid in your Jupiter transactions recognised as fee events. ## Setup 1. In rotki, add your Solana address. 2. Open History and let the initial sync run. Jupiter swaps and Lend activity are decoded automatically. ## FAQ ### Which Solana RPC does rotki use for Jupiter activity? rotki is a local application that talks directly to the Solana 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. # Kraken Connect Kraken to rotki to import spot trades, ledger entries, staking rewards, margin events, and balances. rotki uses a read-only API key signed from your machine. ## Features - Spot trades imported as swap events, including instant-buy and convert orders. - Ledger entries (deposits, withdrawals, fees, and transfers) imported as asset movements and events. - Staking rewards imported, including ETH2 and Kraken's staked-asset products. - Margin events (margin, rollover, and settlement ledger entries) recognised. - Kraken Futures balances queried via a separate Futures API key. - KFEE valued at $0.01 when used to pay trading fees. ## Limitations - Some Kraken ledger entry types are recognised as informational events rather than fully accounted. - Kraken Futures history is not imported; only futures balances are queried. - rotki has no Kraken-specific CSV importer. To backfill older history without the API, format it into rotki's own generic CSV import (generic trades or generic events). - Kraken's API rate limits depend on your account tier (Starter / Intermediate / Pro); higher tiers retrieve history faster. ## Setup 1. In Kraken Pro, open Settings → API and click "Create API key". 2. Under permissions, enable only "Query Funds" and "Query Ledger Entries". Leave trading and withdrawal permissions off. 3. Save the key and copy the API key and private key. 4. In rotki, open API Keys → Exchanges → Add Kraken, paste the key and secret, and pick your account tier. 5. Optional: to track Kraken Futures balances, generate a separate Futures API key from futures.kraken.com and add it under the same exchange entry. ## FAQ ### Does rotki support Kraken Futures? rotki can query your Kraken Futures balances. Generate a separate Futures API key at futures.kraken.com and add it alongside your spot key. Futures trade history is not imported. ### Will rotki ever be able to trade or withdraw from my Kraken account? No. rotki only asks for the "Query Funds" and "Query Ledger Entries" permissions. Even if you grant more, rotki never sends trade or withdrawal calls. ### Where are my Kraken API keys sent? rotki is a local application: your Kraken API key is stored on your computer and used to sign each request, which goes directly from your machine to Kraken's API. No rotki-operated server ever sees the key or the request. ### Can I import Kraken CSV exports instead of using an API key? rotki does not have a Kraken-specific CSV importer. Connect a read-only API key, or backfill older history using rotki's own generic CSV import (the generic trades and generic events formats). # KuCoin Connect your KuCoin account to rotki to import spot trades (current and v1 legacy formats), deposits, withdrawals, and balances. rotki uses a read-only API key signed from your machine. ## Features - Spot trades imported as swap events; both the current API responses and the older v1 trade format are handled. - Deposits and withdrawals imported as asset movements, including paginated historical entries. - CSV import of KuCoin trade exports for periods before your API key existed. ## Limitations - KuCoin margin trades are not imported; only spot trades, deposits, and withdrawals are retrieved. ## Setup 1. In KuCoin, open Account → API Management → Create API. 2. Set permission to "General" (read-only). Leave "Trade" and "Transfer" off. 3. Set an API passphrase when prompted - you'll need it in rotki. 4. Whitelist your IP if you want extra safety. 5. In rotki, open API Keys → Exchanges → Add KuCoin and paste the key, secret, and passphrase. ## FAQ ### Where are my KuCoin API keys sent? rotki is a local application: your KuCoin API key is stored on your computer and used to sign each request, which goes directly from your machine to KuCoin's API. No rotki-operated server ever sees the key or the request. ### What does the API passphrase do? KuCoin requires a user-set passphrase alongside the key and secret as an additional signing factor. rotki needs all three to authenticate API calls. ### Can rotki withdraw from my KuCoin account? No. rotki only requests the General (read-only) scope and never sends withdrawal or transfer calls. ### Are my old v1 trades imported? Yes. rotki detects KuCoin v1 trade entries and imports them with the correct timestamp and pair conversion. # Kusama Add your Kusama addresses to rotki to track your KSM balances. rotki queries the Kusama RPC endpoint you configure. ## Features - KSM address balances (free and reserved) read directly from the Substrate node you connect to. - Configurable Kusama RPC endpoint: use a public node or your own. ## Setup 1. In rotki, open Blockchain & Accounts → Kusama → Add address. 2. Paste your Kusama address. 3. Optional: in Settings → RPC, configure your preferred Kusama endpoint. ## FAQ ### Which Kusama RPC does rotki use? rotki is a local application that talks directly to the Kusama RPC endpoint you configure - a public node or your own. The query goes from your computer to that endpoint without passing through any rotki-operated server. ### What balances does rotki track for Kusama? rotki reads your native KSM balance (free and reserved) from the Substrate node you connect to. # KyberSwap rotki decodes KyberSwap aggregator trades, including swaps with refunds, where the refund is deducted from the original swap amount for a clean result. You choose which RPC endpoint handles the queries. ## Features - KyberSwap aggregator trades decoded as swap events. - Swaps with a refund are netted, so the refund is deducted from the original swap amount. - Decoded on Ethereum, Arbitrum, Optimism, Base, Polygon, Scroll, Monad, and Hyperliquid. ## Setup 1. In rotki, add your address under a chain where you've used KyberSwap. 2. Open History and let the initial sync run. KyberSwap trades are decoded automatically. ## FAQ ### Which RPC does rotki use for KyberSwap activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. ### Are refunds handled? Yes. When a KyberSwap trade returns a refund, rotki deducts it from the original swap amount so your cost basis stays accurate. # Lido rotki decodes Lido staking (ETH submitted for stETH) and stETH/wstETH wrapping, tracks your stETH and wstETH balances, and reads Lido CSM (Community Staking Module) node-operator bond balances. You choose which Ethereum RPC endpoint handles the queries. ## Features - ETH submitted to Lido decoded as a staking deposit, with the stETH received recognised. - stETH to wstETH wrapping and unwrapping decoded. - stETH and wstETH balances tracked alongside the rest of your portfolio. - Lido CSM node-operator bond balances read from the CSM accounting contract. ## Setup 1. In rotki, add your Ethereum address. stETH/wstETH balances and Lido staking events are detected automatically. 2. Open History and let the initial sync run. Lido events are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for Lido activity? 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. ### Are Lido CSM bonds tracked? Yes. rotki reads your node-operator bond balance from the Lido CSM accounting contract. ### How are staking rewards reflected? Lido rewards accrue through stETH rebases, so they are reflected in your stETH balance over time and carried into your balance history. # Liquity rotki tracks Liquity v1 troves and Liquity v2 transactions, the Stability Pool, LQTY staking, and DSProxy-managed troves (including ones created via DefiSaver). Debts appear as liabilities in your dashboard so your net worth stays accurate. ## Features - Trove collateral, debt, borrowing fees, and liquidation events decoded for v1. - Liquity v2 transactions decoded, including proxy detection and proxy-deployment transactions. - Stability Pool LUSD deposits, withdrawals, and LQTY rewards tracked. - LQTY staking deposits and rewards (including frontend fees) decoded. - DSProxy-managed troves and their events recognised, including those created via DefiSaver. - Profit tracking for your Liquity staking and Stability Pool positions. - Total collateral ratio shown in the Trove section. - Debts shown as liabilities in dashboard balances. ## Setup 1. In rotki, add your Ethereum address. Liquity positions are detected automatically. 2. DSProxy-managed troves are picked up from the owner address you track. 3. Open History and let the initial sync run. Liquity events are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for Liquity activity? 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. ### Does rotki support both Liquity v1 and v2? Yes. v1 troves, the Stability Pool, and LQTY staking are decoded, and Liquity v2 transactions including proxy interactions are handled. ### What if I created my trove via DefiSaver? rotki detects DSProxy-managed troves automatically and decodes their events, including DefiSaver-created ones. # LlamaZip rotki decodes LlamaZip swaps, DefiLlama's calldata-optimised swap router built for L2 cost savings. You choose which RPC endpoint handles the queries. ## Features - LlamaZip swaps decoded as swap events. - Decoded on Arbitrum and Optimism, where LlamaZip is deployed. ## Setup 1. In rotki, add your Arbitrum or Optimism address. 2. Open History and let the initial sync run. LlamaZip swaps are decoded automatically. ## FAQ ### Which RPC does rotki use for LlamaZip activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Locked GNO rotki decodes the GNO you deposit into the Ethereum locking contract used to run Gnosis Chain validators, plus the GNO you receive back when you unlock. You choose which Ethereum RPC endpoint handles the queries. ## Features - GNO deposits into the locking contract decoded as protocol events. - GNO returned from the locking contract (unlock) recognised. ## Setup 1. In rotki, add your Ethereum address (the locking contract is on Ethereum). 2. Open History and let the initial sync run. Locked GNO events are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for Locked GNO activity? 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. # Magpie rotki decodes Magpie aggregator trades across several EVM chains. You choose which RPC endpoint handles the queries. ## Features - Magpie aggregator swaps decoded as swap events. - Decoded on Ethereum, Arbitrum, Optimism, Base, Polygon, Gnosis, BNB Smart Chain, and Scroll. ## Setup 1. In rotki, add your address under a chain where you've used Magpie. 2. Open History and let the initial sync run. Magpie swaps are decoded automatically. ## FAQ ### Which RPC does rotki use for Magpie activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # MakerDAO rotki decodes MakerDAO vaults (CDPs), DAI Savings Rate (DSR) deposits, and the MKR-to-SKY and DAI-to-USDS migrations into the Sky protocol. You choose which Ethereum RPC endpoint handles the queries. ## Features - Vault (CDP) collateral deposits, withdrawals, and debt payback decoded as protocol events. - Collateral types read generically from each vault's ilk, so new collaterals are picked up as long as the vault ABI is unchanged. - DAI Savings Rate (DSR) deposits and withdrawals tracked. - Vault collateralization ratio computed from your locked collateral and outstanding debt. - Sky migration transactions (MKR to SKY, DAI to USDS) decoded under the Sky counterparty. - Vault debt shown as a liability in dashboard balances. ## Setup 1. In rotki, add your Ethereum address. MakerDAO positions are detected automatically. 2. Optional: refresh MakerDAO data under Settings → Manage Data → Refresh protocol data. 3. Open History and let the initial sync run. MakerDAO events are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for MakerDAO activity? 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. ### Is the Sky migration supported? Yes. MKR-to-SKY and DAI-to-USDS migrations are decoded so your balances reconcile across the rebrand. ### Are new collateral types tracked? Yes. rotki reads the collateral type from each vault's ilk, so new collaterals are picked up as long as the vault ABI is unchanged. # Merkl rotki decodes the reward claims you make from the Merkl distributor, including rewards routed through Merkl by other protocols such as Morpho. You choose which RPC endpoint handles the queries. ## Features - Merkl reward claims decoded as income events with the Merkl counterparty. - Because any claim from the Merkl distributor is decoded, rewards routed through Merkl by other protocols (for example Morpho) are captured too. - Works on rotki's supported EVM chains where the Merkl distributor is used. ## Setup 1. In rotki, add the address(es) you use to claim Merkl rewards. 2. Open History and let the initial sync run. Merkl claims are decoded automatically. ## FAQ ### Which RPC does rotki use for Merkl activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. ### Are rewards from third-party protocols (for example Morpho) distributed via Merkl captured? Yes. rotki decodes any claim from the Merkl distributor, so rewards routed through Merkl are recognised as Merkl reward income. # MetaMask Swaps rotki decodes swaps executed through MetaMask's built-in swap feature. You choose which RPC endpoint handles the queries. ## Features - MetaMask in-wallet swaps decoded as swap events, with the MetaMask swap fee recognised. - Decoded on Ethereum, Arbitrum, Optimism, Polygon, and BNB Smart Chain. ## Setup 1. In rotki, add the EVM address you use in MetaMask. 2. Open History and let the initial sync run. MetaMask swaps are decoded automatically. ## FAQ ### Which RPC does rotki use for MetaMask swap activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # MintClub rotki decodes the token claims you make from MintClub distributions on Base. You choose which Base RPC endpoint handles the queries. ## Features - MintClub distribution claims decoded as income events with the MintClub counterparty. ## Limitations - Only MintClub distribution claims are decoded, on Base. ## Setup 1. In rotki, add your Base address. 2. Open History and let the initial sync run. MintClub claims are decoded automatically. ## FAQ ### Which Base RPC does rotki use for MintClub activity? rotki is a local application that talks directly to the Base 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. # Monad Add your Monad addresses to rotki to track balances and decode on-chain activity. You choose which Monad RPC endpoint handles the queries. ## Features - Native and token balances tracked for your Monad addresses. - Monad transactions retrieved and decoded into readable history events. - Protocol decoders on Monad: Uniswap, Curve, KyberSwap, Morpho, WooFi, 0x, Circle CCTP, and WMON wrapping. ## Setup 1. In rotki, open Blockchain & Accounts → Monad → Add address. 2. Open History and let the initial sync run. Monad transactions are decoded automatically. ## FAQ ### Which Monad RPC does rotki use? rotki is a local application that talks directly to the Monad 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. ### Which protocols are decoded on Monad? rotki decodes Uniswap, Curve, KyberSwap, Morpho, WooFi, 0x, Circle CCTP, and WMON wrapping on Monad, in addition to native and token transfers. # Monerium rotki decodes the mints and burns of Monerium's regulated e-money tokens (EURe, GBPe, USDe, ISKe) on the chains where you hold them, and tracks their balances. Connecting your Monerium account enriches those events with bank-transfer, bridge, memo, and IBAN details and is a Basic (or higher) feature. You choose which RPC endpoint handles the queries. ## Features - Monerium mints (issuance) and burns (redemption) of EURe, GBPe, USDe, and ISKe decoded as protocol events on the free tier. - Monerium token balances tracked like any other token. - Decoded on Ethereum, Gnosis, Polygon, Arbitrum, Base, and Scroll. - With a Basic subscription: connect your Monerium account to match your orders and enrich events with issue/redeem/bridge labels, the counterpart IBAN, and the order memo. ## Setup 1. In rotki, add your address under a chain where you hold Monerium tokens (Ethereum, Gnosis, Polygon, Arbitrum, Base, or Scroll). Mints and burns are decoded automatically. 2. Optional (Basic or higher): connect your Monerium account so rotki can match orders and enrich the on-chain events. 3. Open History and let the initial sync run. ## FAQ ### Which RPC does rotki use for Monerium activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. ### What works on the free tier and what needs a subscription? Decoding Monerium mints and burns and tracking your token balances work on the free tier. Connecting your Monerium account to match orders and enrich events with bank-transfer, bridge, memo, and IBAN details requires a Basic (or higher) subscription. # Morpho rotki decodes Morpho Blue lending positions, Morpho vault (MetaMorpho) positions, and Merkl-distributed Morpho rewards. Bundled Morpho transactions that perform several actions in one call are unpacked into separate events. ## Features - Morpho Blue deposits, withdrawals, and borrow liabilities decoded. - Morpho vault (MetaMorpho) positions tracked, with vault tokens resolved to their underlying assets. - Bundled transactions that perform multiple actions in one call are decoded as separate events. - Morpho rewards distributed via Merkl decoded as income events. - Decoded on Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Smart Chain, Scroll, Hyperliquid, and Monad. ## Setup 1. In rotki, add your address under a chain where your Morpho position lives. Positions are detected automatically. 2. Open History and let the initial sync run. Morpho events are decoded automatically. ## FAQ ### Which RPC does rotki use for Morpho activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. ### Does rotki support both Morpho Blue and Morpho vaults? Yes. Morpho Blue lending positions and Morpho vault (MetaMorpho) positions are both tracked, including Merkl rewards routed to either. ### Are bundled Morpho transactions decoded? Yes. Transactions that perform multiple actions in one call are unpacked into their individual events. # Nexo Import your Nexo history into rotki via CSV: interest accruals, deposits, withdrawals, conversions, and loan events. CSV files are processed entirely on your computer. ## Features - CSV import of Nexo's transaction history export. - Interest, cashback, dividend, and bonus entries recognised as income events for tax reporting. - Deposits, withdrawals, and conversions imported. - Loan repayments and liquidations recognised where present in the CSV. ## Limitations - Nexo is integrated via CSV import only; there is no real-time API integration. ## Setup 1. In Nexo, export your transaction history as CSV. 2. In rotki, open Import Data and select your Nexo file. ## FAQ ### Is Nexo interest income included in my tax report? Yes. rotki treats Nexo interest entries as income events and includes them in PnL and tax exports. ### Does my Nexo data leave my machine? No. CSV imports are parsed entirely on your computer; the file never leaves your machine. ### Why is Nexo not available via API? Nexo does not offer a stable public account API, so CSV import is the supported path. # Octant rotki decodes Octant GLM locking and unlocking, and your Octant epoch reward claims. You choose which Ethereum RPC endpoint handles the queries. ## Features - GLM locking and unlocking in Octant decoded as protocol events. - Octant epoch reward claims (paid in ETH) decoded as income. ## Setup 1. In rotki, add your Ethereum address. 2. Open History and let the initial sync run. Octant events are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for Octant activity? 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. ### Are Octant rewards taxable income? rotki decodes your epoch reward claims as income events. Talk to a tax professional about your specific jurisdiction. # Odos rotki decodes Odos aggregator trades across several EVM chains. You choose which RPC endpoint handles the queries. ## Features - Odos aggregator swaps decoded as swap events. - Decoded on Ethereum, Arbitrum, Optimism, Base, Polygon, BNB Smart Chain, and Scroll. ## Setup 1. In rotki, add your address under a chain where you've used Odos. 2. Open History and let the initial sync run. Odos swaps are decoded automatically. ## FAQ ### Which RPC does rotki use for Odos activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # OKX Connect OKX to rotki to import spot trades, conversions, deposits, withdrawals, and balances. rotki uses a read-only API key signed from your machine. ## Features - Spot trades imported as swap events from your OKX account. - OKX conversions imported as trades. - Deposits and withdrawals imported as asset movements. - Balance reconciliation across your OKX account. ## Limitations - Margin and derivatives history is not imported. ## Setup 1. In OKX, open Account → API → Create V5 API Key. 2. Set permissions to "Read" only. Leave trade and withdraw permissions disabled. 3. Set an API passphrase - you'll need it in rotki. 4. Whitelist your IP for additional safety. 5. In rotki, open API Keys → Exchanges → Add OKX and paste the key, secret, and passphrase. ## FAQ ### Why does OKX need a passphrase? OKX uses a user-set passphrase as part of its API signing. rotki needs the API key, secret, and passphrase to authenticate. ### Where are my OKX API keys sent? rotki is a local application: your OKX API key is stored on your computer and used to sign each request, which goes directly from your machine to OKX's API. No rotki-operated server ever sees the key or the request. ### Can rotki trade or withdraw on OKX? No. rotki only requests the Read scope and never sends trading or withdrawal calls. # Omni rotki decodes your Omni genesis airdrop claim and OMNI staking on Ethereum. You choose which Ethereum RPC endpoint handles the queries. ## Features - Omni genesis airdrop claims decoded, including the ETH paid as a claim fee. - OMNI staking decoded as protocol events. ## Setup 1. In rotki, add your Ethereum address. 2. Open History and let the initial sync run. Omni events are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for Omni activity? 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. # OpenOcean rotki decodes OpenOcean aggregator trades on rotki's supported EVM chains. You choose which RPC endpoint handles the queries. ## Features - OpenOcean aggregator swaps decoded as swap events with the OpenOcean counterparty. - Works on rotki's supported EVM chains where the OpenOcean exchange contract is used. ## Setup 1. In rotki, add your address under a chain where you've used OpenOcean. 2. Open History and let the initial sync run. OpenOcean swaps are decoded automatically. ## FAQ ### Which RPC does rotki use for OpenOcean activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Optimism Add your Optimism addresses to rotki to track OP and token balances, decoded transaction history, and DeFi activity. You choose which Optimism RPC endpoint handles the queries. ## Features - Native, ETH, and ERC-20 token balances tracked for your Optimism addresses. - Transactions decoded into readable events: swaps, transfers, bridges, and protocol interactions. - DeFi protocols decoded on Optimism, including Velodrome, Aave, Curve, Balancer, Uniswap, and more. - Superchain bridge deposits and withdrawals linked across Ethereum and Optimism. - Reuse an Ethereum address on Optimism in rotki. ## Setup 1. In rotki, open Blockchain & Accounts → Optimism → Add address. 2. Paste your address (you can reuse the same one you use on Ethereum). 3. Optional: in Settings → RPC, set your preferred Optimism RPC endpoint. ## FAQ ### Which Optimism RPC does rotki use? rotki is a local application that talks directly to the Optimism 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. ### Can I track the same address on Ethereum and Optimism? Yes. Add it under both chains; rotki keeps balances and history separate per chain but lets you view a unified portfolio. ### Are L1-to-L2 bridge transactions decoded? Yes. rotki links the L1 deposit/withdrawal events with their counterpart on Optimism so your transfers are not double-counted. # Paladin rotki decodes the reward claims you make from Paladin Quest veCRV bribe markets. You choose which Ethereum RPC endpoint handles the queries. ## Features - Paladin Quest veCRV bribe reward claims decoded as income events, labelled with the bribe period. ## Setup 1. In rotki, add your Ethereum address. 2. Open History and let the initial sync run. Paladin Quest claims are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for Paladin activity? 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. # ParaSwap rotki decodes ParaSwap aggregator trades across several EVM chains. You choose which RPC endpoint handles the queries. ## Features - ParaSwap aggregator swaps decoded as swap events. - Decoded on Ethereum, Arbitrum, Optimism, Base, Polygon, Gnosis, and BNB Smart Chain. ## Setup 1. In rotki, add your address under a chain where you've used ParaSwap. 2. Open History and let the initial sync run. ParaSwap swaps are decoded automatically. ## FAQ ### Which RPC does rotki use for ParaSwap activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Pendle Finance rotki decodes Pendle swaps into and out of Principal Tokens (PT) and Yield Tokens (YT), tracks your Pendle balances, and decodes vePendle locks and reward claims. You choose which RPC endpoint handles the queries. ## Features - Swaps into and out of Principal Tokens (PT) and Yield Tokens (YT) decoded as swap events. - Pendle position balances (PT, YT, and LP) queried and included in your portfolio. - vePendle locks decoded, labelled with the PENDLE amount and the unlock date. - Reward claims decoded, including transactions that claim several rewards at once. - Decoded on Ethereum, Arbitrum, Optimism, Base, BNB Smart Chain, and Hyperliquid (vePendle locking is on Ethereum). ## Setup 1. In rotki, add your address under a chain where you use Pendle. Positions are detected automatically. 2. Open History and let the initial sync run. Pendle events are decoded automatically. ## FAQ ### Which RPC does rotki use for Pendle activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. ### Are PT and YT positions priced separately? Yes. Principal Tokens and Yield Tokens are tracked with their own balances and prices. ### Is vePendle tracked? Yes. vePendle locks are decoded and your locked PENDLE appears in your portfolio. # Pickle Finance rotki decodes Pickle Finance jar deposits and withdrawals, and recognises the Cornichon hack-compensation airdrop claim. You choose which Ethereum RPC endpoint handles the queries. ## Features - Pickle jar deposits and withdrawals decoded as protocol events. - Cornichon (CORN) hack-compensation airdrop claim recognised. ## Setup 1. In rotki, add your Ethereum address. Pickle activity is detected automatically. 2. Open History and let the initial sync run. Pickle events are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for Pickle activity? 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. # Polkadot Add your Polkadot addresses to rotki to track your DOT balances. rotki queries the Polkadot RPC endpoint you configure. ## Features - DOT address balances (free and reserved) read directly from the Substrate node you connect to. - Configurable Polkadot RPC endpoint: use a public node or your own. ## Setup 1. In rotki, open Blockchain & Accounts → Polkadot → Add address. 2. Paste your Polkadot address. 3. Optional: in Settings → RPC, configure your preferred Polkadot endpoint. ## FAQ ### Which Polkadot RPC does rotki use? rotki is a local application that talks directly to the Polkadot RPC endpoint you configure - a public node or your own. The query goes from your computer to that endpoint without passing through any rotki-operated server. ### What balances does rotki track for Polkadot? rotki reads your native DOT balance (free and reserved) from the Substrate node you connect to. # Poloniex Connect Poloniex to rotki to import spot trades, deposits, withdrawals, and balances. rotki uses a read-only API key signed from your machine. ## Features - Spot trades imported as swap events with matched spend and receive sides. - Deposits and withdrawals imported as asset movements. - Balance reconciliation across your Poloniex account. ## Limitations - Margin and derivatives history is not imported. ## Setup 1. In Poloniex, open Account → API Keys → Create new key. 2. Grant read-only scopes and leave trade and withdrawal permissions off. 3. Whitelist your IP if available. 4. In rotki, open API Keys → Exchanges → Add Poloniex and paste the key and secret. ## FAQ ### Where are my Poloniex API keys sent? rotki is a local application: your Poloniex API key is stored on your computer and used to sign each request, which goes directly from your machine to Poloniex's API. No rotki-operated server ever sees the key or the request. ### Can rotki trade or withdraw on Poloniex? No. rotki only requests read-only scopes and never sends trade or withdrawal calls. # Polygon Bridge rotki decodes Polygon PoS bridge deposits and withdrawals between Ethereum and Polygon, and the MATIC-to-POL token migration. Source and destination legs are linked so bridged assets are not double-counted. For Polygon PoS chain balances see the \[Polygon PoS]\(/integrations/polygon-pos) integration. You choose which RPC endpoint handles the queries. ## Features - Polygon PoS bridge deposits and withdrawals decoded as protocol events, including the Exit NFT used to complete a withdrawal. - Source-chain (Ethereum) and destination-chain (Polygon) legs linked to avoid double-counting. - MATIC-to-POL token migration decoded. ## Setup 1. In rotki, add your address on both Ethereum and Polygon PoS. 2. Open History and let the initial sync run. Bridge and migration events are decoded automatically. ## FAQ ### How is this different from the Polygon PoS integration? The Polygon PoS integration tracks balances and activity on the Polygon chain itself. This page covers the Ethereum-side Polygon mechanisms: the PoS bridge transfers and the MATIC-to-POL migration. ### Which RPC does rotki use for these events? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Polygon PoS Add your Polygon PoS addresses to rotki to track POL (formerly MATIC) and token balances, decoded transactions, and DeFi activity. You choose which Polygon RPC endpoint handles the queries. ## Features - POL (MATIC) and ERC-20 token balances tracked for your Polygon PoS addresses. - Transactions decoded into readable events: swaps, transfers, bridges, and DeFi interactions. - DeFi protocols decoded on Polygon, including Aave, Curve, QuickSwap, and more. - Polygon PoS bridge transfers linked with their Ethereum counterparts. ## Setup 1. In rotki, open Blockchain & Accounts → Polygon PoS → Add address. 2. Paste your address. 3. Optional: in Settings → RPC, configure your preferred Polygon RPC endpoint. ## FAQ ### Which Polygon RPC does rotki use? rotki is a local application that talks directly to the Polygon 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. ### Is POL (the renamed MATIC) handled correctly? Yes. rotki tracks POL/MATIC under its current asset mapping with correct pricing. # Puffer Finance rotki decodes Puffer Finance airdrop claims (Puffer S1 and PufferXEigen S2) as airdrop income, and tracks pufETH like any other token balance. You choose which Ethereum RPC endpoint handles the queries. ## Features - Puffer S1 and PufferXEigen S2 airdrop claims decoded as airdrop income events. - pufETH tracked as a token balance alongside the rest of your portfolio. ## Setup 1. In rotki, add your Ethereum address. 2. Open History and let the initial sync run. Puffer airdrop claims are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for Puffer activity? 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. ### Were the Puffer airdrops captured? Yes. Both the Puffer S1 and PufferXEigen S2 airdrop claims are decoded as airdrop income. # Pump.fun rotki decodes your Pump.fun buys and sells on Solana as trade events and recognises the Pump.fun protocol and coin-creator fees, so your memecoin activity has a clear cost basis. You choose which Solana RPC endpoint handles the queries. ## Features - Pump.fun buys and sells decoded as trade events on Solana. - Pump.fun protocol fee and coin-creator fee recognised as fee events. ## Setup 1. In rotki, add your Solana address. Pump.fun activity is decoded automatically. 2. Open History and let the initial sync run. ## FAQ ### Which Solana RPC does rotki use for Pump.fun activity? rotki is a local application that talks directly to the Solana 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. # QuickSwap rotki decodes QuickSwap swaps, including native-token swaps (ETH, POL), and tracks your QuickSwap LP balances. You choose which RPC endpoint handles the queries. ## Features - QuickSwap swaps decoded as swap events, including native-token (ETH, POL) swaps. - QuickSwap LP positions reflected in your portfolio. - Decoded on Polygon PoS and Base. ## Setup 1. In rotki, add your Polygon PoS or Base address. QuickSwap activity is decoded automatically. 2. Open History and let the initial sync run. ## FAQ ### Which RPC does rotki use for QuickSwap activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. ### Are POL/MATIC native-token swaps decoded? Yes. QuickSwap native-token swaps are decoded as swap events. # Rainbow Swaps rotki decodes swaps executed through the Rainbow Wallet swap router, including the Rainbow fee. You choose which RPC endpoint handles the queries. ## Features - Rainbow Wallet swaps decoded as swap events, with the Rainbow fee recognised. - Decoded on Ethereum, Arbitrum, Optimism, Base, Polygon, and BNB Smart Chain. ## Setup 1. In rotki, add the EVM address you use in Rainbow Wallet. 2. Open History and let the initial sync run. Rainbow swaps are decoded automatically. ## FAQ ### Which RPC does rotki use for Rainbow swap activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # rotki Sponsorship rotki recognises the purchase and mint of a rotki Sponsorship NFT so your sponsorship appears in your event history, with its tier, alongside the rest of your portfolio. You choose which Ethereum RPC endpoint handles the queries. ## Features - rotki Sponsorship NFT purchase and mint decoded as protocol events. - Tier (Bronze, Silver, or Gold) shown in the decoded event. ## Setup 1. In rotki, add the Ethereum address you used for the sponsorship mint. 2. Open History and let the initial sync run. Sponsorship events are decoded automatically. ## FAQ ### What is rotki Sponsorship? An NFT mint that supports rotki development. Read more at rotki.com/sponsor. ### Which Ethereum RPC does rotki use? 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. # Runmoney rotki decodes Runmoney club activity on Base: the membership join (fee and NFT) and USDC staking and unstaking. You choose which Base RPC endpoint handles the queries. ## Features - Runmoney club join decoded, including the ETH membership fee and the membership NFT received. - USDC staking and unstaking in Runmoney decoded as protocol events. ## Setup 1. In rotki, add your Base address. 2. Open History and let the initial sync run. Runmoney events are decoded automatically. ## FAQ ### Which Base RPC does rotki use for Runmoney activity? rotki is a local application that talks directly to the Base 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. # Safe (Gnosis Safe) Track Safe multisig accounts in rotki: balances, transactions, decoded DeFi activity, and multisig management events for treasuries, DAOs, and personal multisigs. You choose which RPC endpoint handles the queries. ## Features - Add any Safe address as a read-only watch address - no Safe owner keys needed. - Multisig management events decoded: Safe creation, owner additions and removals, threshold changes, master-copy upgrades, and execution success/failure. - DeFi decoders run on Safe-routed transactions, so protocols like Aave, Curve, and Uniswap are decoded when the transaction goes through a Safe. - Works across the EVM chains where Safe is deployed (Ethereum, Arbitrum, Optimism, Polygon, Base, Gnosis, Scroll, BNB Smart Chain, and more). ## Setup 1. In rotki, add your Safe address as a tracked address on the chain where it is deployed. 2. Open History and let the initial sync run. Safe transactions and decoded DeFi events appear automatically. ## FAQ ### Does rotki need Safe owner signatures or keys? No. Safe addresses are tracked as read-only watch addresses. rotki never asks for owner keys or signatures. ### Are DeFi events done via a Safe decoded? Yes. Protocols like Aave, Curve, and Uniswap are decoded when the transaction is routed through a Safe. ### Which RPC does rotki use for Safe activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Scroll Add your Scroll addresses to rotki to track ETH and ERC-20 balances, decoded transactions, bridge transfers, and DeFi activity on the Scroll zkEVM. You choose which Scroll RPC endpoint handles the queries. ## Features - ETH and ERC-20 token balances tracked for your Scroll addresses. - Transactions decoded into readable events: swaps, transfers, bridges, and DeFi interactions. - DeFi protocols decoded on Scroll, including Aave, Compound, KyberSwap, SushiSwap, and Morpho. - Scroll-to-Ethereum bridge transfers linked across both chains. ## Setup 1. In rotki, open Blockchain & Accounts → Scroll → Add address. 2. Paste your address. 3. Optional: in Settings → RPC, configure your preferred Scroll RPC endpoint. ## FAQ ### Which Scroll RPC does rotki use? rotki is a local application that talks directly to the Scroll 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. ### Are Scroll bridge transactions decoded? Yes. Scroll-to-Ethereum bridge transfers are linked across both chains so they aren't double-counted. # ShapeShift Import your ShapeShift swap history into rotki via CSV. ShapeShift went fully non-custodial in 2021 and operates as a DEX aggregator; rotki recognises the trades and reconciles them with the rest of your wallet activity. CSV files are processed on your machine. ## Features - CSV import of ShapeShift trade and swap history exports. - Swaps imported with matched spend and receive sides for tax accounting. - Integrates with the rest of your portfolio so the swaps flow into your PnL. ## Setup 1. Export your ShapeShift history from app.shapeshift.com → Transaction History. 2. In rotki, open Import Data and select your ShapeShift file. ## FAQ ### Is ShapeShift custodial? No. ShapeShift went fully non-custodial in 2021. It now operates as a DEX aggregator; you keep custody of your own wallet. ### Does my ShapeShift data leave my machine? No. CSV imports are parsed entirely on your computer; the file never leaves your machine. # Shutter rotki decodes Shutter Network SHU airdrop claims into the vesting contract, vested SHU redemptions, and SHU delegation changes. You choose which Ethereum RPC endpoint handles the queries. ## Features - SHU airdrop claims into the vesting contract decoded as airdrop income. - Redemptions of vested SHU decoded. - SHU delegation changes decoded. ## Setup 1. In rotki, add your Ethereum address. 2. Open History and let the initial sync run. Shutter events are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for Shutter activity? 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. # Sky rotki decodes activity on Sky (the rebrand of MakerDAO): Sky PSM direct swaps and the migrations from MKR and DAI, and tracks your USDS and sUSDS balances. You choose which Ethereum RPC endpoint handles the queries. ## Features - USDS and sUSDS tracked as token balances alongside the rest of your portfolio. - Sky PSM direct swaps decoded as swap events. - DAI-to-USDS and MKR-to-SKY migration events decoded. - Works alongside the MakerDAO integration, which continues to decode the legacy MakerDAO contracts. ## Setup 1. In rotki, add your Ethereum address. Sky balances and transactions are detected automatically. 2. Open History and let the initial sync run. Sky events are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for Sky activity? 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. ### Is Sky the same protocol as MakerDAO? Sky is the rebrand of MakerDAO. rotki decodes both the legacy MakerDAO contracts and the new Sky contracts, including the migration between them. ### Are my sUSDS savings tracked? Yes. Your sUSDS balance is tracked and appears in your portfolio. # Socket rotki decodes Socket (Bungee) cross-chain bridge transactions. You choose which RPC endpoint handles the queries. ## Features - Socket (Bungee) bridge transactions decoded as protocol events on rotki's supported EVM chains. - Bridge legs linked across chains where both ends are tracked, so transferred assets aren't double-counted. ## Setup 1. In rotki, add your addresses on both the source and destination chains. 2. Open History and let the initial sync run. Socket bridge events are decoded automatically. ## FAQ ### Which RPC does rotki use for Socket activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Solana Add your Solana addresses to rotki to track SOL, staked SOL, and SPL token balances with decoded transaction history. Jupiter swaps, Jito tips, and Jupiter Lend activity are recognised automatically. You choose which Solana RPC endpoint handles the queries. ## Features - SOL, staked SOL, and SPL token balances tracked for your Solana addresses. - Staked SOL summed from your stake accounts and included in your portfolio. - Jupiter aggregator swaps decoded as trade events. - Jito tips recognised as fee events. - Jupiter Lend activity (deposits, withdrawals, borrows, repays) decoded as events. ## Setup 1. In rotki, open Blockchain & Accounts → Solana → Add address. 2. Paste your Solana address. rotki validates the format and rejects invalid addresses. 3. Optional: in Settings → RPC, configure your preferred Solana RPC endpoint. ## FAQ ### Which Solana RPC does rotki use? rotki is a local application that talks directly to the Solana 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. ### Does rotki include staked SOL? Yes. Both native SOL and staked SOL balances are counted in your Solana portfolio. ### Are Jupiter swaps and Jito tips decoded? Yes. rotki decodes Jupiter aggregator swaps as trades and recognises Jito tip payments as fee events. # Spark rotki decodes your Spark Protocol activity: Spark Lend supplies and borrows, Spark Savings (sDAI / sUSDS) deposits and withdrawals, the SPK airdrop claim and staking, and Spark proxy-account balances. You choose which RPC endpoint handles the queries. ## Features - Spark Lend supplies, withdrawals, borrows, and repayments decoded. - Spark Savings sDAI and sUSDS deposit and withdraw events decoded. - SPK airdrop claims and SPK staking decoded as events. - Spark proxy-account balances detected. - Decoded on Ethereum, Arbitrum, Optimism, Base, and Gnosis. ## Setup 1. In rotki, add your address under a chain where your Spark activity lives. Proxy positions are detected automatically. 2. Open History and let the initial sync run. Spark events are decoded automatically. ## FAQ ### Which RPC does rotki use for Spark activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. ### Are sDAI and sUSDS deposits tracked? Yes. Spark Savings deposits and withdrawals are decoded as protocol events. ### Was the SPK airdrop captured? Yes. SPK airdrop claims and any subsequent staking events are decoded. # StakeDAO rotki decodes StakeDAO V2 Curve strategy transactions, detects vault balances, and decodes votemarket bribe and bounty claims. You choose which Ethereum RPC endpoint handles the queries. ## Features - StakeDAO V2 Curve strategy transactions decoded, with vault balances detected. - Votemarket bribe and bounty claims decoded as income events. - Strategy withdrawals decoded. ## Setup 1. In rotki, add your Ethereum address. StakeDAO positions are detected automatically. 2. Open History and let the initial sync run. StakeDAO events are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for StakeDAO activity? 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. ### Are votemarket bribes captured? Yes. Votemarket bribe and bounty claims are decoded as income events. # Summer.fi rotki decodes Summer.fi (formerly Oasis) vault interactions and detects token balances held on Summer.fi proxy accounts. You choose which RPC endpoint handles the queries. ## Features - Summer.fi vault deposits and withdrawals decoded as protocol events. - Token balances held on Summer.fi proxy accounts detected. - Decoded on Ethereum, Arbitrum, Optimism, and Base. ## Setup 1. In rotki, add your address under a chain where your Summer.fi activity lives. 2. If you use a Summer.fi proxy account, its balance is included automatically once the owner address is tracked. 3. Open History and let the initial sync run. Summer.fi events are decoded automatically. ## FAQ ### Which RPC does rotki use for Summer.fi activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. ### Does rotki track balances on Summer.fi proxy accounts? Yes. Summer.fi proxy account balances are detected automatically once the owner address is tracked. # Superfluid rotki decodes Superfluid money streams and super-token wrapping on rotki's supported EVM chains. You choose which RPC endpoint handles the queries. ## Features - Superfluid streams decoded: start and stop events labelled with the monthly flow rate, sender, and receiver. - Super-token upgrades (wrapping) and downgrades (unwrapping) decoded. ## Setup 1. In rotki, add your address under a chain where you use Superfluid. 2. Open History and let the initial sync run. Superfluid events are decoded automatically. ## FAQ ### Which RPC does rotki use for Superfluid activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # SushiSwap rotki decodes SushiSwap swaps and tracks liquidity-provider balances, including swaps routed through the RedSnwapper and Route Processor routers. You choose which RPC endpoint handles the queries. ## Features - SushiSwap swaps decoded as swap events. - SushiSwap LP balances reflected in the LP tokens view. - Swaps through the RedSnwapper (RP5/RP6) and older Route Processor routers decoded. - Decoded on Ethereum, Arbitrum, Optimism, Base, Polygon, Gnosis, BNB Smart Chain, Scroll, and Hyperliquid. ## Setup 1. In rotki, add your address under a chain where you've used SushiSwap. 2. Open History and let the initial sync run. SushiSwap activity is decoded automatically. ## FAQ ### Which RPC does rotki use for SushiSwap activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. ### Are RedSnwapper router swaps decoded? Yes. SushiSwap RedSnwapper (RP5/RP6) and older Route Processor router swaps are decoded. # The Graph rotki decodes The Graph GRT delegations and undelegations, indexer reward distributions, and delegation transfers from Ethereum to Arbitrum. You choose which RPC endpoint handles the queries. ## Features - GRT delegations and undelegations decoded as protocol events. - Indexer reward distributions decoded as income. - Delegation transfers from Ethereum to Arbitrum (L2) decoded. ## Setup 1. In rotki, add your Ethereum address (and your Arbitrum address if you moved delegations to L2). 2. Open History and let the initial sync run. The Graph events are decoded automatically. ## FAQ ### Which RPC does rotki use for The Graph activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Umami rotki decodes Umami vault deposits and withdrawals on Arbitrum, with protocol fees shown as separate entries. You choose which Arbitrum RPC endpoint handles the queries. ## Features - Umami deposits and withdrawals on Arbitrum decoded as protocol events. - Protocol fees on deposit and withdraw decoded as separate entries. ## Setup 1. In rotki, add your Arbitrum address. Umami positions are detected automatically. 2. Open History and let the initial sync run. Umami events are decoded automatically. ## FAQ ### Which Arbitrum RPC does rotki use for Umami activity? rotki is a local application that talks directly to the Arbitrum 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. ### Are Umami protocol fees shown separately? Yes. Fees on deposit and withdraw are decoded as their own entries for clear accounting. # Uniswap rotki decodes Uniswap v2, v3, and v4 swaps and liquidity-provider positions across the EVM chains where Uniswap is deployed. You choose which RPC endpoint handles the queries. ## Features - Uniswap v2 swaps and LP positions decoded across supported EVM chains. - Uniswap v3 swaps and concentrated-liquidity positions decoded with the correct base and quote sides. - Uniswap v4 swaps and LP balances decoded, including native ETH fees paid via internal transactions. - LP position values reflected in your portfolio. ## Setup 1. In rotki, add your address under a chain where you've used Uniswap (Ethereum, Arbitrum, Optimism, Base, Polygon, and more). 2. Open History and let the initial sync run. Uniswap activity is decoded automatically. ## FAQ ### Which RPC does rotki use for Uniswap activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. ### Does rotki support Uniswap v4? Yes. Uniswap v4 swaps and LP balances are decoded, including native ETH fees paid through internal transactions. ### Do v3 concentrated-liquidity positions show up in my portfolio? Yes. v3 LP positions are decoded and their values flow into your portfolio totals. # Uphold Import your Uphold transaction history into rotki via CSV: trades, deposits, withdrawals, and BAT reward payouts. CSV files are processed entirely on your computer. ## Features - CSV import of Uphold transaction history exports, including multi-asset trades. - Trades imported with matched spend and receive sides. - Integrates with the rest of your portfolio for unified PnL and tax reporting. ## Setup 1. In Uphold, open Activity → Documents → Generate Transaction History CSV. 2. In rotki, open Import Data and select your Uphold file. ## FAQ ### Does my Uphold data leave my machine? No. CSV imports are parsed entirely on your computer; the file never leaves your machine. ### Are BAT (Brave) rewards tracked? Yes. BAT payouts received via Uphold are imported from the CSV as income events. # Velodrome Finance rotki decodes Velodrome swaps, liquidity-pool positions, gauge reward claims, and veVELO locking on Optimism. You choose which Optimism RPC endpoint handles the queries. ## Features - Velodrome swaps decoded as swap events. - Velodrome LP positions tracked, with balances reflected in your portfolio. - Gauge reward claims decoded as income. - veVELO locking decoded. ## Setup 1. In rotki, add your Optimism address. Velodrome activity is decoded automatically. 2. Optional: refresh Velodrome data under Settings → Manage Data → Refresh protocol data. 3. Open History and let the initial sync run. Velodrome events are decoded automatically. ## FAQ ### Which Optimism RPC does rotki use for Velodrome activity? rotki is a local application that talks directly to the Optimism 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. ### Are Velodrome gauge rewards captured? Yes. Gauge reward claims are decoded as income events. # Votium rotki decodes Votium bribe claims (the rewards vlCVX holders earn for delegating votes) as income events. You choose which Ethereum RPC endpoint handles the queries. ## Features - Votium bribe claims decoded as income events with the Votium counterparty. - Each claimed token is recorded with its own amount and price. ## Setup 1. In rotki, add your Ethereum address. 2. Open History and let the initial sync run. Votium claims are decoded automatically. ## FAQ ### Which Ethereum RPC does rotki use for Votium activity? 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. ### Are bribe claims tax-relevant? rotki decodes them as income events. Talk to a tax professional about treatment in your jurisdiction. # WalletConnect rotki decodes WalletConnect (WCT) activity on Optimism: airdrop claims, staking deposits, stake-weight changes, and reward claims, and detects WCT staked balances. rotki also lets you connect a wallet via WalletConnect to switch chains from the on-chain page. You choose which Optimism RPC endpoint handles the queries. ## Features - WCT airdrop claims decoded as airdrop income on Optimism. - WCT staking deposits and stake-weight changes decoded as protocol events. - WCT staking reward claims decoded as income. - WCT staked balances detected for tracked addresses. ## Setup 1. In rotki, add your Optimism address. 2. Open History and let the initial sync run. WCT events are decoded automatically. ## FAQ ### Which Optimism RPC does rotki use for WalletConnect activity? rotki is a local application that talks directly to the Optimism 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. ### Was the WCT airdrop captured? Yes. WCT airdrop claims on Optimism are decoded as airdrop income. ### Are WCT staking rewards tracked? Yes. Reward claim events are decoded as income, and staked balances are detected. # Wrapped Ether (WETH) rotki decodes WETH deposit (wrap) and withdraw (unwrap) events so ETH and WETH movements appear as their underlying ETH transfer rather than confusing wrap/unwrap noise. You choose which RPC endpoint handles the queries. ## Features - WETH deposit (wrap) and withdraw (unwrap) events decoded into the underlying ETH movement. - WETH tracked as a token balance on the EVM chains rotki supports. ## Setup 1. In rotki, add your address under any EVM chain. WETH activity is decoded automatically. 2. Open History and let the initial sync run. WETH events are decoded automatically. ## FAQ ### Why does rotki convert WETH wraps to ETH movements? From a cost-basis perspective WETH is ETH - wrapping or unwrapping is not a taxable event. rotki presents the underlying ETH movement to keep your event history readable. ### Which RPC does rotki use for WETH activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # Wrapped POL (WMATIC / WPOL) rotki decodes WMATIC / WPOL deposit (wrap) and withdraw (unwrap) events so POL and WPOL movements appear as their underlying native-token transfer. You choose which Polygon RPC endpoint handles the queries. ## Features - Wrap and unwrap events decoded into the underlying POL movement. - WPOL tracked as a token balance alongside native POL. ## Setup 1. In rotki, add your Polygon address. WPOL activity is decoded automatically. 2. Open History and let the initial sync run. WPOL events are decoded automatically. ## FAQ ### What's the difference between WMATIC and WPOL? Same contract, renamed alongside the MATIC-to-POL token rename. rotki handles both labels and the underlying balance. ### Which Polygon RPC does rotki use? rotki is a local application that talks directly to the Polygon 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. # WMON rotki decodes WMON deposit (wrap) and withdraw (unwrap) events on Monad so MON and WMON movements appear as their underlying native-token transfer. You choose which Monad RPC endpoint handles the queries. ## Features - Wrap and unwrap events decoded into the underlying MON movement. - WMON tracked as a token balance alongside native MON. ## Setup 1. In rotki, add your Monad address. WMON activity is decoded automatically. 2. Open History and let the initial sync run. WMON events are decoded automatically. ## FAQ ### What is WMON? WMON is the ERC-20 wrapper of Monad's native MON token, the equivalent of WETH on Ethereum. ### Which Monad RPC does rotki use? rotki is a local application that talks directly to the Monad 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. # WOO X Connect WOO X to rotki to import spot trades, deposits, withdrawals, and balances. rotki uses a read-only API key signed from your machine. ## Features - Spot trades imported as swap events from your WOO X account. - Deposits and withdrawals imported as asset movements. - Balance reconciliation across your WOO X account. ## Limitations - Margin and derivatives history is not imported. ## Setup 1. In WOO X, open the profile menu → Subaccounts and API and create a new API key. 2. Set permissions to "Read" only and leave trade and transfer permissions off. 3. Whitelist your IP for additional safety. 4. In rotki, open API Keys → Exchanges → Add WOO X and paste the key and secret. ## FAQ ### Where are my WOO X API keys sent? rotki is a local application: your WOO X API key is stored on your computer and used to sign each request, which goes directly from your machine to WOO X's API. No rotki-operated server ever sees the key or the request. ### Can rotki trade or withdraw on WOO X? No. rotki only requests Read-only scopes and never sends trade or withdrawal calls. # Wrapped xDAI (WXDAI) rotki decodes WXDAI deposit (wrap) and withdraw (unwrap) events so xDAI and WXDAI movements appear as their underlying native-token transfer. You choose which Gnosis RPC endpoint handles the queries. ## Features - Wrap and unwrap events decoded into the underlying xDAI movement. - WXDAI tracked as a token balance alongside native xDAI. ## Setup 1. In rotki, add your Gnosis address. WXDAI activity is decoded automatically. 2. Open History and let the initial sync run. WXDAI events are decoded automatically. ## FAQ ### What is WXDAI? WXDAI is the ERC-20 wrapper of Gnosis Chain's native xDAI, the equivalent of WETH on Ethereum. ### Which Gnosis RPC does rotki use? rotki is a local application that talks directly to the Gnosis 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. # Yearn rotki decodes Yearn vault deposits and withdrawals (v2 and v3), staking transactions, and reward claims across several EVM chains. You choose which RPC endpoint handles the queries. ## Features - Yearn v2 and v3 vault deposits and withdrawals decoded. - Yearn staking deposits, withdrawals, and reward claims decoded. - Vault positions reflected in your portfolio. - Decoded on Ethereum, Arbitrum, Optimism, Base, Polygon, and Gnosis. ## Setup 1. In rotki, add your address under a chain where you've used Yearn. Vault positions are detected automatically. 2. Optional: refresh Yearn data under Settings → Manage Data → Refresh protocol data. 3. Open History and let the initial sync run. Yearn events are decoded automatically. ## FAQ ### Which RPC does rotki use for Yearn activity? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. ### Which chains are supported? Yearn is decoded on Ethereum, Arbitrum, Optimism, Base, Polygon, and Gnosis. ### Are Yearn staking rewards captured? Yes. Staking deposits, withdrawals, and reward claims are all decoded. # ZKSync Bridge rotki decodes ZKSync bridge deposits and ZKSync Lite batch withdrawals on the Ethereum side. For ZKSync Lite balances see the \[ZKSync Lite]\(/integrations/zksync-lite) blockchain integration. You choose which RPC endpoint handles the queries. ## Features - ZKSync bridge deposits decoded on the Ethereum side. - ZKSync Lite batch withdrawals decoded on the Ethereum side. - Source and destination legs linked across L1 and L2. ## Setup 1. In rotki, add your address on Ethereum and ZKSync Lite. 2. Open History and let the initial sync run. Bridge events are decoded automatically. ## FAQ ### Does this integration cover both ZKSync Lite and ZKSync Era? This page covers bridge events. For ZKSync Lite balance tracking, see the dedicated ZKSync Lite integration. ### Which RPC does rotki use for these events? rotki is a local application that talks directly to the RPC endpoint you configure for each chain - the public default, a third-party provider, or your own node. Each query goes from your computer to that endpoint without passing through any rotki-operated server. # ZKSync Lite Add your ZKSync Lite addresses to rotki to track balances and decoded transaction history on the original ZKSync rollup. You choose which ZKSync Lite endpoint handles the queries. ## Features - Balances tracked for your ZKSync Lite addresses. - Transactions decoded into readable events: transfers, swaps, and L1-to-L2 withdrawals. ## Setup 1. In rotki, open Blockchain & Accounts → ZKSync Lite → Add address. 2. Paste your address. ## FAQ ### Which ZKSync Lite endpoint does rotki use? rotki is a local application that queries the ZKSync Lite endpoint you configure directly from your computer, without passing through any rotki-operated server. ### Is this the same as ZKSync Era? No. ZKSync Lite is the original rollup (formerly ZKSync 1). ZKSync Era is the EVM-compatible chain; they are separate integrations with separate addresses. # rotki vs Awaken Awaken and rotki both put on-chain activity at the center: DeFi positions, swaps, NFTs, and the messy reality of wallet history. Awaken does this as a hosted service, while rotki does it as a local-first, open-source desktop application that decodes your activity on your own machine. ## How Awaken works Awaken is a cloud tool with a strong focus on DeFi and NFT tax handling, and it offers importers to help people move over from other hosted services. You connect your wallets and accounts, and Awaken processes that history on its servers. The trade-off is that your on-chain history is uploaded to the vendor. ## How rotki works rotki reads your on-chain activity through RPC endpoints you choose and decodes it locally into readable events, with full profit and loss accounting. Everything is stored in an encrypted database on your own computer, and because rotki is open source, you can verify exactly how each protocol is decoded rather than trusting a closed cloud pipeline. ## Privacy and ownership For on-chain-heavy users this matters a lot: your wallet history is sensitive, and a hosted tool concentrates it on its servers. rotki keeps that history local and self-custodied, so there is no central store to breach and no dependence on a vendor's handling of your data. ## The trade-off rotki does not offer a one-click hosted importer, and it asks you to connect your accounts, run a desktop app, and keep your own backups. In return it decodes your DeFi and NFT activity locally, with open-source transparency and your on-chain history kept on your own machine. For anyone who wants that history private and auditable rather than uploaded to a vendor, that is the trade worth making, and the reason to choose rotki. # rotki vs CoinLedger CoinLedger is built around getting you to a finished tax report quickly, with exports into consumer filing software. rotki is a local-first, open-source desktop application that produces the same kind of reports while keeping your data on your own machine. The tools overlap on output but differ on where your data lives. ## How CoinLedger works CoinLedger is a hosted service. You connect exchanges and wallets, it imports your history into its cloud, and it focuses on turning that into a filing-ready tax report with direct exports to popular tax software. The cost is the usual one: your full history sits on the vendor's servers. ## How rotki works rotki runs locally and stores your data in an encrypted database on your computer. It connects to exchanges with read-only API keys and reads chains through your own RPC endpoints, and it is open source so you can audit it. It produces accounting and tax reports and standard exports without uploading your data anywhere. ## Privacy and ownership If you would rather not hand your complete transaction history to a tax vendor, rotki is the answer. Your data stays self-custodied and local, there is no cloud account to be breached, and you are not trusting a closed pipeline to handle your records. ## The trade-off rotki does not wire directly into consumer filing software, and it asks you to run a desktop app and keep your own backups. In return you get privacy, self-custody, and open-source transparency, with your records processed on your own machine instead of a vendor's cloud. For anyone who would rather own their data than hand it over for a faster filing flow, that is the trade worth making, and the reason to choose rotki. # rotki vs CoinTracker CoinTracker and rotki both track your crypto portfolio and prepare tax reports, but they make a very different promise about where your data lives. CoinTracker is a cloud service built around convenience and mobile access. rotki is a local-first desktop application built around privacy and ownership. ## How CoinTracker works CoinTracker is designed to be always on and always synced. You connect your exchanges and wallets, and your data is stored in CoinTracker's cloud so you can open the web or mobile app from any device and see an up-to-date view. The trade-off is that your full transaction history is held on the vendor's servers. ## How rotki works rotki runs on your computer and stores your data in an encrypted local database. It connects to exchanges with read-only API keys and reads on-chain activity through RPC endpoints you choose. Nothing is uploaded to rotki-operated servers, and the code is open source so you can verify how it behaves. The result is a portfolio tracker and tax tool where you, not a vendor, hold the data. ## Privacy and ownership If you would rather not place your entire financial history in a third-party cloud, this is the deciding factor. rotki keeps that history local and self-custodied. There is no vendor account that could be breached, sold, or mined, and you are not relying on someone else's retention policy. ## The trade-off rotki is desktop-first and does not chase the mobile, always-synced cloud experience. It asks you to run a desktop app and keep your own backups. In exchange you get privacy, self-custody, and open-source software you can audit, with your data on your machine rather than a vendor's. For anyone who values owning their financial data, that is a trade worth making, and the reason to choose rotki. # rotki vs CoinTracking CoinTracking is one of the oldest names in crypto tax software, known for a deep and report-heavy hosted platform. rotki approaches the same job as a local-first, open-source desktop application. Both will track your portfolio and produce tax reports; the question is whether you want that work done in the cloud or on your own machine. ## How CoinTracking works CoinTracking is a hosted account. You import your trades and transfers through API connections or files, and CoinTracking stores that history on its servers and turns it into a large range of reports, charts, and tax outputs. Breadth of reporting is its reputation. As with any hosted tool, the cost is that your full history is held by the vendor. ## How rotki works rotki runs on your computer and stores everything in an encrypted local database. It pulls exchange data with read-only API keys and on-chain activity through RPC endpoints you control, and it is open source so you can verify how it works. It is built to give you accurate accounting and tax reports without your data leaving your machine. ## Privacy and ownership This is the heart of the comparison. A long-lived hosted account accumulates years of your financial history in one place. rotki keeps that history local and self-custodied, so there is no vendor-side store to breach and no dependence on someone else's security or retention practices. ## The trade-off rotki does not aim to match every report in a hosted catalog. It focuses on accurate core accounting, transparent on-chain decoding, and keeping your data local. That focus is deliberate: the work happens on your machine, in software you can audit, with your history never handed to a vendor. For privacy, open source, and self-custody, that is the trade worth making, and the reason to choose rotki. # rotki vs Koinly Koinly and rotki solve the same problem from opposite ends. Both connect to your exchanges and wallets, reconcile your trades and transfers, and produce portfolio views and tax reports. The difference is architectural: Koinly is a hosted cloud service, and rotki is a local-first desktop application. ## How Koinly works Koinly is a web application. You create an account, link your exchanges through API connections or file uploads, add your public wallet addresses, and Koinly imports that history into its servers. From there it builds your dashboard and generates tax reports, with broad coverage of country-specific forms. It runs in a browser and has a mobile app, but the cost of that convenience is that your complete financial history lives in someone else's cloud. ## How rotki works rotki runs on your own computer. It connects to exchanges using read-only API keys and reads your on-chain activity through RPC endpoints you control, then stores everything in an encrypted local database. Nothing passes through rotki-operated servers. Because rotki is open source, you can read the code and verify exactly how your data is handled, rather than trusting a closed system. ## Privacy and ownership This is the core reason to pick rotki. A hosted tool concentrates the transaction histories of many users in one place, which makes the vendor a target and means a single breach can expose a lot of people. With rotki, the blast radius of a problem is your own device. You are not handing your full financial history to a third party, and you are not depending on a vendor's data-retention or security practices. ## Tax reporting and DeFi rotki produces accounting and tax reports locally, and it decodes on-chain activity into readable events so that DeFi positions, swaps, and rewards are accounted for with proper profit and loss. Koinly's strength is the breadth of its ready-made country reports; rotki's strength is doing the same core work without your data leaving your machine. ## The trade-off rotki asks a little more of you than a hosted tool does: you run a desktop app and keep your own backups. What you get back is ownership. Your transaction history stays on your machine, encrypted and under your control, in software you can audit line by line. For anyone who cares about privacy and self-custody, that is a trade worth making, and it is the reason to choose rotki. # rotki vs ZenLedger ZenLedger is a hosted crypto tax platform with features aimed at investors and the tax professionals who serve them. rotki is a local-first, open-source desktop application. Both produce accounting and tax reports; the difference is whether your records live in a managed cloud account or on your own machine. ## How ZenLedger works ZenLedger is a cloud service. You connect exchanges and wallets, your history is imported to its servers, and it builds reports with workflows oriented toward tax filing and working with professionals. The familiar cost is that your full transaction history is stored by the vendor. ## How rotki works rotki runs on your computer and keeps your data in an encrypted local database. It reads exchanges through read-only API keys and chains through RPC endpoints you control, and it is open source so you can verify its behavior. It produces reports and exports you can share with an accountant, all without your data leaving your machine. ## Privacy and ownership This is the deciding factor. A hosted tax platform holds your complete financial history on its servers. rotki keeps that history local and self-custodied, removing the central store that could be breached and the dependence on a vendor's security and retention choices. ## The trade-off rotki does not replicate the hosted, professional-managed account model, and it asks you to run a desktop app and manage your own backups. In return it gives you privacy, self-custody, and open-source transparency, with your data on your own machine; you can still export reports to share with an accountant. For anyone who would rather keep their financial history local than hand it to a platform, that is the trade worth making, and the reason to choose rotki. # CSV import Not every source can be connected with an API key, and you often have older history that predates any key you hold. CSV import is how rotki fills those gaps: you bring in the file, rotki reads it on your machine, and the activity joins the rest of your portfolio and accounting. ## When CSV import is the right tool For supported exchanges, a read-only API key is usually the better default because it keeps updating as you trade. CSV import is for everything else: exchanges or tools without an API connection in rotki, accounts you have closed, or historical data you exported once. It is what lets you complete your records. ## How importing works You export a CSV from the source, pick the matching importer in rotki (or the generic importer for custom data), and run it. Because exports differ between providers, a format rotki does not recognise can be mapped through the generic importer. Everything is processed locally and stored in your encrypted database, and you can review and edit imported events afterwards. ## Which sources have a built-in importer rotki ships dedicated CSV importers for a range of exchanges and tools, including Binance, KuCoin, Bitstamp, Bittrex, Coinbase Pro, Crypto.com, BitMEX, Uphold, Bisq, ShapeShift, BlockFi and Nexo. It also imports from other tax and portfolio tools, including CoinTracking, CoinLedger, Blockpit and Bitcoin.tax, which helps if you are moving over from one of them. For anything without a dedicated importer, the generic rotki CSV format lets you map your own columns. ## Keeping it accurate A CSV is a snapshot, so you re-import to stay current, and messy exports can leave gaps worth a quick manual fix. Once imported, the data is accounted for alongside your API and on-chain activity, so your portfolio view and tax reports reflect your full history, all without anything leaving your computer. # DeFi portfolio tracking DeFi is where many portfolio trackers fall short: a block explorer shows you hashes, not what actually happened. rotki turns that raw on-chain activity into a portfolio you can read, and it does so locally, with endpoints you control. ## From raw transactions to readable events rotki reads the activity for the addresses you add and decodes each transaction into a categorised event: a swap, a deposit into a liquidity pool, a staking reward, a transfer. Those events carry the accounting through to profit and loss, so your DeFi history is both visible and properly accounted for. ## You choose how chains are read To read on-chain data, rotki queries an RPC endpoint or data provider. You decide which one, whether a public provider, a service you trust, or your own node, so you control who sees those requests and how much throughput you get for large histories. Decoded results are stored in your local encrypted database. ## Which chains rotki covers rotki tracks activity across several EVM chains, including Ethereum, Arbitrum One, Base, Optimism, Polygon PoS, Gnosis, BNB Smart Chain, Scroll, Avalanche and zkSync Lite, alongside non-EVM networks such as Bitcoin, Solana, Polkadot and Kusama. The supported set grows over time; the [integrations directory](https://rotki.com/integrations) lists every chain, exchange and protocol rotki currently reads. ## Protocol coverage New DeFi protocols appear constantly, and decoding coverage for specific protocols varies; brand-new or niche protocols may need a manual review to categorise. Many protocols are supported out of the box and coverage keeps growing, and where rotki needs a hand you can correct an event yourself. The result is a multi-chain DeFi portfolio you can follow clearly, tracked privately on your own machine. # Local-first crypto accounting Crypto accounting means turning a messy stream of trades, transfers and on-chain events into a coherent ledger you can report from. rotki does that work locally: it lives on your computer, reads your accounts, and keeps the resulting books in an encrypted database that never has to leave your machine. ## Building an accurate ledger rotki pulls balances and transactions from the exchanges and wallets you add and decodes on-chain activity into readable, categorised events. Where automation needs a hand, for example an unusual transaction or an off-exchange trade, you can edit events and add manual entries so the ledger reflects reality. ## Accounting you control You choose the cost-basis method and accounting period, and rotki applies them on your machine to calculate profit and loss. Because it is local and open source, you can see how each figure is derived rather than relying on calculations you cannot inspect. ## Who it is for rotki gives you the accounting foundation and exportable reports. It is not multi-user bookkeeping software and it is not tax advice. For an individual or a small operation that wants accurate, private, auditable crypto books, doing the accounting locally is a good fit. # Open-source crypto tax software rotki approaches crypto taxes differently from most tools: it is open source, and it runs on your computer. That combination is deliberate. You are not uploading your transaction history to a service and trusting calculations you cannot see; you can read exactly how rotki turns your trades and on-chain activity into a tax report. ## Why open source matters for taxes Tax calculations involve judgement calls: which cost-basis method to use, how to treat a transfer between your own wallets, how to value a DeFi reward. With closed software you have to take the vendor's word for how those decisions are made. Because rotki is open source, the accounting logic is public and auditable. If a number looks wrong, you can trace why. ## How rotki produces your report rotki builds your history from the exchanges and wallets you add, decodes on-chain activity into readable events, and then applies your accounting settings to calculate gains and losses. It produces a detailed, exportable report of taxable events for the period you choose. All of that happens locally on your machine. ## Cost-basis methods rotki supports rotki supports four cost-basis methods: FIFO (first in, first out), LIFO (last in, first out), HIFO (highest in, first out) and ACB (average cost basis). You pick the method and the accounting period in settings, and rotki applies it locally when it builds the report. The profit-and-loss report and its underlying events can be exported as CSV for your records or your accountant. ## What rotki does and does not do rotki gives you accurate, auditable accounting and a clear report of taxable events. It does not pre-fill your country's specific government forms, and it is not tax advice. If you want to understand and own your crypto accounting while keeping it private, running open-source software locally is a solid basis for that. # Privacy-first portfolio management Most portfolio trackers ask you to upload your accounts and addresses to their servers. That is convenient, but it means your complete financial history lives in someone else's cloud. rotki is built the other way around: it is a privacy-first desktop application that keeps your data on your own machine. ## Where your data lives rotki stores everything in a local database encrypted with SQLCipher using 256-bit AES, with the encryption key derived from your account password. Your balances, transactions and notes are on your device, not in a vendor account. Because rotki is open source, you can read the code that handles your data and confirm this for yourself. ## How rotki reads your accounts Exchanges are connected with read-only API keys, so rotki can see your balances and trades but cannot withdraw. On-chain balances are read by querying chain data through an RPC endpoint or data provider that you choose, so you decide who sees those requests: a provider you trust, or your own node. ## The trade-off A local-first tracker asks a bit more of you: you run a desktop app and you keep your own backups. In return you get ownership and privacy, plus an optional zero-knowledge sync if you want multi-device backups without giving up that control. If you would rather not hand your full portfolio to a cloud service, that is a trade worth making.