All Projects → AleoHQ → snarkOS

AleoHQ / snarkOS

Licence: GPL-3.0 license
A Decentralized Operating System for Zero-Knowledge Applications

Programming Languages

rust
11053 projects
Dockerfile
14818 projects
shell
77523 projects

Projects that are alternatives of or similar to snarkOS

awesome-zkp-starter-pack
A curated collection of links for zero-knowledge proof cryptography used in blockchains
Stars: ✭ 63 (-95.16%)
Mutual labels:  zero-knowledge, zksnarks
snarkVM
A Virtual Machine for Zero-Knowledge Executions
Stars: ✭ 345 (-73.5%)
Mutual labels:  zero-knowledge, aleo
bellman
Bellman zkSNARK library for community with Ethereum's BN256 support
Stars: ✭ 121 (-90.71%)
Mutual labels:  zero-knowledge, zksnarks
FlashPaper
One-time encrypted password/secret sharing
Stars: ✭ 85 (-93.47%)
Mutual labels:  zero-knowledge
schnorr-nizk
Schnorr Protocol for Non-interactive Zero-Knowledge Proofs
Stars: ✭ 67 (-94.85%)
Mutual labels:  zero-knowledge
dalek-rangeproofs
This was a pure-Rust implementation of a rangeproof scheme. It is now obsoleted by Bulletproofs.
Stars: ✭ 16 (-98.77%)
Mutual labels:  zero-knowledge
zk
Cross-platform zero knowledge proofs
Stars: ✭ 44 (-96.62%)
Mutual labels:  zero-knowledge
zkp
Experimental zero-knowledge proof compiler in Rust macros
Stars: ✭ 121 (-90.71%)
Mutual labels:  zero-knowledge
ripp
Argument systems for inner pairing products
Stars: ✭ 34 (-97.39%)
Mutual labels:  zksnarks
crypto-in-action
algebra arithmetic, finite fields, elliptic curves, zero-knowledge
Stars: ✭ 65 (-95.01%)
Mutual labels:  zero-knowledge
Cryptpad
Collaboration suite, end-to-end encrypted and open-source.
Stars: ✭ 3,125 (+140.02%)
Mutual labels:  zero-knowledge
plonk
A pure Rust PLONK implementation using arkworks as a backend.
Stars: ✭ 128 (-90.17%)
Mutual labels:  zero-knowledge
FISCO-BCOS
FISCO BCOS是由微众牵头的金链盟主导研发、对外开源、安全可控的企业级金融区块链底层技术平台。 单链配置下,性能TPS可达万级。提供群组架构、并行计算、分布式存储、可插拔的共识机制、隐私保护算法、支持全链路国密算法等诸多特性。 经过多个机构、多个应用,长时间在生产环境中的实践检验,具备金融级的高性能、高可用性及高安全性。FISCO BCOS is a secure and reliable financial-grade open-source blockchain platform. The platform provides rich features including group architecture, cross-chain communication protoc…
Stars: ✭ 1,603 (+23.12%)
Mutual labels:  zero-knowledge
examples
Examples of NuID's zero knowledge authentication and key management facilities in various languages and frameworks. Open an Issue or PR if you'd like to see your favorite tool here.
Stars: ✭ 42 (-96.77%)
Mutual labels:  zero-knowledge
wordlines
Mobile ZK Puzzle Game with NFT rewards
Stars: ✭ 180 (-86.18%)
Mutual labels:  zero-knowledge
zkp-ecdsa
Proves knowledge of an ECDSA-P256 signature under one of many public keys that are stored in a list.
Stars: ✭ 118 (-90.94%)
Mutual labels:  zero-knowledge
arkworks-gadgets
Zero-knowledge gadgets for Webb's cross-chain blockchain applications.
Stars: ✭ 72 (-94.47%)
Mutual labels:  zero-knowledge
dusk-blindbid
Implementation of the blindbid logic within Zero Knowledge Proofs
Stars: ✭ 18 (-98.62%)
Mutual labels:  zero-knowledge
aeonflux
Infinitely presentable (aeon) rerandomisable (flux) anonymous credentials.
Stars: ✭ 25 (-98.08%)
Mutual labels:  zero-knowledge
MLSAG
Multilayered Linkable Spontaneous Anonymous Group - Implemented as is from paper. Not Monero specific
Stars: ✭ 19 (-98.54%)
Mutual labels:  zero-knowledge

snarkOS

Table of Contents

1. Overview

snarkOS is a decentralized operating system for private applications. It forms the backbone of Aleo and enables applications to verify and store state in a publicly verifiable manner.

2. Build Guide

2.1 Requirements

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: 50 Mbps of upload and download bandwidth

Please note to run an Aleo proving node that is competitive, the machine will require more than these requirements.

2.2 Installation

Before beginning, please ensure your machine has Rust v1.62+ installed. Instructions to install Rust can be found here.

Start by cloning the snarkOS 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

3a. Run an Aleo Client Node

Start by following the instructions in the Build Guide.

Next, to start a client node, from the snarkOS directory, run:

./run-client.sh

3b. Run an Aleo Prover Node

Note: The Aleo prover node will be available in Phase 2.

Start by following the instructions in the Build Guide.

Next, to generate an Aleo prover address, run:

snarkos experimental new_account 

or from the snarkOS directory, run:

cargo run --release -- experimental new_account

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
     View Key  AViewKey1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx  <-- Save Me
      Address  aleo1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx  <-- Use Me For The Next Step

Next, to start a proving node, from the snarkOS directory, run:

./run-prover.sh

When prompted, enter your Aleo prover address:

Enter your Aleo prover address:
aleo1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

4. FAQs

1. My node is unable to compile.

  • Ensure your machine has Rust v1.62+ installed. Instructions to install Rust can be found here.
  • If large errors appear during compilation, try running cargo clean.
  • Ensure snarkOS is started using ./run-client.sh or ./run-prover.sh.

2. My node is unable to connect to peers on the network.

  • Ensure ports 4130/tcp and 4180/tcp are open on your router and OS firewall.
  • Ensure snarkOS is started using ./run-client.sh or ./run-prover.sh.

3. I can't generate a new address

  • Before running the command above (snarkos experimental new_account) try source ~/.bashrc
  • Also double check the spelling of snarkos. Note the directory is /snarkOS, the command is snarkos

5. Command Line Interface

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 [FLAGS] [OPTIONS] [SUBCOMMAND]

FLAGS:
        --display    If the flag is set, the node will render a read-only display
    -h, --help       Prints help information
        --norpc      If the flag is set, the node will not initialize the RPC server
    -V, --version    Prints version information

OPTIONS:
        --connect <connect>          Specify the IP address and port of a peer to connect to
        --dev <dev>                  Enables development mode, specify a unique ID for the local node
        --network <network>          Specify the network of this node [default: 2]
        --node <node>                Specify the IP address and port for the node server [default: 0.0.0.0:4132]
        --prover <prover>            Specify this as a prover node, with the given prover address
        --rpc <rpc>                  Specify the IP address and port for the RPC server [default: 0.0.0.0:3032]
        --password <rpc-password>    Specify the password for the RPC server [default: pass]
        --username <rpc-username>    Specify the username for the RPC server [default: root]
        --verbosity <verbosity>      Specify the verbosity of the node [options: 0, 1, 2, 3] [default: 2]

SUBCOMMANDS:
    clean           Removes the ledger files from storage
    experimental    Experimental features
    help            Prints this message or the help of the given subcommand(s)
    update          Updates snarkOS to the latest version

6. Development

We welcome all contributions to snarkOS. Please refer to the license for the terms of contributions.

7. License

License: GPL v3

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].