Asset research / Bitcoin

Bitcoin class action guide

Understand Bitcoin records, connect them to account history, and keep the technical facts separate from legal conclusions.

Define the matter before the asset

Researching a Bitcoin class action starts with the particular business, product, service, or event. Holding bitcoin does not by itself establish a claim. A network name is not a substitute for identifying the relevant legal parties, alleged conduct, dates, and official documents.

Keep two questions separate: what do your records show, and what legal requirements apply to the matter? The first can support the second, but it cannot answer it on its own.

Read the technical record with context

A bitcoin transaction can involve multiple inputs and outputs. Some outputs can represent change. Preserve the transaction identifier and the specific output or account entry you are discussing instead of treating a visible total as a personal payment.

The complete Bitcoin records guide develops a practical workflow for identifying entries, preserving original files, and documenting what remains uncertain.

Start a concise evidence index

  • Transaction identifier.
  • Relevant output.
  • Exchange account entry.
  • Original timestamp.
  • Unit and network.
  • The statement, receipt, email, or export that connects the activity to your account.
  • A note of what each record supports and what it does not establish.

Include the account history

Public network records do not necessarily explain the business relationship behind an interaction. Exchange trades, account credits, customer communications, and internal platform activity can require separate records. Preserve account exports as originally downloaded, then create a clearly labeled working copy for sorting and annotation.

Write down the original time zone and any normalization you apply. Separate fees from principal amounts. When a record is missing, document the gap and the steps already taken to locate it.

Keep the file relevant and private

Collect information for the question you need to answer. Avoid sharing unrelated transaction history, account identifiers, or personal details more widely than required. Never include a private key or recovery phrase in a recordkeeping file intended for a third party.

Use the claim documents checklist to organize the file, then compare it with the verified official instructions. Read the class action overview for the distinction between transaction evidence and the legal scope of a case.

Source & scope. The technical guidance draws on the network’s own documentation. Legal applicability remains a separate question. Bitcoin Developer Guide: Transactions.