Alexandre Bourget - Co-Founder of EOS Canada, shipped support in ` eos -bios` to launch a fully-featured node with a single command (similar to the mainnet ). It starts as a great developer tool, and is also able to orchestrate the mainnet launch of the EOS network.

If you'd like to findmore greatEOS related content, make sure to subscribe to our YouTube Channel.

Transcription:

Everyone, I've got great news! I just had my CEO run "EOS BIOS" on his own laptop and he launched a network with one command. I'm going to show you that, and then you can dive into the repository and discover more. Especially about the "discovery" protocol. Which I think is going to allow us to launch the mainnet with a single command.

So here I'm in the terminal and if you want to use that on your own system, you type 'git clone' and github.com/eosCanada. That's the repository. And in there, you go inside "sample," "configs," and "docker". There's a few files in there. So you'll want to download the binary from this place, and go to the releases. Grab the distribution for your platform; Linux and Mac and Windows. Put that somewhere. I have it in my path. It's in "eos-bios," and if I run "eos-bios --help" I can see the available commands. Like "discover," this will discover the network through the discovery protocol and "boot" is what we're interested in today.

If I run "eos-bios boot"... Okay. Hang on tight.

Now it's discovering the network here. There's only one node in this network. It's creating an account. It goes through the whole boot process. It allows me to look at my "docker instance." This is going to run it through "docker." And see how it's done all the actions? It's waiting.

So if I'm going to look at the logs there, it did go through the "boot sequence," "set code," "new account," all the things that we need to have a solid mainnet. Transfer to 5,000 rows, I'm going to skip that. And then we're ready to publish that data for another person to join our network. And that's it. The node is running. All the system contracts are in there.

This is a great development environment. And if you didn't have the image installed, the "docker image," it would just have downloaded it. So you can try that. One line!

So you might have noticed this is all local, it's running on "docker" on my own machine. The same tooling will be able to be used to launch a mainnet.

By all means, please go to the repository, come to the EOS BIOS channel. In the repository there's a link to the telegram channel.