Skip to content

Render the Notify CPU Stipend in the Cluster Genesis - #185

Draft
heifner wants to merge 2 commits into
masterfrom
feature/notify-cpu-stipend
Draft

heifner wants to merge 2 commits into
masterfrom
feature/notify-cpu-stipend

Conversation

@heifner

@heifner heifner commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

wire-sysio's chain parameters gain notify_cpu_stipend: the CPU, in microseconds, of a notified contract's code that whoever pays for the notifying action covers, with the contract paying only past it. The cluster genesis renders it as Constants.NOTIFY_CPU_STIPEND (100, the chain's default), and docs/production-bootstrap.md lists it in its initial_configuration table. Governance changes the value through setparams.

Paired changes

Land these together: wire-cdt first, then wire-sysio right after it, then wire-libraries-ts and wire-tools-ts.

wire-sysio's chain parameters gain `notify_cpu_stipend`, the CPU in microseconds of a notified contract's code that whoever pays for the notifying action covers. The genesis renderer sets it to `Constants.NOTIFY_CPU_STIPEND`, 100, matching the chain default, and production-bootstrap.md lists it. Governance changes it later through `setparams`.
…stipend

Brings in #186, which lowers `max_transaction_cpu_usage` to 150000 and `max_block_cpu_usage` to 200000; `notify_cpu_stipend` (100) stays within both. #186's test of the genesis keys now ends with `notify_cpu_stipend`, after the members that keep wire-sysio's defaults, and the bootstrap doc's table puts it in the free cell beside `max_transaction_cpu_usage`.

This branch has not been deployed

No deployments
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