Skip to content

Commit

Permalink
update
Browse files Browse the repository at this point in the history
  • Loading branch information
victoriaxyz committed Dec 19, 2024
1 parent c7e36b4 commit 70b27df
Showing 1 changed file with 6 additions and 5 deletions.
11 changes: 6 additions & 5 deletions docs/authentication/web3/metamask.mdx
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: MetaMask
title: MetaMask Wallet
description: Learn how to set up Web3 authentication with MetaMask.
---

Expand All @@ -15,7 +15,7 @@ description: Learn how to set up Web3 authentication with MetaMask.
- Use MetaMask to authenticate users with Web3
</TutorialHero>

Enabling [MetaMask](https://metamask.io/) as a Web3 provider allows your users to sign in and sign up to your Clerk application with their MetaMask wallet.
Enabling [MetaMask](https://metamask.io/) as a Web3 provider allows your users to sign in and up to your Clerk application with their MetaMask wallet.

## Enable MetaMask as a Web3 provider

Expand All @@ -32,14 +32,15 @@ The simplest way to test authentication is to visit your Clerk application's [Ac
- **For production**`https://accounts.your-domain.com/sign-in`
1. On the sign-in page, you should see **MetaMask** as an option. Use it to sign in with your MetaMask wallet.

## Collect additional user information during sign-up
## Collect additional user information during sign-up (optional)

Web3 applications typically utilize a hexadecimal wallet address to identify users, which offers a high level of privacy. However, when bridging the gap between Web3 and Web2, it's often necessary to gather human-readable information about the user, such as their email address, phone number, or a username.
Web3 applications typically use a hexadecimal wallet address to identify users, which offers a high level of privacy. However, when bridging the gap between Web3 and Web2, it's often necessary to gather human-readable information about the user, such as their email address, phone number, or a username.

To collect additional information about your user during sign-up:

1. In the Clerk Dashboard, navigate to the [**Email, phone, username**](https://dashboard.clerk.com/last-active?path=user-authentication/email-phone-username) page.
1. On this page, toggle on attributes you wish to collect from your user during sign up. Select the settings icon next to an attribute to set it as **Required**. When set as **Required**, Clerk automatically prompts the user for this information after they authenticate with MetaMask.
1. On this page, toggle on attributes you wish to collect from your user during sign up.
1. To set an attribute as required, select the settings icon next to the enabled attribute. Clerk will automatically prompt the user for this information after authenticating with MetaMask.

## Connect MetaMask to existing account

Expand Down

0 comments on commit 70b27df

Please sign in to comment.