You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extrinsic 18210366-2 reaped account 12EX.. with 1257.831 Dot (12,578,310,000,000 planks) in reserve.
You can re-execute the block with npx @acala-network/chopsticks@latest run-block -c polkadot --html --open -b 18210366.
See how account 15oM.. was endowed while 12EX.. was reaped. Only 5 DOT of free balance carried over and no reserve. The 638 mDot got dusted rightfully since they did not use transfer_all:
I only fund this through some accounting inconsistency in the crowd loan state. The cause is assumed to be the currency->fungible migration. We could fix this with the Asset Hub migration.
Proposed Fix
There are more accounts of this kind, and in light of the asset hub migration they are causing issues in our accounting. It would be preferable to fix them in advance.
First, we need to identify all accounts that are affected by this. This requires to analyze the history by either querying an archive node or indexing all transactions. Specifically, you need to analyze all transfer transactions and query the reserves before and after. An accounts it faulty if it does not have a reserve anymore after the transfer but had one prior to it.
All such accounts should be written into a CSV for manual inspection with their respective missing amount and block.
As second step, we can either create a migration or a pallet. The migration would be a one-off thing and immediately fix the accounts, whereas the pallet would still need to be triggered by either the fellowship or a root referendum.
The fix would be to mint and reserve that amount on the account.
The text was updated successfully, but these errors were encountered:
As second step, we can either create a migration or a pallet. The migration would be a one-off thing and immediately fix the accounts, whereas the pallet would still need to be triggered by either the fellowship or a root referendum.
What is the exact fix? to refund the mistakenly dusted deposit?
Extrinsic 18210366-2 reaped account 12EX.. with 1257.831 Dot (12,578,310,000,000 planks) in reserve.
You can re-execute the block with
npx @acala-network/chopsticks@latest run-block -c polkadot --html --open -b 18210366
.See how account
15oM..
was endowed while12EX..
was reaped. Only 5 DOT of free balance carried over and no reserve. The 638 mDot got dusted rightfully since they did not usetransfer_all
:I only fund this through some accounting inconsistency in the crowd loan state. The cause is assumed to be the currency->fungible migration. We could fix this with the Asset Hub migration.
Proposed Fix
There are more accounts of this kind, and in light of the asset hub migration they are causing issues in our accounting. It would be preferable to fix them in advance.
First, we need to identify all accounts that are affected by this. This requires to analyze the history by either querying an archive node or indexing all transactions. Specifically, you need to analyze all transfer transactions and query the reserves before and after. An accounts it faulty if it does not have a reserve anymore after the transfer but had one prior to it.
All such accounts should be written into a CSV for manual inspection with their respective missing amount and block.
As second step, we can either create a migration or a pallet. The migration would be a one-off thing and immediately fix the accounts, whereas the pallet would still need to be triggered by either the fellowship or a root referendum.
The fix would be to mint and reserve that amount on the account.
The text was updated successfully, but these errors were encountered: