docs: second pass of 7702 default

jakehobbs · jakehobbs · commit 702d16604080 · 2026-01-22T16:39:16.000-08:00
diff --git a/fern/wallets/pages/transactions/cross-chain-swap-tokens/api.mdx b/fern/wallets/pages/transactions/cross-chain-swap-tokens/api.mdx
@@ -9,7 +9,7 @@ You will need to fill in values wrapped in curly braces like `{SIGNER_ADDRESS}`.
   additional actions after a cross-chain swap.
 </Info>
 
-Use your signer address directly as the `from` field. Request a cross-chain swap quote by specifying both the source chain (`chainId`) and destination chain (`toChainId`). In addition, just like in [single-chain swaps](/wallets/transactions/swap-tokens) you can specify either a `minimumToAmount` or a `fromAmount`.
+Use your signer address directly as the `from` field to enable [EIP-7702](/wallets/transactions/using-eip-7702) by default. Request a cross-chain swap quote by specifying both the source chain (`chainId`) and destination chain (`toChainId`). In addition, just like in [single-chain swaps](/wallets/transactions/swap-tokens) you can specify either a `minimumToAmount` or a `fromAmount`.
 
 <Info>
   If you're using an EOA or just want the raw array of calls returned, pass the
diff --git a/fern/wallets/pages/transactions/pay-gas-with-any-token/api-postop.mdx b/fern/wallets/pages/transactions/pay-gas-with-any-token/api-postop.mdx
@@ -4,7 +4,7 @@ for full descriptions of the parameters used in the following example.
 
 <Steps>
   <Step title="Prepare Calls">
-    Prepare calls using the `paymasterService` capability. Use your signer address directly as the `from` field.
+    Prepare calls using the `paymasterService` capability. Use your signer address directly as the `from` field to enable [EIP-7702](/wallets/transactions/using-eip-7702) by default.
 ```bash
 curl --request POST \
   --url https://api.g.alchemy.com/v2/$ALCHEMY_API_KEY \
@@ -43,6 +43,6 @@ curl --request POST \
 ```
   </Step>
   <Step title="Sign & Send">
-    Sign the returned signature request and send using `wallet_sendPreparedCalls`. See the [send transactions guide](/wallets/transactions/send-transactions) for more info.
+    Sign the returned signature request and send using `wallet_sendPreparedCalls`. On the first transaction for a new account, the response type will be `array` containing both an EIP-7702 authorization and a user operation. See the [send transactions guide](/wallets/transactions/send-transactions) for a complete example.
   </Step>
 </Steps>
diff --git a/fern/wallets/pages/transactions/pay-gas-with-any-token/api-preop.mdx b/fern/wallets/pages/transactions/pay-gas-with-any-token/api-preop.mdx
@@ -1,6 +1,6 @@
 <Steps>
   <Step title="Initial Prepare Calls">
-    Prepare calls using the `paymasterService` capability. Use your signer address directly as the `from` field.
+    Prepare calls using the `paymasterService` capability. Use your signer address directly as the `from` field to enable [EIP-7702](/wallets/transactions/using-eip-7702) by default.
 
     ```bash
     curl --request POST \
@@ -74,6 +74,6 @@
   </Step>
 
   <Step title="Sign & Send">
-    Sign and send the last prepared calls result as usual using `wallet_sendPreparedCalls`. See the [send transactions guide](/wallets/transactions/send-transactions) for more info.
+    Sign and send the last prepared calls result as usual using `wallet_sendPreparedCalls`. On the first transaction for a new account, the response type will be `array` containing both an EIP-7702 authorization and a user operation. See the [send transactions guide](/wallets/transactions/send-transactions) for a complete example.
   </Step>
 </Steps>
diff --git a/fern/wallets/pages/transactions/retry-transactions/api.mdx b/fern/wallets/pages/transactions/retry-transactions/api.mdx
@@ -4,7 +4,7 @@ You will need to fill in values wrapped in curly braces like `{SIGNER_ADDRESS}`.
 
 <Step title="Send the initial transaction">
 
-Use your signer address directly as the `from` field.
+Use your signer address directly as the `from` field to enable [EIP-7702](/wallets/transactions/using-eip-7702) by default.
 
 ```bash
 curl -X POST https://api.g.alchemy.com/v2/{API_KEY} \
@@ -55,7 +55,7 @@ This returns:
 }
 ```
 
-Sign the `raw` field and send the transaction as usual. See the [sending transactions documentation](/wallets/transactions/send-transactions) for more details.
+Sign the `raw` field and send the transaction as usual. On the first transaction for a new account, the response type will be `array` containing both an EIP-7702 authorization and a user operation. See the [sending transactions documentation](/wallets/transactions/send-transactions) for more details.
 
 </Step>
 
diff --git a/fern/wallets/pages/transactions/send-batch-transactions/api.mdx b/fern/wallets/pages/transactions/send-batch-transactions/api.mdx
@@ -9,7 +9,7 @@ for full descriptions of the parameters used in the following example.
 
 <Steps>
   <Step title="Prepare Calls">
-    Prepare calls with multiple calls specified in the batch. Use your signer address directly as the `from` field.
+    Prepare calls with multiple calls specified in the batch. Use your signer address directly as the `from` field to enable [EIP-7702](/wallets/transactions/using-eip-7702) by default.
 ```bash twoslash
 curl --request POST \
   --url https://api.g.alchemy.com/v2/$ALCHEMY_API_KEY \
diff --git a/fern/wallets/pages/transactions/send-parallel-transactions/api.mdx b/fern/wallets/pages/transactions/send-parallel-transactions/api.mdx
@@ -2,7 +2,7 @@ You will need to fill in values wrapped in curly braces like `{SIGNER_ADDRESS}`.
 
 <Steps>
   <Step title="Prepare parallel calls">
-    Use your signer address directly as the `from` field. To send parallel calls, use the `nonceOverride` capability. This allows us to specify a `nonceKey` parameter, a hex value that fits inside a `uint152` and differentiates transactions.
+    Use your signer address directly as the `from` field to enable [EIP-7702](/wallets/transactions/using-eip-7702) by default. To send parallel calls, use the `nonceOverride` capability. This allows us to specify a `nonceKey` parameter, a hex value that fits inside a `uint152` and differentiates transactions.
 
     In production, as long as the nonce key override is nonzero (zero is the default), and different between `prepareCalls` requests, the transactions will be processed in parallel.
 
@@ -90,6 +90,8 @@ You will need to fill in values wrapped in curly braces like `{SIGNER_ADDRESS}`.
     ```
 
     Note the two `signatureRequest` objects that were returned for each request! Also keep the returned `data` object from each request, you'll need them when we send the parallel transactions!
+
+    On the first transaction for a new account, the response type will be `array` containing both an EIP-7702 authorization and a user operation. See [Send Transactions](/wallets/transactions/send-transactions) for handling first-time authorization signing.
   </Step>
 
   <Step title="Sign the signature requests">
diff --git a/fern/wallets/pages/transactions/send-transactions/api.mdx b/fern/wallets/pages/transactions/send-transactions/api.mdx
@@ -23,7 +23,7 @@ SIGNER_PRIVATE_KEY=your-signer-private-key
 
 <Step title="Prepare Calls">
 
-Prepare the calls using your signer address as the `from` field. With 7702-enabled accounts, you can use your signer address directly without first calling `wallet_requestAccount`.
+Prepare the calls using your signer address as the `from` field to enable [EIP-7702](/wallets/transactions/using-eip-7702) by default. You can use your signer address directly without first calling `wallet_requestAccount`.
 
 ```bash twoslash
 PREPARE_CALLS_RESPONSE=$(curl --request POST \
diff --git a/fern/wallets/pages/transactions/sponsor-gas/api.mdx b/fern/wallets/pages/transactions/sponsor-gas/api.mdx
@@ -4,7 +4,7 @@ for full descriptions of the parameters used in the following example.
 
 <Steps>
   <Step title="Prepare Calls">
-    Prepare calls using the `paymasterService` capability. Use your signer address directly as the `from` field.
+    Prepare calls using the `paymasterService` capability. Use your signer address directly as the `from` field to enable [EIP-7702](/wallets/transactions/using-eip-7702) by default.
 ```bash
 curl --request POST \
   --url https://api.g.alchemy.com/v2/$ALCHEMY_API_KEY \
diff --git a/fern/wallets/pages/transactions/swap-tokens/api.mdx b/fern/wallets/pages/transactions/swap-tokens/api.mdx
@@ -4,7 +4,7 @@ You will need to fill in values wrapped in curly braces like `{SIGNER_ADDRESS}`.
 
 <Step title="Request a swap quote">
 
-Use your signer address directly as the `from` field. Note that `postCalls` are optional and allow you to batch an array of calls after the swap.
+Use your signer address directly as the `from` field to enable [EIP-7702](/wallets/transactions/using-eip-7702) by default. Note that `postCalls` are optional and allow you to batch an array of calls after the swap.
 
 <Info>
   If you're using an EOA or just want the raw array of calls returned, pass the
diff --git a/fern/wallets/pages/transactions/using-eip-7702/api.mdx b/fern/wallets/pages/transactions/using-eip-7702/api.mdx
@@ -2,7 +2,7 @@ See the [`wallet_prepareCalls` API
 reference](/wallets/api-reference/smart-wallets/wallet-api-endpoints/wallet-api-endpoints/wallet-prepare-calls)
 for full descriptions of the parameters used in the following example.
 
-EIP-7702 is now the default mode when using your signer address directly with `wallet_prepareCalls`. The API will automatically return authorization requests when delegation is needed.
+EIP-7702 is now the default mode when using your signer address directly with `wallet_prepareCalls`. The API will automatically return an authorization request when delegation is needed.
 
 <Steps>
   <Step title="Prepare Calls">
diff --git a/fern/wallets/pages/transactions/using-eip-7702/index.mdx b/fern/wallets/pages/transactions/using-eip-7702/index.mdx
@@ -137,26 +137,20 @@ Once delegated, the user's account behaves as a Smart Wallet while keeping the s
     process.env.PRIVATE_KEY!,
   );
 
-  // Create client without account first
-  const clientWithoutAccount = createSmartWalletClient({
+  const client = createSmartWalletClient({
     transport: alchemy({ apiKey: process.env.ALCHEMY_API_KEY! }),
     chain: sepolia,
     signer,
   });
 
   // Request a Smart Contract Account
-  const account = await clientWithoutAccount.requestAccount();
+  const account = await client.requestAccount();
 
-  // Create a new client with the SCA address
-  const client = createSmartWalletClient({
-    transport: alchemy({ apiKey: process.env.ALCHEMY_API_KEY! }),
-    chain: sepolia,
-    signer,
-    account: account.address, // Use the SCA address, not the signer address
+  // Use the SCA address as the `from` param to bypass 7702 mode
+  await client.sendCalls({
+    from: account.address,
+    calls: [...],
   });
-
-  // Transactions will now use the SCA instead of 7702
-  await client.sendCalls({ calls: [...] });
   ```
 
   **API Example:**
@@ -192,8 +186,6 @@ Once delegated, the user's account behaves as a Smart Wallet while keeping the s
   * When you need backwards compatibility with existing Smart Contract Accounts
   * When working with chains that don't yet support EIP-7702
   * When you have specific requirements for smart contract account architecture
-
-  Note: If an existing non-7702 account is found in our database for a given signer, the system will automatically use that account even when you pass the signer address directly.
 </Accordion>
 
 ## Next steps
