Skip to content

fix(ui): don't warn that a pending setDelegate invalidates proposals - #131

Open
mellowcroc wants to merge 1 commit into
mainfrom
fix/setdelegate-config-nonce-warning
Open

fix(ui): don't warn that a pending setDelegate invalidates proposals#131
mellowcroc wants to merge 1 commit into
mainfrom
fix/setdelegate-config-nonce-warning

Conversation

@mellowcroc

Copy link
Copy Markdown
Collaborator

Summary

The new-proposal form shows "There are pending governance proposals. If one executes before this proposal, the config nonce will change and this proposal will be invalidated" whenever a pending proposal is classified as governance. That classification (ui/app/transactions/new/page.tsx:283) wrongly includes setDelegate.

setDelegate does not bump the config nonce — only owner-set and threshold changes do (MinaGuard.executeOwnerChange at MinaGuard.ts:1233 and executeThresholdChange at 1298; the contract even documents "Does not bump configNonce" on the delegate path, MinaGuard.ts:1315). So a pending setDelegate proposal invalidates nothing, and the banner is a false alarm.

Fix

Remove 'setDelegate' from the governance classification, leaving addOwner / removeOwner / changeThreshold.

Impact

Display-only — no safety or on-chain behavior change. The contract already enforces config-nonce invalidation correctly; this only stops the UI from raising a misleading warning when a delegate change is pending.

setDelegate does not bump the config nonce — only owner-set / threshold changes do (MinaGuard.executeOwnerChange / executeThresholdChange). A pending setDelegate therefore invalidates no other proposals, so it must not trigger the 'pending governance proposals … will be invalidated' banner. Remove it from that classification.
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.

1 participant