Bump Plonky3 by arthurpaulino · Pull Request #77 · argumentcomputer/multi-stark

arthurpaulino · 2026-09-01T12:32:45Z

Bump the Plonky3 dependency, fix breaking changes and patch the CUDA pipeline accordingly.

Adapt the CUDA PCS to Plonky3's pruned multiproof protocol while preserving the recursive verifier's compact per-query circuit. Add a verified advice re-encoder that expands native pruned authentication frontiers only at the recursion boundary, leaving native proof serialization and verification unchanged. Bring the CUDA PCS in line with upstream domain semantics by enforcing the minimum committed LDE height, restoring row bit reversal for domain evaluations, and covering Goldilocks log-height 32. Transfer the initial reduced FRI opening into its resident LDE without an extra allocation or device copy. Replace per-column cudaMemcpy2D submissions during Merkle construction with one coalesced gather kernel and cap staging at 32 MiB. Serialize concurrent quotient scheduling to prevent transient recursive-prover OOMs while retaining parallel GPU kernel execution. Update the compatibility digest and keep the CPU-only build independent of CUDA. The CUDA smoke suite passes 50 tests and produces byte-identical 17,213-byte CPU/GPU proofs. On the RTX PRO 6000 q50 Vector.extract_append workload, inner plus outer STARK proving is 65.87s on CPU and 8.81s on CUDA (7.48x), with identical proof sizes.

Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

samuelburnham · 2026-09-02T02:42:07Z

 use crate::cuda::mmcs::CudaCommitMmcs;
 let ldes: Option<Vec<_>> = inputs
- .par_iter()
+ .iter()


Is this intentional?

Yes. It only affects the cuda accelerated path. It tries to prevent OOMs.

`advice.rs` re-encoded a pruned FRI multiproof into one authentication path per query, for a recursive verifier that consumed the legacy per-query transport. That verifier now consumes the native pruned multiproof directly, so the expansion has no caller: nothing in this crate references `advice`, and the only downstream user (aiur) imported just its `AdviceError` type, which it can define locally. Drop the module and its `pub mod advice;` declaration. The library is self-consistent without it (lib + tests build clean; 35 tests pass). The frontier expansion remains recoverable from history if a fallback to the per-query transport is ever wanted.

gabriel-barrett · 2026-09-02T14:57:19Z

 assert_eq!(
 proof_bytes.len(),
-77_637,
+22_017,


Interesting, it seems like proof_bytes is much smaller now. What is the reasoning?

arthurpaulino · 2026-09-01T12:32:45Z

Bump the Plonky3 dependency, fix breaking changes and patch the CUDA pipeline accordingly.

Adapt the CUDA PCS to Plonky3's pruned multiproof protocol while preserving the recursive verifier's compact per-query circuit. Add a verified advice re-encoder that expands native pruned authentication frontiers only at the recursion boundary, leaving native proof serialization and verification unchanged. Bring the CUDA PCS in line with upstream domain semantics by enforcing the minimum committed LDE height, restoring row bit reversal for domain evaluations, and covering Goldilocks log-height 32. Transfer the initial reduced FRI opening into its resident LDE without an extra allocation or device copy. Replace per-column cudaMemcpy2D submissions during Merkle construction with one coalesced gather kernel and cap staging at 32 MiB. Serialize concurrent quotient scheduling to prevent transient recursive-prover OOMs while retaining parallel GPU kernel execution. Update the compatibility digest and keep the CPU-only build independent of CUDA. The CUDA smoke suite passes 50 tests and produces byte-identical 17,213-byte CPU/GPU proofs. On the RTX PRO 6000 q50 Vector.extract_append workload, inner plus outer STARK proving is 65.87s on CPU and 8.81s on CUDA (7.48x), with identical proof sizes.

Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

samuelburnham · 2026-09-02T02:42:07Z

 use crate::cuda::mmcs::CudaCommitMmcs;
 let ldes: Option<Vec<_>> = inputs
- .par_iter()
+ .iter()


Is this intentional?

Yes. It only affects the cuda accelerated path. It tries to prevent OOMs.

`advice.rs` re-encoded a pruned FRI multiproof into one authentication path per query, for a recursive verifier that consumed the legacy per-query transport. That verifier now consumes the native pruned multiproof directly, so the expansion has no caller: nothing in this crate references `advice`, and the only downstream user (aiur) imported just its `AdviceError` type, which it can define locally. Drop the module and its `pub mod advice;` declaration. The library is self-consistent without it (lib + tests build clean; 35 tests pass). The frontier expansion remains recoverable from history if a fallback to the per-query transport is ever wanted.

gabriel-barrett · 2026-09-02T14:57:19Z

 assert_eq!(
 proof_bytes.len(),
-77_637,
+22_017,


Interesting, it seems like proof_bytes is much smaller now. What is the reasoning?

arthurpaulino · 2026-09-01T12:32:45Z

Bump the Plonky3 dependency, fix breaking changes and patch the CUDA pipeline accordingly.

Adapt the CUDA PCS to Plonky3's pruned multiproof protocol while preserving the recursive verifier's compact per-query circuit. Add a verified advice re-encoder that expands native pruned authentication frontiers only at the recursion boundary, leaving native proof serialization and verification unchanged. Bring the CUDA PCS in line with upstream domain semantics by enforcing the minimum committed LDE height, restoring row bit reversal for domain evaluations, and covering Goldilocks log-height 32. Transfer the initial reduced FRI opening into its resident LDE without an extra allocation or device copy. Replace per-column cudaMemcpy2D submissions during Merkle construction with one coalesced gather kernel and cap staging at 32 MiB. Serialize concurrent quotient scheduling to prevent transient recursive-prover OOMs while retaining parallel GPU kernel execution. Update the compatibility digest and keep the CPU-only build independent of CUDA. The CUDA smoke suite passes 50 tests and produces byte-identical 17,213-byte CPU/GPU proofs. On the RTX PRO 6000 q50 Vector.extract_append workload, inner plus outer STARK proving is 65.87s on CPU and 8.81s on CUDA (7.48x), with identical proof sizes.

Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

samuelburnham · 2026-09-02T02:42:07Z

 use crate::cuda::mmcs::CudaCommitMmcs;
 let ldes: Option<Vec<_>> = inputs
- .par_iter()
+ .iter()


Is this intentional?

Yes. It only affects the cuda accelerated path. It tries to prevent OOMs.

`advice.rs` re-encoded a pruned FRI multiproof into one authentication path per query, for a recursive verifier that consumed the legacy per-query transport. That verifier now consumes the native pruned multiproof directly, so the expansion has no caller: nothing in this crate references `advice`, and the only downstream user (aiur) imported just its `AdviceError` type, which it can define locally. Drop the module and its `pub mod advice;` declaration. The library is self-consistent without it (lib + tests build clean; 35 tests pass). The frontier expansion remains recoverable from history if a fallback to the per-query transport is ever wanted.

gabriel-barrett · 2026-09-02T14:57:19Z

 assert_eq!(
 proof_bytes.len(),
-77_637,
+22_017,


Interesting, it seems like proof_bytes is much smaller now. What is the reasoning?

arthurpaulino · 2026-09-01T12:32:45Z

Bump the Plonky3 dependency, fix breaking changes and patch the CUDA pipeline accordingly.

Adapt the CUDA PCS to Plonky3's pruned multiproof protocol while preserving the recursive verifier's compact per-query circuit. Add a verified advice re-encoder that expands native pruned authentication frontiers only at the recursion boundary, leaving native proof serialization and verification unchanged. Bring the CUDA PCS in line with upstream domain semantics by enforcing the minimum committed LDE height, restoring row bit reversal for domain evaluations, and covering Goldilocks log-height 32. Transfer the initial reduced FRI opening into its resident LDE without an extra allocation or device copy. Replace per-column cudaMemcpy2D submissions during Merkle construction with one coalesced gather kernel and cap staging at 32 MiB. Serialize concurrent quotient scheduling to prevent transient recursive-prover OOMs while retaining parallel GPU kernel execution. Update the compatibility digest and keep the CPU-only build independent of CUDA. The CUDA smoke suite passes 50 tests and produces byte-identical 17,213-byte CPU/GPU proofs. On the RTX PRO 6000 q50 Vector.extract_append workload, inner plus outer STARK proving is 65.87s on CPU and 8.81s on CUDA (7.48x), with identical proof sizes.

Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

samuelburnham · 2026-09-02T02:42:07Z

 use crate::cuda::mmcs::CudaCommitMmcs;
 let ldes: Option<Vec<_>> = inputs
- .par_iter()
+ .iter()


Is this intentional?

Yes. It only affects the cuda accelerated path. It tries to prevent OOMs.

`advice.rs` re-encoded a pruned FRI multiproof into one authentication path per query, for a recursive verifier that consumed the legacy per-query transport. That verifier now consumes the native pruned multiproof directly, so the expansion has no caller: nothing in this crate references `advice`, and the only downstream user (aiur) imported just its `AdviceError` type, which it can define locally. Drop the module and its `pub mod advice;` declaration. The library is self-consistent without it (lib + tests build clean; 35 tests pass). The frontier expansion remains recoverable from history if a fallback to the per-query transport is ever wanted.

gabriel-barrett · 2026-09-02T14:57:19Z

 assert_eq!(
 proof_bytes.len(),
-77_637,
+22_017,


Interesting, it seems like proof_bytes is much smaller now. What is the reasoning?

arthurpaulino · 2026-09-01T12:32:45Z

Bump the Plonky3 dependency, fix breaking changes and patch the CUDA pipeline accordingly.

Adapt the CUDA PCS to Plonky3's pruned multiproof protocol while preserving the recursive verifier's compact per-query circuit. Add a verified advice re-encoder that expands native pruned authentication frontiers only at the recursion boundary, leaving native proof serialization and verification unchanged. Bring the CUDA PCS in line with upstream domain semantics by enforcing the minimum committed LDE height, restoring row bit reversal for domain evaluations, and covering Goldilocks log-height 32. Transfer the initial reduced FRI opening into its resident LDE without an extra allocation or device copy. Replace per-column cudaMemcpy2D submissions during Merkle construction with one coalesced gather kernel and cap staging at 32 MiB. Serialize concurrent quotient scheduling to prevent transient recursive-prover OOMs while retaining parallel GPU kernel execution. Update the compatibility digest and keep the CPU-only build independent of CUDA. The CUDA smoke suite passes 50 tests and produces byte-identical 17,213-byte CPU/GPU proofs. On the RTX PRO 6000 q50 Vector.extract_append workload, inner plus outer STARK proving is 65.87s on CPU and 8.81s on CUDA (7.48x), with identical proof sizes.

Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

samuelburnham · 2026-09-02T02:42:07Z

 use crate::cuda::mmcs::CudaCommitMmcs;
 let ldes: Option<Vec<_>> = inputs
- .par_iter()
+ .iter()


Is this intentional?

Yes. It only affects the cuda accelerated path. It tries to prevent OOMs.

`advice.rs` re-encoded a pruned FRI multiproof into one authentication path per query, for a recursive verifier that consumed the legacy per-query transport. That verifier now consumes the native pruned multiproof directly, so the expansion has no caller: nothing in this crate references `advice`, and the only downstream user (aiur) imported just its `AdviceError` type, which it can define locally. Drop the module and its `pub mod advice;` declaration. The library is self-consistent without it (lib + tests build clean; 35 tests pass). The frontier expansion remains recoverable from history if a fallback to the per-query transport is ever wanted.

gabriel-barrett · 2026-09-02T14:57:19Z

 assert_eq!(
 proof_bytes.len(),
-77_637,
+22_017,


Interesting, it seems like proof_bytes is much smaller now. What is the reasoning?

arthurpaulino · 2026-09-01T12:32:45Z

Bump the Plonky3 dependency, fix breaking changes and patch the CUDA pipeline accordingly.

Adapt the CUDA PCS to Plonky3's pruned multiproof protocol while preserving the recursive verifier's compact per-query circuit. Add a verified advice re-encoder that expands native pruned authentication frontiers only at the recursion boundary, leaving native proof serialization and verification unchanged. Bring the CUDA PCS in line with upstream domain semantics by enforcing the minimum committed LDE height, restoring row bit reversal for domain evaluations, and covering Goldilocks log-height 32. Transfer the initial reduced FRI opening into its resident LDE without an extra allocation or device copy. Replace per-column cudaMemcpy2D submissions during Merkle construction with one coalesced gather kernel and cap staging at 32 MiB. Serialize concurrent quotient scheduling to prevent transient recursive-prover OOMs while retaining parallel GPU kernel execution. Update the compatibility digest and keep the CPU-only build independent of CUDA. The CUDA smoke suite passes 50 tests and produces byte-identical 17,213-byte CPU/GPU proofs. On the RTX PRO 6000 q50 Vector.extract_append workload, inner plus outer STARK proving is 65.87s on CPU and 8.81s on CUDA (7.48x), with identical proof sizes.

Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

samuelburnham · 2026-09-02T02:42:07Z

 use crate::cuda::mmcs::CudaCommitMmcs;
 let ldes: Option<Vec<_>> = inputs
- .par_iter()
+ .iter()


Is this intentional?

Yes. It only affects the cuda accelerated path. It tries to prevent OOMs.

`advice.rs` re-encoded a pruned FRI multiproof into one authentication path per query, for a recursive verifier that consumed the legacy per-query transport. That verifier now consumes the native pruned multiproof directly, so the expansion has no caller: nothing in this crate references `advice`, and the only downstream user (aiur) imported just its `AdviceError` type, which it can define locally. Drop the module and its `pub mod advice;` declaration. The library is self-consistent without it (lib + tests build clean; 35 tests pass). The frontier expansion remains recoverable from history if a fallback to the per-query transport is ever wanted.

gabriel-barrett · 2026-09-02T14:57:19Z

 assert_eq!(
 proof_bytes.len(),
-77_637,
+22_017,


Interesting, it seems like proof_bytes is much smaller now. What is the reasoning?

arthurpaulino · 2026-09-01T12:32:45Z

Bump the Plonky3 dependency, fix breaking changes and patch the CUDA pipeline accordingly.

Adapt the CUDA PCS to Plonky3's pruned multiproof protocol while preserving the recursive verifier's compact per-query circuit. Add a verified advice re-encoder that expands native pruned authentication frontiers only at the recursion boundary, leaving native proof serialization and verification unchanged. Bring the CUDA PCS in line with upstream domain semantics by enforcing the minimum committed LDE height, restoring row bit reversal for domain evaluations, and covering Goldilocks log-height 32. Transfer the initial reduced FRI opening into its resident LDE without an extra allocation or device copy. Replace per-column cudaMemcpy2D submissions during Merkle construction with one coalesced gather kernel and cap staging at 32 MiB. Serialize concurrent quotient scheduling to prevent transient recursive-prover OOMs while retaining parallel GPU kernel execution. Update the compatibility digest and keep the CPU-only build independent of CUDA. The CUDA smoke suite passes 50 tests and produces byte-identical 17,213-byte CPU/GPU proofs. On the RTX PRO 6000 q50 Vector.extract_append workload, inner plus outer STARK proving is 65.87s on CPU and 8.81s on CUDA (7.48x), with identical proof sizes.

Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

samuelburnham · 2026-09-02T02:42:07Z

 use crate::cuda::mmcs::CudaCommitMmcs;
 let ldes: Option<Vec<_>> = inputs
- .par_iter()
+ .iter()


Is this intentional?

Yes. It only affects the cuda accelerated path. It tries to prevent OOMs.

`advice.rs` re-encoded a pruned FRI multiproof into one authentication path per query, for a recursive verifier that consumed the legacy per-query transport. That verifier now consumes the native pruned multiproof directly, so the expansion has no caller: nothing in this crate references `advice`, and the only downstream user (aiur) imported just its `AdviceError` type, which it can define locally. Drop the module and its `pub mod advice;` declaration. The library is self-consistent without it (lib + tests build clean; 35 tests pass). The frontier expansion remains recoverable from history if a fallback to the per-query transport is ever wanted.

gabriel-barrett · 2026-09-02T14:57:19Z

 assert_eq!(
 proof_bytes.len(),
-77_637,
+22_017,


Interesting, it seems like proof_bytes is much smaller now. What is the reasoning?

arthurpaulino · 2026-09-01T12:32:45Z

Bump the Plonky3 dependency, fix breaking changes and patch the CUDA pipeline accordingly.

Adapt the CUDA PCS to Plonky3's pruned multiproof protocol while preserving the recursive verifier's compact per-query circuit. Add a verified advice re-encoder that expands native pruned authentication frontiers only at the recursion boundary, leaving native proof serialization and verification unchanged. Bring the CUDA PCS in line with upstream domain semantics by enforcing the minimum committed LDE height, restoring row bit reversal for domain evaluations, and covering Goldilocks log-height 32. Transfer the initial reduced FRI opening into its resident LDE without an extra allocation or device copy. Replace per-column cudaMemcpy2D submissions during Merkle construction with one coalesced gather kernel and cap staging at 32 MiB. Serialize concurrent quotient scheduling to prevent transient recursive-prover OOMs while retaining parallel GPU kernel execution. Update the compatibility digest and keep the CPU-only build independent of CUDA. The CUDA smoke suite passes 50 tests and produces byte-identical 17,213-byte CPU/GPU proofs. On the RTX PRO 6000 q50 Vector.extract_append workload, inner plus outer STARK proving is 65.87s on CPU and 8.81s on CUDA (7.48x), with identical proof sizes.

Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

samuelburnham · 2026-09-02T02:42:07Z

 use crate::cuda::mmcs::CudaCommitMmcs;
 let ldes: Option<Vec<_>> = inputs
- .par_iter()
+ .iter()


Is this intentional?

Yes. It only affects the cuda accelerated path. It tries to prevent OOMs.

`advice.rs` re-encoded a pruned FRI multiproof into one authentication path per query, for a recursive verifier that consumed the legacy per-query transport. That verifier now consumes the native pruned multiproof directly, so the expansion has no caller: nothing in this crate references `advice`, and the only downstream user (aiur) imported just its `AdviceError` type, which it can define locally. Drop the module and its `pub mod advice;` declaration. The library is self-consistent without it (lib + tests build clean; 35 tests pass). The frontier expansion remains recoverable from history if a fallback to the per-query transport is ever wanted.

gabriel-barrett · 2026-09-02T14:57:19Z

 assert_eq!(
 proof_bytes.len(),
-77_637,
+22_017,


Interesting, it seems like proof_bytes is much smaller now. What is the reasoning?

arthurpaulino added 3 commits September 1, 2026 12:49

Bump Plonky3 dependency
9d470ac

Fix the Nix Rust 1.98 toolchain hash
fac47fa
Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

arthurpaulino force-pushed the ap/bump-p3 branch from bc69d37 to fac47faCompare September 1, 2026 12:50

samuelburnham previously approved these changes Sep 2, 2026
View reviewed changes

gabriel-barrett reviewed Sep 2, 2026
View reviewed changes

Comment threadsrc/verifier.rs Outdated

arthurpaulino dismissed samuelburnham’s stale review via 2a1d3a5September 2, 2026 17:14

arthurpaulino force-pushed the ap/bump-p3 branch from 8f3c50d to 2a1d3a5Compare September 2, 2026 17:14

arthurpaulino enabled auto-merge (squash) September 2, 2026 17:17

gabriel-barrett approved these changes Sep 2, 2026
View reviewed changes

arthurpaulino merged commit a8aab73 into mainSep 2, 2026
7 checks passed

arthurpaulino deleted the ap/bump-p3 branch September 2, 2026 17:22

arthurpaulino added 3 commits September 1, 2026 12:49

Bump Plonky3 dependency
9d470ac

Fix the Nix Rust 1.98 toolchain hash
fac47fa
Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

arthurpaulino force-pushed the ap/bump-p3 branch from bc69d37 to fac47faCompare September 1, 2026 12:50

samuelburnham previously approved these changes Sep 2, 2026
View reviewed changes

gabriel-barrett reviewed Sep 2, 2026
View reviewed changes

Comment threadsrc/verifier.rs Outdated

arthurpaulino dismissed samuelburnham’s stale review via 2a1d3a5September 2, 2026 17:14

arthurpaulino force-pushed the ap/bump-p3 branch from 8f3c50d to 2a1d3a5Compare September 2, 2026 17:14

arthurpaulino enabled auto-merge (squash) September 2, 2026 17:17

gabriel-barrett approved these changes Sep 2, 2026
View reviewed changes

arthurpaulino merged commit a8aab73 into mainSep 2, 2026
7 checks passed

arthurpaulino deleted the ap/bump-p3 branch September 2, 2026 17:22

arthurpaulino added 3 commits September 1, 2026 12:49

Bump Plonky3 dependency
9d470ac

Fix the Nix Rust 1.98 toolchain hash
fac47fa
Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

arthurpaulino force-pushed the ap/bump-p3 branch from bc69d37 to fac47faCompare September 1, 2026 12:50

samuelburnham previously approved these changes Sep 2, 2026
View reviewed changes

gabriel-barrett reviewed Sep 2, 2026
View reviewed changes

Comment threadsrc/verifier.rs Outdated

arthurpaulino dismissed samuelburnham’s stale review via 2a1d3a5September 2, 2026 17:14

arthurpaulino force-pushed the ap/bump-p3 branch from 8f3c50d to 2a1d3a5Compare September 2, 2026 17:14

arthurpaulino enabled auto-merge (squash) September 2, 2026 17:17

gabriel-barrett approved these changes Sep 2, 2026
View reviewed changes

arthurpaulino merged commit a8aab73 into mainSep 2, 2026
7 checks passed

arthurpaulino deleted the ap/bump-p3 branch September 2, 2026 17:22

arthurpaulino added 3 commits September 1, 2026 12:49

Bump Plonky3 dependency
9d470ac

Fix the Nix Rust 1.98 toolchain hash
fac47fa
Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

arthurpaulino force-pushed the ap/bump-p3 branch from bc69d37 to fac47faCompare September 1, 2026 12:50

samuelburnham previously approved these changes Sep 2, 2026
View reviewed changes

gabriel-barrett reviewed Sep 2, 2026
View reviewed changes

Comment threadsrc/verifier.rs Outdated

arthurpaulino dismissed samuelburnham’s stale review via 2a1d3a5September 2, 2026 17:14

arthurpaulino force-pushed the ap/bump-p3 branch from 8f3c50d to 2a1d3a5Compare September 2, 2026 17:14

arthurpaulino enabled auto-merge (squash) September 2, 2026 17:17

gabriel-barrett approved these changes Sep 2, 2026
View reviewed changes

arthurpaulino merged commit a8aab73 into mainSep 2, 2026
7 checks passed

arthurpaulino deleted the ap/bump-p3 branch September 2, 2026 17:22

arthurpaulino added 3 commits September 1, 2026 12:49

Bump Plonky3 dependency
9d470ac

Fix the Nix Rust 1.98 toolchain hash
fac47fa
Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

arthurpaulino force-pushed the ap/bump-p3 branch from bc69d37 to fac47faCompare September 1, 2026 12:50

samuelburnham previously approved these changes Sep 2, 2026
View reviewed changes

gabriel-barrett reviewed Sep 2, 2026
View reviewed changes

Comment threadsrc/verifier.rs Outdated

arthurpaulino dismissed samuelburnham’s stale review via 2a1d3a5September 2, 2026 17:14

arthurpaulino force-pushed the ap/bump-p3 branch from 8f3c50d to 2a1d3a5Compare September 2, 2026 17:14

arthurpaulino enabled auto-merge (squash) September 2, 2026 17:17

gabriel-barrett approved these changes Sep 2, 2026
View reviewed changes

arthurpaulino merged commit a8aab73 into mainSep 2, 2026
7 checks passed

arthurpaulino deleted the ap/bump-p3 branch September 2, 2026 17:22

arthurpaulino added 3 commits September 1, 2026 12:49

Bump Plonky3 dependency
9d470ac

Fix the Nix Rust 1.98 toolchain hash
fac47fa
Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

arthurpaulino force-pushed the ap/bump-p3 branch from bc69d37 to fac47faCompare September 1, 2026 12:50

samuelburnham previously approved these changes Sep 2, 2026
View reviewed changes

gabriel-barrett reviewed Sep 2, 2026
View reviewed changes

Comment threadsrc/verifier.rs Outdated

arthurpaulino dismissed samuelburnham’s stale review via 2a1d3a5September 2, 2026 17:14

arthurpaulino force-pushed the ap/bump-p3 branch from 8f3c50d to 2a1d3a5Compare September 2, 2026 17:14

arthurpaulino enabled auto-merge (squash) September 2, 2026 17:17

gabriel-barrett approved these changes Sep 2, 2026
View reviewed changes

arthurpaulino merged commit a8aab73 into mainSep 2, 2026
7 checks passed

arthurpaulino deleted the ap/bump-p3 branch September 2, 2026 17:22

arthurpaulino added 3 commits September 1, 2026 12:49

Bump Plonky3 dependency
9d470ac

Fix the Nix Rust 1.98 toolchain hash
fac47fa
Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

arthurpaulino force-pushed the ap/bump-p3 branch from bc69d37 to fac47faCompare September 1, 2026 12:50

samuelburnham previously approved these changes Sep 2, 2026
View reviewed changes

gabriel-barrett reviewed Sep 2, 2026
View reviewed changes

Comment threadsrc/verifier.rs Outdated

arthurpaulino dismissed samuelburnham’s stale review via 2a1d3a5September 2, 2026 17:14

arthurpaulino force-pushed the ap/bump-p3 branch from 8f3c50d to 2a1d3a5Compare September 2, 2026 17:14

arthurpaulino enabled auto-merge (squash) September 2, 2026 17:17

gabriel-barrett approved these changes Sep 2, 2026
View reviewed changes

arthurpaulino merged commit a8aab73 into mainSep 2, 2026
7 checks passed

arthurpaulino deleted the ap/bump-p3 branch September 2, 2026 17:22

arthurpaulino added 3 commits September 1, 2026 12:49

Bump Plonky3 dependency
9d470ac

Fix the Nix Rust 1.98 toolchain hash
fac47fa
Update the fixed-output hash used by Fenix to match the Rust 1.98 channel manifest selected by rust-toolchain.toml. This restores both the packaged Nix build and the development shell without changing the pinned toolchain or flake inputs.

arthurpaulino force-pushed the ap/bump-p3 branch from bc69d37 to fac47faCompare September 1, 2026 12:50

samuelburnham previously approved these changes Sep 2, 2026
View reviewed changes

gabriel-barrett reviewed Sep 2, 2026
View reviewed changes

Comment threadsrc/verifier.rs Outdated

arthurpaulino dismissed samuelburnham’s stale review via 2a1d3a5September 2, 2026 17:14

arthurpaulino force-pushed the ap/bump-p3 branch from 8f3c50d to 2a1d3a5Compare September 2, 2026 17:14

arthurpaulino enabled auto-merge (squash) September 2, 2026 17:17

gabriel-barrett approved these changes Sep 2, 2026
View reviewed changes

arthurpaulino merged commit a8aab73 into mainSep 2, 2026
7 checks passed

arthurpaulino deleted the ap/bump-p3 branch September 2, 2026 17:22

Uh oh!

Conversation

arthurpaulino commented Sep 1, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

arthurpaulino commented Sep 1, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

arthurpaulino commented Sep 1, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

arthurpaulino commented Sep 1, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants