Skip to content

feat(standards): bound the fee payment of the plain multisig component - #3802

Open
mmagician wants to merge 2 commits into
release/v0.16.0-rcfrom
mmagician-claude/rc-bound-plain-multisig
Open

feat(standards): bound the fee payment of the plain multisig component#3802
mmagician wants to merge 2 commits into
release/v0.16.0-rcfrom
mmagician-claude/rc-bound-plain-multisig

Conversation

@mmagician

@mmagician mmagician commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

Summary

Closes #3763.

#3786 bounded the fee payment of the guarded and smart multisig component, but left plain AuthMultisig unbounded, The same change lands on next as part of #3798.

…ig components

The guarded and smart multisig components carried the same bounded fee
flow; it now lives in `multisig::pay_bounded_fee`, with the bound
defined once, and the components keep only what differs (the guardian
signature slot). Inline comments trimmed as requested on #3798.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KkQzFtRjyDwQ7iVtRbsHsn
`AuthMultisig` paid the fee through the unbounded `fee::pay_fee`, so a
host-supplied rate could move the vault's fee-asset balance into the
TX_FEE note, below the default quorum where a per-procedure override
applies (#3763). It now pays through `multisig::pay_bounded_fee` like
the guarded and smart components: native fee asset only, at most twice
the computed fee.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KkQzFtRjyDwQ7iVtRbsHsn
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