My wallet address: sugbAAEUWyzK9cB7Cu1SYwLoxZ6Airm14A1DGTRJwyzPkVgXu
Pledged to: Operator # 1
After Operator # 1 logs out and unlocks funds
My pledge cannot be retrieved.
Retrieve invalid using Polkadot protocol. Not using astrology. Of course, I have also tried using Astral multiple times.
Here are my records using Polkadot:
Thanks for your Watcher’s Oath entry!
We noticed that you have an error in the wallet you provided. The actual address is sugbAAEUWyzK9cB7Cu1SYwLoxZ6Eirm14a1DGTRJwyzPkVgXu.
This is indeed a protocol level bug that is an eligible entry for The Watcher’s Oath. An issue has been raised to fix the bug: Incorrectly tracking of the `NominatorCount` cause fail to `unlock_nominator` after operator is de-registered and cleaned up · Issue #3588 · autonomys/subspace · GitHub
Thanks again for taking the time to seek out the edge-cases and the behaviour overlooked by others. You should wear your Watcher mantle proudly!
1: Would adding an Autonomy logo make it more handsome?
2: I did not submit the address incorrectly.
3: I will try to submit the question as briefly as possible to avoid misunderstandings.
3: Please fix it and contact me. I can cooperate to test whether it is complete.
Supplementary submission:
Operator # 3 (Active) also encountered a similar issue.
Wallet address: sucAQuMJp6RC8RTfcerwDkXqzZhm6PS7w4Mt3VmYSwDJqKzX4
encoded call hash: 0x3e4e0da51c2567918abcf629849c1c7e272e9575979f1aaa17698584e40d4053
This extrinsic is included in block #2890181 and failed with error UnlockPeriodNotComplete because the unlocking period is not complete yet, which is 14_400 domain blocks and approximately a bit more than one day.
When you submit this extrinsic, the best domain is #1,917,796 but you can only unlock after the domain block #1,920,273:
{
totalWithdrawalAmount: 0
totalStorageFeeWithdrawal: 199,816,751,415,057,938,696
withdrawals: []
withdrawalInShares: {
domainEpoch: [
0
19,060
]
unlockAtConfirmedDomainBlockNumber: 1,920,273
shares: 559,984,607,200,000,000,000
storageFeeRefund: 199,816,751,415,057,938,696
}
}
But you can definitely unlock now since the best domain block is now #1,923,301
sucAQuMJp6RC8RTfcerwDkXqzZhm6PS7w4Mt3VmYSwDJqKzX4
Most of the tokens have been successfully unlocked and redeemed from operator # 3. thank you. There is a small issue now. I don’t know about this account. Approximately 300+tai3 cannot be redeemed. But I don’t know which node it was pledged to. Can you help me check? I go from top to bottom on Astrol. I redeemed it once. But I still can’t find it. This should be an issue with Astral.
sucAQuMJp6RC8RTfcerwDkXqzZhm6PS7w4Mt3VmYSwDJqKzX4 is still staked on operator 1 with ~50 tai3 on deposits and ~250tai3 on withdrawals that are ready to unlock:
// Deposits
{
known: {
shares: 45,597,984,115,200,000,000
storageFeeDeposit: 11,400,000,000,000,000,000
}
pending: null
}
// Withdrawals
{
totalWithdrawalAmount: 0
totalStorageFeeWithdrawal: 48,589,328,440,780,740,237
withdrawals: [
{
unlockAtConfirmedDomainBlockNumber: 825,202
amountToUnlock: 0
storageFeeRefund: 0
}
]
withdrawalInShares: {
domainEpoch: [
0
8,139
]
unlockAtConfirmedDomainBlockNumber: 1,117,681
shares: 194,397,487,004,800,000,000
storageFeeRefund: 48,589,328,440,780,740,237
}
}
I’ve tried my best. I can’t handle it. There are no button links on Astrol. There is no actual amount (so I have never known where these Tai3 are), and submitting Polkadot is useless. Please help me take another look.
The 5 tai3 just funds that are transferable, there are more funds on this account that are locked:
Also I forgot, the operator 1 is affected by Incorrectly tracking of the `NominatorCount` cause fail to `unlock_nominator` after operator is de-registered and cleaned up · Issue #3588 · autonomys/subspace · GitHub, so you won’t be able to call unlockNominator before this issue is migrated on Taurus.
Forget about it. I thought it had been fixed. I’ll wait for the release of the new version before experimenting. I have many wallets. There are quite a few issues. Test them one by one after the upgrade and repair.
