zec
/
orchard
mirror of https://github.com/zcash/orchard.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
orchard/Cargo.toml

86 lines
1.7 KiB
TOML
Raw Normal View History

Initial commit
2020-10-20 14:12:37 -07:00
[package]
Rename to Orchard
2021-01-08 08:32:36 -08:00
name = "orchard"
Initial commit
2020-10-20 14:12:37 -07:00
version = "0.0.0"
authors = [
"Sean Bowe <sean@electriccoin.co>",
Update crate authors
2020-10-20 15:03:33 -07:00
"Jack Grigg <jack@electriccoin.co>",
Initial commit
2020-10-20 14:12:37 -07:00
]
edition = "2018"
Better description
2020-10-20 14:36:48 -07:00
description = "Sapling on stilts!"
Update Cargo.toml Co-authored-by: ebfull <ewillbefull@gmail.com>
2021-04-26 16:41:14 -07:00
license-file = "LICENSE-BOSL"
Rename to Orchard
2021-01-08 08:32:36 -08:00
repository = "https://github.com/zcash/orchard"
documentation = "https://docs.rs/orchard"
Initial commit
2020-10-20 14:12:37 -07:00
readme = "README.md"
Changing TGPPL references to BOSL
2021-04-16 09:24:18 -07:00
# We are not publishing this yet.
Change to TGPPL
2020-10-20 14:12:51 -07:00
publish = false
Initial commit
2020-10-20 14:12:37 -07:00
[package.metadata.docs.rs]
rustdoc-args = [ "--html-in-header", "katex-header.html" ]
Collect benchmarks on criterion.dev
2020-10-20 15:18:25 -07:00
Add halo2 to dependencies
2020-10-20 15:18:40 -07:00
[dependencies]
fpe 0.5
2021-09-13 09:54:56 -07:00
aes = "0.7"
Use ArrayVec Co-authored-by: Daira Hopwood <daira@jacaranda.org>
2021-05-03 08:55:37 -07:00
arrayvec = "0.7.0"
mul::overflow.rs: Overflow check in variable-base scalar mul Simplify the canonicity check for variable-base scalar multiplication, by range-checking the low 130 bits rather than the low 127 bits. Signed-off-by: Daira Hopwood <daira@jacaranda.org> Co-authored-by: ying tong <yingtong@z.cash>
2021-06-13 06:06:34 -07:00
bigint = "4"
Migrate to bitvec 0.22, ff 0.10, group 0.10, pasta_curves 0.1
2021-06-04 12:38:28 -07:00
bitvec = "0.22"
Orchard key components
2021-03-05 15:25:45 -08:00
blake2b_simd = "0.5"
ff 0.11, group 0.11, pasta_curves 0.2 etc.
2021-09-06 12:18:18 -07:00
ff = "0.11"
fpe 0.5
2021-09-13 09:54:56 -07:00
fpe = "0.5"
ff 0.11, group 0.11, pasta_curves 0.2 etc.
2021-09-06 12:18:18 -07:00
group = "0.11"
Switch to halo2 0.1.0-beta.1 This is equivalent to the git revision we were previously patching.
2021-09-28 12:48:19 -07:00
halo2 = "=0.1.0-beta.1"
Update proptests to generate Merkle paths
2021-06-08 00:27:08 -07:00
lazy_static = "1"
memuse 0.2
2021-09-14 12:40:15 -07:00
memuse = { version = "0.2", features = ["nonempty"] }
Require pasta_curves 0.2.1 and bump halo2 revision - pasta_curves 0.2.1 is the first version that was relicensed as MIT OR Apache-2.0. - The halo2 revision includes the new license text.
2021-09-22 13:40:15 -07:00
pasta_curves = "0.2.1"
Add proptest generators for action and bundle types.
2021-04-27 06:49:49 -07:00
proptest = { version = "1.0.0", optional = true }
Implement ValueCommit^Orchard
2021-04-14 21:13:41 -07:00
rand = "0.8"
Use reddsa 0.1 instead of the git dependency
2021-11-19 15:10:46 -08:00
reddsa = "0.1"
nonempty 0.7 We can now correctly measure the heap-allocated memory used by a bundle.
2021-06-23 04:00:56 -07:00
nonempty = "0.7"
Add serde support for OrchardIncrementalTreeDigest
2021-06-17 09:57:47 -07:00
serde = { version = "1.0", features = ["derive"] }
Orchard key components
2021-03-05 15:25:45 -08:00
subtle = "2.3"
Use patches for halo2 and zcash_note_encryption dependencies While these two are in flux, it's hard to keep these revisions consistent (e.g. https://github.com/zcash/zcash/pull/5217 currently depends on two different versions of zcash_note_encryption). Using patches allows the downstream users (i.e. zcashd) to define its own set of patches, and keep everything in sync. This works fine now because we aren't actively making changes to the public APIs, only additions.
2021-06-14 15:17:15 -07:00
zcash_note_encryption = "0.0"
incrementalmerkletree 0.2
2021-12-17 08:39:48 -08:00
incrementalmerkletree = "0.2"
Orchard key components
2021-03-05 15:25:45 -08:00
Arity-3 Poseidon chip
2021-02-08 14:56:58 -08:00
# Developer tooling dependencies
plotters = { version = "0.3.0", optional = true }
Collect benchmarks on criterion.dev
2020-10-20 15:18:25 -07:00
[dev-dependencies]
criterion = "0.3"
Add test vectors from the reference implementation These are generated using v1.1 of the reference implementation.
2021-03-09 12:08:26 -08:00
hex = "0.4"
Use builder to generate "valid" bundles via proptest.
2021-04-27 12:56:36 -07:00
proptest = "1.0.0"
Migrate to latest `zcash_note_encryption` API
2021-12-16 21:31:24 -08:00
zcash_note_encryption = { version = "0.0", features = ["pre-zip-212"] }
Collect benchmarks on criterion.dev
2020-10-20 15:18:25 -07:00
Add circuit benchmarks and (on Unix) flamegraphs - Benchmarks: `cargo bench` - Flamegraphs: `cargo bench -- --profile-time 100`
2021-06-16 06:46:17 -07:00
[target.'cfg(unix)'.dev-dependencies]
pprof 0.6
2021-12-17 09:05:23 -08:00
pprof = { version = "0.6", features = ["criterion", "flamegraph"] }
Add circuit benchmarks and (on Unix) flamegraphs - Benchmarks: `cargo bench` - Flamegraphs: `cargo bench -- --profile-time 100`
2021-06-16 06:46:17 -07:00
Collect benchmarks on criterion.dev
2020-10-20 15:18:25 -07:00
[lib]
bench = false
Add small key derivation benchmarks
2021-03-19 22:19:51 -07:00
Add proptest generators for action and bundle types.
2021-04-27 06:49:49 -07:00
[features]
Arity-3 Poseidon chip
2021-02-08 14:56:58 -08:00
dev-graph = ["halo2/dev-graph", "plotters"]
Add proptest generators for action and bundle types.
2021-04-27 06:49:49 -07:00
test-dependencies = ["proptest"]
Add benchmark for note decryption
2021-08-05 17:03:03 -07:00
[[bench]]
name = "note_decryption"
harness = false
Expose and benchmark Sinsemilla primitive
2021-08-10 04:45:23 -07:00
[[bench]]
name = "primitives"
harness = false
Add small key derivation benchmarks
2021-03-19 22:19:51 -07:00
[[bench]]
name = "small"
harness = false
Use patches for halo2 and zcash_note_encryption dependencies While these two are in flux, it's hard to keep these revisions consistent (e.g. https://github.com/zcash/zcash/pull/5217 currently depends on two different versions of zcash_note_encryption). Using patches allows the downstream users (i.e. zcashd) to define its own set of patches, and keep everything in sync. This works fine now because we aren't actively making changes to the public APIs, only additions.
2021-06-14 15:17:15 -07:00
Add circuit benchmarks and (on Unix) flamegraphs - Benchmarks: `cargo bench` - Flamegraphs: `cargo bench -- --profile-time 100`
2021-06-16 06:46:17 -07:00
[[bench]]
name = "circuit"
harness = false
[profile.release]
debug = true
[profile.bench]
debug = true
Use patches for halo2 and zcash_note_encryption dependencies While these two are in flux, it's hard to keep these revisions consistent (e.g. https://github.com/zcash/zcash/pull/5217 currently depends on two different versions of zcash_note_encryption). Using patches allows the downstream users (i.e. zcashd) to define its own set of patches, and keep everything in sync. This works fine now because we aren't actively making changes to the public APIs, only additions.
2021-06-14 15:17:15 -07:00
[patch.crates-io]
Migrate to latest `zcash_note_encryption` API
2021-12-16 21:31:24 -08:00
zcash_note_encryption = { git = "https://github.com/zcash/librustzcash.git", rev = "76f364593a6d5b190dd23d26f8202adcd031b2d3" }