Bug Description
BNB reported that on BNB testnet, after a proposal is published, the decoded execution details are not visible on the published proposal page. They only see the decoded execution in the proposal editor before publishing.
Expected Behavior
After publishing a proposal, users should still be able to see the decoded execution/action details on the published proposal page, matching what is shown in the editor.
Actual Behavior
Decoded execution details are visible in the editor, but disappear / are not shown once the proposal is published.
Context
- Reported by: BNB, via our Telegram group
- Network: BNB testnet
- Area: proposal publishing / execution decoding display
- Suspected issue: something in the published proposal view, proposal payload persistence, or decoder data hydration differs from the editor flow.
Debug Notes / Things to Check
- Compare the editor execution decoding path with the published proposal detail rendering path.
- Verify whether decoded execution data is persisted with the proposal or recomputed from stored execution payloads.
- Confirm BNB testnet proposal network/action type(s), especially if chain-specific decoding is involved.
- Check whether published proposal view receives the same execution payload / metadata as the editor.
Bug Description
BNB reported that on BNB testnet, after a proposal is published, the decoded execution details are not visible on the published proposal page. They only see the decoded execution in the proposal editor before publishing.
Expected Behavior
After publishing a proposal, users should still be able to see the decoded execution/action details on the published proposal page, matching what is shown in the editor.
Actual Behavior
Decoded execution details are visible in the editor, but disappear / are not shown once the proposal is published.
Context
Debug Notes / Things to Check