Blockchain transaction types are the categories of on-chain activity — transfers, trades, swaps, staking actions, rewards, minting, and burning — that determine the accounting treatment, journal entry structure, and tax implications for each recorded event. Finance teams begin with this taxonomy because every downstream accounting decision depends on accurate transaction classification.
What Are the 7 Core Blockchain Transaction Types?
The 7 core blockchain transaction types are transfers, trades, swaps, staking actions, rewards, minting, and burning. As the foundational taxonomy within crypto fundamentals for finance teams, each type triggers a distinct accounting event with specific debit/credit rules, cost basis implications, and tax treatment.
The classification below represents the standard taxonomy used by crypto subledgers, accounting firms, and regulatory frameworks including the OECD Crypto-Asset Reporting Framework (CARF) and EU DAC8 directive.
| Type | On-Chain Action | Accounting Event | Cost Basis Impact |
|---|---|---|---|
| Transfer | Asset moves between addresses | No disposal (if same entity) | Basis carries forward |
| Trade | Fiat-to-crypto or crypto-to-fiat | Purchase or disposal | New basis (buy) or gain/loss (sell) |
| Swap | Crypto-to-crypto exchange | Disposal + acquisition | Realized gain/loss + new basis |
| Stake | Lock tokens in validator/protocol | Reclassification | Basis carries forward |
| Reward | New tokens received from protocol | Income recognition | FMV at receipt = new basis |
| Mint | New token created on-chain | Acquisition or income | Depends on context |
| Burn | Token permanently destroyed | Disposal or loss | Realized loss at FMV |
The 7 types listed above cover 95%+ of transaction volume for most organizations. Specialized types — approvals, delegations, wraps/unwraps, and governance votes — exist as subtypes within these categories.
How Do Transfers Differ from Trades in Crypto Accounting?
Transfers differ from trades in crypto accounting because transfers move assets between addresses without changing ownership, while trades exchange one asset type for another — creating a disposal event that requires gain/loss calculation.
Transfers
Transfers occur when the same entity sends crypto from one wallet to another wallet under the same entity’s control. Common transfer scenarios include:
- Moving Bitcoin from a Coinbase account to a cold storage wallet
- Transferring Ethereum from a hot wallet to a Fireblocks vault
- Sending USDC between two wallets within the same organization
Transfers are tax-neutral events. The cost basis of the transferred asset carries forward to the receiving address. The gas fee paid for the transfer is recorded as an operating expense or added to the cost basis of the transferred asset, depending on the organization’s accounting policy.
Trades
Trades involve exchanging one asset for another — either fiat-to-crypto (purchase), crypto-to-fiat (sale), or crypto-to-crypto (swap). Every trade triggers a disposal of the outgoing asset and requires calculating the realized gain or loss based on the cost basis method (FIFO, LIFO, HIFO, or Specific Identification).
What Is the Accounting Treatment for Token Swaps?
The accounting treatment for token swaps follows a two-leg disposal-and-acquisition model: the outgoing token is disposed of at fair market value (FMV), generating a realized gain or loss, and the incoming token is acquired at FMV, establishing a new cost basis.
A token swap on a decentralized exchange such as Uniswap generates a single on-chain transaction containing both legs. The crypto subledger decodes the swap event from the smart contract logs and splits the event into two accounting entries.
| Account | Debit | Credit |
|---|---|---|
| USDC Holdings | $4,000 | — |
| ETH Holdings | — | $2,000 |
| Realized Gain on Crypto | — | $2,000 |
The $2,000 realized gain represents the difference between the disposal proceeds (FMV at swap time) and the original cost basis. Swap fees (DEX trading fees + gas fees) reduce the net proceeds, lowering the realized gain.
How Are Staking Transactions Classified?
Staking transactions are classified in 3 phases: the initial stake (reclassification), the ongoing reward accrual (income recognition), and the unstake (reclassification reversal). Each phase triggers a distinct journal entry pattern.
Phase 1 — Stake (Lock)
Staking locks tokens in a validator or protocol smart contract. The tokens remain owned by the entity but are restricted. The accounting treatment reclassifies the asset from unrestricted to restricted holdings:
| Account | Debit | Credit |
|---|---|---|
| Staked ETH (Restricted) | $10,000 | — |
| ETH Holdings (Unrestricted) | — | $10,000 |
The cost basis carries forward from the unstaked position to the staked position. Staking itself is not a disposal event — no gain or loss is recognized at the time of staking.
Phase 2 — Rewards
Staking rewards are new tokens generated by the protocol and distributed to the staker. Reward tokens are recognized as income at fair market value (FMV) on the date of receipt. The FMV at receipt establishes the cost basis for future disposals.
Revenue classification depends on the entity’s business model: staking income, protocol revenue, or other income.
Phase 3 — Unstake (Unlock)
Unstaking reverses the reclassification journal entry, moving the asset from restricted back to unrestricted holdings. Unstaking is not a disposal event.
What Triggers a Minting Event and How Is Minting Recorded?
A minting event is triggered when a new token is created on-chain — either through protocol issuance, NFT creation, or smart contract deployment. The accounting treatment for minting depends on the context: acquisition (if the entity paid to mint), income (if the entity received minted tokens as compensation), or zero-cost basis (if the mint cost is negligible).
Three common minting scenarios exist:
-
NFT Minting — The entity pays a mint price plus gas fee to create a new ERC-721 or ERC-1155 token. The cost basis equals the mint price plus gas fee. The minted NFT is recorded as a digital asset acquisition.
-
Protocol Token Minting — The protocol mints new tokens as part of a vesting schedule, airdrop, or liquidity mining program. The recipient records the minted tokens as income at FMV on the date of receipt.
-
LP Token Minting — Depositing assets into a Uniswap or Aave liquidity pool mints LP tokens representing the deposited position. The LP token’s cost basis equals the FMV of the deposited assets. The token standard (ERC-20 for fungible LP tokens, ERC-721 for position NFTs on Uniswap V3) determines the valuation methodology applied to the minted position.
What Happens When Tokens Are Burned?
Token burning permanently removes tokens from circulation by sending tokens to an address with no private key (a “burn address”). The accounting treatment for a burn depends on whether the burn is voluntary (strategic token reduction) or involuntary (protocol-mandated).
Voluntary burns — The entity deliberately destroys tokens it holds. The burned tokens are derecognized from the balance sheet. A realized loss equal to the cost basis of the burned tokens is recorded, because no proceeds are received.
Involuntary or protocol burns — Certain protocols burn tokens as part of transaction processing (Ethereum’s EIP-1559 base fee burn) or governance mechanisms. These burns are not recorded as disposals by the transacting entity — the burned base fee is part of the gas cost, not a separate event.
| Account | Debit | Credit |
|---|---|---|
| Loss on Token Burn | $500 | — |
| Governance Token Holdings | — | $500 |
How Does Transaction Type Affect Reconciliation?
Transaction type directly affects reconciliation by determining the matching rules, validation criteria, and exception handling logic that the subledger applies to each record.
The reconciliation engine applies type-specific rules:
- Transfers — Internal transfer detection matches outgoing and incoming records across wallets using amount correlation, timestamp proximity, and address ownership. Unmatched transfers create reconciliation exceptions.
- Trades — Cross-source matching compares exchange trade records against on-chain settlement records. Discrepancies in trade amount, timestamp, or fee amount trigger manual review.
- Swaps — DEX swap reconciliation requires decoding smart contract events to extract the input token, output token, and effective exchange rate. Multi-hop routing and aggregator transactions add complexity.
- Staking/Rewards — Reward transactions are validated against protocol emission schedules. Missing rewards indicate unstaking events, slashing events, or data ingestion gaps.
- Gas fees — Gas fee tracking reconciles the fee amount recorded by the data source against the actual gas consumed on-chain. Fee discrepancies arise from failed transactions (gas consumed but transaction reverted) and EIP-1559 priority fee variations.
Rule-based categorization classifies each transaction type automatically, reducing manual categorization effort by 95%+ for organizations with consistent transaction patterns.
How Does Transaction Classification Flow into Journal Entries?
Transaction classification flows into journal entries through the journal entry mapping layer of the crypto subledger, where each transaction type maps to a predefined debit/credit template in the chart of accounts.
The mapping follows double-entry bookkeeping principles adapted for digital assets:
| Transaction Type | Debit Account | Credit Account |
|---|---|---|
| Buy (fiat → crypto) | Digital Asset Holdings | Cash / Bank |
| Sell (crypto → fiat) | Cash / Bank | Digital Asset Holdings |
| Swap (crypto → crypto) | Incoming Asset Holdings | Outgoing Asset Holdings |
| Transfer (same entity) | Destination Wallet | Source Wallet |
| Staking reward | Staked Asset Holdings | Staking Income |
| Gas fee (operating) | Network Fee Expense | ETH Holdings |
| Mint (purchase) | Digital Asset Holdings | Cash / ETH Holdings |
| Burn (voluntary) | Loss on Disposal | Digital Asset Holdings |
Actual journal entries include gain/loss calculations for disposals, fee allocations, and multi-currency conversion when the transaction currency differs from the entity’s functional currency.
The 8 transaction-to-account mappings in the table above form the foundation of the subledger’s journal entry automation.