> For the complete documentation index, see [llms.txt](https://docs.fluentlabs.xyz/learn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fluentlabs.xyz/learn/resources/devnet-changelog.md).

# Devnet Changelog

All notable changes to Fluent's devnets is documented in this section.

## Devnet Version 0 <a href="#devnet-version-0" id="devnet-version-0"></a>

*(Private)*

### Added: <a href="#added" id="added"></a>

* `rWasm` (reduced-Wasm) to generate a flattened binary representation of Wasm, ensuring backward compatibility with the Wasm instruction set.
* `Fluentbase` framework and Rust SDK designed for creating simple Wasm-based applications.
* `Fluent Network` client with support for Wasm-based apps.

### Unsupported: <a href="#unsupported" id="unsupported"></a>

* `Fluentbase` framework lacks support for floating-point operations.
* Standardization of code is pending; thus, passing block/tx context elements inside apps is currently not feasible.
* Doesn't support Solidity or Vyper for writing smart contracts.

***

## Devnet Version 1 <a href="#devnet-version-1" id="devnet-version-1"></a>

*(Priavte)*

### Added: <a href="#added-1" id="added-1"></a>

* Introduction of a new ABI codec to manage input/output parameters.
* Inclusion of input capabilities with block and tx context information (block hash, origin, caller, etc.).
* Full EVM compatibility with support for Solidity and Vyper contracts.

### Changed: <a href="#changed" id="changed"></a>

* Might partially break backward compatibility with the previous version because it affects ABI encoding and requires recompilation of all previously deployed smart contracts.

### Unreleased: <a href="#unreleased" id="unreleased"></a>

* Planned support for L1/L2 messaging between Ethereum testnet and the Fluent network.

***

## Devnet Version 2 <a href="#devnet-version-2-current" id="devnet-version-2-current"></a>

*(Current / Public)*

### Added <a href="#added-2" id="added-2"></a>

* Introduction of the Compatibility Contracts (CCs) providing support for forkless and upgradable Wasm and EVM environments. The CCs are extensible to additional execution runtimes like MoveVM and RISC-V in the future.
* L1/L2 messaging between Ethereum testnet and the Fluent network.
* The new version of the rWASM VM and compiler reducing compilation time, binary size, and execution time, while also addressing critical bug fixes.
  * It achieves 99% compliance with the official Wasm spec, with the exception of a few complex edge cases involving import tables and export globals that the execution environment cannot support.
* Interoperability between EVM and Wasm-based apps though the CCs.

### Changed <a href="#changed-1" id="changed-1"></a>

* Updated to the latest version of revm/reth.
* Introduced a new codec for ABI encoding.
* Revised the deployment scheme.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fluentlabs.xyz/learn/resources/devnet-changelog.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.