-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
token 3.1.0 behaviour differences to token 2.6.0 #1231
Comments
I think this is probably ok. Previously the self-transfer was a blind ✔️, but now with 3.1.0 we actually fully validate the transfer, so this transaction legitimately should have failed. If you agree Trent, let's chat with the kin team about it |
Yep this failure is expected, 18 != 5. I'll raise with KIN folks tomorrow |
Found another invalid transaction: 2x4...TwU This was a self-transfer of 550 KIN when the account only had 540 KIN. 3.1.0 correctly rejects this transaction with
|
A non-kin one this time, a self TransferChecked of 1 wrapped SOL with an account holding 0 SOL: 4Qu...goD. 3.1.0 correctly rejects this transaction with
|
Thankfully looks like none of these have been CPI'd so far, so should all be easily fixable client-side changes 🤞 |
100KIN self-transfer between an account with 0 KIN in it: https://explorer.solana.com/tx/27AuGC8YVJbrNAKrtTAG1o6iBNsyrQQs6XskM1nv5PwX7X5fnFtYhKwhMzJJ3kDXazdxDuzyfoCu9UySyKwf3zzm |
The mainnet-beta transaction cgq..Fgc succeeded, but failed on the
bvb
running a custom build that shims in the token 3.1.0 binary.Transaction details from
bvb
that caused the node to fork off mainnet-beta:The text was updated successfully, but these errors were encountered: