Skip to content

Merge "Create a smart account" page and other fixes #2208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

alexandratran
Copy link
Contributor

@alexandratran alexandratran commented Aug 7, 2025

Description

This PR:

  • Merges "Create a MetaMask smart account" and "Configure accounts and signers" into one page, making clarifications and edits as needed.
    • Moves deploy parameters into the smart account API reference.
    • Updates links throughout docs as needed.
  • Adds "Partner integrations" section to the DTK home page.
  • Hides experimental "Store and retrieve delegations" page.

Preview

https://metamask-docs-git-dtk-fixes-consensys-ddffed67.vercel.app/delegation-toolkit/development/

Checklist

Complete this checklist before merging your PR:

  • If this PR contains a major change to the documentation content, I have added an entry to the top of the "What's new?" page.
  • The proposed changes have been reviewed and approved by a member of the documentation team.

@alexandratran alexandratran requested review from a team as code owners August 7, 2025 21:43
Copy link

vercel bot commented Aug 7, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
metamask-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 9:43pm

@@ -48,9 +48,9 @@ const bundlerClient = createBundlerClient({
### 3. Create a delegator account

Create an account to represent Alice, the delegator who will create a delegation.
The delegator must be a [smart account](../how-to/create-smart-account/index.md).
The delegator must be a [smart account](../concepts/smart-accounts.md).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should say delegator must be a MetaMask smart account, as only MM account supports delegation? Or do you think it's redundant?


The MetaMask Delegation Toolkit supports different [MetaMask smart account types](../../concepts/smart-accounts.md#smart-account-implementation-types),
The MetaMask Delegation Toolkit is embedded, meaning that the end user can instantly interact with a dapp without wallet authorization, confirmations, or corporate logos.
Copy link
Member

@AyushBherwani1998 AyushBherwani1998 Aug 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not true, and doesn't fit right. The toolkit is not embedded, the accounts are embedded. Also, embedded wallet doesn't mean that a dApp doesn't need wallet authorization. It totally depends on the dApp. Since we are a smart account layer, not a signer layer this is not the stand out feature of smart account/ or something we should mention as it can't be always true.

For instance, if someone is using Privy as a signer for MetaMask smart account, by default it'll show confirmation screens of privy for signing cause Privy by default uses iFrame for signature.

The MetaMask Delegation Toolkit supports different [MetaMask smart account types](../../concepts/smart-accounts.md#smart-account-implementation-types),
The MetaMask Delegation Toolkit is embedded, meaning that the end user can instantly interact with a dapp without wallet authorization, confirmations, or corporate logos.
You can enable users to create a [MetaMask smart account](../concepts/smart-accounts.md) directly in your dapp.
The toolkit supports different [smart account types](../concepts/smart-accounts.md#smart-account-implementation-types),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should say to check out below instead of sending to a different page. Both have almost same content for the types of smart account.


### Configure an account signatory
### Create a Hybrid smart account with an account signatory
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Create a Hybrid smart account with an account signatory
### Create a Hybrid smart account with an Account signatory

We can use Account since it's Viem class.


To work with WebAuthn, install the [Ox SDK](https://oxlib.sh/).

To use WebAuthn, install the [Ox SDK](https://oxlib.sh/).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can revert, because WebAuthn is part of Viem SDK, but 0x is required for getting address, and PublicKey from credentials.


- In conjunction with [Viem Account Abstraction clients](configure.md), deploy the smart account
and [send user operations](send-user-operation.md).
- [Sign delegations](create-delegation/index.md) that can be used to grant specific rights and permissions to other accounts.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [Sign delegations](create-delegation/index.md) that can be used to grant specific rights and permissions to other accounts.
- [Create delegations](create-delegation/index.md) that can be used to grant specific rights and permissions to other accounts.

- In conjunction with [Viem Account Abstraction clients](configure.md), deploy the smart account
and [send user operations](send-user-operation.md).
- [Sign delegations](create-delegation/index.md) that can be used to grant specific rights and permissions to other accounts.
Smart accounts that sign delegations are called *delegator accounts*.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Smart accounts that sign delegations are called *delegator accounts*.
Smart accounts that create delegations are called *delegator accounts*.

Copy link
Member

@AyushBherwani1998 AyushBherwani1998 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

left some comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants