Starknet — Cairo VM, native account abstraction
Starknet is not EVM — it runs the Cairo VM with first-class account abstraction. Different decoder, same audit-trail discipline.
Starknet's design choices put it apart from the other Ethereum zk-Rollups. The Cairo VM is purpose-built for STARK proofs rather than EVM-equivalent. Every account is a smart-contract account by default — no EOA-vs-SC distinction. Gas can be paid in STRK or ETH. The bridge to Ethereum mainnet uses zk-proof finality (typically 4–8 hours). For a finance team, the practical implication is that Starknet activity needs its own decoder path, but the accounting outputs match the rest of the EVM rollups.
What's tracked on Starknet
STRK and ETH transfers
Native dual gas-token model — STRK or ETH per transaction.
Cairo contract calls
Decoded against the contract's Cairo ABI.
Native account abstraction
Multi-sig, social recovery, and session-key wallets are first-class.
STRK staking
Validator staking with per-epoch reward accrual (post-staking-launch).
Ekubo, Avnu, JediSwap
Starknet DeFi positions with realized-gain tracking.
Starknet accounting questions
Why is Starknet different from zkSync Era?
zkSync Era is EVM-equivalent — Solidity bytecode runs natively. Starknet uses Cairo, which requires re-compiling Solidity contracts via Warp or writing Cairo directly. The accounting outputs are equivalent; the ecosystem of contracts is different.
Can I pay gas in STRK or ETH?
Both. The transaction declares its fee token. We track per-transaction with the right denomination.
Other chain coverage and tax guides relevant to this network.
Book Starknet the right way
Free during Alpha. Connect a wallet, see every transaction reconciled to journal entries.