Merge branch 'main' into solana-pk-fixes

Author: yashovardhan

docusaurus.config.js

@@ -105,6 +105,9 @@ const config = {
     SENTRY_KEY: process.env.SENTRY_KEY,
     LINEA_ENS_URL: process.env.LINEA_ENS_URL,
     SEGMENT_ANALYTICS_KEY: process.env.SEGMENT_ANALYTICS_KEY,
+    DISCOURSE_API_KEY: process.env.DISCOURSE_API_KEY,
+    DISCOURSE_API_USERNAME: process.env.DISCOURSE_API_USERNAME,
+    DISCOURSE_CATEGORY_ID: process.env.DISCOURSE_CATEGORY_ID,
   },
 
   trailingSlash: true,
@@ -460,14 +463,14 @@ const config = {
           },
           {
             filename: 'llms-services.txt',
-            includePatterns: ['services/**/*.{md,mdx}'],
+            includePatterns: ['services/**/*.md'],
             fullContent: false,
             title: 'Services documentation',
             description: 'Documentation links for MetaMask services',
           },
           {
             filename: 'llms-services-full.txt',
-            includePatterns: ['services/**/*.{md,mdx}'],
+            includePatterns: ['services/**/*.md'],
             fullContent: true,
             title: 'Services documentation',
             description: 'Complete documentation for MetaMask services',

gator-sidebar.js

@@ -34,6 +34,11 @@ const sidebar = {
             'get-started/use-scaffold-eth/advanced-permissions',
           ],
         },
+        {
+          type: "link",
+          label: "LLM context",
+          href: "https://docs.metamask.io/llms-smart-accounts-kit-full.txt"
+        },
         'get-started/supported-networks',
       ],
     },

gator_versioned_docs/version-0.1.0/guides/advanced-permissions/execute-on-metamask-users-behalf.md

@@ -96,8 +96,9 @@ const sessionAccount = privateKeyToAccount("0x...");
 
 ### 4. Check the EOA account code
 
-Currently, Advanced Permissions do not support automatically upgrading a MetaMask user's account to a [MetaMask smart account](../../concepts/smart-accounts.md). Therefore, you must 
-ensure that the user is upgraded to a smart account before requesting Advanced Permissions.
+Advanced Permissions support the automatic upgrading of a MetaMask user's account to a [MetaMask smart account](../../concepts/smart-accounts.md),
+when using MetaMask Flask version 13.9.0 or later. For earlier versions, you must ensure that the 
+user is upgraded to a smart account before requesting Advanced Permissions.
 
 If the user has not yet been upgraded, you can handle the upgrade [programmatically](/wallet/how-to/send-transactions/send-batch-transactions/#about-atomic-batch-transactions) or ask the 
 user to [switch to a smart account manually](https://support.metamask.io/configure/accounts/switch-to-or-revert-from-a-smart-account/#how-to-switch-to-a-metamask-smart-account).
@@ -139,9 +140,11 @@ if (code) {
 
 ### 5. Request Advanced Permissions
 
-Request Advanced Permissions from the user. In this example, you'll request an
-[ERC-20 periodic permission](use-permissions/erc20-token.md#erc-20-periodic-permission) using the Wallet Client's 
-[`requestExecutionPermissions`](../../reference/advanced-permissions/wallet-client.md#requestexecutionpermissions) action.
+Request Advanced Permissions from the user using the Wallet Client's `requestExecutionPermissions` action.
+In this example, you'll request an
+[ERC-20 periodic permission](use-permissions/erc20-token.md#erc-20-periodic-permission).
+
+See the [`requestExecutionPermissions`](../../reference/advanced-permissions/wallet-client.md#requestexecutionpermissions) API reference for more information.
 
 ```typescript
 import { sepolia as chain } from "viem/chains";
@@ -233,8 +236,10 @@ const sessionAccountWalletClient = createWalletClient({
 The session account can now redeem the permissions. The redeem transaction is sent to the `DelegationManager` contract, which validates the delegation and executes actions on the user's behalf.
 
 To redeem the permissions, use the client action based on your session account type.
-A smart account uses the Bundler Client's [`sendUserOperationWithDelegation`](../../reference/advanced-permissions/bundler-client.md#senduseroperationwithdelegation) action,
-and an EOA uses the Wallet Client's [`sendTransactionWithDelegation`](../../reference/advanced-permissions/wallet-client.md#sendtransactionwithdelegation) action:
+A smart account uses the Bundler Client's `sendUserOperationWithDelegation` action,
+and an EOA uses the Wallet Client's `sendTransactionWithDelegation` action.
+
+See the [`sendUserOperationWithDelegation`](../../reference/advanced-permissions/bundler-client.md#senduseroperationwithdelegation) and [`sendTransactionWithDelegation`](../../reference/advanced-permissions/wallet-client.md#sendtransactionwithdelegation) API reference for more information.
 
 <Tabs>
 <TabItem value="Smart account">

gator_versioned_docs/version-0.1.0/guides/advanced-permissions/use-permissions/erc20-token.md

@@ -24,6 +24,8 @@ This permission type ensures a per-period limit for ERC-20 token transfers. At t
 For example, a user signs an ERC-7715 permission that lets a dapp spend up to 10 USDC on their behalf each day. The dapp can transfer a total of
 10 USDC per day; the limit resets at the beginning of the next day.
 
+See the [ERC-20 periodic permission API reference](../../../reference/advanced-permissions/permissions.md#erc-20-periodic-permission) for more information.
+
 <Tabs>
 <TabItem value="example.ts">
 
@@ -92,6 +94,8 @@ configured rate, up to the maximum allowed amount.
 For example, a user signs an ERC-7715 permission that allows a dapp to spend 0.1 USDC per second, starting with an initial amount
 of 1 USDC, up to a maximum of 2 USDC.
 
+See the [ERC-20 stream permission API reference](../../../reference/advanced-permissions/permissions.md#erc-20-stream-permission) for more information.
+
 <Tabs>
 <TabItem value="example.ts">
 

gator_versioned_docs/version-0.1.0/guides/advanced-permissions/use-permissions/native-token.md

@@ -24,6 +24,8 @@ This permission type ensures a per-period limit for native token transfers. At t
 For example, a user signs an ERC-7715 permission that lets a dapp spend up to 0.001 ETH on their behalf each day. The dapp can transfer a total of
 0.001 USDC per day; the limit resets at the beginning of the next day.
 
+See the [native token periodic permission API reference](../../../reference/advanced-permissions/permissions.md#native-token-periodic-permission) for more information.
+
 <Tabs>
 <TabItem value="example.ts">
 
@@ -89,6 +91,8 @@ configured rate, up to the maximum allowed amount.
 For example, a user signs an ERC-7715 permission that allows a dapp to spend 0.0001 ETH per second, starting with an initial amount
 of 0.1 ETH, up to a maximum of 1 ETH.
 
+See the [native token stream permission API reference](../../../reference/advanced-permissions/permissions.md#native-token-stream-permission) for more information.
+
 <Tabs>
 <TabItem value="example.ts">
 

gator_versioned_docs/version-0.1.0/reference/delegation/index.md

@@ -315,6 +315,62 @@ export const delegation = createDelegation({
 </TabItem>
 </Tabs>
 
+
+## `getDelegationHashOffchain`
+
+Returns the delegation hash. 
+
+### Parameters
+
+| Name | Type | Required | Description |
+| --- | --- | --- | --- |
+| `input` | `Delegation` | Yes | The delegation object to hash. |
+
+### Example
+
+<Tabs>
+<TabItem value ="example.ts">
+
+```ts
+import { getDelegationHashOffchain } from "@metamask/smart-accounts-kit/utils";
+import { delegation } from "./config.ts";
+
+const delegationHash = getDelegationHashOffchain(delegation);
+```
+
+</TabItem>
+<TabItem value ="config.ts">
+
+```ts
+import { 
+  getSmartAccountsEnvironment,
+  createDelegation,
+} from "@metamask/smart-accounts-kit";
+import { parseEther } from "viem";
+import { sepolia } from "viem/chains";
+
+const environment = getSmartAccountsEnvironment(sepolia.id);
+
+// The address to which the delegation is granted. It can be an EOA address, or
+// smart account address.
+const delegate = "0x2FcB88EC2359fA635566E66415D31dD381CF5585";
+
+export const delegation = createDelegation({
+  to: delegate,
+  // Address that is granting the delegation.
+  from: "0x7E48cA6b7fe6F3d57fdd0448B03b839958416fC1",
+  environment,
+  scope: {
+    type: "nativeTokenTransferAmount",
+    // 0.001 ETH in wei format.
+    maxAmount: parseEther("0.001"),
+  },
+});
+```
+
+</TabItem>
+</Tabs>
+
 ## `getSmartAccountsEnvironment`
 
 Resolves the `SmartAccountsEnvironment` for a chain.
@@ -419,12 +475,13 @@ Signs the delegation and returns the delegation signature.
 
 | Name | Type | Required | Description |
 | --- | --- | --- | --- |
-| `signer` | `WalletClient` | Yes | [Viem Wallet Client](https://viem.sh/docs/clients/wallet#wallet-client) to sign the delegation. |
+| `privateKey` | `Hex` | Yes | The private key to use for signing the delegation. |
 | `delegation` | `Omit<Delegation, "signature">` | Yes | The unsigned delegation object to sign. |
 | `chainId` | `number` | Yes | The chain ID on which the delegation manager is deployed. |
 | `delegationManager` | `0x${string}` | Yes | The address of the Delegation Manager. |
 | `name` | `string` | No | The name of the domain of the Delegation Manager. The default is `DelegationManager`. |
 | `version` | `string` | No | The version of the domain of the Delegation Manager. The default is `1`. |
+| `allowInsecureUnrestrictedDelegation` | `boolean` | No | Whether to allow insecure unrestricted delegation with no caveats. The default is `false`. |
 
 ### Example
 
@@ -433,11 +490,11 @@ Signs the delegation and returns the delegation signature.
 
 ```ts
 import { signDelegation } from "@metamask/smart-accounts-kit";
-import { walletClient, delegation, delegationManager } from "./config.ts";
+import { privateKey, delegation, delegationManager } from "./config.ts";
 import { sepolia } from "viem/chains";
 
 const signature = signDelegation({
-  signer: walletClient,
+  privateKey,
   delegation,
   chainId: sepolia.id,
   delegationManager,
@@ -459,13 +516,8 @@ import { sepolia } from "viem/chains";
 const environment = getSmartAccountsEnvironment(sepolia.id);
 export const delegationManager = environment.DelegationManager;
 
-const account = privateKeyToAccount(delegateWallet as `0x${string}`);
-
-export const walletClient = createWalletClient({
-  account,
-  transport: http(),
-  chain: sepolia,
-});
+export const privateKey = `0x12141..`;
+const account = privateKeyToAccount(privateKey);
 
 // The address to which the delegation is granted. It can be an EOA address, or
 // smart account address.

gator_versioned_sidebars/version-0.11.0-sidebars.json

@@ -18,7 +18,7 @@ Use [testnet endpoints](../get-started/endpoints.md) during development and init
 | Testnet     | Faucet URL        | Bridge URL                    |                             
 |-------------|-------------------|-------------------------------|
 | [Arbitrum Sepolia](https://docs.arbitrum.io/launch-orbit-chain/how-tos/add-orbit-chain-to-bridge-ui)| [Arbitrum Sepolia faucet](https://faucet.quicknode.com/arbitrum/sepolia)| [Arbitrum bridge](https://bridge.arbitrum.io/)|
-| [Avalanche Fuji](https://docs.avax.network/learn/networks/fuji-testnet)| [Avalanche Fuji faucet](https://faucet.avax.network)| [Avalanche bridge](https://bridge.avax.network/)|
+| [Avalanche Fuji](https://build.avax.network/academy/avalanche-l1/interchain-messaging/03-avalanche-starter-kit/04-networks)| [Avalanche Fuji faucet](https://faucet.avax.network)| [Avalanche bridge](https://bridge.avax.network/)|
 | [Base Sepolia](https://docs.base.org/chain/using-base#metamask-1)| [Base Sepolia faucet](https://faucet.quicknode.com/base/sepolia)| [Base bridge](https://bridge.base.org/deposit)|
 | [Blast Sepolia](https://docs.blast.io/using-blast)| [Blast Sepolia faucet](https://faucet.quicknode.com/blast/sepolia)|     |
 | [Binance Smart Chain (BSC) Sepolia](https://academy.binance.com/en/articles/connecting-metamask-to-binance-smart-chain)| [BSC Sepolia faucet](https://www.bnbchain.org/en/testnet-faucet)| [BSC bridge](https://www.bnbchain.org/en/bnb-chain-bridge)|

services/how-to/get-testnet-tokens.md

@@ -15,22 +15,21 @@ Calls to the network are routed to [partner infrastructure providers](#partners-
 
 :::
 
-Avalanche is a Proof of Stake (PoS), layer 1 platform that features 3 built-in blockchains: 
-- [Contract Chain (C-Chain)](https://docs.avax.network/learn/primary-network#c-chain)
-- [Exchange Chain (X-Chain)](https://docs.avax.network/learn/primary-network#x-chain)
-- [Platform Chain (P-Chain)](https://docs.avax.network/learn/primary-network#p-chain)
+Avalanche is a Proof of Stake (PoS), layer 1 platform that features 3 built-in blockchains:
+- [Contract Chain (C-Chain)](https://build.avax.network/docs/primary-network#c-chain-contract-chain)
+- [Exchange Chain (X-Chain)](https://build.avax.network/docs/primary-network#x-chain-exchange-chain)
+- [Platform Chain (P-Chain)](https://build.avax.network/docs/primary-network#p-chain-platform-chain)
 
 Infura provides access to the C-Chain only.
 
-The C-Chain supports the Ethereum Virtual Machine (EVM), allowing Ethereum developers to deploy Solidity 
-smart contract dapps onto the C-Chain. Dapps can run on both Avalanche and Ethereum. Avalanche 
-Platform's C-Chain is EVM-compatible, but it is not identical. 
+The C-Chain supports the Ethereum Virtual Machine (EVM), allowing Ethereum developers to deploy Solidity
+smart contract dapps onto the C-Chain. Dapps can run on both Avalanche and Ethereum. Avalanche
+Platform's C-Chain is EVM-compatible, but it is not identical.
 
 :::info See also
 
-- View the [official Avalanche C-Chain documentation](https://docs.avax.network/dapps) 
+- View the [official Avalanche C-Chain documentation](https://build.avax.network/)
 for more information about building on the Avalanche C-Chain.
-- View the [differences between developing on Ethereum versus Avalanche C-Chain](https://docs.avax.network/dapps/end-to-end/launch-ethereum-dapp#gotchas-and-things-to-look-out-for). 
 
 :::