Skip to content


Ryan Kowalick edited this page Apr 15, 2019 · 25 revisions

There are currently 3 Filecoin developer networks (aka devnets) available for development and testing.

Both are subject to frequent downtimes for a variety of reasons, including bugs, breaking changes, or the polar vortex ⛄. There is no SLA; until we have a status page, please ping in #fil-chat if you would like to confirm status.


At the moment, this is the network to use by default, for testing and experimenting. Nodes are deployed from master manually.

The Getting Started page contains instructions for connecting your nodes to this network.


Deployed from master by CI every day at 0600 UTC. This network is for people contributing to go-filecoin. You should probably avoid it unless that describes you.

Test (for Infra and pre-release testing)

Deployed via CI by tagging a commit with test-devnet-{d}.{d}.{d} where d is a positive integer. This network is for people working on infra or testing a pre-release. You should probably avoid it unless that describes you.



auto-seal-interval-seconds 300


auto-seal-interval-seconds 300


auto-seal-interval-seconds 300

Network Health

To get an idea of the state of each network, you can visit the network dashboard (port 8010). Once the page is loaded, wait about 5 to 10 seconds for heartbeats to arrive. A healthy network should show at least 5 nodes with the nickname "boot".

Each network is set up to mine a new block about every 30 seconds. If the "Last Block" column on the far right remains blank, or the number increments far beyond the 30 second mining time, this indicates that the network is no longer mining, or is not mining at the desired rate.

Another indication that a network is not in a healthy state is the background color of the tipset value. If all colors are the same, the nodes are in consensus. Two or more colors that persist may indicate that the nodes have fallen out of consensus.

You can’t perform that action at this time.