ref-fvm
ref-fvm copied to clipboard
Reference implementation of the Filecoin Virtual Machine
We tested the following contract in Remix: contract OutputTest { function test() public returns (uint) { return 1; } function testView() public view returns (uint) { return 1; } function...
eta: 2024Q2 description: A series of additional incremental protocol upgrades (besides nv17) to move system functionality from privileged space to user space. The result will be a lighter and less...
eta: 2024Q1 description: Developers will be able to deploy custom smart contracts written in Rust, AssemblyScript, or Go, and compiled to WASM bytecode. SDKs, tutorials, and other developer materials will...
Upstream (https://github.com/paritytech/wasm-instrument) has seen recent development. While we've pretty much completely forked off, we should investigate the latest changes (looks like more accurate charging for functions) and consider backporting their...
1. CREATE/CREATE2 will fail at `maxCallDepth - 2` in some cases, and `maxCallDepth - 1` when resurrecting. 2. EXTCODE* will fail at `maxCallDepth`. 3. SELFDESTRUCT will fail at `maxCallDepth`.
When cargo fetches a dependency with git: 1. It'll fetch all submodules. 2. It won't cache them. This means we'll re-download the test vectors every time. Unfortunately, I really don't...
I.e., the tests in https://github.com/filecoin-project/ref-fvm/tree/fc6547afef2c258a96549438b6e5bcacb0f2d403/tools/solidity-tests. To do this, we'll need to make sure we can run these _quickly_. That'll likely require actor caching, at least, to avoid having to pay...
**Summary:** Benchmark the average _filecoin_ gas cost of EVM operations. While we can't tell users _exactly_ how much any operation will cost, we can give a general idea by benchmarking...
The `fvm` crate can be difficult to use natively from Rust for a few reasons, including: - The incompatibility of `fvm-2` and `fvm-3`, - the lack of semantic versioning, -...