ref-fvm
ref-fvm copied to clipboard
Reference implementation of the Filecoin Virtual Machine
This is a tracking issue for a proposal that has been made over in FIPs: https://github.com/filecoin-project/FIPs/discussions/379
When we do changes in lotus repo, related to FEVM, we should hide them behind feature flags. Reference in [Slack thread](https://filecoinproject.slack.com/archives/CP50PPW2X/p1662391040284279?thread_ts=1662201745.670769&cid=CP50PPW2X)
> The only remaining part is exposing the log level. I'd like to replace `debug::enabled` with `debug::log_level`. _Originally posted by @Stebalien in https://github.com/filecoin-project/ref-fvm/issues/173#issuecomment-1069404726_
The Filecoin network has several limits at different layers that hinder the installation of typical statically-linked Wasm code in a single message: - Mpool limit: 64KiB per message - Gossipsub...
We need to determine the Wasm bytecode limits for user-deployed actors. Assuming no internal block chunking, IPLD block limits may apply.
Even though we have prototyped a minimal actor deployment flow here: https://github.com/filecoin-project/ref-fvm/issues/444, we need a final design that takes into account aspects like: - How actor code CIDs will be...
The FVM has several operations that require knowledge of the links between IPLD blocks: - When a block is opened, the FVM needs to know what it points to, so...
The FVM must parse IPLD blocks created by actors for: - Validation. - State traversal. - Reachability analysis. However, the FVM must be able to charge for IPLD parsing/validation operations...
## Context The Ethereum blockchain has the concept of logs, which are events emitted from smart contracts during execution. Logs contain arbitrary data, and are annotated with zero to four...
I think we should remove the DeleteActor syscall. Or, if something actively prevents that, reduce its functionality to leave the top-level actor object in the state tree. The critical state...