Marvin Jones
5d8882fa7b
Codebase-wide rename of the stale loader_core crate name to program_loader_core (192 call sites, plus Cargo.toml dependency declarations), needed after the loader crate's rename landed upstream. ping_receiver/wrapped_token's UpdateSources handler, cross_zone_inbox's inbox_source_marker_account_id (moved from the now-superseded cross_zone_marker crate), and several test/genesis call sites still referenced ProgramId-bijection addresses or pre-unification struct shapes (CrossZoneMessage.src_program_id, WrappedTokenConfig/ ReceiverConfig field types, InboxInstruction::Dispatch's tuple form) that this branch's own dispatch-address unification had already moved past elsewhere.
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.