Repository navigation
Releases: wickra-lib/wickra-zk
Release list
wickra-zk v0.2.0
wickra-zk v0.2.0 — zero-knowledge proofs of backtest performance: the deterministic Wickra engine runs inside a RISC Zero zkVM guest, and the receipt proves the report hash and headline metrics without revealing the candles or the strategy. Native Rust plus a C ABI hub for Python, Node.js, C, C++, C#, Go, Java and R; Linux and macOS.
Install
cargo install wickra-zk-cli
pip install wickra-zk
npm install wickra-zk
dotnet add package Wickra.Zk
go get github.com/wickra-lib/wickra-zk-goJava (Maven Central):
<dependency>
<groupId>org.wickra</groupId>
<artifactId>wickra-zk</artifactId>
<version>0.2.0</version>
</dependency>R (r-universe):
install.packages("wickrazk", repos = "https://wickra-lib.r-universe.dev")Attached assets
Pre-built artefacts for every supported platform — the same files this
workflow run published to crates.io, PyPI, and npm — plus standalone
CLI binaries and the C ABI libraries. C# ships to NuGet, Java to Maven
Central, Go to the wickra-zk-go module, and R to r-universe via
their own release jobs.
Auto-generated changelog
See below; GitHub computes it from the commits since the previous tag.
About this release page
The release run published every package -- crates.io, PyPI, npm, NuGet, Maven Central and the Go module -- but its Go mirror step could not write the module's ~95 MB native libraries through the GitHub blob API (the mirror was then published by hand from the same artifacts, signed; the action now uploads large files another way), which skipped the jobs that assemble this page. It was completed from that run's own build artifacts; the jars are the ones on Maven Central (sha1 checked). The build-provenance attestation can only be produced inside the release workflow, so this version has none; the next release carries it again.
What's Changed
- deps: uv 0.12.19 for the lockfile bootstrap by @kingchenc in #71
- deps: follow the family line for CI actions, exec-maven-plugin and Test.Sdk by @kingchenc in #72
- deps: yoke-derive 0.8.4 and tests for clippy 1.99 by @kingchenc in #77
- deps(cargo): bump thiserror from 2.0.20 to 2.0.21 in the cargo group across 1 directory by @dependabot[bot] in #73
- deps(npm): bump @napi-rs/cli from 3.10.4 to 3.10.5 in /bindings/node in the node-binding group across 1 directory by @dependabot[bot] in #75
- deps(actions): bump the github-actions group across 1 directory with 6 updates by @dependabot[bot] in #74
- deps(cargo): bump thiserror from 2.0.20 to 2.0.21 in /bindings/wasm in the wasm-deps group by @dependabot[bot] in #78
- deps: wickra-core 1.0.7 (host, wasm and guest) by @kingchenc in #79
- ci: ci-ok, follow-family and signed bot commits by @kingchenc in #80
- release: 0.2.0 on wickra 2.0 by @kingchenc in #81
Full Changelog: v0.1.4...v0.2.0
The guest artefact of this release
This page was completed by hand and lacks two files the release workflow attaches: wickra-zk-guest.bin and guest-image-id.json. Both are part of the tagged source and identical to what the run built:
- Guest ELF:
guest/methods/elf/wickra-zk-guest.binatv0.2.0, sha2569a8ddd99b08326ed54338979a16a509448062a5b0007902678b17bf3b812b056. - Image id:
8efa8f7f19f20ebd96515b450a09f52b60e071f4219c4e7d8b5d6a88d90d4aac-- whatwickra-zk versionprints and what a verifier pins (guest/methods/src/guest_id.rs).
The wickra-zk-0.2.0.jar here is the one on Maven Central (sha1 checked); the workflow itself does not attach the jar.
wickra-zk v0.1.4
wickra-zk v0.1.4 — zero-knowledge proofs of backtest performance: the deterministic Wickra engine runs inside a RISC Zero zkVM guest, and the receipt proves the report hash and headline metrics without revealing the candles or the strategy. Native Rust plus a C ABI hub for Python, Node.js, C, C++, C#, Go, Java and R; Linux and macOS.
Install
cargo install wickra-zk-cli
pip install wickra-zk
npm install wickra-zk
dotnet add package Wickra.Zk
go get github.com/wickra-lib/wickra-zk-goJava (Maven Central):
<dependency>
<groupId>org.wickra</groupId>
<artifactId>wickra-zk</artifactId>
<version>0.1.4</version>
</dependency>R (r-universe):
install.packages("wickrazk", repos = "https://wickra-lib.r-universe.dev")Attached assets
Pre-built artefacts for every supported platform — the same files this
workflow run published to crates.io, PyPI, and npm — plus standalone
CLI binaries and the C ABI libraries. C# ships to NuGet, Java to Maven
Central, Go to the wickra-zk-go module, and R to r-universe via
their own release jobs.
Auto-generated changelog
See below; GitHub computes it from the commits since the previous tag.
What's Changed
- docs: show the org banner as vectors so its text is sharp at any size by @kingchenc in #69
- release: bump 0.1.3 -> 0.1.4 by @kingchenc in #70
Full Changelog: v0.1.3...v0.1.4
wickra-zk v0.1.3
wickra-zk v0.1.3 — zero-knowledge proofs of backtest performance: the deterministic Wickra engine runs inside a RISC Zero zkVM guest, and the receipt proves the report hash and headline metrics without revealing the candles or the strategy. Native Rust plus a C ABI hub for Python, Node.js, C, C++, C#, Go, Java and R; Linux and macOS.
Install
cargo install wickra-zk-cli
pip install wickra-zk
npm install wickra-zk
dotnet add package Wickra.Zk
go get github.com/wickra-lib/wickra-zk-goJava (Maven Central):
<dependency>
<groupId>org.wickra</groupId>
<artifactId>wickra-zk</artifactId>
<version>0.1.3</version>
</dependency>R (r-universe):
install.packages("wickrazk", repos = "https://wickra-lib.r-universe.dev")Attached assets
Pre-built artefacts for every supported platform — the same files this
workflow run published to crates.io, PyPI, and npm — plus standalone
CLI binaries and the C ABI libraries. C# ships to NuGet, Java to Maven
Central, Go to the wickra-zk-go module, and R to r-universe via
their own release jobs.
Auto-generated changelog
See below; GitHub computes it from the commits since the previous tag.
What's Changed
- deps: wickra-core 1.0.5 in the lock by @kingchenc in #62
- docs: the static badges come from the org's rendered files, not shields.io by @kingchenc in #63
- deps: wickra-core 1.0.5 in the guest, the rebuilt guest and its receipt by @kingchenc in #64
- deps: @napi-rs/cli 3.10.4 with the loader it generates by @kingchenc in #65
- deps: uv 0.12.18 for the lockfile bootstrap by @kingchenc in #67
- deps: refresh the lockfile by @kingchenc in #66
- release: bump 0.1.2 -> 0.1.3 by @kingchenc in #68
Full Changelog: v0.1.2...v0.1.3
wickra-zk v0.1.2
wickra-zk v0.1.2 — zero-knowledge proofs of backtest performance: the deterministic Wickra engine runs inside a RISC Zero zkVM guest, and the receipt proves the report hash and headline metrics without revealing the candles or the strategy. Native Rust plus a C ABI hub for Python, Node.js, C, C++, C#, Go, Java and R; Linux and macOS.
Install
cargo install wickra-zk-cli
pip install wickra-zk
npm install wickra-zk
dotnet add package Wickra.Zk
go get github.com/wickra-lib/wickra-zk-goJava (Maven Central):
<dependency>
<groupId>org.wickra</groupId>
<artifactId>wickra-zk</artifactId>
<version>0.1.2</version>
</dependency>R (r-universe):
install.packages("wickrazk", repos = "https://wickra-lib.r-universe.dev")Attached assets
Pre-built artefacts for every supported platform — the same files this
workflow run published to crates.io, PyPI, and npm — plus standalone
CLI binaries and the C ABI libraries. C# ships to NuGet, Java to Maven
Central, Go to the wickra-zk-go module, and R to r-universe via
their own release jobs.
Auto-generated changelog
See below; GitHub computes it from the commits since the previous tag.
What's Changed
- bench: the nightly run fits its budget, and verification is measured by @kingchenc in #52
- docs: BENCHMARKS.md carries the measurements by @kingchenc in #53
- chore: uv 0.12.15 with matching checksums; the link check covers NuGet and pkg.go.dev by @kingchenc in #54
- chore: a re-resolved wasm lock and the family's spelling of shared things by @kingchenc in #55
- deps(cargo): bump the cargo group with 4 updates by @dependabot[bot] in #57
- docs: every README in wickra's shape; the Java loader reads the library the jar ships by @kingchenc in #56
- deps: actions/setup-java 6.0.1 and Microsoft.NET.Test.Sdk 18.10.0, the line Dependabot proposed in six siblings by @kingchenc in #60
- deps: the family pins follow the owners' releases; release: 0.1.2 by @kingchenc in #61
Full Changelog: v0.1.1...v0.1.2
wickra-zk v0.1.1
wickra-zk v0.1.1 — zero-knowledge proofs of backtest performance: the deterministic Wickra engine runs inside a RISC Zero zkVM guest, and the receipt proves the report hash and headline metrics without revealing the candles or the strategy. Native Rust plus a C ABI hub for Python, Node.js, C, C++, C#, Go, Java and R; Linux and macOS.
Install
cargo install wickra-zk-cli
pip install wickra-zk
npm install wickra-zk
dotnet add package Wickra.Zk
go get github.com/wickra-lib/wickra-zk-goJava (Maven Central):
<dependency>
<groupId>org.wickra</groupId>
<artifactId>wickra-zk</artifactId>
<version>0.1.1</version>
</dependency>R (r-universe):
install.packages("wickrazk", repos = "https://wickra-lib.r-universe.dev")Attached assets
Pre-built artefacts for every supported platform — the same files this
workflow run published to crates.io, PyPI, and npm — plus standalone
CLI binaries and the C ABI libraries. C# ships to NuGet, Java to Maven
Central, Go to the wickra-zk-go module, and R to r-universe via
their own release jobs.
Auto-generated changelog
See below; GitHub computes it from the commits since the previous tag.
What's Changed
- nuget: the native library ships as one runtime package per RID by @kingchenc in #50
- release: bump 0.1.0 -> 0.1.1 by @kingchenc in #51
Full Changelog: v0.1.0...v0.1.1