rotki primary sources — 2026-04-30

Project status in this pass

  • No canonical standalone whitepaper or litepaper surfaced.
  • The clearest current source of truth is the official docs corpus, llms.txt, premium guides, verification docs, and the first-party GitHub repository.

Primary-source snapshots

1) Docs llms.txt

  • URL: https://docs.rotki.com/llms.txt
  • Key excerpt:
    • Enumerates a very broad first-party docs surface across installation, portfolio tracking, history/events, tax accounting, exchange integrations, external-service APIs, data management, premium, and contribution guides.
    • This was the fastest way to verify that rotki is not only a tax tool, but a wider self-hosted portfolio/accounting stack with operator-style docs.

2) Docs intro / “What is rotki?”

  • URL: https://docs.rotki.com/index.html
  • Key excerpt:
    • Describes rotki as “an open-source asset management and accounting application specializing in crypto assets” that also aims to help with tax reporting.
    • Includes an unusually strong disclaimer that rotki imports, stores, displays, and reports on user-provided transaction data but does not provide tax or legal advice.
    • Helps frame rotki as tooling and reporting infrastructure rather than as a tax-filing service.

3) Quick start guide

  • URL: https://docs.rotki.com/usage-guides/quick-start.html
  • Key excerpt:
    • Says the user’s local account exists only on the device and that rotki does not store the data on its servers.
    • Walks through adding blockchain accounts and read-only exchange API keys, then generating a profit/loss report.
    • Recommends Etherscan API keys, custom RPC nodes, and indexer configuration, showing that rotki is designed for power users who manage their own data pipelines.

4) Exchange API keys guide

  • URL: https://docs.rotki.com/usage-guides/integrations/exchange-keys.html
  • Key excerpt:
    • Lists a wide range of supported exchanges and repeatedly stresses that rotki only needs read-only API permissions.
    • Documents sync settings, exchange-specific caveats, and operational details such as Binance market-pair limits and Kraken Futures handling.
    • Reinforces that rotki is a portfolio and accounting control plane rather than a trading venue.

5) Onchain transactions guide

  • URL: https://docs.rotki.com/usage-guides/history/onchain.html
  • Key excerpt:
    • Says rotki can perform onchain transactions by connecting a wallet through WalletConnect or a browser wallet.
    • Notes that current support is limited to native-token and ERC-20 sends on supported EVM chains and labels the feature experimental.
    • Shows rotki has some execution capability, but that execution is a secondary feature built around connected wallets rather than custodial infrastructure.

6) Premium overview

  • URL: https://docs.rotki.com/premium/
  • Key excerpt:
    • Says the base version will remain open-source and free.
    • Says premium unlocks extended portfolio tracking, advanced analytics, cloud backup and sync, premium-only integrations, and priority support.
    • Shows rotki’s business model is layered onto an open-source base rather than replacing it.

7) Verify your download

  • URL: https://docs.rotki.com/requirement-and-installation/verify.html
  • Key excerpt:
    • Recommends SHA512 checksum verification and GitHub Artifact Attestations for published binaries.
    • Explicitly frames these checks as protection against supply-chain attacks or tampered mirrors.
    • This is a strong signal that rotki’s self-sovereign posture extends to software-distribution trust, not only to data storage.

8) GitHub repository README

  • URL: https://github.com/rotki/rotki
  • Key excerpt:
    • Calls rotki “a privacy-focused portfolio manager, accounting, and analytics tool.”
    • Describes it as open-source, self-hosted, and privacy-focused, with local encrypted storage and self-sovereign control over data.
    • Confirms the project’s code-centric, community-contribution-oriented operating model.

Working conclusion

rotki is best cataloged as privacy-first self-hosted finance-ops software for crypto: portfolio tracking, accounting, tax-style reporting, exchange and chain ingestion, and optional premium sync/analytics layered over local encrypted data ownership. In this pass, the docs structure and GitHub repo were the real primary-source surface, not any formal whitepaper.