Linea — the ConsenSys zk-EVM with MetaMask defaults
Linea is the ConsenSys-built zk-EVM, and it's the L2 most MetaMask users hit when they tap "Switch Network." We cover it like any other EVM L2.
Linea ships full EVM-equivalent execution with zk-proof finality. From an accounting perspective it behaves like Ethereum mainnet — same Solidity, same ABIs, same DeFi protocols deployed on the chain (Aave, Lynex, ZeroLend) with mostly identical decoders. The only L2-specific items to track are the bridge events (deposit and withdraw), the slightly different fee structure (L1 data cost + L2 execution cost broken out), and the LINEA token allocation when it ships.
What's tracked on Linea
ETH and ERC-20 transfers
Same EVM coverage as Ethereum mainnet.
L1 ↔ Linea bridge
zk-proof bridge with typically 12–24 hour settlement.
Aave on Linea, Lynex, ZeroLend
DeFi positions tracked end-to-end.
MetaMask Snaps activity
Snap-mediated transactions (where MetaMask is the wallet) carry the same audit trail.
Common Linea transaction patterns we classify
- Send / receive ETH (Linea)
- ERC-20 transfer on Linea (in / out)
- Linea bridge deposit (Ethereum → Linea)
- Linea bridge withdrawal (Linea → Ethereum)
- Token approval (gas only, no balance change)
- Aave V3 on Linea supply / withdraw / borrow / repay
- Lynex swap or liquidity position
- ZeroLend supply / borrow
- Velocore swap or LP position
- EchoDEX swap
- NFT mint or transfer (ERC-721 / ERC-1155)
- MetaMask Snap-mediated transaction
What changes when you book Linea
L2 fees have two components that must be broken out
Linea transaction fees consist of an L2 execution cost plus an L1 data cost (the fee Linea pays to post compressed transaction data to Ethereum mainnet). Both components appear in the transaction receipt. Wag3s breaks them out per transaction, allowing you to book them against different accounts if your policy treats L1 settlement costs differently from L2 compute costs.
Bridge timing creates an in-transit balance
Deposits from Ethereum to Linea take minutes to appear on the L2 after the L1 transaction confirms. Withdrawals from Linea back to Ethereum involve proof verification, which can take several hours. Wag3s tracks the in-flight state for both directions so your balance sheet does not show an unexplained deduction while assets are in transit.
Linea is EVM-equivalent — existing Ethereum decoders apply unchanged
Because Linea achieves full EVM equivalence (not just EVM compatibility), Solidity contract ABIs compiled for Ethereum work identically on Linea. This means Wag3s applies the same DeFi protocol decoders as Ethereum mainnet, with no reinterpretation needed. Teams migrating activity from Ethereum to Linea see consistent classification logic across both chains in the same workspace.
Linea accounting questions
Is Linea different from zkSync Era?
Linea is full EVM-equivalent (Solidity bytecode runs natively); zkSync Era requires its own zk-EVM compilation flow. From an accounting perspective both produce equivalent outputs — same transaction shapes, same DeFi protocols.
Are MetaMask-routed transactions different on Linea?
No — MetaMask is just the wallet UI. The on-chain transaction is the same as any EVM transaction. We decode it the same way.
How does Wag3s handle cross-L2 transfers between Linea and other rollups?
Assets bridged between Linea and another L2 (e.g. via a third-party bridge like Hop or Across) are treated as intra-entity transfers with cost-basis continuity — no realised gain — as long as both addresses belong to the same entity in your Wag3s workspace. Bridge fees are booked as an operating expense on the transfer date.
Other chain coverage and tax guides relevant to this network.
Book Linea the right way
Free during Alpha. Connect a wallet, see every transaction reconciled to journal entries.