From ec12a6dd9d1c88d6b550d570b5005a8c8f947eb3 Mon Sep 17 00:00:00 2001 From: jakehobbs Date: Tue, 26 May 2026 17:43:21 -0700 Subject: [PATCH 1/3] Clarify that client-side JWT migrations still need the React sending and sponsorship setup. Co-Authored-By: Codex Opus 4.6 (1M context) Co-authored-by: Cursor --- .../wallets/wallet-integrations/privy/jwt-auth-migration.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/wallets/wallet-integrations/privy/jwt-auth-migration.mdx b/content/wallets/wallet-integrations/privy/jwt-auth-migration.mdx index 00587c3e0..a3952d740 100644 --- a/content/wallets/wallet-integrations/privy/jwt-auth-migration.mdx +++ b/content/wallets/wallet-integrations/privy/jwt-auth-migration.mdx @@ -95,6 +95,10 @@ Install `@alchemy/wallet-apis` and wire up `createSmartWalletClient`. See the [P Use this path if you have a React or React Native app and want the migration to happen in the user's browser/device. + +Client-side migrations still need to reconnect sending and gas sponsorship after Privy auth is wired up. Follow the [React migration guide Step 2](/docs/wallets/wallet-integrations/privy/react-migration#step-2-reconnect-sending-and-gas-sponsorship) to connect Privy wallets to Alchemy's transaction infrastructure. + + ### 4a. Integrate Privy auth (client-side) Instead of calling a Privy login function directly, you subscribe the Privy SDK to your existing auth provider's state using the `useSubscribeToJwtAuthWithFlag` hook. Privy will automatically authenticate when your provider reports the user is logged in. From 5b72d5495eba7ab85a85d1284f8af11bcf7e02eb Mon Sep 17 00:00:00 2001 From: jakehobbs Date: Tue, 26 May 2026 17:50:06 -0700 Subject: [PATCH 2/3] Keep the JWT migration reconnect guidance in the shared setup step so both paths read consistently. Co-Authored-By: Codex Opus 4.6 (1M context) Co-authored-by: Cursor --- .../wallet-integrations/privy/jwt-auth-migration.mdx | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/content/wallets/wallet-integrations/privy/jwt-auth-migration.mdx b/content/wallets/wallet-integrations/privy/jwt-auth-migration.mdx index a3952d740..f420e25cf 100644 --- a/content/wallets/wallet-integrations/privy/jwt-auth-migration.mdx +++ b/content/wallets/wallet-integrations/privy/jwt-auth-migration.mdx @@ -87,7 +87,7 @@ While existing users still need migrating, you don't want Privy to auto-create a ## Step 3: Reconnect sending and gas sponsorship -Install `@alchemy/wallet-apis` and wire up `createSmartWalletClient`. See the [Privy signer integration guide](/docs/wallets/third-party/signers/privy) for full setup details, or follow the [React migration guide Step 2](/docs/wallets/wallet-integrations/privy/react-migration#step-2-reconnect-sending-and-gas-sponsorship) for a walkthrough. +This step applies before either migration path below, including client-side migrations. Install `@alchemy/wallet-apis` and wire up `createSmartWalletClient`. See the [Privy signer integration guide](/docs/wallets/third-party/signers/privy) for full setup details, or follow the [React migration guide Step 2](/docs/wallets/wallet-integrations/privy/react-migration#step-2-reconnect-sending-and-gas-sponsorship) for a walkthrough. *** @@ -95,10 +95,6 @@ Install `@alchemy/wallet-apis` and wire up `createSmartWalletClient`. See the [P Use this path if you have a React or React Native app and want the migration to happen in the user's browser/device. - -Client-side migrations still need to reconnect sending and gas sponsorship after Privy auth is wired up. Follow the [React migration guide Step 2](/docs/wallets/wallet-integrations/privy/react-migration#step-2-reconnect-sending-and-gas-sponsorship) to connect Privy wallets to Alchemy's transaction infrastructure. - - ### 4a. Integrate Privy auth (client-side) Instead of calling a Privy login function directly, you subscribe the Privy SDK to your existing auth provider's state using the `useSubscribeToJwtAuthWithFlag` hook. Privy will automatically authenticate when your provider reports the user is logged in. From 830583ad69d4752b12870e81a10fb7a7e0e6ba78 Mon Sep 17 00:00:00 2001 From: jakehobbs Date: Tue, 26 May 2026 17:53:30 -0700 Subject: [PATCH 3/3] Make the client-side migration path point readers back to the shared reconnect step so the setup is not missed. Co-Authored-By: Codex Opus 4.6 (1M context) Co-authored-by: Cursor --- .../wallets/wallet-integrations/privy/jwt-auth-migration.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/wallets/wallet-integrations/privy/jwt-auth-migration.mdx b/content/wallets/wallet-integrations/privy/jwt-auth-migration.mdx index f420e25cf..eda9a4326 100644 --- a/content/wallets/wallet-integrations/privy/jwt-auth-migration.mdx +++ b/content/wallets/wallet-integrations/privy/jwt-auth-migration.mdx @@ -87,7 +87,7 @@ While existing users still need migrating, you don't want Privy to auto-create a ## Step 3: Reconnect sending and gas sponsorship -This step applies before either migration path below, including client-side migrations. Install `@alchemy/wallet-apis` and wire up `createSmartWalletClient`. See the [Privy signer integration guide](/docs/wallets/third-party/signers/privy) for full setup details, or follow the [React migration guide Step 2](/docs/wallets/wallet-integrations/privy/react-migration#step-2-reconnect-sending-and-gas-sponsorship) for a walkthrough. +This step applies before either migration path below. Install `@alchemy/wallet-apis` and wire up `createSmartWalletClient`. See the [Privy signer integration guide](/docs/wallets/third-party/signers/privy) for full setup details, or follow the [React migration guide Step 2](/docs/wallets/wallet-integrations/privy/react-migration#step-2-reconnect-sending-and-gas-sponsorship) for a walkthrough. *** @@ -95,6 +95,8 @@ This step applies before either migration path below, including client-side migr Use this path if you have a React or React Native app and want the migration to happen in the user's browser/device. +Before building the client-side flow, complete [Step 3](#step-3-reconnect-sending-and-gas-sponsorship) so your Privy wallets are connected to Alchemy's transaction infrastructure. + ### 4a. Integrate Privy auth (client-side) Instead of calling a Privy login function directly, you subscribe the Privy SDK to your existing auth provider's state using the `useSubscribeToJwtAuthWithFlag` hook. Privy will automatically authenticate when your provider reports the user is logged in.