chore: update jellyfish & arkworks deps (#3601)

* upgrade alloy from 0.13 to 1.0

* bindings

* add migration

* remove rand_v0.9

* clippy

* remove commented test

* clippy

* clippy

* update alloy version for just gen-bindings

* layout test: only exit with non-zero on error

Newer versions of forge will fail a test if vm.ffi returns with
non-zero exit code.

* add migration test for postgres

* filesystem migration test

* add more events in fs test

* clippy

* clippy

* update ark deps

* fix advz compatibility

* pin serde to 1.0.219 for alloy compatibility

* start/stop vm broadcast in same fn

* Workaround foundry CreatCollision issue

As long as we start/stop broadcasts in the same function we can work
around the issue.

See: foundry-rs/foundry#11633

Also, Revert "start/stop vm broadcast in same fn"

This reverts commit 5f4a580.

* don't use startBroadcast for single tx

* cargo hakari

* fixing rand & hakari

* fix compilation error

* upgrade bn254 submodule

* update vk

* fmt

* fix serde version for alloy compilation

* update bindings for bn254 update

* contract test fix

* Delete hotshot-state-prover/src/bin/state-relay-watcher.rs

* fk alloy

* remove todo comment

* address comments

* fix decode_raw_log()

* fmt

* cdn deps

* manually remove the unwanted `print-trace` feature

* update vk for v1/v2

* fix bindings for V1/V2

* audit

* plastic surgery

* address comments

* alloy features

* use dummy [email protected]

* revert ark-relations patch

---------

Co-authored-by: imabdulbasit <[email protected]>
Co-authored-by: Abdul Basit <[email protected]>
Co-authored-by: sveitser <[email protected]>

Author: 3 people

.cargo/audit.toml

@@ -13,6 +13,6 @@ ignore = [
     # To upgrade async-tungstenite we need a new release of tide-websockets, which seems unlikely
     # https://github.com/http-rs/tide-websockets
     "RUSTSEC-2025-0009",
-    # Requires jf to upgrade ark from 0.4 to 0.5, so we can use tracing-subscriber 0.3 exclusively
+    # Still here because of `ark-relations` crate.
     "RUSTSEC-2025-0055",
 ]

.config/hakari.toml

@@ -0,0 +1,38 @@
+# This file contains settings for `cargo hakari`.
+# See https://docs.rs/cargo-hakari/latest/cargo_hakari/config for a full list of options.
+
+hakari-package = "workspace-hack"
+
+# Format version for hakari's output. Version 4 requires cargo-hakari 0.9.22 or above.
+dep-format-version = "4"
+
+# Setting workspace.resolver = "2" or higher in the root Cargo.toml is HIGHLY recommended.
+# Hakari works much better with the v2 resolver. (The v2 and v3 resolvers are identical from
+# hakari's perspective, so you're welcome to set either.)
+#
+# For more about the new feature resolver, see:
+# https://blog.rust-lang.org/2021/03/25/Rust-1.51.0.html#cargos-new-feature-resolver
+resolver = "2"
+
+# Add triples corresponding to platforms commonly used by developers here.
+# https://doc.rust-lang.org/rustc/platform-support.html
+platforms = [
+    # "x86_64-unknown-linux-gnu",
+    # "x86_64-apple-darwin",
+    # "aarch64-apple-darwin",
+    # "x86_64-pc-windows-msvc",
+]
+
+# Write out exact versions rather than a semver range. (Defaults to false.)
+# exact-versions = true
+
+[traversal-excludes]
+third-party = [
+  # `jf-vid` has features that need to be explicitly enabled via HotShot features --
+  # namely "gpu-vid" and "test-srs". Hence, we exclude it from `workspace-hack` so that
+  # these features are not enabled for all crates by default.
+  { name = "jf-advz", git = "https://github.com/EspressoSystems/jellyfish-compat", tag = "jf-advz-v0.2.1" },
+  # `sqlx` has internal packages that can have different features depending on the host/target platform.
+  # This only gets pulled in indirectly via the CDN, so it's safe to just exclude.
+  { name = "sqlx" }
+]