In directory copied, modify the base_config.ini to fit your needs. Usually,
for development purposes, the bind address should be changed from 0.0.0.0 to
127.0.0.1 for config keys http-server-address, p2p-listen-endpoint,
and p2p-server-address so you are not exposing you development node to
the external world.
Once configuration is done, simply run:
This gives you a fully fledged development environment, a chain loaded
with all system contracts, very similar to what you will get on the
main network once launched.
The sample configuration sets up a single node, as it doesn’t point to
other block producer candidates (skips the peers discovery).
We keep an updated list of the different stages launched with eos-bios here: