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
After ToB audit, we tend to disable the feature of automatic ATA account creation at the moment. So, what happens if a user withdraw SPL token to an non-existent destination?
To solve the problem, a few updates need to be done when "non-existent destination" case happened:
The solana program needs to make the withdraw_spl_token call successful.
The solana program needs to increment the program nonce even though the SPL token transfer cannot be done.
The solana program needs to signal the "non-existent destination" case by printing a proper log message, for example: ata does not exist or non-existent destination.
zetaclient interpret this withdraw_spl_token transaction as failed if above log message (in 3) is detected.
The text was updated successfully, but these errors were encountered:
The context:
After ToB audit, we tend to disable the feature of automatic ATA account creation at the moment. So, what happens if a user withdraw SPL token to an non-existent destination?
To solve the problem, a few updates need to be done when "non-existent destination" case happened:
withdraw_spl_token
call successful.ata does not exist
ornon-existent destination
.withdraw_spl_token
transaction as failed if above log message (in 3) is detected.The text was updated successfully, but these errors were encountered: