11 releases

0.5.3 Oct 21, 2021
0.5.2 Mar 29, 2021
0.4.1 Dec 7, 2020
0.4.0 Nov 10, 2020
0.2.1 May 26, 2020

#708 in Magic Beans

Download history 57/week @ 2022-01-27 60/week @ 2022-02-03 28/week @ 2022-02-10 443/week @ 2022-02-17 116/week @ 2022-02-24 125/week @ 2022-03-03 135/week @ 2022-03-10 136/week @ 2022-03-17 222/week @ 2022-03-24 69/week @ 2022-03-31 33/week @ 2022-04-07 139/week @ 2022-04-14 141/week @ 2022-04-21 80/week @ 2022-04-28 62/week @ 2022-05-05 193/week @ 2022-05-12

480 downloads per month
Used in 3 crates



GitHub Workflow Status Codecov GitHub release (latest by date) License Apache 2.0 License MIT Twitter Discord

Forest is an implementation of Filecoin written in Rust. The implementation will take a modular approach to building a full Filecoin node in Rust from the Filecoin Protocol Specification, specifically the virtual machine, blockchain, and node system.

Our crates:

component description/crates
forest the command-line interface and daemon (1 crate/workspace)
node the networking stack and storage (7 crates)
blockchain the chain structure and synchronization (6 crates)
vm state transition and actors, messages, addresses (9 crates)
key_management Filecoin account management (1 crate)
crypto cryptographic functions, signatures, and verification (1 crate)
encoding serialization library for encoding and decoding (1 crate)
ipld the IPLD model for content-addressable data (9 crates)
types the forest types (2 crates)
utils the forest toolbox (12 crates)


rustc >= 1.57.0


# Clone repository
git clone --recursive https://github.com/chainsafe/forest
cd forest

# Install binary to $HOME/.cargo/bin and run node
make install

To create release binaries, checkout the latest tag and compile with the release feature. GitHub release (latest by date)

git checkout $TAG
cargo build --release --bin forest --features release

OpenCL, hwloc and a compatible assembly linker (ex. clang) are also required to build Filecoin proofs.


Run the node with custom config and bootnodes

forest --config /path/to/your_config.toml

Example of config options available:

data_dir = "<directory for all chain and networking data>"
genesis_file = "<relative file path of genesis car file>"

listening_multiaddr = "<multiaddress>"
bootstrap_peers = ["<multiaddress>"]

Example of a multiaddress: "/ip4/"


The Forest logger uses Rust's log filtering options with the RUST_LOG environment variable. For example:

RUST_LOG="debug,forest_libp2p::service=info" forest

Will show all debug logs by default, but the forest_libp2p::service logs will be limited to info


# To run base tests
cargo test # use `make test-release` for longer compilation but faster execution

# To pull serialization vectors submodule and run serialization and conformance tests
make test-vectors

# To run all tests and all features enabled
make test-all

Joining the testnet

Build with the interopnet config with:

make interopnet

# Run and import past the state migrations to latest network version
./target/release/forest --import-snapshot ./types/networks/src/interopnet/snapshot.car

Importing the snapshot only needs to happen during the first run. Following this, to restart the daemon run:


Interacting with Forest via CLI

When the Forest daemon is started, an admin token will be displayed. You will need this for commands that require a higher level of authorization (like a password). Forest, as mentioned above, uses multiaddresses for networking. This is no different in the CLI. To set the host and the port to use, if not using the default port or using a remote host, set the FULLNODE_API_INFO environment variable. This is also where you can set a token for authentication.

FULLNODE_API_INFO="<token goes here>:/ip4/<host>/tcp/<port>/http

Note that if a token is not present in the FULLNODE_API_INFO env variable, the colon is removed.

Forest developers will prepend this variable to CLI commands over using export on Linux or its equivalant on Windows. This will look like the following:

FULLNODE_API_INFO="..." forest auth api-info -p admin


Work in progress.


ChainSafe Security Policy

Reporting a Security Bug

We take all security issues seriously, if you believe you have found a security issue within a ChainSafe project please notify us immediately. If an issue is confirmed, we will take all necessary precautions to ensure a statement and patch release is made in a timely manner.

Please email a description of the flaw and any related information (e.g. reproduction steps, version) to security at chainsafe dot io.


Forest is dual licensed under MIT + Apache 2.0.


~100K SLoC