| description |
|---|
A list of frequent asked questions about FVM, FEVM and how to build on Filecoin network. |
Here’s a collection of general FAQs that the team has gathered. If you are looking for more technical FAQs, please head to Filecoin Community Discussion.
The FVM (Filecoin virtual machine) enables developers to write and deploy custom code to run on top of the Filecoin blockchain. This means developers can create apps, markets, and organizations built around data stored on Filecoin.
FVM allows us to think about data stored on Filecoin differently. Apps can now build a new layer on the Filecoin network to enable trading, lending, data derivatives, and decentralized organizations built around datasets.
FVM can create incentives to solve problems that Filecoin participants face today around data replication, data aggregation, and liquidity for miners. Beyond these, there is a long tail of data storage and retrieval problems that will also be resolved by user programmability on top of Filecoin.
Aptos is a Move-based L1 chain, whereas FVM is a WASM runtime on the Filecoin chain. The latter comes with an EVM right of the box; the former does not. The FVM also supports programmable storage with deals on Filecoin.
The FVM operates on blockchain state data — it does not operate on data stored in the Filecoin network. This is because access to that data depends on network requests, an unsealed copy’s availability, and the SPs’ availability to supply that data.
Access and manipulation of data stored in the network will happen via L2 solutions, for example, retrieval networks or compute-over-data networks, e.g., Saturn or CoD.
Unlike other EVM chains, FEVM specifically allows you to write contracts that orchestrate programmable storage. This means contracts that can coordinate storage providers, data health, perpetual storage mechanisms, and more. Other EVM chains do not have direct access to Filecoin blockchain state data.
An actor is code that the Filecoin virtual machine can run. Actors are also referred to as smart contracts.
Built-in actors are code that come precompilied into the Filecoin clients and can be run using the FVM. They are similar to Ethereum precompiles.
Having storage contracts as a native primitive open to smart contract developers. Reduce costs of writing to storage from an EVM smart contract to a separate storage service.
FEVM allows Solidity developers to easily write/port actors to the FVM using the tools that have already been introduced in the Ethereum ecosystem.
Applications that natively make use of storage contracts. Perpetual storage contracts, Data DAOs, etc.
Perpetual storage is a unique actor design paradigm only available on the FVM that allows users the ability to renew Filecoin storage deals and to keep them active indefinitely. This could be achieved by using a Decentralized Autonomous Organization (DAO) structure for example.
Data DAOs are a unique design paradigm FVM developers could create which use Filecoin storage to store all their data instead of a service like AWS (which is currently used).
Yes.
Not necessarily. You can use any of the public RPC nodes on either mainnet or the [Calibration testnet](/networks/calibration/details/
api.hyperspace.node.glif.io/rpc/v1api.zondax.ch/fil/node/hyperspace/rpc/v1
They are synergistic. Compute over data solutions such as Bacalhau can use the FVM.
Many different languages already compile to WASM so developers can pick their favorite.
No, the FEVM is its own instance of the EVM built on top of Filecoin. You will need to redeploy smart contracts that exist in the EVM to the FEVM. Bridges can be built to top of the FEVM which connect it to other blockchains however.
When an EVM is deployed to FEVM, it is compiled with WASM and an actor instance is created in FEVM that runs the EVM bytecode. The user-defined FEVM actor is then able to interact with the Filecoin network via built-in actors like the Market and Miner APIs.
No, it must be deployed to the FEVM.
React, Ethers.js, web.js, ReactJS work well.
How do we convert from msg.sender in a FEVM contract, which returns an EVM 0x address, to the underlying Filecoin f address?
You can use the npm @glif/filecoin-address package or the Zondax mock API has the constructor that calls mock_generate_deals();.
Store a number limit on running DealClient and publish_deal and have it authorized to replicate.
The intent of FEVM/FVM is to compute over state data (the metadata of your stored data). Storage providers are the ones that are able to store your data and upload the deal to the Filecoin network. Data retrieval happens via Retrieval Providers, accepting the client’s ask to retrieve and working with storage providers to decrypt the data to deliver to the client. FEVM/FVM is able to build logic around these 2 processes and automate, add verification and proofs, time-lock retrievals etc.
How do I close a storage deal on Filecoin and stop storage providers (SP) from storing my data on-chain
It’s not impossible but storage providers are incentivized not to close the storage deal as they are slashed for not providing Proof of Spacetime (PoSt). Someone has to pay for the broken promise a miner makes to the chain and you need a custom market actor for it most likely to make the deal. You need to make deals for a certain amount of time - right now the boundaries are 6-18 months. You cannot ask a storage provider to take down your data without contacting them off-chain.