Add Token-2022 memo-transfer Pinocchio example

[MarkFeder]

What

Adds a Pinocchio implementation of the Token-2022 memo-transfer example. The example previously had only an anchor version (no native), so this is a fresh port. It follows the same kit + litesvm + official-@solana-program-packages template as the merged Token-2022 pinocchio examples, and builds directly on the account-extension shape from immutable-owner (#696).

How it works

The single instruction creates a Token-2022 token account with the MemoTransfer extension enabled. Once enabled, every transfer into the account must be preceded by a memo instruction, or the transfer fails.

The program hand-rolls three CPIs:

1. CreateAccount — with space for the extension.
2. InitializeAccount3 (variant 18): [18] + owner(32).
3. EnableRequiredMemoTransfers — wrapper MemoTransferExtension (variant 30), sub Enable (0), empty data → [30, 0].

Unlike ImmutableOwner (which must be initialized before InitializeAccount), this extension is enabled after the account is initialized, and the enable must be signed by the account owner (here, the payer). The owner is the payer, so a single signature covers funding and the enable.

The extended token account is 171 bytes (base 165 + account-type byte 1 + a 5-byte MemoTransfer TLV entry whose value is a single bool).

Test

litesvm + @solana/kit. The test creates a plain Token-2022 mint client-side, invokes the program to create the token account, then decodes it with the official @solana-program/token-2022 codec and asserts:

• the account is owned by Token-2022 and sized to 171 bytes,
• the decoded mint and owner, and
• the MemoTransfer extension's requireIncomingTransferMemos is true.

Token-2022 Memo Transfer (Pinocchio)
  ✔ Creates a Token-2022 token account with required memo transfers enabled
1 passing

Verified locally: cargo build-sbf, the litesvm test, tsc --noEmit, Prettier, cargo fmt --check, Clippy, and pnpm install --frozen-lockfile all clean.

[greptile-apps]

Greptile Summary

The PR adds a Pinocchio Token-2022 memo-transfer example that creates an extended token account and enables required incoming-transfer memos.

• Adds the Pinocchio program, workspace configuration, package metadata, and build/deployment script.
• Adds LiteSVM tests for account initialization, rejection without a memo, and successful transfer with a preceding memo.

Confidence Score: 5/5

The PR appears safe to merge.

The previously reported memo-enforcement coverage gap is fixed by explicit rejection and successful-transfer cases, and no blocking failure remains.

Important Files Changed

Filename	Overview
tokens/token-2022/memo-transfer/pinocchio/program/src/instructions/create_token_account.rs	Creates, initializes, and enables the MemoTransfer extension on a correctly sized Token-2022 account using the payer as owner and signer.
tokens/token-2022/memo-transfer/pinocchio/program/src/processor.rs	Dispatches the example’s single data-free instruction to the token-account creation handler.
tokens/token-2022/memo-transfer/pinocchio/tests/test.ts	Verifies the extended account state and now covers both memo-less transfer rejection and memo-prefixed transfer success.
tokens/token-2022/memo-transfer/pinocchio/package.json	Defines the example’s pinned-lockfile-compatible build and LiteSVM test environment.
Cargo.toml	Registers the new Pinocchio program as a workspace member.

_{Reviews (2): Last reviewed commit: "token-2022 memo-transfer pinocchio: test..." | Re-trigger Greptile}

[MarkFeder]

@amilz could you take a look at this one when you get a chance?

No open review threads left on it, so it is ready for maintainer review. It is one of 23 open Pinocchio ports I have up — they are independent and self-contained, so they can be reviewed and merged in any order: https://github.com/solana-developers/program-examples/pulls/MarkFeder