Missing Functions in spl-token-2022 Crate (e.g., InitializeTokenMetadata)

[shrimpwtf]

There are several instructions used by the spl-token-2022 program that are entirely missing from the spl-token-2022 Rust crate. For example, instructions starting after discriminator 44 — such as InitializeTokenMetadata — are not defined or documented in the crate.

As a result, attempts to parse these instructions programmatically result in generic 0xc (InvalidInstruction) errors, since the enum or instruction parser in the crate doesn’t recognize them. This severely limits the crate’s utility for developers who need to build tooling, analytics, or custom program integrations based on SPL Token 2022.

Given that these are valid instructions executed on-chain by the official program, it’s critical that the Rust crate remains in sync with all supported instructions of the deployed program. As core contributors and maintainers of the ecosystem, it’s essential to ensure that all instructions — including any metadata or extended functionality — are available and documented in the crate.

[joncinque]

This is by design! Those instructions are actually part of the spl-token-metadata-interface, so if you'd like to parse them, you need to look at those instead: https://github.com/solana-program/token-metadata/blob/main/interface/src/instruction.rs

We could potentially re-export them if that makes things clearer though

[shrimpwtf]

This is by design! Those instructions are actually part of the spl-token-metadata-interface, so if you'd like to parse them, you need to look at those instead: https://github.com/solana-program/token-metadata/blob/main/interface/src/instruction.rs

We could potentially re-export them if that makes things clearer though

Thanks for taking the time to respond. I can understand if this is intentional, however when I'm for example trying to parse the blockchain in general and want to deserialize to work out what is happening it makes the logic unpredictable and inefficient as the spl-token-2022 crate should deserialize any instruction that is coming from the program itself. the typescript sdk has these built in and is capable of parsing them but the rust one is not. I think they should be merged or re-exported in a way where you can simply call deserialize and it can parse anything. For the longest time we've been getting 0xc errors and struggling to work out why and this was the cause, I definately must not be the only one too.

[oxy-Op]

I’ve run into the same issue — my parsing logic breaks when it encounters these instructions. For example, InitializeTokenMetadata was missing, and it caused the general deserialization to silently fail. Now I have to handle it separately, which makes the parsing flow more complex and harder to maintain.