-
Notifications
You must be signed in to change notification settings - Fork 11.4k
Unstake transaction history #21441
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
Comments
Thank you for opening this issue, a team member will review it shortly. Until then, please do not interact with any users that claim to be from Sui support and do not click on any links! |
Yes, the Split transaction is the key here. Another account used staking_pool::split to divide its own StakedSui (which is required for Unstake) and transferred a portion to this account. As a result, even though this account has no prior Stake transaction, it can still execute an Unstake. |
Hi @1-4200 , thanks for quick reply. |
I would track it by tracing the previousTransaction of the StakedSui. That said since this involves tracking historical object states, an unpruned fullnode would likely be required. |
I am querying for staking transactions against this account 0x86f3734ed8b3ea7d5b9615dd19caf314aada227777423f2ffaf42abf726532dc. and I found very first transaction as UnStake transaction. Can you please enlighten me that without doing single staking transaction before this Unstake transaction, how this Unstake possible?
Does Split transaction play role in this scenario ? If yes then how can we get to know that what was the respective Staking transaction against this Unstake.
The text was updated successfully, but these errors were encountered: