blockifier: remove native_classes whitelist from the static config #12478
+5
−36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Note
Low Risk
Config/schema and bindings cleanup with limited behavioral impact; main risk is breaking consumers that still expect the removed static config fields or rely on the Python whitelist conversion.
Overview
native_classes_whitelistis removed from the staticCairoNativeRunConfigsurface (struct field, default, and config dumping) and from the generated nodeconfig_schema.jsonentries under bothbatcher_config.static_configandgateway_config.static_config.Node config pointer wiring is updated so the whitelist only points to
batcher_config.dynamic_config.native_classes_whitelist(with a TODO about gateway support), and native blockifier Python bindings now ignore thenative_classes_whitelistfield duringPyCairoNativeRunConfig -> CairoNativeRunConfigconversion for cross-repo compatibility. Related native class manager tests are adjusted to reflect the config shape change while still validating whitelist behavior viaget_runnable’s parameter.Written by Cursor Bugbot for commit 959aca2. This will update automatically on new commits. Configure here.