fix: use lean keychain-memory signer to avoid cloud SDK dep bloat

The umbrella @solana/keychain pulls in every backend signer (AWS KMS, GCP
KMS, Fireblocks, ...), dragging the full AWS SDK into the lockfile and
tripping the safe-chain minimum-package-age guard in CI. Use the
config-based createMemorySigner from @solana/keychain-memory instead;
the plugin-client signing path is unchanged.

Author: amilz

packages/docs-examples/cookbook/wallets/sign-with-keychain/kit.ts

@@ -1,15 +1,14 @@
 // #region sign
 import { createClient, generateKeyPairSigner, lamports } from "@solana/kit";
-import { createKeychainSigner } from "@solana/keychain";
+import { createMemorySigner } from "@solana/keychain-memory";
 import { rpcAirdrop, solanaRpc } from "@solana/kit-plugin-rpc";
 import { airdropSigner, signer } from "@solana/kit-plugin-signer";
 import { getTransferSolInstruction } from "@solana-program/system";
 
-// One factory, one config shape for every backend. Swap `backend: "memory"`
-// for "aws-kms", "vault", "turnkey", ... and the rest of this file is
-// identical — each backend returns the same `SolanaSigner` interface.
-const keychainSigner = await createKeychainSigner({
-  backend: "memory",
+// Every Keychain backend returns the same `SolanaSigner`. Swap this in-memory
+// signer for `createAwsKmsSigner`, `createVaultSigner`, ... and the rest of
+// this file is identical.
+const keychainSigner = await createMemorySigner({
   privateKey: crypto.getRandomValues(new Uint8Array(32)),
 });
 

packages/docs-examples/package.json

@@ -16,7 +16,7 @@
     "@solana-program/system": "^0.12.0",
     "@solana-program/token": "^0.13.0",
     "@solana-program/token-2022": "^0.9.0",
-    "@solana/keychain": "^1.3.0",
+    "@solana/keychain-memory": "^1.3.0",
     "@solana/kit": "^6.8.0",
     "@solana/kit-plugin-rpc": "^0.11.1",
     "@solana/kit-plugin-signer": "^0.10.0",