Skip to content

feat(vm): optimize voting power management (TIP-944) - #7068

Open
yanghang8612 wants to merge 4 commits into
release_v4.8.3from
feature/tip-944-voting-power
Open

yanghang8612 wants to merge 4 commits into
release_v4.8.3from
feature/tip-944-voting-power

Conversation

@yanghang8612

@yanghang8612 yanghang8612 commented Oct 27, 2026 •

Copy link
Copy Markdown
Collaborator

What does this PR do?

Implement TIP-944 behind ALLOW_TVM_VOTE_POWER_OPTIMIZATION (103), aligning legacy voting-power state transitions for TVM voting, Stake 1.0 freezing/unfreezing, and self-destruct stake receipt and cleanup.

Why are these changes required?

Keep TVM account-state transitions consistent with native NewResourceModel rules.

Related to TIP-944.

This PR has been tested by:

  • ./gradlew clean build -x test on macOS ARM64 / JDK 17.
  • Focused regression suite: 65 tests, 64 passed and 1 existing benchmark skipped, including real VM execution, enclosing-call rollback, and Stake 1.0 switch combinations.
  • Required Checkstyle tasks and .github/scripts/check_math_usage.sh.

Follow up

Coordinate on-chain activation. Existing feature prerequisites and voting-power selection conditions remain applicable; no historical account-state migration is introduced.

Extra details

Targets release_v4.8.3. Proposal validation, application, and parameter output place 103 after 102. TIP-945 has independent runtime activation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

topic:vm VM, smart contract

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants