-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edit delegation for multishard wallet. Unchange voting power trigger on wallets with different lock period. #3027
Comments
Status verification: ❌ What has been verified: Unchanged voting power should trigger if locking period the same ✅Unchanged voting power should NOT trigger if locking period is different ❌Example: Kapture.2025-01-30.at.13.06.09.mp4Expected result: When trigger unchanged voting power, locking period should not be available and set to actual position ❌When Unchanged voting power is active - locking period always set to x0.1 which may mess up the user Example: Kapture.2025-01-30.at.13.01.56.mp4Expected result: Actual result: |
Status verification: ❌ What has been verified: |
Status verification: ✅ |
Description
If user has a few accounts into multishard wallet with delegations and different locked period, when he started to edit it - will be used the x1 locking period.
Test data:
spektr-database.json
Steps to Reproduce
Expected Behavior
Pre-field state won't trigger, because locking period is different
Actual Behavior
Pre-filed state triggered with x1 loking period
Kapture.2025-01-23.at.11.05.30.mp4
Environment
b445163
The text was updated successfully, but these errors were encountered: