Skip to content

Commit

Permalink
Fix version (#977)
Browse files Browse the repository at this point in the history
* chore: Release

* update README

---------

Co-authored-by: François Garillot <francois@garillot.net>
  • Loading branch information
arthurpaulino and huitseeker authored Dec 19, 2023
1 parent 061b135 commit 3ab302f
Show file tree
Hide file tree
Showing 4 changed files with 10 additions and 10 deletions.
8 changes: 4 additions & 4 deletions Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[package]
name = "lurk"
version = "0.2.0"
authors = ["porcuquine <porcuquine@gmail.com>"]
version = "0.3.0"
authors = ["Lurk Lab Engineering <engineering@lurk-lab.com>"]
license = "MIT OR Apache-2.0"
description = "Turing-Complete Zero Knowledge"
edition = "2021"
Expand Down Expand Up @@ -30,8 +30,8 @@ generic-array = "0.14.7"
hex = { version = "0.4.3", features = ["serde"] }
indexmap = { version = "2.1.0", features = ["rayon", "serde"] }
itertools = "0.11"
lurk-macros = { path = "lurk-macros" }
lurk-metrics = { path = "lurk-metrics" }
lurk-macros = { version = "0.2.0", path = "lurk-macros" }
lurk-metrics = { version = "0.2.0", path = "lurk-metrics" }
metrics = { workspace = true }
neptune = { workspace = true, features = ["arity2", "arity4", "arity8", "arity16", "pasta"] }
nom = "7.1.3"
Expand Down
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,9 @@
[msrv-image]: https://img.shields.io/badge/rustc-1.70+-blue.svg
[crates-image]: https://img.shields.io/crates/v/lurk.svg

# Status (Alpha)
# Status (Beta)

Lurk is currently in Alpha. Code that runs in the Lurk Alpha release is expected to also run in Lurk Beta, and eventually Lurk 1.0. However, some low-level data representations are anticipated to change, and we will be refactoring the circuit implementation to increase auditability and further our confidence in Lurk's cryptographic security. Also note that since Lurk inherits some security properties from the underlying proving system, those who would rely on Lurk should investigate the security and status of Nova itself. We encourage early adopters to begin writing real applications taking advantage of Lurk so you can begin to familiarize yourself with the programming model. Likewise, we welcome your feedback -- which will help ensure ongoing development meets user need.
Lurk is currently in [Beta](https://blog.lurk-lang.org/posts/lurk-beta/), which is backwards compatible with code that ran in Lurk Alpha and is expected to be compatible with Lurk 1.0. However, some low-level data representations are anticipated to change, and we will be refactoring the evaluation model (and consequently its circuit) for efficiency purposes. Also note that since Lurk inherits some security properties from the underlying proving system, those who would rely on Lurk should investigate the security and status of Nova/SuperNova itself. We encourage early adopters to begin writing real applications taking advantage of Lurk so you can begin to familiarize yourself with the programming model. Likewise, we welcome your feedback -- which will help ensure ongoing development meets user need.

For support and discussions, please visit our [Zulip forum](https://zulip.lurk-lab.com/).

Expand Down Expand Up @@ -49,7 +49,7 @@ Lurk's Alpha release has undergone a [security audit](https://blog.lurk-lang.org

# Versioning

Please note that the Lurk language and spec will be versioned independently from the crates that implement the spec. This is necessary semantic versioning implies different requirements for the language and its implementation. For example, Lurk Alpha is released as crate `lurk 0.2.0`. It is our intention for these two versioning systems to coincide at 1.0. The next major Lurk release will be Lurk Beta, but there may be multiple minor-version crate releases before then.
Please note that the Lurk language and spec will be versioned independently from the crates that implement the spec. This is necessary because semantic versioning implies different requirements for the language and its implementation. For example, Lurk Alpha is released as crate `lurk 0.2.0` and Lurk Beta is released as crate `lurk 0.3.0`. It is our intention for these two versioning systems to coincide at 1.0.

---

Expand Down
2 changes: 1 addition & 1 deletion lurk-macros/Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "lurk-macros"
version = "0.1.0"
version = "0.2.0"
authors = ["porcuquine <porcuquine@gmail.com>"]
license = "MIT OR Apache-2.0"
description = "Custom derives for `lurk`"
Expand Down
4 changes: 2 additions & 2 deletions lurk-metrics/Cargo.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[package]
name = "lurk-metrics"
authors = ["Lurk Lab <engineering@lurk-lab.com>"]
version = "0.1.0"
version = "0.2.0"
edition = "2021"
license = "MIT OR Apache-2.0"
description = "Metrics Sink for lurk"
Expand All @@ -15,4 +15,4 @@ tracing = { workspace = true }

[dev-dependencies]
regex = { version = "1.9.4", features = ["unicode-case"] }
tracing-test = { version = "0.2", features = ["no-env-filter"] }
tracing-test = { version = "0.2", features = ["no-env-filter"] }

1 comment on commit 3ab302f

@github-actions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Benchmarks

Table of Contents

Overview

This benchmark report shows the Fibonacci GPU benchmark.
NVIDIA L4
Intel(R) Xeon(R) CPU @ 2.20GHz
125.78 GB RAM
Workflow run: https://github.com/lurk-lab/lurk-rs/actions/runs/7268336604

Benchmark Results

LEM Fibonacci Prove - rc = 100

fib-ref=061b1354d5edddb493731e545226757dc7a45bfe fib-ref=3ab302f3b668aeb9d1c4f54e54694b17b7651adc
num-100 3.85 s (✅ 1.00x) 3.86 s (✅ 1.00x slower)
num-200 7.70 s (✅ 1.00x) 7.70 s (✅ 1.00x slower)

LEM Fibonacci Prove - rc = 600

fib-ref=061b1354d5edddb493731e545226757dc7a45bfe fib-ref=3ab302f3b668aeb9d1c4f54e54694b17b7651adc
num-100 3.30 s (✅ 1.00x) 3.31 s (✅ 1.01x slower)
num-200 7.26 s (✅ 1.00x) 7.27 s (✅ 1.00x slower)

Made with criterion-table

Please sign in to comment.