Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FVM M2.1 incremental delivery plan #692

Closed
10 tasks done
raulk opened this issue Aug 8, 2022 · 7 comments
Closed
10 tasks done

FVM M2.1 incremental delivery plan #692

raulk opened this issue Aug 8, 2022 · 7 comments

Comments

@raulk
Copy link
Member

raulk commented Aug 8, 2022

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.

image

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.

@raulk raulk pinned this issue Aug 8, 2022
@ancjf
Copy link

ancjf commented Aug 16, 2022

This is great for ecosystems on Ethereum migrating to Filecoin. When can I run some test programs?

@dd45e640b42e6da7da96faee3996ef7c

This is great for ecosystems on Ethereum migrating to Filecoin. When can I run some test programs?

https://kb.factor8.io/en/docs/wallabynet

@dd45e640b42e6da7da96faee3996ef7c
Copy link

dd45e640b42e6da7da96faee3996ef7c commented Aug 27, 2022

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

@ancjf
Copy link

ancjf commented Sep 1, 2022

Thanks, this allows me to test the program as quickly as possible

@stebansaa
Copy link

stebansaa commented Sep 28, 2022

So do we have full RPC compatibility at this stage? Would like to test deploying a few contracts.

@raulk
Copy link
Member Author

raulk commented Oct 3, 2022

@stebansaa Yes, it's in early stages, so expect dragons! 🐉

@raulk
Copy link
Member Author

raulk commented Feb 26, 2023

Incremental delivery has been completed, and we have initiated the mainnet handoff procedure. FVM M2.1 (FEVM) will be on mainnet on March 14th.

@raulk raulk closed this as completed Feb 26, 2023
@Stebalien Stebalien unpinned this issue Feb 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants