Twitter: HANA EVM

Abstract

HANA EVM is an Ethereum virtual machine on Sui that enables dApp developers to use Ethereum tooling to scale and get access to liquidity on Sui.

Ethreum is the most dominant infrastructure for dApp developers and end-users, while the progress of the Move ecosystem, including Aptos and Sui, will be remarkable.

HANA EVM is a cross-chain solution that allows dApp developers to access the advantages of Sui. It enables full compatibility with Ethereum on Sui.

Moreover, unlike traditional EVM compatibility, our solution is synchronous thanks to EVM-as-a-contract architecture and the transaction format powered by Move language.

This opens up new kinds of decentralized applications and user experiences. EVM-compatible applications and Aptos-powered applications magically coexist in one blockchain, enabling both ecosystems to flourish in a co-dependent manner.

The solution supports all tools available in the Ethereum ecosystem — MetaMask, Truffle, Hardhat, Remix, etc. also, allows any Ethereum application to be run on Sui without any changes to its codebase, including UniSwap, SushiSwap, Aave, and Curve.

Architecture

The functionality of EVM on Sui is to host EVM byte code execution environment on top of Sui’s Move language runtime. Before going deep, as a premise, we stress that it’s not layer 2 or side chain. The consensus and security of our EVM state is achieved by the underlying Sui blockchain. We build a smart contract that does state transition following EVM rules. The entire EVM state is stored in the contract storage. Therefore the primary jobs that our EVM performs are simplified to:

  1. State transition
  2. Exposing EVM compatible interface.

Unlike rollups and sidechains, EVM state isn’t stored in the form of commitment to an external source of the state: literally, the whole state data, for example, account states and block info, reside in the smart contract storage deployed on Sui. This smart contract emulates EVM and receives transaction messages from users and interprets them. Finally, it performs state transitions. Gas cost calculation and fee deduction are done natively by Sui Core, making all of them out of our concern.

The rationale behind this architecture is not just to simplify the architecture but rather to freely borrow the security of the native chain, Sui. The Crypto economy has expanded rapidly as many independent chains developed their interoperability gadget. However, most of the interoperability solutions depend on centralized and notoriously complex bridging mechanisms that have been long accused of their operators-reliant security. Also, intricate bridging contract is suffering from critical bugs that have been exploited repeatedly, resulting in the significant loss of locked assets. This is against the philosophy of most cryptopians who treasure trustless, self-sovereign, and censorship-resistant programmable assets.

As briefly mentioned, because our EVM is built natively on top of Sui layer one, it’s inherently a trustless EVM execution environment, where no trusts in middlemen are present and purely the code being deployed alone is and will be the law.

From technical perspective, our EVM comprises of:

  1. EVM execution environment
  2. EVM compatible API proxy

EVM execution environment