🦁 The Leo Programming Language. A Programming Language for Formally Verified, Zero-Knowledge Applications
Go to file
bors[bot] cbf15c480a
Merge #690 #691
690: Bump tracing from 0.1.24 to 0.1.25 r=collinc97 a=dependabot-preview[bot]

Bumps [tracing](https://github.com/tokio-rs/tracing) from 0.1.24 to 0.1.25.
<details>
<summary>Commits</summary>
<ul>
<li><a href="4ad1e62a2d"><code>4ad1e62</code></a> tracing: prepare to release v0.1.25</li>
<li><a href="c22b62e281"><code>c22b62e</code></a> tracing: highlight <code>Span::entered</code> in more docs</li>
<li><a href="a358728b1e"><code>a358728</code></a> tracing: simplify common case of immediately entering the span (<a href="https://github-redirect.dependabot.com/tokio-rs/tracing/issues/1252">#1252</a>)</li>
<li><a href="4538d74d22"><code>4538d74</code></a> subscriber: prepare to release v0.2.16 (<a href="https://github-redirect.dependabot.com/tokio-rs/tracing/issues/1256">#1256</a>)</li>
<li><a href="a0201ba798"><code>a0201ba</code></a> log: prepare to release v0.1.2</li>
<li><a href="0cdd5e88ac"><code>0cdd5e8</code></a> log: forward <code>LogTracer::enabled</code> to the subscriber  (<a href="https://github-redirect.dependabot.com/tokio-rs/tracing/issues/1254">#1254</a>)</li>
<li><a href="8d83326a5f"><code>8d83326</code></a> subscriber: fix FmtCollector not forwarding max level  (<a href="https://github-redirect.dependabot.com/tokio-rs/tracing/issues/1251">#1251</a>)</li>
<li><a href="31aa6afecc"><code>31aa6af</code></a> subscriber: set the max <code>log</code> <code>LevelFilter</code> in <code>init</code> (<a href="https://github-redirect.dependabot.com/tokio-rs/tracing/issues/1248">#1248</a>)</li>
<li><a href="2a9d17f73f"><code>2a9d17f</code></a> log: compare <code>log</code> record <code>Level</code>s against the max level (<a href="https://github-redirect.dependabot.com/tokio-rs/tracing/issues/1247">#1247</a>)</li>
<li>See full diff in <a href="https://github.com/tokio-rs/tracing/compare/tracing-0.1.24...tracing-0.1.25">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=tracing&package-manager=cargo&previous-version=0.1.24&new-version=0.1.25)](https://dependabot.com/compatibility-score/?dependency-name=tracing&package-manager=cargo&previous-version=0.1.24&new-version=0.1.25)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)



</details>

691: Bump self_update from 0.24.0 to 0.25.0 r=collinc97 a=dependabot-preview[bot]

Bumps [self_update](https://github.com/jaemk/self_update) from 0.24.0 to 0.25.0.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/jaemk/self_update/blob/master/CHANGELOG.md">self_update's changelog</a>.</em></p>
<blockquote>
<h2>[0.25.0]</h2>
<h3>Added</h3>
<h3>Changed</h3>
<ul>
<li>Fix io error triggered when updating binary contained in a zipped folder.</li>
<li>Fix issues updating Windows binaries on non-<code>C:</code> drives.</li>
</ul>
<h3>Removed</h3>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a href="https://github.com/jaemk/self_update/commits">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=self_update&package-manager=cargo&previous-version=0.24.0&new-version=0.25.0)](https://dependabot.com/compatibility-score/?dependency-name=self_update&package-manager=cargo&previous-version=0.24.0&new-version=0.25.0)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)



</details>

Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
2021-02-25 01:33:51 +00:00
.cargo Update .cargo/config 2020-08-21 04:23:52 -07:00
.github Merge pull request #590 from AleoHQ/feature/bors-badge 2021-02-10 20:35:06 -08:00
.resources chore(leo): bump version for new release 2021-02-07 08:14:56 -08:00
.travis Adds SSH key for snarkOS 2020-06-07 22:55:49 -07:00
asg merge master and resolve bors failing test 2021-02-18 11:50:13 -05:00
ast re-add syntax in, then add deprecation warning for it 2021-02-16 15:33:31 -05:00
compiler Bump bincode from 1.3.1 to 1.3.2 2021-02-24 10:47:15 +00:00
examples rebase and replace const keyword in tests 2021-02-16 14:19:20 -05:00
gadgets refactor Field + PrimeField -> PrimeField, all tests still pass 2021-02-16 14:41:59 -05:00
grammar re-add syntax in, then add deprecation warning for it 2021-02-16 15:33:31 -05:00
imports asg refactor 2021-02-16 13:32:34 -08:00
input Adds README.md 2021-02-10 22:27:37 -08:00
leo Merge #676 2021-02-18 06:07:11 +00:00
linter Adds README.md 2021-02-10 22:27:37 -08:00
package Merge #676 2021-02-18 06:07:11 +00:00
state bump snarkvm module versions to 0.0.4 2021-02-11 17:33:53 -08:00
.codecov.yml Adds configuration files for tooling 2020-06-07 22:53:45 -07:00
.gitignore allow outputs directory in leo package 2020-08-03 12:59:49 -07: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
.travis.yml Migrate to snarkVM 2020-12-30 12:40:45 -04:00
bors.toml Set bors approval minimum to 1 2021-02-11 13:21:40 -08:00
Cargo.lock Merge #690 #691 2021-02-25 01:33:51 +00:00
Cargo.toml Bump self_update from 0.24.0 to 0.25.0 2021-02-24 10:48:02 +00:00
CONTRIBUTING.md add contributing.md 2021-02-16 15:22:02 -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 add bors badge to readme 2021-01-29 16:47:48 -05: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