-
Notifications
You must be signed in to change notification settings - Fork 4.5k
feature: add new token program feature #18780
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing/reusing the existing token upgrade infra makes sense to me
@joncinque - when we have the final SPL Token binary, let's make a SPL Token release over in SPL-land as well. Then replace |
Yes, please! We need that for some ledger-app-solana changes I have cued. I'll probably also bump spl-token in |
Ah yes, great call! Should this next release be version 3.2.0 then? |
Codecov Report
@@ Coverage Diff @@
## master #18780 +/- ##
=========================================
- Coverage 82.8% 82.8% -0.1%
=========================================
Files 441 441
Lines 124988 125017 +29
=========================================
+ Hits 103578 103586 +8
- Misses 21410 21431 +21 |
@CriesofCarrots I added the transaction parser with the upgrade, could you take a look at it? Otherwise, just double-checking, is there a potential problem with backporting this to 1.6? spl-token v3.2.0 uses solana-program v1.7.4 |
Thank you! 😍 Looks great.
Oof. Correct, this likely won't be backportable to v1.6 for the reason you noted. I guess this would need to head to MNB on the v1.7 train. (Rolling back SPL to v1.6 doesn't seem very feasible to me.) |
Ah, beans. The program will soak on mainnet for a bit, so let's hope lines up with the timeline for 1.7. |
@joncinque , actually... while I believe I've had troubles in the past with spl dependencies bringing in newer minor-version solana-program crates, in this case it looks like if we release a new version of |
No harm in releasing a new |
All right, let's roll the dice! |
That should be everything now 🤞 |
@joncinque , alas, it does build fine with the new atoken, but doesn't please
Sorry for the hassle |
Ah bummer, oh well, it was worth a shot! |
Merging on not-really-red, the removal of the v1.6 label causes this to look failed, when it isn't |
* feature: add new token program feature * Fixup test * Update to spl-token v3.2.0 * Update Cargo.lock + fmt * Update token program version in fetch-spl.sh * Bump associated token program to 1.0.3 * Add aToken so (cherry picked from commit 51f3b9a) # Conflicts: # Cargo.lock # account-decoder/Cargo.toml # accounts-cluster-bench/Cargo.toml # programs/bpf/Cargo.lock # rpc/Cargo.toml # sdk/src/feature_set.rs # tokens/Cargo.toml # transaction-status/Cargo.toml
* feature: add new token program feature (#18780) * feature: add new token program feature * Fixup test * Update to spl-token v3.2.0 * Update Cargo.lock + fmt * Update token program version in fetch-spl.sh * Bump associated token program to 1.0.3 * Add aToken so (cherry picked from commit 51f3b9a) # Conflicts: # Cargo.lock # account-decoder/Cargo.toml # accounts-cluster-bench/Cargo.toml # programs/bpf/Cargo.lock # rpc/Cargo.toml # sdk/src/feature_set.rs # tokens/Cargo.toml # transaction-status/Cargo.toml * Fix merge issues * Re-generate lock files Co-authored-by: Jon Cinque <jon.cinque@gmail.com>
Problem
We need to deploy a new token program.
Summary of Changes
Add a feature for it! Since we already have a new token program id in the code, and that one was enabled at slot 66528004, and we're at 87877768 as of this writing, it felt ok to change this up.
On the other hand, I left the old feature in the feature set so it can still be queried. Let me know if you prefer to remove that too.
After, this will reuse the hack to the account db to force in the new token program for one of our validators: #15212 (comment) <--- this is more for me to remember
Fixes #