FVM M2.1 incremental delivery plan
raulk opened this issue · 7 comments
Context
The FVM team has decided to deliver FVM M2.1 (FEVM) in an incremental fashion. This allows the Filecoin community:
- continuously experiment with FEVM, as it's being built
- test existing Ethereum tooling (e.g. MetaMask, Hardhat, Remix, Foundry, Truffle, etc.)
- adapt existing Filecoin tooling by integrating it with FEVM (e.g. wallets, explorers, etc.)
- test the compatibility of existing Ethereum audited, battle-tested contracts by deploying them to FEVM
- identify and raise bugs as they're being encountered
Plan
This is a draft plan -- it is subject to change and refinement as we move along.
FEVM releases are named after minerals under the different degrees of the Mohs mineral hardness scale. We find this framework is appropriate because it establishes progression, provides plenty of attractive codenames to adopt, and aligns with the mental model of maturity/hardness increasing over time as the feature set becomes denser.
We are not committing to having 10 releases exactly; we may add intermediate releases, merge some, or skip some entirely, as work progressing.
Upcoming testnets
We are also working with testnet infrastructure providers to set up a dedicated testnet so that early builders, and other curious beings, can get their hands dirty as features are delivered.
This testnet would be the spiritual counterpart to Wallaby (Wasm testnet), but for FEVM. We expect it more unstable and bleeding edge, as FEVM is the active focus of development. We expect frequent resets, potentially even weekly.
This is great for ecosystems on Ethereum migrating to Filecoin. When can I run some test programs?
This is great for ecosystems on Ethereum migrating to Filecoin. When can I run some test programs?
Upcoming testnets
We are also working with testnet infrastructure providers to set up a dedicated testnet so that early builders, and other curious beings, can get their hands dirty as features are delivered.
This testnet would be the spiritual counterpart to Wallaby (Wasm testnet), but for FEVM. We expect it more unstable and bleeding edge, as FEVM is the active focus of development. We expect frequent resets, potentially even weekly.
@raulk i assume we are "just doing it" on wallaby as i write this? I'll adjust the docs a bit with the selenium reset on tuesday
ref: https://factor8solutions.slack.com/archives/C03KGBTJ0BY/p1661444672938659
Thanks, this allows me to test the program as quickly as possible
So do we have full RPC compatibility at this stage? Would like to test deploying a few contracts.
@stebansaa Yes, it's in early stages, so expect dragons! 🐉
Incremental delivery has been completed, and we have initiated the mainnet handoff procedure. FVM M2.1 (FEVM) will be on mainnet on March 14th.