- 1. Overview
- 2. Build Guide
- 3. Run an Aleo Node
- 4. FAQs
- 5. Command Line Interface
- 6. Development Guide
- 7. License
snarkOS is a decentralized operating system for zero-knowledge applications. This code forms the backbone of Aleo network, which verifies transactions and stores the encrypted state applications in a publicly-verifiable manner.
The following are minimum requirements to run an Aleo node:
- CPU: 16-cores (32-cores preferred)
- RAM: 16GB of memory (32GB preferred)
- Storage: 128GB of disk space
- Network: 10 Mbps of upload and download bandwidth
Please note to run an Aleo Prover that is competitive, the machine will require more than these requirements.
Before beginning, please ensure your machine has Rust v1.65+ installed. Instructions to install Rust can be found here.
Start by cloning this Github repository:
git clone https://github.com/AleoHQ/snarkOS.git --depth 1
Next, move into the snarkOS directory:
cd snarkOS
[For Ubuntu users] A helper script to install dependencies is available. From the snarkOS directory, run:
./build_ubuntu.sh
Lastly, install snarkOS:
cargo install --path .
Start by following the instructions in the Build Guide.
Next, to start a client node, from the snarkOS directory, run:
./run-client.sh
Start by following the instructions in the Build Guide.
Next, generate an Aleo account address:
snarkos account new
This will output a new Aleo account in the terminal.
Please remember to save the account private key and view key. The following is an example output:
Attention - Remember to store this account private key and view key.
Private Key APrivateKey1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx <-- Save Me And Use In The Next Step
View Key AViewKey1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx <-- Save Me
Address aleo1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx <-- Save Me
Next, to start a proving node, from the snarkOS directory, run:
./run-prover.sh
When prompted, enter your Aleo private key:
Enter the Aleo Prover account private key:
APrivateKey1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
- Ensure your machine has
Rust v1.65+installed. Instructions to install Rust can be found here. - If large errors appear during compilation, try running
cargo clean. - Ensure
snarkOSis started using./run-client.shor./run-prover.sh.
- Ensure ports
4133/tcpand3033/tcpare open on your router and OS firewall. - Ensure
snarkOSis started using./run-client.shor./run-prover.sh.
- Before running the command above (
snarkos account new) trysource ~/.bashrc - Also double-check the spelling of
snarkos. Note the directory is/snarkOS, the command issnarkos
To run a node with custom settings, refer to the full list of options and flags available in the snarkOS CLI.
The full list of CLI flags and options can be viewed with snarkos --help:
snarkOS
The Aleo Team <[email protected]>
USAGE:
snarkos [OPTIONS] <SUBCOMMAND>
OPTIONS:
-h, --help Print help information
-v, --verbosity <VERBOSITY> Specify the verbosity [options: 0, 1, 2, 3] [default: 2]
SUBCOMMANDS:
account Commands to manage Aleo accounts
clean Cleans the snarkOS node storage
help Print this message or the help of the given subcommand(s)
start Starts the snarkOS node
update Update snarkOS
The following are the options for the snarkos start command:
USAGE:
snarkos start [OPTIONS]
OPTIONS:
--network <NETWORK_ID> Specify the network ID of this node [default: 3]
--beacon <PRIVATE_KEY> Specify this node as a beacon, with the account private key as an argument
--validator <PRIVATE KEY> Specify this node as a validator, with the account private key as an argument
--prover <PRIVATE KEY> Specify this node as a prover, with the given account private key as an argument
--client <PRIVATE_KEY> Specify this node as a client, with an optional account private key as an argument
--node <IP:PORT> Specify the IP address and port for the node server [default: 0.0.0.0:4133]
--connect <IP:PORT> Specify the IP address and port of a peer to connect to
--rest <REST> Specify the IP address and port for the REST server [default: 0.0.0.0:3033]
--norest If the flag is set, the node will not initialize the REST server
--nodisplay If the flag is set, the node will not render the display
--verbosity <VERBOSITY_LEVEL> Specify the verbosity of the node [options: 0, 1, 2, 3] [default: 2]
--logfile <PATH> Specify the path to the file where logs will be stored [default: /tmp/snarkos.log]
--dev <NODE_ID> Enables development mode, specify a unique ID for this node
-h, --help Print help information
In one terminal, start the beacon by running:
cargo run --release -- start --nodisplay --dev 0 --beacon ""
In a second terminal, run:
cargo run --release -- start --nodisplay --dev 1 --prover ""
This procedure can be repeated to start more nodes.
It is important to initialize the nodes starting from 0 and incrementing by 1 for each new node.
The following is a list of options to initialize a node (replace <NODE_ID> with a number starting from 0):
cargo run --release -- start --nodisplay --dev <NODE_ID> --beacon ""
cargo run --release -- start --nodisplay --dev <NODE_ID> --validator ""
cargo run --release -- start --nodisplay --dev <NODE_ID> --prover ""
cargo run --release -- start --nodisplay --dev <NODE_ID> --client ""
cargo run --release -- start --nodisplay --dev <NODE_ID>
When no node type is specified, the node will default to --client.
To clean up the node storage, run:
cargo run --release -- clean --dev <NODE_ID>
We welcome all contributions to snarkOS. Please refer to the license for the terms of contributions.
