Skip to content

Per instance ere launch#1409

Draft
chetanyb wants to merge 3 commits into
ethpandaops:mainfrom
chetanyb:per-instance-ere-launch
Draft

Per instance ere launch#1409
chetanyb wants to merge 3 commits into
ethpandaops:mainfrom
chetanyb:per-instance-ere-launch

Conversation

@chetanyb
Copy link
Copy Markdown
Collaborator

Summary

  • Fixes error message paths to correctly reference per-instance zkvm configs
  • Launches ere-servers per-instance rather than per-proof-type, enabling separate GPU pools
  • GPU validation now checks exclusivity across all ere zkvms, not just first-per-proof-type

Known Limitations

Global zkboost_params.zkvms backward compatibility: When multiple instances share a global zkvms list (no per-instance override), each instance now launches its own ere-server with the same GPU config. This will fail GPU exclusivity validation. Workaround: use per-instance zkvms with distinctgpu.device_ids.

This is a design tradeoff — global zkvms previously meant "one shared ere-server", now they mean "template copied per-instance". A follow-up could add explicit shared: true semantics if needed.

Test plan

  • Existing configs with per-instance zkvms work
  • GPU overlap across instances is rejected
  • Error messages show correct instances[N].zkvms[M] paths

🤖 Generated with Claude Code

chetanyb added 3 commits May 25, 2026 16:56
- Validate zkboost instances using the effective zkvm list that the
launcher renders: per-instance zkvms when present, otherwise top-level
zkvms.

- Avoid injecting the default mock when any instance defines its own
zkvms, fail early on duplicate proof types within a single rendered
instance, and keep requested proof type plus ERE GPU validation aligned
with the launcher behavior.

- Add dry-run fixtures covering global zkvms, per-instance zkvms,
default mock injection, duplicate proof types, missing requested proof
types, and GPU overlap validation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant