Skip to content

Regenerate Sysio Contract Types for the Notify CPU Stipend - #153

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

SysioContractTypes.ts is regenerated from wire-sysio's receiver-pays branch. The blockchain_parameters type of sysio.bios and sysio.system gains notify_cpu_stipend: the CPU, in microseconds, of a notified contract's code that whoever pays for the notifying action covers. It defaults to 100, and 0 means no stipend.

#151 also regenerates this file, so whichever of the two lands second regenerates it again.

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`, so the `blockchain_parameters` type of `sysio.bios` and `sysio.system` gains the field.

@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.

Reviewed the current diff and relevant SDK context with OCR. No actionable findings: both generated notify_cpu_stipend declarations match the paired producer's uint32 field and flow through the setparams action types. The exact generated file passed ESM and CommonJS type-checks, and git diff --check passed. Full tests and cross-repo integration were not run; compatibility assumes the documented paired rollout.

…stipend

Brings in #148 and #151. `SysioContractTypes.ts` is regenerated from wire-sysio #752 merged with master `fd459c6aec`, and differs from master only by the two `notify_cpu_stipend` fields.

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