Marvin Jones
013e439c60
CallerData and the PDA derivation primitives keyed authorization off a program's image id (ProgramId), so two deployments of identical bytecode with different update_auth collided on the same PDA. Switch derivation, wire fields, and comparisons to the program's real dispatch AccountId throughout the host, guest, and test-harness code, including the privacy-circuit test harness's default dispatch address and the wrapped_token/ping_receiver governance-authorization check, which compared against the wrong address via the legacy bijection.
Programs
This crate serves two purposes at once:
- Provide one entrypoint for
cargo risczero buildto build guest binaries used in LEZ in one shot. - Provide access to the built binaries wrapped with
Programtype.
Binaries
This crate contains binaries taken from sub-directories: one per each program. This binaries are meant to be compiled with cargo risczero build. No other use is intended for them.
Library
You may import this crate as a library but it will only make sense if you enable artifacts feature flag.
Enabling this flag will make crate expect that binaries where already built and put in the right place (use just build-artifacts for that).
Why not just risc0_build::embed_methods() ?
Because this will either provide non-deterministic guest build or requires Docker. And forcing to use Docker to build the project is not an option for us especially because we also build Docker images for our services, which would mean we would have to call docker from docker (and this is not really feasible).
risc0_build::embed_methods() works well when you don't need deterministic build or Docker is not a problem. This is the case for our tests and we use it there.