VeChain Docs
  • Welcome to VeChain
  • Blockchain Basics
    • Introduction to blockchain
    • Introduction to digital property
    • The evolution of the internet
  • Introduction to VeChain
    • About the VeChain blockchain
      • Consensus Deep Dive
      • Governance
    • Dual-Token Economic Model
      • VeChain (VET)
      • VeThor (VTHO)
    • Acquire VeChain Assets
    • Sustainability
  • Core Concepts
    • Networks
      • Thor Solo Node
      • Testnet
      • Mainnet
    • Nodes
      • Node Rewards Programme
    • Blocks
      • Block Model
    • Transactions
      • Transaction Model
      • Transaction Fees
      • Transaction Calculation
      • Meta Transaction Features
        • Transaction Uniqueness
        • Controllable Transaction Lifecycle
        • Clauses (Multi-Task Transaction)
        • Fee Delegation
          • Multi-Party Payment (MPP)
          • Designated Gas Payer (VIP-191)
        • Transaction Dependency
    • Block Explorers
    • Wallets
      • VeWorld
        • User Guide
          • Setup
          • Wallet
          • Signing
          • Activities
          • Settings
        • FAQ
      • Sync2
        • User Guide
          • Setup
          • Wallet
          • Signing
          • Activities
          • Settings
        • FAQ
      • Sync
        • User Guide
          • Wallet
          • Ledger Device
          • Browser dApps and web
          • Interact with dApps
          • Activities
          • Settings
          • Report an Issue
          • Contributing
        • FAQ
    • EVM Compatibility
      • VeChain Modifications
      • Methodology
      • Test Coverage
        • Gas model
        • Raw transaction
        • hardhat specific
          • Ganache failures
          • evm_increaseTime
        • Failures in constructor
        • eth_sign
        • Contract address prediction
        • BadBeacon proxy address at 0x1
      • How to Recreate
      • Additional Information
        • Using Governance Contracts
        • ERC1820/ERC777 Testnet
        • Delegate Options
    • Account Abstraction
      • UserOperation
      • Bundler
      • EntryPoint Contract
      • Account Factory Contract
      • Paymaster Contract
    • Token Bound Accounts
  • How to run a node
    • Nodes
    • How to run a Thor Solo Node
    • Custom Network
    • Connect Sync2 to a Thor Solo Node
  • Developer Resources
    • Getting Started
    • How to build on VeChain
      • Connect to the Network
      • Read Data
        • Read Blocks
        • Read Transactions
        • Read Accounts
        • States & Views
        • Events & Logs
        • VET Transfers
      • Write Data
        • Transactions
        • Fee Delegation
      • Listen to Changes
        • Events
        • VET Transfers
        • Transactions
        • Blocks
        • Beats
      • Build with Hardhat
      • Utilities
        • BigInt and Unit-Handling
        • Name Service Lookups
    • Example dApps
      • Buy me a Coffee
      • Token Bound Accounts
      • PWA with Privy and Account Abstraction
    • EVM Compatibility for Developers
      • Key Architectural Differences and Optimizations
      • Practical Implications for Developers: Key Considerations
      • RPC Methods (Detailed Breakdown)
      • Frequently Asked Questions (FAQs)
      • VeChain Blockchain Specifications
      • Key Differences Between VeChain and Ethereum (Summary)
      • Best Practices for Developing on VeChainThor
    • How to verify Address-Ownership
      • Next.js Session Verification
    • Debug Reverted Transactions
    • Account Abstraction
    • VIP-191: Designated Gas Payer
      • How to Integrate VIP-191 (I)
      • How to Integrate VIP-191 (II)
      • How to Integrate VIP-191 (III)
    • Index with Graph Node
      • Setup with Docker
      • Index with OpenZeppelin
        • Create Subgraph Project
        • Configure Contracts
        • Deploy Subgraph and start Indexing
        • Track Subgraph Indexing
        • Access Subgraph
        • Update Subgraph
    • SDKs & Providers
      • SDK
        • Architecture
        • Accounts
        • Bloom Filter
        • Certificates
        • Contracts
        • Cryptography
        • Debug
        • Encoding
        • Polls
        • Subscriptions
        • Thor Client
        • Transactions
      • Thor DevKit
        • Installation
        • Usage
          • Cryptography
          • Accounts
          • Encoding
          • Transactions
          • Certificates
          • Bloom Filter
      • DApp Kit
        • v2
          • Installation
          • React
            • Installation
            • Usage
          • Vanilla JS
            • Installation
            • Usage
          • Core
            • Installation
            • Usage
          • Theme Variables
          • i18n
        • v1
          • Installation
          • React
            • Installation
            • Usage
          • Vanilla JS
            • Installation
            • Usage
          • Core
            • Installation
            • Usage
          • Theme Variables
          • i18n
          • Node Polyfills
          • V0 to V1
        • v0
          • Installation
          • Usage
          • React
            • Installation
            • Usage
          • Vanilla (UI)
            • Installation
            • Usage
          • Styles (UI)
          • i18n
      • DevPal
      • Web3-Providers-Connex
        • Installation
        • Usage
      • Connex
        • Installation
        • API Specification
    • Frameworks & IDEs
      • Hardhat
      • Remix
    • Built-in Contracts
    • VORJ
    • Useful Links
  • How to contribute
Powered by GitBook
On this page
  • What is Ethereum?
  • What is the EVM?
  • Why is EVM compatibility important?
  • VeChain EVM Compatibility

Was this helpful?

  1. Core Concepts

EVM Compatibility

Ethereum virtual machine (EVM) compatibility with the VeChainThor blockchain

What is Ethereum?

Ethereum was the first programmable blockchain. Ethereum programability is achieved through the Ethereum Virtual Machine (EVM). Before Ethereum the only use case for blockchain was the Bitcoin blockchain and the use of its native asset bitcoin as a form of digital money. The creation of Ethereum and the introduction of programability extended the use case of blockchain technology beyond digital money into use cases such as decentralized financial services (DeFi), games, social networks, the creation of non-fungible tokens (NFTs) and other applications that respect your privacy and cannot censor you.

What is the EVM?

The Ethereum Virtual Machine (EVM) is a key component of the Ethereum blockchain. The EVM can be considered the computational engine of the Ethereum blockchain. The EVM manages and maintains the state of the blockchain. For this reason it is often referred to as the "world computer". The EVM enables programability to exist and function on the Ethereum blockchain.

Why is EVM compatibility important?

EVM compatibility is important because it enhances interoperability, developer adoption, network effects and code reusability across the entire blockchain ecosystem. This creates a more vibrant and collaborative environment for building decentralized applications and services.

EVM compatibility is important for several reasons:

  • Interoperability: EVM compatibility enables different blockchain networks to communicate and interact with each other. This allows developers to build decentralized applications that can be used across multiple blockchain networks, which enhances the interoperability of the entire blockchain ecosystem.

  • Developer Adoption: EVM compatibility makes it easier for developers to create and deploy smart contracts on the Ethereum blockchain and other EVM compatible blockchains. This is because developers can use familiar programming languages and tools which reduces the learning curve and makes it easier to build decentralized applications.

  • Network Effects: EVM compatibility creates network effects, which means that as more blockchain networks become EVM compatible the value and utility of the blockchain ecosystem as a whole increases. This creates a virtuous cycle that attracts more developers and users to the network, which further enhances its value.

  • Code Reusability: EVM compatibility allows developers to reuse code and smart contracts across multiple blockchain networks, which reduces development time and costs. This is particularly important for enterprise applications, where there may be multiple blockchain networks involved.

VeChain EVM Compatibility

VeChain is EVM compatible. VeChain originated as a fork of Ethereum and the EVM and maintains a high level of EVM compatibility despite some modifications that were introduced into VeChain to make it more enterprise friendly, scalable and sustainable.

PreviousFAQNextVeChain Modifications

Last updated 10 months ago

Was this helpful?