# \[RFC\] Token-2022 Client Warnings and Squads Proposal Construction **URL:** \ **Category:** CoW Grants Program\ **Created:** [October 1, 2026, 1:25pm UTC](https://forum.cow.fi/t/rfc-token-2022-client-warnings-and-squads-proposal-construction/3603 "2026-10-01T13:25:36Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![naina](https://avatars.discourse-cdn.com/v4/letter/n/919ad9/32.png) [@naina](https://forum.cow.fi/u/naina)\ **Post date:** [October 1, 2026, 1:25pm UTC](https://forum.cow.fi/t/rfc-token-2022-client-warnings-and-squads-proposal-construction/3603/1 "2026-10-01T13:25:36Z")
# Purpose We want to confirm whether the CoW team wants external help building client warnings for Token-2022 edge cases and standardizing Squads proposal construction. This is a scope discussion. We are not requesting funding at this stage. If the scope is useful and a prototype meets the team’s requirements, we would return with a separate milestone-based grant application. GitHub: [Naina9760 · GitHub](https://github.com/naina9760) ## Proposed contribution We are considering a TypeScript package built alongside the official `@cowprotocol/sdk-trading-solana` package. The package would provide: 1. A standardized method to extract CoW Solana instructions and wrap them into a Squads multisig proposal. 2. Client warnings for Token-2022 accounts before a transaction is presented to signers. 3. Stable error codes for client validation failures. 4. Reproducible local validator tests. ## Proposed preflight warnings The initial test matrix would cover: - Standard SPL tokens - Token-2022 mints - Transfer fee extensions - Transfer hook extensions - Frozen token accounts - Non-transferable tokens - Permanent delegates - Incorrect mint addresses The library would warn users in the client interface when a transaction involves these extensions. We understand that on-chain state can change between proposal creation and execution. All absolute security guarantees must be enforced by the on-chain settlement program. ## Technical boundaries We do not propose to: - Replace the official CoW Solana SDK - Change the CoW settlement program - Create a new on-chain program - Operate a relay - Store private keys - Hold user funds - Claim an official Squads relationship The official CoW SDK remains responsible for quote retrieval and instruction generation. Our package would only wrap those instructions for multisig proposals and provide client warnings. ## Initial proof If the scope is useful, our first public proof would include: - A Token-2022 compatibility matrix - Reproducible local validator tests - A devnet example using a multisig - A clear record of which contributor authored each implementation ## Sources reviewed Official Solana program design: > Official Solana program repository: > **[GitHub - cowprotocol/solana-programs: Solana programs for CoW Protocol](https://github.com/cowprotocol/solana-programs)** > > Solana programs for CoW Protocol Official Solana trading SDK documentation: > ## Questions for the CoW team 1. Is a multisig proposal helper already part of the internal Solana roadmap? 2. Does the `sdk-trading-solana` package currently export instructions suitable for direct use with Squads? 3. Which Token-2022 checks should integrations perform in the client UI before signing? 4. Which Token-2022 checks must only be enforced by the settlement program? 5. How does the settlement program intend to handle Token-2022 transfer fees during execution? 6. Would the team review a devnet prototype covering this scope? Technical guidance from @mfw78, @Sov, or @Chim9 would be appreciated. ---
**Author:** ![Sov](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.cow.fi/sov/32/1295_2.png) [@Sov](https://forum.cow.fi/u/Sov)\ **Post date:** [October 2, 2026, 2:51pm UTC](https://forum.cow.fi/t/rfc-token-2022-client-warnings-and-squads-proposal-construction/3603/2 "2026-10-02T14:51:59Z")
Hi @naina, thanks for the write-up. Most of the questions here are already covered in the existing docs: - Squads / multisig: the sdk-trading-solana README covers using `buildOrder` to get the raw instruction for bundling, or `signAndSend` with a Squads/Safe-style multisig flow: [https://github.com/cowprotocol/cow-sdk/blob/main/packages/sdk-trading-solana/README.md?plain=1#L92-L117](https://github.com/cowprotocol/cow-sdk/blob/main/packages/sdk-trading-solana/README.md?plain=1#L92-L117) - Token-2022: the solana-programs DESIGN.md explains how Token-2022 and its extensions are handled: [solana-programs/DESIGN.md at main · cowprotocol/solana-programs · GitHub](https://github.com/cowprotocol/solana-programs/blob/main/DESIGN.md?plain=1#L385-L389) Since the Solana SDK is still marked experimental, the committee isn’t looking to fund wrapper tooling around it at this stage.