Skip to content

Cluster-tool: Drop base_per_transaction_net_usage from generated genesis#28

Merged
heifner merged 2 commits into
masterfrom
cleanup/remove-base-per-transaction-net-usage
Jul 15, 2026
Merged

Cluster-tool: Drop base_per_transaction_net_usage from generated genesis#28
heifner merged 2 commits into
masterfrom
cleanup/remove-base-per-transaction-net-usage

Conversation

@heifner

@heifner heifner commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Summary

wire-sysio removes base_per_transaction_net_usage from chain_config (Wire-Network/wire-sysio#519), so freshly generated genesis files must not carry it. Drops the field from ClusterConfigGenesisRenderer and aligns the production-bootstrap doc table with the launcher defaults.

Old genesis files that still carry the field parse fine (unknown keys are ignored) and produce the same chain id as without it; dropping it keeps generated files canonical.

wire-sysio removes the parameter from chain_config (it no longer
participates in NET billing), so freshly generated genesis files must
not carry it. Aligns the production-bootstrap doc table with the
launcher defaults.
max_block_net_usage: 1_048_576,
target_block_net_usage_pct: 10_000,
max_transaction_net_usage: 524_288,
base_per_transaction_net_usage: 12,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P2] Please add a regression assertion for the removed field

This changes the generated genesis schema, but no test verifies that base_per_transaction_net_usage is absent. The existing genesis-renderer tests still pass if this deletion is reverted. Please add an assertion in packages/cluster-tool/tests/config/NodeConfig.test.ts against the parsed initial_configuration, as required by the repository test policy.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added in 4747809: NodeConfig.test.ts now parses the rendered genesis and asserts initial_configuration has no base_per_transaction_net_usage, anchored by a neighbor-field check so the assertion reads the right object. Reverting the renderer deletion fails the suite.

…_usage

Review follow-up: lock the schema change in with a regression assertion
on the parsed initial_configuration so reverting the renderer deletion
fails the suite.
@heifner
heifner requested a review from huangminghuang July 15, 2026 21:18

@huangminghuang huangminghuang left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-reviewed at 4747809. The regression test addresses the prior finding; local build and all 530 cluster-tool tests pass.

@heifner
heifner merged commit 762b881 into master Jul 15, 2026
@heifner
heifner deleted the cleanup/remove-base-per-transaction-net-usage branch July 15, 2026 21:31
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.

2 participants