rebrand delegation toolkit to smart accounts kit

Author: AyushBherwani1998

delegation-toolkit/index.md

@@ -203,8 +203,8 @@ const config = {
       '@docusaurus/plugin-content-docs',
       {
         id: 'gator',
-        path: 'delegation-toolkit',
-        routeBasePath: 'delegation-toolkit',
+        path: 'smart-accounts-kit',
+        routeBasePath: 'smart-accounts-kit',
         editUrl: 'https://github.com/MetaMask/metamask-docs/edit/main/',
         sidebarPath: require.resolve('./gator-sidebar.js'),
         breadcrumbs: false,
@@ -453,8 +453,8 @@ const config = {
                 to: '/wallet',
               },
               {
-                label: 'Delegation Toolkit',
-                to: '/delegation-toolkit',
+                label: 'MetaMaskSmart Accounts Kit',
+                to: '/smart-accounts-kit',
               },
               {
                 label: 'Embedded Wallets',
@@ -490,8 +490,8 @@ const config = {
                 href: 'https://github.com/MetaMask/metamask-sdk/',
               },
               {
-                label: 'Delegation Toolkit GitHub',
-                href: 'https://github.com/MetaMask/delegation-toolkit',
+                label: 'Smart Accounts Kit GitHub',
+                href: 'https://github.com/MetaMask/smart-accounts-kit',
               },
               {
                 label: 'MetaMask mobile GitHub',

docusaurus.config.js

@@ -18,7 +18,7 @@ Create and manage smart accounts for your users with just a single toggle on the
 
 ## Getting Started
 
-Our native smart accounts powered by [MetaMask Delegation Toolkit](/delegation-toolkit) simplify setup, enabling you to create and manage smart accounts effortlessly with popular libraries like Viem, Ethers, and Wagmi —no need for third-party packages to achieve ERC-4337 compatibility.
+Our native smart accounts powered by [MetaMask Smart Accounts kit](/smart-accounts-kit) simplify setup, enabling you to create and manage smart accounts effortlessly with popular libraries like Viem, Ethers, and Wagmi —no need for third-party packages to achieve ERC-4337 compatibility.
 
 We are working closely with different partners in the account abstraction ecosystem and will provide support for evolving standards like EIP-7702, ERC-7579 (Modular Accounts), and ERC-7555 (account discovery) as they get finalized.
 

embedded-wallets/features/smart-accounts.mdx

@@ -5,7 +5,7 @@ keywords: [caveats, caveat enforcers, delegation]
 
 # Caveat enforcers
 
-The MetaMask Delegation Toolkit provides *caveat enforcers*, which are smart contracts that implement rules and restrictions (*caveats*) on delegations.
+The MetaMask Smart Acocunts Kit provides *caveat enforcers*, which are smart contracts that implement rules and restrictions (*caveats*) on delegations.
 They serve as the underlying mechanism that enables conditional execution within the [Delegation Framework](./index.md#delegation-framework).
 
 A caveat enforcer acts as a gate that validates whether a delegation can be used for a particular execution. When a delegate attempts to execute an action on behalf of a delegator, each caveat enforcer specified in the delegation evaluates whether the execution meets its defined criteria.
@@ -119,7 +119,7 @@ This "all-or-nothing" approach ensures that delegations only execute exactly as
 
 ## Caveat builder
 
-While caveat enforcers operate at the smart contract level, most developers interact with them through the `CaveatBuilder` interface in the MetaMask Delegation Toolkit.
+While caveat enforcers operate at the smart contract level, most developers interact with them through the `CaveatBuilder` interface in the MetaMask Smart Accounts Kit.
 
 The `CaveatBuilder` provides a developer-friendly TypeScript API that:
 
@@ -152,7 +152,7 @@ When designing delegations with caveats, consider these best practices:
 
 ## Available caveat enforcers
 
-The Delegation Toolkit provides [out-of-the-box caveat enforcers](../../reference/delegation/caveats.md)
+The Smart Accounts Kit provides [out-of-the-box caveat enforcers](../../reference/delegation/caveats.md)
 for common restriction patterns, including:
 
 - Limiting target addresses and methods.

…ation-toolkit/assets/erc7715-request.png …-accounts-kit/assets/erc7715-request.pngdelegation-toolkit/assets/erc7715-request.png renamed to smart-accounts-kit/assets/erc7715-request.png delegation-toolkit/assets/erc7715-request.png renamed to smart-accounts-kit/assets/erc7715-request.png

@@ -1,7 +1,7 @@
 ---
 description: Learn about delegation, the delegation lifecycle, and the Delegation Framework.
 toc_max_heading_level: 2
-keywords: [delegation toolkit, delegation, delegator, delegate, delegation framework]
+keywords: [smart accounts kit, delegation, delegator, delegate, delegation framework]
 ---
 
 import Tabs from "@theme/Tabs"; 
@@ -14,7 +14,7 @@ or externally owned account (EOA) to perform specific executions on its behalf.
 The account that grants the permission is called the *delegator account*, while the account that receives the permission
 is called the *delegate account*.
 
-The MetaMask Delegation Toolkit follows the [ERC-7710](https://eips.ethereum.org/EIPS/eip-7710) standard for smart contract delegation.
+The MetaMask Smart Accounts Kit follows the [ERC-7710](https://eips.ethereum.org/EIPS/eip-7710) standard for smart contract delegation.
 In addition, users can use [caveat enforcers](caveat-enforcers.md) to apply rules and restrictions to delegations.
 For example: Alice delegates the ability to spend her USDC to Bob, limiting the amount to 100 USDC.
 
@@ -65,7 +65,7 @@ You can create the following delegation types:
 
 ## Delegation Framework
 
-The MetaMask Delegation Toolkit includes the Delegation Framework, which is a
+The MetaMask Smart Accounts Kit includes the Delegation Framework, which is a
 [set of comprehensively audited smart contracts](https://github.com/MetaMask/delegation-framework) that
 collectively handle delegator account creation, the delegation lifecycle,
 and caveat enforcement.
@@ -152,7 +152,7 @@ sequenceDiagram
 ## Execution modes
 
 When redeeming a delegation using [`redeemDelegations`](../../reference/delegation/index.md#redeemdelegations), you must pass an execution mode for each delegation chain you pass to the method.
-The Delegation Toolkit supports the following execution modes, based on [ERC-7579](https://erc7579.com/):
+The Smart Accounts Kit supports the following execution modes, based on [ERC-7579](https://erc7579.com/):
 
 | Execution mode | Number of delegation chains passed to `redeemDelegations` | Processing method | Does user operation continue execution if redemption reverts? |
 |--|--|--|--|

…/concepts/delegation/caveat-enforcers.md …/concepts/delegation/caveat-enforcers.mddelegation-toolkit/concepts/delegation/caveat-enforcers.md renamed to smart-accounts-kit/concepts/delegation/caveat-enforcers.md delegation-toolkit/concepts/delegation/caveat-enforcers.md renamed to smart-accounts-kit/concepts/delegation/caveat-enforcers.md

@@ -5,7 +5,7 @@ keywords: [ERC-7715, 7715, permissions, wallet, smart account]
 
 # ERC-7715 permissions
 
-The Delegation Toolkit supports [ERC-7715](https://eips.ethereum.org/EIPS/eip-7715), which lets you request fine-grained permissions from a MetaMask user to execute transactions on their behalf.
+The Smart Accounts Kit supports [ERC-7715](https://eips.ethereum.org/EIPS/eip-7715), which lets you request fine-grained permissions from a MetaMask user to execute transactions on their behalf.
 For example, a user can grant your dapp permission to spend 10 USDC per day to buy ETH over the course of a month.
 Once the permission is granted, your dapp can use the allocated 10 USDC each day to purchase ETH directly from the MetaMask user's account.
 
@@ -23,7 +23,7 @@ Dapps can use this method to request a wallet to grant the dapp permission to ex
 `wallet_grantPermissions` requires a `signer` parameter, which identifies the entity requesting or managing the permission.
 Common signer implementations include wallet signers, single key and multisig signers, and account signers.
 
-The Delegation Toolkit supports multiple types of signers, but [an account signer is used in this documentation's examples](../guides/erc7715/execute-on-metamask-users-behalf.md) as a common implementation.
+The Smart Accounts Kit supports multiple types of signers, but [an account signer is used in this documentation's examples](../guides/erc7715/execute-on-metamask-users-behalf.md) as a common implementation.
 With an account signer, a session account is created and used for the single purpose of requesting and redeeming ERC-7715 permissions, and does not contain tokens.
 The session account can be granted with permissions and redeem them as specified in [ERC-7710](https://eips.ethereum.org/EIPS/eip-7710).
 The session account can be a smart account or an externally owned account (EOA).
@@ -56,7 +56,7 @@ The ERC-7715 permissions lifecycle is as follows:
   It can be a [smart account](smart-accounts.md) or an externally owned account (EOA).
 
 2. **Request permissions** - Request permissions from the user.
-  The Delegation Toolkit supports [ERC-20 token permissions](../guides/erc7715/use-permissions/erc20-token.md) and
+  The Smart Accounts Kit supports [ERC-20 token permissions](../guides/erc7715/use-permissions/erc20-token.md) and
   [native token permissions](../guides/erc7715/use-permissions/native-token.md).
 
 4. **Redeem permissions** - Once the permission is granted, the session account can redeem the permission, executing on the user's behalf.

…ion-toolkit/concepts/delegation/index.md …ccounts-kit/concepts/delegation/index.mddelegation-toolkit/concepts/delegation/index.md renamed to smart-accounts-kit/concepts/delegation/index.md delegation-toolkit/concepts/delegation/index.md renamed to smart-accounts-kit/concepts/delegation/index.md

@@ -5,7 +5,7 @@ keywords: [MetaMask, smart accounts, account abstraction, ERC-4337]
 
 # MetaMask Smart Accounts
 
-The MetaMask Delegation Toolkit enables you to create and manage MetaMask Smart Accounts.
+The MetaMask Smart Accounts Kit enables you to create and manage MetaMask Smart Accounts.
 MetaMask Smart Accounts are [ERC-4337](https://eips.ethereum.org/EIPS/eip-4337) smart contract accounts
 that support programmable account behavior and advanced features such as multi-signature approvals,
 automated transaction batching, and custom security policies.
@@ -37,7 +37,7 @@ ERC-4337 introduces the following concepts:
 
 ## Smart account implementation types
 
-The MetaMask Delegation Toolkit supports three types of MetaMask Smart Accounts, each offering unique features and use cases.
+The MetaMask Smart Acocunts Kit supports three types of MetaMask Smart Accounts, each offering unique features and use cases.
 
 See [Create a smart account](../guides/smart-accounts/create-smart-account.md) to learn how to use these different account types.
 

delegation-toolkit/concepts/erc7715.md smart-accounts-kit/concepts/erc7715.mddelegation-toolkit/concepts/erc7715.md renamed to smart-accounts-kit/concepts/erc7715.md

@@ -14,7 +14,7 @@ This is an experimental feature and may change in future releases.
 [ERC-7710](https://eip.tools/eip/7710) introduces a standard way for MetaMask Smart Accounts to delegate capabilities to other
 smart accounts or externally owned accounts (EOAs).
 
-The MetaMask Delegation Toolkit provides two experimental functions, `erc7710BundlerActions()` and `erc7710WalletActions()`, that let
+The MetaMask Smart Accounts Kit provides two experimental functions, `erc7710BundlerActions()` and `erc7710WalletActions()`, that let
 a caller redeem delegations granted by MetaMask's permissions system.
 
 ## Extract relevant data
@@ -128,8 +128,8 @@ import { createPublicClient, http, createBundlerClient } from "viem";
 import { generatePrivateKey, privateKeyToAccount } from "viem/accounts";
 import { sepolia as chain } from "viem/chains";
 import { createBundlerClient } from "viem/account-abstraction";
-import { erc7710BundlerActions } from "@metamask/delegation-toolkit/experimental";
-import { toMetaMaskSmartAccount, Implementation } from "@metamask/delegation-toolkit";
+import { erc7710BundlerActions } from "@metamask/smart-accounts-kit/experimental";
+import { toMetaMaskSmartAccount, Implementation } from "@metamask/smart-accounts-kit";
 
 export const publicClient = createPublicClient({
   chain: chain,
@@ -212,7 +212,7 @@ const hash = walletClient.sendTransactionWithDelegation({
 import { http, createPublicClient, createWalletClient } from "viem";
 import { generatePrivateKey, privateKeyToAccount } from "viem/accounts";
 import { sepolia as chain } from "viem/chains";
-import { erc7710WalletActions } from "@metamask/delegation-toolkit/experimental";
+import { erc7710WalletActions } from "@metamask/smart-accounts-kit/experimental";
 
 export const publicClient = createPublicClient({
   chain,