Coming from Ethereum

This document briefly highlights how Tetra differs from EVM‑based blockchains and what matters for Ethereum developers.

Main differences

• TetraChain uses its own TVM virtual machine (compatible with TON Virtual Machine), not EVM, so bytecode, opcodes, and tooling are different.

• TVM contracts interact through asynchronous messages; Ethereum contracts call each other synchronously inside one transaction.

• TVM has its own languages (Tolk, FunC, Fift, Tact, TVM Solidity)

Execution and accounts

• Every Tetra account can have code, data, and balance; execution is triggered by incoming messages.

• Read‑only get methods are executed off‑chain and cannot be called from other contracts.

• Tetra wallets are smart contracts that wrap signatures and send internal messages.

TVM vs EVM (short table)

Aspect	TetraChain (TVM)	Ethereum (EVM)
VM	TVM, own instruction set	EVM
Execution model	Asynchronous messages	Synchronous call tree
Accounts	Any account can have code + balance	EOAs vs contract accounts
Languages	Tolk, FunC, Fift, Tact, TVM Solidity	Solidity, Vyper
Compatibility	Not EVM‑compatible by default	Native EVM

Where to read more

For detailed guidance specifically for Ethereum developers, including TVM vs EVM and ecosystem differences, please use the link below

Coming from Ethereum - TON DocsTON Docs