-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Decode token instructions #11281
Decode token instructions #11281
Conversation
Example:
|
@jackcmay , could you please take a look at the account field names I've chosen, in particular? (The test in |
Codecov Report
@@ Coverage Diff @@
## master #11281 +/- ##
=========================================
+ Coverage 82.5% 82.6% +0.1%
=========================================
Files 316 317 +1
Lines 74543 75059 +516
=========================================
+ Hits 61504 62019 +515
- Misses 13039 13040 +1 |
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.
+1. I'll let @jackcmay approve
@CriesofCarrots how about I update those variable names to make them consistent? Can you point me to an example? |
}) | ||
); | ||
|
||
// Test Approve, incl multisig |
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.
Shall we re-release token now that this is fixed in: solana-labs/solana-program-library#164
Doesn't require a change to the program, just the helpers in instruction.rs
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.
Sounds good. I'll publish a new patch version tonight or tomorrow am.
In looking at this again, it's not inconsistency, per se. It's just that Anyone have any opinions about the fact that I stripped out |
e8661e8
to
2c767aa
Compare
2c767aa
to
9de854e
Compare
@jackcmay updated. This look okay to you? |
* Token->SplToken * Add spl_token instruction parsing * Rebase on master * Gracefully fail key len mismatches (cherry picked from commit 0f551d4) # Conflicts: # Cargo.lock # transaction-status/Cargo.toml
* Decode token instructions (#11281) * Token->SplToken * Add spl_token instruction parsing * Rebase on master * Gracefully fail key len mismatches (cherry picked from commit 0f551d4) # Conflicts: # Cargo.lock # transaction-status/Cargo.toml * Fix conflicts Co-authored-by: Tyera Eulberg <[email protected]> Co-authored-by: Tyera Eulberg <[email protected]>
Problem
We need an easy way for users to view SPL Token transaction instructions, without having to resort to client-side language-specific decoding libraries.
Summary of Changes
getConfirmedBlock
andgetConfirmedTransaction
rpc responses. (A lot of this code could be simplified in the future by a verbose instruction-set enum produced by a procedural macro, such as Program macro to generate helper fns and documentation #10826 . That work is currently deprioritized, so in the meantime, this will unblock Token support in the Explorer and for other downstream users.)Mostly closes #10476