raulk
raulk
Right now it's pretty trivial to lie to an AutoNAT client by reporting incorrect dialback results. We should register a Notifee and track incoming connections when a dialback is requested,...
See https://github.com/filecoin-project/fvm-evm/blob/main/shared/src/bytecode.rs#L15.
## Goal To allow early experimenters to get an initial impression of running FEVM contracts on Filecoin. Only basic contracts will be supported at this stage, i.e. contracts that are...
## Current situation - Docs on precompiled contracts: https://www.evm.codes/precompiled - [evmodin](https://github.com/vorot93/evmodin) (implementation that fvm-evm is currently based on) is **agnostic** of precompiles. - [Akula](https://github.com/akula-bft/akula) (Ethereum client using evmodin, built by...
## Context and motivation In order to ship the EVM runtime as a built-in actor, the easiest solution is to place the code inside the builtin-actors repo so that its...
## Motivation Foreign runtimes (e.g. EVM) make assumptions about the addressing scheme. Furthermore, existing workloads deployed on those runtimes (e.g. smart contracts on Ethereum) make further assumptions, as is the...
## 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...
ARM64 architecture wasn't the problem in https://github.com/filecoin-project/ref-fvm/issues/599, the ancient Linux kernel was. However, we should run unit, integration and conformance tests (as well as the build, obviously) on CI on...
(For M2.2) Besides `invoke` we are adding new entrypoints to actors to support [account abstraction](https://github.com/filecoin-project/FIPs/discussions/388) and updatable actors. Both the FVM and clients will need to make a quick determination...
## Context For M1 (nv16), we are going with unlimited max pages given that the system can only run trusted logic via builtin system actors. However, it's not clear what...