Crates.io | starky |
lib.rs | starky |
version | |
source | src |
created_at | 2023-01-30 20:42:25.655417 |
updated_at | 2024-11-25 18:05:37.018343 |
description | Implementation of STARKs |
homepage | https://github.com/0xPolygonZero/plonky2 |
repository | https://github.com/0xPolygonZero/plonky2 |
max_upload_size | |
id | 772082 |
Cargo.toml error: | TOML parse error at line 21, column 1 | 21 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
Starky is a FRI-based STARK implementation.
It is built for speed, features highly efficient recursive verification through plonky2
circuits and gadgets, and is
being used as backend proving system for the Polygon Zero Type-1 zkEVM.
While STARKs can be made Zero-Knowledge, the primary purpose of starky
is to provide fast STARK proof generation. As such,
ZK is disabled by default on starky
. Applications requiring their proof to be zero-knowledge
would need to apply a
recursive wrapper on top of their STARK proof with the zero_knowledge
parameter activated in their CircuitConfig
.
See plonky2
documentation for more info.
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.