Consensys-Incorporated/zesu#140 adds an opt-in "zisk-object" build target that emits zesu-zisk.o (published as zesu.zisk.o) using Zbb/Zbs RISC-V extensions, in addition to the existing baseline zesu.rv64im.o guest artifact. Both are now published by the manual release workflow, and CI/benchmark workflows run a matrix comparing the two variants.
docs/get-started/get-guest-program.mdx only documents zesu.rv64im.o as "the" guest artifact, targeting the rv64im baseline ISA. It doesn't mention the new Zbb/Zbs-optimized ZisK variant, so integrators using ZisK have no documented guidance on which artifact to pull or why it exists.
Suggested docs to update: docs/get-started/get-guest-program.mdx — add a section describing the two published guest artifacts (zesu.rv64im.o vs zesu.zisk.o), when to use each, and the Zbb/Zbs performance rationale. Cross-reference from any ZisK-specific
integration guidance.
Consensys-Incorporated/zesu#140 adds an opt-in "zisk-object" build target that emits zesu-zisk.o (published as zesu.zisk.o) using Zbb/Zbs RISC-V extensions, in addition to the existing baseline zesu.rv64im.o guest artifact. Both are now published by the manual release workflow, and CI/benchmark workflows run a matrix comparing the two variants.
docs/get-started/get-guest-program.mdxonly documents zesu.rv64im.o as "the" guest artifact, targeting the rv64im baseline ISA. It doesn't mention the new Zbb/Zbs-optimized ZisK variant, so integrators using ZisK have no documented guidance on which artifact to pull or why it exists.Suggested docs to update:
docs/get-started/get-guest-program.mdx— add a section describing the two published guest artifacts (zesu.rv64im.o vs zesu.zisk.o), when to use each, and the Zbb/Zbs performance rationale. Cross-reference from any ZisK-specificintegration guidance.