What should a crypto record capture?
Keep enough information to reconstruct what moved, where it moved, what it cost, and why it happened.
Crypto Record Keeping Guide
Keep The Record Before The Detail Disappears.
Do not wait for a missing record to become a problem. Capture the event while the platform screen still shows it.
Keep enough information to reconstruct what moved, where it moved, what it cost, and why it happened.
- 01EVENT
- 02PLATFORM
- 03AMOUNT
- 04FEE
- 05IDENTIFIER
- 06PURPOSE
- 07RECORD
Direct answers
Evidence first. Interpretation later.
One record or one spreadsheet dump?
Use one record per event. Mixing unrelated transfers into a single note makes later reconstruction harder.
What must never go in the record?
Do not store seed phrases, private keys, passwords, OTP codes, full card numbers, or API secrets.
When should I reconcile?
Review monthly for active accounts, and after any large transfer, new platform, wallet migration, or closed account.
One record per event
Capture the fields that make reconstruction possible.
Date and time
Anchor the event to the platform or wallet timestamp.
Platform
Exchange, wallet, swap, casino, merchant, mining, or P2P venue.
Asset and amount
Record the asset, amount, and fiat reference only when captured at the time.
Fee
Source, withdrawal, swap, or network fee shown for that event.
Network
The network used for the blockchain transfer or deposit.
Identifier
Transaction hash, order ID, invoice, or platform reference.
Destination
Where funds went, without storing recovery or login secrets.
Purpose
Short note explaining the reason for the movement.
Record categories
Cover every place crypto actually moves.
Exchange records
Deposits, withdrawals, trades, conversions, fees, and account exports.
Wallet transfers
Sends, receives, network, fee, destination context, and hash.
Swaps and trades
Input asset, output asset, provider, quoted versus actual result, and reference.
P2P orders
Agreement, payment method, limited counterparty reference, timeline, and receipts.
Casino funding
Deposit and withdrawal references, asset, network, account context, and hash.
Mining
Reward timestamp, amount, fee or maintenance note, and payout reference.
Loans
Collateral, borrowed amount, interest, repayment, and liquidation events if any.
Merchant payments
Invoice or order ID, provider, amount, network, status, receipt, and settlement.
What not to store
A ledger is not a password manager.
Seed phrase or recovery phrase
Keep this out of transaction notes, exports, and shared folders.
Private key
Keep this out of transaction notes, exports, and shared folders.
Password or master password
Keep this out of transaction notes, exports, and shared folders.
OTP or authenticator codes
Keep this out of transaction notes, exports, and shared folders.
Full card number
Keep this out of transaction notes, exports, and shared folders.
API secret
Keep this out of transaction notes, exports, and shared folders.
Records may also be needed for accounting or tax reporting under the rules that apply to the user.
Supporting tools
Generators, calculators, and hubs that feed the ledger.
P2P Deal Proof GeneratorPreserve deal terms, references, timeline, and receipt checklist.Before You Send CryptoVerify destination details before the irreversible send.On and Off Ramp HubConnect cash-access events to the same ledger habit.Best Crypto WalletsSeparate custody decisions from the record of what moved.Mining BoxTrack mining costs and BTC output with clear payout references.Merchant BoxKeep invoice, payment, and settlement identifiers together.Borrow vs SellRecord collateral, loan, and repayment events separately from sales.Security ToolkitProtect access to the accounts that hold the source exports.
FAQ
Record-keeping questions
What belongs in a crypto transaction record?
Record date and time, platform, transaction type, asset, amount, fee, network, identifier, destination context, purpose, and related receipt or statement location.
Which events deserve their own record?
Exchange deposits and withdrawals, blockchain transfers, swaps, trades, P2P orders, casino funding, mining rewards, crypto-backed loans, and merchant payments.
What should I never store in a record file?
Never store seed phrases, private keys, passwords, OTP codes, full card numbers, or API secrets. Those belong in dedicated security controls, not a transaction ledger.
How should I handle missing history?
Export what remains, list known accounts and wallets, match transfers by hash and timestamp, preserve support records, and mark unresolved fields as missing instead of inventing them.
Are records only for taxes?
No. Records help reconstruct transfers and costs later. Records may also be needed for accounting or tax reporting under the rules that apply to the user.
Final record action board