lock files for v0.11.0

Author: AyushBherwani1998

gator_versioned_docs/version-0.11.0/concepts/caveat-enforcers.md

@@ -127,15 +127,15 @@ The `CaveatBuilder` provides a developer-friendly TypeScript API that:
 - Provides type-checking and validation for caveat parameters.
 - Handles the creation of the `caveats` array needed when creating a delegation.
 
-Each [caveat type](../how-to/create-delegation/restrict-delegation.md#caveat-types) in the `CaveatBuilder`
+Each [caveat type](../reference/caveats.md) in the `CaveatBuilder`
 corresponds to a specific caveat enforcer contract. For example, when you use:
 
 ```typescript
 caveatBuilder.addCaveat("allowedTargets", ["0xc11F3a8E5C7D16b75c9E2F60d26f5321C6Af5E92"]);
 ```
 
 The builder is creating a caveat that references the
-[`AllowedTargetsEnforcer`](../how-to/create-delegation/restrict-delegation.md#allowedtargets) contract address and
+[`AllowedTargetsEnforcer`](../reference/caveats.md#allowedtargets) contract address and
 properly encodes the provided addresses as terms for that enforcer.
 
 ## Caveat enforcer best practices
@@ -145,14 +145,14 @@ When designing delegations with caveats, consider these best practices:
 - **Combine caveat enforcers appropriately** - Use multiple caveat enforcers to create comprehensive restrictions.
 
 - **Consider caveat enforcer order** - When using caveat enforcers that modify external contract states, the order matters.
-  For example, using [`NativeTokenPaymentEnforcer`](../how-to/create-delegation/restrict-delegation.md#nativetokenpayment) before
-  [`NativeBalanceChangeEnforcer`](../how-to/create-delegation/restrict-delegation.md#nativebalancechange) might cause validation failures.
+  For example, using [`NativeTokenPaymentEnforcer`](../reference/caveats.md#nativetokenpayment) before
+  [`NativeBalanceChangeEnforcer`](../reference/caveats.md#nativebalancechange) might cause validation failures.
 
 - **Be careful with unbounded delegations** - Always include appropriate caveat enforcers to limit what a delegate can do.
 
 ## Available caveat enforcers
 
-The Delegation Toolkit provides [many out-of-the-box caveat enforcers](../how-to/create-delegation/restrict-delegation.md#caveat-types)
+The Delegation Toolkit provides [many out-of-the-box caveat enforcers](../reference/caveats.md)
 for common restriction patterns, including:
 
 - Limiting target addresses and methods.

gator_versioned_docs/version-0.11.0/concepts/delegation.md

@@ -5,8 +5,10 @@ sidebar_position: 2
 
 # Delegation
 
-*Delegation* is the ability for a [delegator account](delegator-accounts.md) to grant permission to another smart contract account (SCA)
-or externally owned account (EOA) to perform specific executions on the delegator's behalf, under defined rules and restrictions.
+*Delegation* is the ability for a [smart account](smart-accounts.md) to grant permission to another smart account
+or externally owned account (EOA) to perform specific executions on their behalf, under defined rules and restrictions.
+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 includes the following delegation features:
 
@@ -45,7 +47,7 @@ The delegation lifecycle is as follows:
     :::
 
 4. **Delegation redemption** - The delegate (the account being granted the permission) redeems the
-   delegation through an [ERC-4337 user operation](delegator-accounts.md#account-abstraction-erc-4337),
+   delegation through an [ERC-4337 user operation](smart-accounts.md#account-abstraction-erc-4337),
    which verifies that the delegated authority is valid in order to perform the execution.
 
 See [how to create a delegation](../how-to/create-delegation/index.md) to get started with the
@@ -62,7 +64,7 @@ It consists of the following components:
 - **Delegator Core** - Delegator Core contains the logic for the ERC-4337 compliant delegator accounts.
   It defines the interface needed for the Delegation Manager to invoke executions on behalf of the accounts.
 
-- **Delegator account implementations** - There are [multiple delegator account implementations](delegator-accounts.md#delegator-account-types),
+- **Delegator account implementations** - There are [multiple delegator account implementations](smart-accounts.md#smart-account-implementation-types),
   with the main difference being the signature scheme used to manage the underlying account.
 
 - **Delegation Manager** - The Delegation Manager validates delegations and triggers executions

gator_versioned_docs/version-0.11.0/concepts/environment.md

@@ -18,7 +18,7 @@ The delegator environment serves several key purposes:
 
 ## Resolve the delegator environment
 
-When you create a [`MetaMaskSmartAccount`](../how-to/create-delegator-account.md) instance, the Delegation Toolkit automatically
+When you create a [MetaMask smart account](smart-accounts.md), the Delegation Toolkit automatically
 resolves the environment based on the version it requires and the chain configured.
 If no environment is found for the specified chain, it throws an error.
 
@@ -66,11 +66,11 @@ export delegatorSmartAccount;
 </Tabs>
 
 :::note
-See the [changelog](../changelog/0.11.0.md) of the toolkit version you are using for supported chains.
+See the changelog of the toolkit version you are using (in the left sidebar) for supported chains.
 :::
 
 Alternatively, you can use the `getDelegatorEnvironment` function to resolve the environment.
-This function is especially useful if your delegator is not a smart contract account when
+This function is especially useful if your delegator is not a smart account when
 [creating a redelegation](../how-to/create-delegation/index.md#create-a-redelegation).
 
 ```typescript
@@ -224,5 +224,5 @@ overrideDeployedEnvironment(
 
 :::note
 Make sure to specify the Delegation Framework version required by the toolkit.
-See the [changelog](../changelog/0.11.0.md) of the toolkit version you are using for its required Framework version.
+See the changelog of the toolkit version you are using (in the left sidebar) for its required Framework version.
 :::

…on-0.11.0/concepts/delegator-accounts.md …ersion-0.11.0/concepts/smart-accounts.mdgator_versioned_docs/version-0.11.0/concepts/delegator-accounts.md renamed to gator_versioned_docs/version-0.11.0/concepts/smart-accounts.md gator_versioned_docs/version-0.11.0/concepts/delegator-accounts.md renamed to gator_versioned_docs/version-0.11.0/concepts/smart-accounts.md

@@ -1,28 +1,30 @@
 ---
-description: Learn about account abstraction, the delegator account flow, and account types.
+description: Learn about MetaMask smart accounts.
 sidebar_position: 1
 ---
 
-# Delegator accounts
+# Smart accounts
 
-The MetaMask Delegation Toolkit enables you to create and manage *delegator accounts*.
-Delegator accounts are [ERC-4337](https://eips.ethereum.org/EIPS/eip-4337) smart contract accounts (SCAs)
+The MetaMask Delegation Toolkit enables you to create and manage MetaMask *smart accounts*.
+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.
-Unlike traditional wallets, which rely on private keys for every transaction, MetaMask delegator
+Unlike traditional wallets, which rely on private keys for every transaction, MetaMask smart
 accounts use smart contracts to govern account logic.
 
+Smart accounts are referenced in the toolkit as `MetaMaskSmartAccount`.
+
 ## Account abstraction (ERC-4337)
 
 Account abstraction, specified by [ERC-4337](https://eips.ethereum.org/EIPS/eip-4337), is a
-mechanism that enables users to manage SCAs containing arbitrary verification logic.
-ERC-4337 enables SCAs to be used as primary accounts in place of traditional private key-based
+mechanism that enables users to manage smart accounts containing arbitrary verification logic.
+ERC-4337 enables smart contracts to be used as primary accounts in place of traditional private key-based
 accounts, or externally owned accounts (EOAs).
 
 ERC-4337 introduces the following concepts:
 
 - **User operation** - A package of instructions signed by a user, specifying executions for
-  the SCA to perform.
+  the smart account to perform.
   User operations are collected and submitted to the network by bundlers.
 
 - **Bundler** - A service that collects multiple user operations, packages them into a single transaction,
@@ -32,15 +34,34 @@ ERC-4337 introduces the following concepts:
   adhere to the required rules and security checks.
 
 - **Paymasters** - Entities that handle the payment of gas fees on behalf of users, often integrated
-  into SCAs to facilitate gas abstraction.
+  into smart accounts to facilitate gas abstraction.
+
+## Smart account implementation types
+
+The MetaMask Delegation Toolkit supports two types of smart accounts, each offering unique features and use cases.
+See [Configure accounts and signers](../how-to/create-smart-account/configure-accounts-signers.md) to learn how to use these different account types.
+
+### Hybrid smart account
+
+The Hybrid smart account is a flexible implementation that supports both an externally owned account (EOA) "owner" and any number of P256 (passkey) signers.
+You can configure any of these signers as the signatory, and use them to sign any data, including user operations, on behalf of the smart account.
+
+This type is referenced in the toolkit as `Implementation.Hybrid`.
+
+### Multisig smart account
+
+The Multisig smart account is an implementation that supports multiple signers with a configurable threshold for valid signatures, allowing for enhanced security and flexibility in account management.
+The signatory must have at least as many signers include as the threshold is configured for the account.
 
-## Delegator account flow
+This type is referenced in the toolkit as `Implementation.Multisig`.
 
-The MetaMask delegator account flow is as follows:
+## Smart account flow
 
-1. **Account setup** - A user creates an SCA by deploying a smart contract, and initializing it with
+The MetaMask smart account flow is as follows:
+
+1. **Account setup** - A user creates a smart account by deploying a smart contract, and initializing it with
    ownership and security settings.
-   The user can customize the SCA in the following ways:
+   The user can customize the smart account in the following ways:
 
     - **Account logic** - They can configure custom logic for actions such as multi-signature
       approvals, spending limits, and automated transaction batching.
@@ -60,20 +81,8 @@ The MetaMask delegator account flow is as follows:
 4. **Validation and execution** - The bundled transaction goes to an entry point contract, which
    validates each user operation and executes them if they meet the smart contract's rules.
 
-## Delegator account types
-
-The MetaMask Delegation Toolkit supports two types of delegator accounts, each offering unique features and use cases.
-See [Configure accounts and signers](../how-to/configure-delegator-accounts-signers.md) to learn how to use these different account types.
-
-### Hybrid Delegator
-
-The Hybrid Delegator is a flexible implementation that supports both an externally owned account (EOA) "owner" and any number of P256 (passkey) signers.
-You can configure any of these signers as the signatory, and use them to sign on behalf of the delegator.
-
-This type is referenced in the toolkit as `Implementation.Hybrid`.
-
-### Multisig Delegator
-
-The Multisig Delegator is an implementation that supports multiple signers with a configurable threshold for valid signatures, allowing for enhanced security and flexibility in account management. The signatory must have at least as many signers include as the threshold is configured for the account.
+## Delegator accounts
 
-This type is referenced in the Toolkit as `Implementation.Multisig`.
+Delegator accounts are a type of smart account that allows users to grant permission to other smart accounts or EOAs
+to perform specific executions on their behalf, under defined rules and restrictions.
+Learn more about [delegation](delegation.md).

gator_versioned_docs/version-0.11.0/experimental/_category_.json

@@ -6,4 +6,4 @@
     "slug": "/experimental",
     "title": "Delegation Toolkit experimental features"
   }
-}
+}

gator_versioned_docs/version-0.11.0/experimental/erc-7710-redeem-delegations.md

@@ -12,8 +12,8 @@ import TabItem from "@theme/TabItem";
 This is an experimental feature and may change in future releases.
 :::
 
-[ERC-7710](https://eip.tools/eip/7710) introduces a standard way for smart contract accounts (SCAs) to delegate capabilities to other
-SCAs or externally owned accounts (EOAs).
+[ERC-7710](https://eip.tools/eip/7710) introduces a standard way for 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
 a caller redeem delegations granted by MetaMask's permissions system.
@@ -57,7 +57,7 @@ const permissionsResponse = [{
 
 const permissionsContext = permissionsResponse[0].context;
 const delegationManager = permissionsResponse[0].signerMeta.delegationManager;
-// accountMeta is only present when the smart contract account is not deployed.
+// accountMeta is only present when the smart account is not deployed.
 const accountMetadata = permissionsResponse[0].accountMeta;
 ```
 
@@ -80,14 +80,11 @@ If you redeem delegations in any other way, it is your responsibility to validat
 
 ## Redeem the permission
 
-Redeem a delegation using one of two methods. Choose the method based on your account type:
+Redeem a delegation with a [smart account](#redeem-with-a-smart-account) or an [externally owned account (EOA)](#redeem-with-an-eoa).
 
-- If redeeming with an SCA, call `sendUserOperationWithDelegation`.
-- If redeeming with an EOA, call `sendTransactionWithDelegation`.
+### Redeem with a smart account
 
-### Redeem with an SCA
-
-To redeem a delegation with a smart contract account, create a [`MetaMaskSmartAccount`](../how-to/create-delegator-account.md#create-a-metamasksmartaccount)
+To redeem a delegation with a smart account, create a [`MetaMaskSmartAccount`](../how-to/create-smart-account/index.md#create-a-metamasksmartaccount)
 and a [Viem Bundler Client](https://viem.sh/account-abstraction/clients/bundler).
 
 After setting up your Bundler Client, you can extend its functionality with `erc7710BundlerActions` actions to support ERC-7710. Once extended, use `sendUserOperationWithDelegation` to redeem the permission.
@@ -213,7 +210,7 @@ const hash = walletClient.sendTransactionWithDelegation({
 <TabItem value="config.ts">
 
 ```typescript
-import { http, createPublicClient } from "viem";
+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";

gator_versioned_docs/version-0.11.0/experimental/erc-7715-request-permissions.md

@@ -21,8 +21,8 @@ The MetaMask Delegation Toolkit provides the experimental actions for ERC-7715 t
 ## Request permissions
 
 To request permissions, extend your [Viem Wallet Client](https://viem.sh/docs/clients/wallet) with `erc7715ProviderActions` actions.
-You'll need a session account to request the permission, which can be either an externally owned account (EOA) or a smart contract account (SCA).
-This example uses an SCA:
+You'll need a session account to request the permission, which can be either a smart account or an externally owned account (EOA).
+This example uses a smart account:
 
 <Tabs>
 <TabItem value="example.ts">
@@ -92,8 +92,8 @@ export const walletClient = createWalletClient({
 </Tabs>
 
 <details>
-  <summary> ERC-7715 request permission sample </summary>
-  
+  <summary>ERC-7715 request permission sample</summary>
+  <div>
   Here's what your ERC-7715 native token streaming allowance request looks like:
 
   ```ts
@@ -120,6 +120,7 @@ export const walletClient = createWalletClient({
   ```
 
   Learn more about the [ERC-7715 permission schema](https://eip.tools/eip/7715).
+  </div>
 </details>
 
 

gator_versioned_docs/version-0.11.0/get-started/quickstart.md

@@ -46,10 +46,9 @@ const bundlerClient = createBundlerClient({
 
 ### 3. Create a delegator account
 
-[Create a delegator account](../how-to/create-delegator-account.md) to set up a delegation.
-The delegator must be a smart account.
+[Create a delegator smart account](../how-to/create-smart-account/index.md) to set up a delegation.
 
-This example configures a [Hybrid Delegator](../how-to/configure-delegator-accounts-signers.md#configure-a-hybrid-delegator):
+This example configures a [Hybrid](../how-to/create-smart-account/configure-accounts-signers.md#configure-a-hybrid-smart-account) delegator account:
 
 ```typescript
 import {
@@ -72,9 +71,9 @@ const delegatorSmartAccount = await toMetaMaskSmartAccount({
 ### 4. Create a delegate account
 
 Create a delegate account to receive the delegation.
-The delegate can be either a smart contract account (SCA) or an externally owned account (EOA).
+The delegate can be either a smart account or an externally owned account (EOA).
 
-This example uses an SCA:
+This example uses a smart account:
 
 ```typescript
 import {
@@ -135,7 +134,7 @@ The delegate account can now [redeem the delegation](../how-to/redeem-delegation
 The redeem transaction is sent to the `DelegationManager` contract, which validates the delegation and
 executes actions on the delegator's behalf.
 
-To prepare the call data for the redeem transaction, use the `redeemDelegation` utility function from the Delegation Toolkit.
+To prepare the calldata for the redeem transaction, use the `redeemDelegation` utility function from the Delegation Toolkit.
 
 ```typescript
 import {

gator_versioned_docs/version-0.11.0/how-to/configure.md

@@ -6,7 +6,8 @@ sidebar_label: Configure the toolkit
 
 # Configure the Delegation Toolkit
 
-The MetaMask Delegation Toolkit enables you to easily integrate delegator accounts into your dapp, enabling a more flexible, secure, and frictionless experience for your users.
+The MetaMask Delegation Toolkit enables you to easily integrate [smart accounts](../concepts/smart-accounts.md) into your dapp,
+enabling a more flexible, secure, and frictionless experience for your users.
 
 The toolkit is highly configurable, allowing you to tailor it to your project's specific needs. It includes support for custom signers, multiple signatory schemes, custom paymasters and bundlers, and more.
 

gator_versioned_docs/version-0.11.0/how-to/create-delegation/create-custom-caveat-enforcer.md

@@ -8,7 +8,7 @@ import TabItem from "@theme/TabItem";
 
 # Create a custom caveat enforcer
 
-When [restricting a delegation](restrict-delegation.md), the MetaMask Delegation Toolkit provides some [out-of-the-box caveat enforcers](restrict-delegation.md#caveat-types)
+When [restricting a delegation](restrict-delegation.md), the MetaMask Delegation Toolkit provides some [out-of-the-box caveat enforcers](../../reference/caveats.md)
 that cover common use cases.
 For more granular or custom control, you can follow the instructions on this page to create custom caveat enforcers from scratch.