Marvin Jones
b9152f58c0
Chained-call and public-transaction dispatch now address the target program directly by AccountId instead of routing through ProgramId and converting internally, closing the gap that blocked PDA-addressed program invocation. The field is named program_account_id (not account_id) to stay unambiguous next to the account_ids list it sits beside in the same structs. Execution/PDA-derivation logic that fundamentally needs the RISC0 image id (self_program_id, caller_program_id, env::verify, PDA seed derivation) stays ProgramId-typed, recovering it from the dispatched AccountId via the existing bijection where needed.
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.