Token 2022 Support

[ubadineke]

@Buzzec I noticed that Token 2022 isn’t supported yet in the Star_Frame Framework. Is there a plan to add support for it, or are there any constraints preventing the implementation? If not, I’d love to give it a try and work on adding support myself.

[stegaBOB]

Hey thanks for this issue! I think we'd be open to supporting it. It would be nice to be able to do it without duplicating all the state and ix code. I think there are equivalents for tokenkeg in 2022, so for those you can just make a new Token2022InstructionSet and plop the tokenkeg instructions inside of it and in theory that should work without duplication. State might be a bit tricky to get working generically, so we should probably brainstorm ways to do that first. I'll give it some more thought

[ubadineke]

Would this work for the Token2022Instruction Set?

pub enum Token2022InstructionSet{
 Legacy(TokenInstructionSet)
TransferFee(TransferFee)
... other token 2022 mint instructions
}

And yes the state would need tweaks, modifying some checks.
Here can be switched to checking if the size is at least 82

star_frame/star_frame_spl/src/token/state.rs

Line 80 in 4b8f52e

if self.account_data()?.len() != Self::LEN {

Also this casting:

star_frame/star_frame_spl/src/token/state.rs

Line 98 in 4b8f52e

bytemuck::checked::try_from_bytes::<MintAccountData>(data)

And a lot more, I can't even think of yet.

[stegaBOB]

Would this work for the Token2022Instruction Set?

pub enum Token2022InstructionSet{
Legacy(TokenInstructionSet)
TransferFee(TransferFee)
... other token 2022 mint instructions
}

The way the instruction set derive works is it has a bunch of instructions in it and derives discriminants for that enum and then matches on them. You can take all of the instructions in the tokenkeg set and put them in a new token22 enum (the individual variants, not the set itself)