Skip to main content
Back to Home
Transparency

Statement Methodology & Definitions

How crypto statements are generated using public blockchain data

Overview

This statement is generated using publicly available blockchain data retrieved in read-only mode. No private keys, signing permissions, or wallet access are required. All data is sourced directly from public blockchain networks.

Data Sources

Source: Public blockchain data (read-only access)

Networks Supported:

  • Bitcoin — Native BTC transactions
  • Ethereum — ETH and ERC-20 tokens (including USDC, USDT)

Data is retrieved from public blockchain explorers and node APIs in read-only mode. No custodial or exchange data is included.

Balance Definitions

Opening Balance

The wallet balance immediately prior to the selected start date. This represents the confirmed balance at the end of the previous period.

Closing Balance

The wallet balance at the end of the selected period, after all transactions and network fees within the period have been applied.

Balance Reconciliation

Opening Balance + Total Inflows − Total Outflows − Network Fees = Closing Balance

Transaction Processing

Ordering: Transactions are ordered chronologically based on blockchain timestamps (block time).

Network Fees: Network fees (gas fees for Ethereum, transaction fees for Bitcoin) are shown as separate line items and deducted from balances.

Contract Interactions (Ethereum): For Ethereum-based assets, token deposits and withdrawals may involve smart contract calls. Fee adjustments are applied where necessary to avoid double-counting.

All transactions are included based on confirmed blockchain data. Pending or unconfirmed transactions are excluded.

Fiat Valuation

Historical Pricing: Fiat values (GBP, USD, EUR, AED, INR) are estimated using historical market pricing data from third-party APIs where available.

Coverage: Pricing coverage may be complete or partial depending on asset, network, and date range.

Limitations: Fiat valuations are for informational purposes only and do not constitute financial or tax advice. Actual market prices may vary.

Timezone & Dates

Timezone: All timestamps are displayed in UTC (Coordinated Universal Time) unless otherwise specified.

Date Format: Date formatting may vary based on selected statement format (International, UK, US, EU, UAE) but does not affect calculations or included transactions.

Statement Format

Statements can be generated in multiple formats (International, UK, US, EU, UAE) which control:

  • Date formatting (YYYY-MM-DD, DD/MM/YYYY, MM/DD/YYYY)
  • Minor wording differences (e.g., "Closing Balance" vs "Ending Balance")

Format selection affects presentation only and does not change calculations, included transactions, or statement content.

Scope & Limitations

Single Wallet, Single Asset: Each statement covers one wallet address and one asset (e.g., BTC, ETH, USDC, or USDT) per statement period.

Self-Custody Only: Statements are designed for self-custody wallets (e.g., MetaMask, Ledger, hardware wallets). Exchange and custodial wallets are not supported.

Maximum Period: Statements can cover up to 5 years of transaction history.

Transaction Volume: For accountant readability, statements are limited to 2,500 transactions per period. High-activity wallets (lifetime activity above 50,000 transactions) are not supported as they typically belong to exchanges or service providers rather than personal users.

Important Information

Not Tax Advice

This statement is provided for informational purposes only and does not constitute tax, legal, accounting, or financial advice. Consult a qualified professional for guidance on your specific situation.

No Regulatory Approval

This service is not regulated, approved, or endorsed by any financial authority, tax authority, or government agency. Generated statements are not official documents.

Acceptance

We do not claim or guarantee that banks, accountants, auditors, or any other third parties will accept these statements. Acceptance is at the sole discretion of the recipient.

User Responsibility

Users are responsible for verifying the accuracy of generated statements and ensuring compliance with applicable laws and regulations in their jurisdiction.

Questions?

This methodology is provided for transparency and clarity. For technical questions about statement generation, please review the documentation or return to the homepage.

Last updated: January 2026