Skip to content

Conversation

@lxcmyf
Copy link
Contributor

@lxcmyf lxcmyf commented Nov 14, 2025

No description provided.

tip-767.md Outdated

- After exceeding the on-chain `proposalExpireTime` and during the nearest maintenance period, the proposal automatically expires (even if approving is incomplete).

**​​Block Validation**​​: Nodes must reject transactions that rely on expired proposals (based on on-chain parameters).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sentence reads a bit confusing—what does it mean?

Copy link
Contributor Author

@lxcmyf lxcmyf Nov 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Federico2014
When a proposal exceeds the voting window specified on the chain, it officially expires. Any transaction that attempts to execute the content of this "expired proposal" must be rejected and verified as illegal by all nodes when packaged into the block.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The term expired proposal is ambiguous. At first, I thought it meant that a proposal becomes expired when its voting window ends. But what you’re saying here is that once a new proposal takes effect, the old one becomes expired?

Copy link
Contributor Author

@lxcmyf lxcmyf Nov 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The proposal transaction initiated has a voting window. If the proposal transaction expires, it will be rejected when approving the proposal transaction. It's that simple.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It just means the related ProposalApproval transaction will be rejected if the proposal exceeds the voting window specified on the chain. This should be clarified.

@lxcmyf lxcmyf force-pushed the master branch 2 times, most recently from 7b08cca to 6b421e4 Compare November 17, 2025 06:11
@Benson0224 Benson0224 merged commit 159ed2c into tronprotocol:master Nov 27, 2025
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.

4 participants