> For the complete documentation index, see [llms.txt](https://envida-protocol.gitbook.io/envida/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://envida-protocol.gitbook.io/envida/blockchain-architecture/runtime-environment.md).

# Runtime Environment

The Application Logic

<figure><img src="https://lh5.googleusercontent.com/cyWSP3ygfGuazRj4PkBTKM_f4R1KXzH_OavPGKfKFK7ckrDIofBWO4e-yDI5SNSVQpzY80TMmQ5hhrxskzcRqtOf1DiAYSvUdTcrM6_XM7GNM76EYpFH67GdzhacYG1siMXFdBOsNZL73Uk6fieQSDLe_A" alt=""><figcaption></figcaption></figure>

Each SugarFunge node contains a runtime. The runtime contains the business logic of the chain. It defines what transactions are valid and invalid and determines how the chain's state changes in response to transactions. In SugarFunge the runtime code is compiled to Wasm to facilitate runtime upgrades and becomes part of blockchains storage state. Developers can run the pre-designed SugarFunge Node and configure its genesis block.

<br>