> For the complete documentation index, see [llms.txt](https://lgcy-network.gitbook.io/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lgcy-network.gitbook.io/welcome/lgcy-virtual-machine/workflow.md).

# Workflow

The compiler first translates the Solidity smart contract into bytecode that is readable and executable on the LVM. The LVM then processes data through opcode, which is equivalent to operating the logic of a stack-based finite state machine. Finally, the LVM accesses blockchain data and invokes External Data Interface through the Interoperation layer.

![](/files/gpjKxwXp5Px7Q87kAbfH)

**PERFORMANCE**

**LIGHTWEIGHT ARCHITECTURE**

LVM adopts a lightweight architecture which reduces resource consumption to guarantee system performance.

**ROBUST**

LGCY transfers and smart contract execution cost bandwidth points only, instead of LGCY, which exempts LGCY from being attacked. Bandwidth consumption is predictable and static since each computational step cost is fixed. This will become LFUEL consumption after LGCY Mainnet is enacted.

**HIGH COMPATIBILITY**

LVM is compatible with EVM and TVM, and will be compatible with more mainstream VMs in the future. This way, all smart contracts on EVM and TVM are executable on LVM.

**LOW COST**

Due to LVM’s bandwidth setup, development costs are reduced, and developers can focus on the logic development of their contract code. Because of our major focus on supporting developers—especially startup projects who often lack funds—the low cost model LGCY offers will greatly help establish new and many dApp projects on the blockchain. LVM also offers all-in-one interfaces for contract deployment, triggering and viewing to offer the convenience for developers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://lgcy-network.gitbook.io/welcome/lgcy-virtual-machine/workflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.