Add Openfort signer guide for Smart Accounts Kit#2956
Open
joalavedra wants to merge 5 commits into
Open
Conversation
Adds a Configure signers guide for using Openfort embedded wallets (EOA account type) as a MetaMask smart account signer, mirroring the existing Privy and Dynamic guides. Updates the signers index card list and sidebar in both the development docs and version 1.6.0. Fixes MetaMask#2955 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
@joalavedra is attempting to deploy a commit to the Consensys Team on Vercel. A member of the Team first needs to authorize it. |
| Set `accountType` to `AccountTypeEnum.EOA` so that the embedded wallet is created as an EOA, which | ||
| acts as the signer for the smart account. | ||
|
|
||
| For an advanced configuration, see Openfort's [documentation](https://www.openfort.io/docs) for configuring appearance, login methods, and wallet recovery. |
Member
There was a problem hiding this comment.
Can you link to the configuration docs? The doc points to overview.
You can keep the sentence to be
`See [Openfort's documentation](link to configuration docs) for an advanced configuration.
Author
There was a problem hiding this comment.
Done — updated both copies of the guide to link to the React UI configuration page (https://www.openfort.io/docs/products/embedded-wallet/react/ui/configuration), which covers login methods, wallet recovery, and appearance/customization, instead of the docs overview. Pushed in 1b7a8b9.
Point the advanced-configuration link at the React UI configuration docs instead of the docs overview, per review feedback. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
lannathompson65-arch
approved these changes
Jul 3, 2026
lannathompson65-arch
approved these changes
Jul 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a "Use Openfort with MetaMask Smart Accounts" guide to the Configure signers section of the Smart Accounts Kit docs, following the structure of the existing Privy and Dynamic guides.
Openfort provides embedded wallets with social, email, and passkey sign-in via the
@openfort/reactSDK. Configured withaccountType: AccountTypeEnum.EOA, the embedded wallet is an EOA that works as a smart account signer through the standard Wagmi Wallet Client — step 3 (toMetaMaskSmartAccount) is identical to the Privy and Dynamic guides.Changes:
smart-accounts-kit/guides/smart-accounts/signers/openfort.md(and the same page ingator_versioned_docs/version-1.6.0/, since the existing signer guides are identical in both).gator-sidebar.jsandgator_versioned_sidebars/version-1.6.0-sidebars.json.Code samples are written against current SDK versions (
@openfort/react@1.1.1, wagmi 3.x, viem 2.x) and verified against working integrations. Prettier passes on all changed files.Disclosure: I'm a founder at Openfort and happy to keep this guide up to date as the SDK evolves.
Issue(s) fixed
Fixes #2955
Preview
/smart-accounts-kit/guides/smart-accounts/signers/openfort(and/smart-accounts-kit/development/guides/smart-accounts/signers/openfort)Checklist
External contributor checklist
🤖 Generated with Claude Code
Note
Low Risk
Documentation-only additions with no application, auth, or infrastructure changes; factual accuracy of SDK snippets should be reviewed per contributor workflow.
Overview
Adds Openfort to the Smart Accounts Kit Configure signers docs so developers can wire Openfort’s embedded EOA wallet into MetaMask Smart Accounts the same way as Privy and Dynamic.
A new how-to page (
openfort.md) covers installing@openfort/react, setting upOpenfortProviderwithOpenfortWagmiBridgeandaccountType: AccountTypeEnum.EOA, and creating the smart account via Wagmi’swalletClientandtoMetaMaskSmartAccount. The same page is duplicated undergator_versioned_docs/version-1.6.0/to match other signer guides.Navigation and discovery are updated in
gator-sidebar.js,version-1.6.0-sidebars.json, and both signersindex.mdxfiles (Openfort card plusopenfortin frontmatter keywords). Novercel.jsonredirects are required because this is a new route only.Reviewed by Cursor Bugbot for commit a9e75fc. Bugbot is set up for automated code reviews on this repo. Configure here.