How It Works
This page provides a high-level overview of how Axion coordinates communication between dApps, Polyglot and AVM.
AVM's transaction lifecycle
When a smart contract is deployed
It goes through a polyglot which check and verify what language is used in smart contract.
Polyglot service provide.
Gas usage estimate for tx execution.
If solidity is used then its code is executed as a evm code inside AVM
Its then passed to AVM.
Unwraps the tx and checks the user's signature
Loads the EVM state, including account data and the smart contract's code, from Axion's storage
Executes the tx inside AVM
A corresponding AVM receipt is generated.
Updates Axion's state to reflect the new state
This completes the tx request.
Last updated