Skip to content

Add notify_cpu_stipend to Blockchain Parameters - #132

Draft
heifner wants to merge 1 commit into
masterfrom
feature/notify-cpu-stipend
Draft

heifner wants to merge 1 commit into
masterfrom
feature/notify-cpu-stipend

Conversation

@heifner

@heifner heifner commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

wire-sysio's chain_config gains notify_cpu_stipend, the CPU in microseconds of a notified contract's code that whoever pays for the notifying action covers: 100 by default, 0 for none. The chain appends it after max_kv_secondary_key_size (id 17), and blockchain_parameters gains it in the same place, so set_blockchain_parameters / get_blockchain_parameters keep matching the chain field for field. A contract built with an older CDT packs one field fewer, so setparams from sysio.bios and sysio.system needs this version.

abigen-pass/blockchain_parameters_test pins the struct's ABI, fields in the chain's order ending with notify_cpu_stipend.

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_config` gains `notify_cpu_stipend`: the CPU, in microseconds, of a notified contract's code that whoever pays for the notifying action covers. The default is 100, and 0 means no stipend. `blockchain_parameters` gains the field last, as the chain packs it, so `set_blockchain_parameters` and `get_blockchain_parameters` keep matching the chain field for field. A toolchain test pins the struct's ABI.

Change-Id: Ica101e9c59a66f06fcc2d7c91db31f96089d5ad4

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