🦁 The Leo Programming Language. A Programming Language for Formally Verified, Zero-Knowledge Applications
Go to file
Alessandro Coglio 2060d0d249 [ABNF] Improve documentation and layout.
Explain better variable and constant declarations.

Leave one blank line between the rules for variable and constant declarations
(not necessary for ABNF, but consistent with the rest of the file and actually
expected by the ABNF-to-LaTeX converter).

Limit lines to 80 columns, by putting the rules for variable and constant
declarations over two lines each, with proper indentation.
2021-04-29 18:16:30 -07:00
.cargo Update config 2021-04-01 14:27:25 -07:00
.circleci final fixes 2021-04-26 19:37:29 +03:00
.github changed testing approach 2021-04-26 19:35:12 +03:00
.resources chore(leo): bump version for new release 2021-04-15 13:49:42 -07:00
asg import global consts, clean up, test type inference on global consts 2021-04-26 17:51:19 -04:00
asg-passes chore(leo): bump version for new release 2021-04-15 13:49:42 -07:00
ast merge master, resolve conflicts, login test is failing 2021-04-26 14:43:21 -04:00
compiler Merge pull request #705 from AleoHQ/feature/485-defines 2021-04-28 14:06:40 -07:00
examples removed test_input from silly sudoku 2021-04-26 22:26:46 +03:00
grammar [ABNF] Improve documentation and layout. 2021-04-29 18:16:30 -07:00
imports Merge branch 'feature/opti-cli-flag' of github.com:AleoHQ/leo into feature/opti-cli-flag 2021-04-26 23:42:57 +03:00
input chore(leo): bump version for new release 2021-04-15 13:49:42 -07:00
leo adds tests for imports 2021-04-28 15:12:08 +03:00
linter chore(leo): bump version for new release 2021-04-15 13:49:42 -07:00
package adds integration tests to Leo CLI 2021-04-21 13:01:11 +03:00
parser merge master, resolve conflicts, login test is failing 2021-04-26 14:43:21 -04:00
state Merge branch 'feature/opti-cli-flag' of github.com:AleoHQ/leo into feature/opti-cli-flag 2021-04-26 23:42:57 +03:00
synthesizer chore(leo): bump version for new release 2021-04-15 13:49:42 -07:00
test-framework Add test-framework comment 2021-04-21 14:54:51 -07:00
tests extract test framework 2021-04-19 06:46:22 -07:00
.codecov.yml Adds configuration files for tooling 2020-06-07 22:53:45 -07:00
.gitignore Update .gitignore 2021-02-24 20:46:54 -08:00
.licenserc.json Update license to 2021 2021-02-01 20:26:56 -08:00
.rustfmt.toml prefer rust fmt imports_granularity over deprecated merge_imports 2021-02-01 09:16:37 -08:00
.rusty-hook.toml Update precommit hook to use stable for clippy 2021-02-01 20:28:33 -08:00
bors.toml Set bors approval minimum to 1 2021-02-11 13:21:40 -08:00
Cargo.lock Bump dirs from 3.0.1 to 3.0.2 2021-04-27 19:25:33 +00:00
Cargo.toml Bump dirs from 3.0.1 to 3.0.2 2021-04-27 19:25:33 +00:00
CONTRIBUTING.md add contributing.md 2021-02-16 15:22:02 -08:00
DEVELOPMENT.md Adds DEVELOPMENT.md 2021-02-24 20:28:27 -08:00
FAQs.md Update and rename FAQ.md to FAQs.md 2020-08-15 03:01:30 -07:00
LICENSE.md Adds LICENSE.md 2021-02-10 22:23:45 -08:00
README.md Update README.md 2021-04-27 19:37:41 -07:00
SECURITY.md Adds SECURITY.md 2021-02-10 22:31:12 -08:00

The Leo Programming Language

Bors enabled

Leo is a functional, statically-typed programming language built for writing private applications.

Table of Contents

1. Overview

Welcome to the Leo programming language.

Leo provides a high-level language that abstracts low-level cryptographic concepts and makes it easy to integrate private applications into your stack. Leo compiles to circuits making zero-knowledge proofs practical.

The syntax of Leo is influenced by traditional programming languages like JavaScript, Scala, and Rust, with a strong emphasis on readability and ease-of-use. Leo offers developers with tools to sanity check circuits including unit tests, integration tests, and console functions.

Leo is one part of a greater ecosystem for building private applications on Aleo. If your goal is to build a user experience on the web that is both truly personal and truly private, then we recommend downloading the Aleo Studio IDE and checking out the Aleo Package Manager.

2. Build Guide

2.1 Install Rust

We recommend installing Rust using rustup. You can install rustup as follows:

  • macOS or Linux:

    curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
    
  • Windows (64-bit):

    Download the Windows 64-bit executable and follow the on-screen instructions.

  • Windows (32-bit):

    Download the Windows 32-bit executable and follow the on-screen instructions.

2.2a Build from Crates.io

We recommend installing Leo this way. In your terminal, run:

cargo install leo-lang

Now to use Leo, in your terminal, run:

leo

2.2b Build from Source Code

Alternatively, you can install Leo by building from the source code as follows:

# Download the source code
git clone https://github.com/AleoHQ/leo
cd leo

# Build in release mode
$ cargo build --release

This will generate an executable under the ./target/release directory. To run Leo, run the following command:

./target/release/leo

3. Quick Start

Use the Leo CLI to create a new project

# create a new `hello-world` Leo project
leo new hello-world
cd hello-world

# build & setup & prove & verify
leo run

The leo new command creates a new Leo project with a given name.

The leo run command will compile the main program, generate keys for a trusted setup, fetch inputs, generate a proof and verify it.

Congratulations! You've just run your first Leo program.

4. Documentation

5. Contributing

Please see our guidelines in the developer documentation

Thank you for helping make Leo better!

6. License

License: GPL v3