Summary: The current execution flow is not clearly restricted enough in the UI, which makes it easy for the wrong account to attempt the final transaction.
Why it matters: Governance systems need to make authorization obvious. If the UI suggests that any account can finalize a proposal when the underlying rule is narrower, users get failed transactions and lose confidence in the process.
Scope:
- Show who is allowed to execute a proposal.
- Explain the required conditions before execution is enabled.
- Disable or hide the action when the connected wallet cannot perform it.
Acceptance notes:
- Execution eligibility is visible in proposal detail views.
- Restricted execution paths are explained in the UI copy.
- The same authorization rules are used consistently across list and detail screens.
Summary: The current execution flow is not clearly restricted enough in the UI, which makes it easy for the wrong account to attempt the final transaction.
Why it matters: Governance systems need to make authorization obvious. If the UI suggests that any account can finalize a proposal when the underlying rule is narrower, users get failed transactions and lose confidence in the process.
Scope:
Acceptance notes: