Alchemy Archived SDK Migration

Overview

Migrate archived Alchemy JavaScript SDK integrations to current capability-specific clients with parity, canary, and rollback evidence. This workflow produces a reviewable artifact and negative-path evidence before any live side effect.

Prerequisites

• Current first-party Alchemy documentation for the selected product, chain, feature, client, authentication method, limit, and lifecycle.
• Named product, application, security, data/privacy, budget, release, and operations owners appropriate to the requested scope.
• Synthetic or approved non-production fixtures, a credential canary, explicit success criteria, and a tested rollback boundary.

Current Contract

alchemy-sdk is deprecated and its repository is archived. Current migration targets are capability-specific: viem for JavaScript EVM RPC, direct documented Data API adapters, @alchemy/wallet-apis for transacting apps and Portfolio support, and Solana Web3.js for Solana. Wallet APIs v5 has a separate first-party migration guide.

Authentication

Inventory every credential the old client could access and grant each replacement adapter only its needed class. Do not let migration move secrets from a server boundary to browser code or merge read and signing authority.