How to add Reown social & email login to your blockchain app

For users who've never touched a crypto wallet, the standard Web3 onboarding flow — install an extension, write down a seed phrase, manage a private key — is a wall, not a welcome mat. Social and email logins let those users authenticate with an account they already have, with a non-custodial wallet provisioned in the background. No seed phrase required.

This guide covers how social and email logins work with Reown, what to consider before integrating them, and how to get them running in your app. If you're building for a more experienced audience, Reown also supports SIWE and SIWX for onchain-native sign-in.

Why Add Social & Email Logins to Your App?

Onboard users who don't own a wallet yet

Requiring a crypto wallet at the front door excludes the majority of internet users. Social and email logins let people start using your app immediately, with a non-custodial wallet provisioned automatically on first login. The blockchain infrastructure is there — users just don't have to set it up themselves before they can do anything useful.

Expand your addressable audience

Most internet users already have at least one social account. Enabling familiar authentication methods removes the step where a large share of potential users bounce. You meet them on a flow they already know, rather than asking them to learn a new one before they've seen any value in your app.

Reduce friction at the critical conversion point

Login is the first real interaction a user has with your app. A complex or unfamiliar authentication flow at that moment drives drop-off before users ever reach the core experience. A streamlined social or email login — combined with in-app payments and swap capabilities — means users can fund a wallet, trade, and transact without ever leaving your app or switching tools.

Who Should Add Social & Email Logins to Their Apps?

Decentralised social apps

Social users expect to sign in and start engaging immediately. Asking them to configure a wallet before they can view content or follow other users creates friction that doesn't exist on any comparable Web2 platform. Social and email logins let users sign in with Farcaster, X, or Google and get into your app in seconds.

Prediction markets

Prediction market users want to participate in events quickly — often while the relevant news is still happening. An email-based login removes the setup barrier and lets users place positions without a wallet configuration step in the way. Lower barrier to entry means more sessions, and more sessions means more activity.

NFT marketplaces

First-time collectors are often deterred by the wallet setup process before they've even seen what they're buying. Social logins let new users authenticate instantly, with a non-custodial wallet created in the background. They can browse, purchase, and hold assets immediately.

Onchain games

Gamers are accustomed to signing in with a Google or Discord account and playing within seconds. Introducing wallet management into that flow — especially for users new to Web3 — is a context mismatch. Social logins preserve the experience gamers expect while still giving them onchain asset ownership. Read more about building games with Reown.

How Do Social & Email Logins Work?

Reown handles both email and social authentication without requiring users to create or manage a wallet manually.

Email login uses a One Time Password (OTP). When a user enters their email address, Reown sends a verification code to that address. Once confirmed, a non-custodial wallet is created and linked to that user's account. The wallet persists across any app that integrates Reown authentication — so the same user identity follows them across your app ecosystem.

Social login skips the OTP step entirely. The user authenticates through their chosen provider (Google, X, Discord, GitHub, Apple, Facebook, or Farcaster) using that platform's standard OAuth flow. Reown handles the wallet creation in the background.

In both cases, private keys are managed securely and the wallet is non-custodial — the user owns the keys, not Reown. Users can also opt to "Upgrade Wallet" later, migrating their assets to a fully self-custodial wallet if they want direct control.

What to Consider When Adding Social & Email Logins

Regulation and compliance

Authentication methods that abstract away key management — email and social logins in particular — may have different compliance implications depending on your jurisdiction and user base. If you're building in a regulated context, review what your obligations are around identity verification, KYC, and custody before going live. Reown's compliance tooling can help teams navigate this.

User experience

You have control over how the login flow is presented. You can choose to show wallet connection options alongside social and email login (for a mixed audience), or lead entirely with social-first options to reduce visual complexity for users new to Web3. Think about your primary user persona when making this decision — a user who already has MetaMask installed has different expectations from a user signing in for the first time.

Security

The non-custodial model means private keys are never stored by Reown. The security of the underlying wallet is robust even though the onboarding flow doesn't surface it. For teams with specific security requirements, the upgrade path to a self-custodial wallet gives users and teams flexibility as needs evolve.

Compatible frameworks

Reown supports React, Next.js, Vue, JavaScript, React Native, Flutter, Android, iOS, and Unity. Verify that your framework is covered before starting integration. Full compatibility details are in the Reown docs.

Before You Add Social & Email Logins

Set up a project on the Reown Dashboard

You'll need a Project ID from the Reown Dashboard to configure the SDK. Sign in, navigate to your team workspace, click + Project, select AppKit, name your project, and copy the Project ID that's generated.

Install the Reown SDK

Add the Reown SDK to your project using your package manager. Full installation instructions for each supported framework are in the authentication docs.

How to Integrate Social & Email Logins: A Step-by-Step Guide

Step 1: Decide which providers to enable

Before touching any configuration, decide which login methods you want to offer. You can enable email, specific social providers (Google, X, GitHub, Discord, Apple, Facebook, Farcaster), or any combination of the two. You can also disable specific providers entirely if they don't fit your audience.

Step 2: Configure your Project ID and initialise the SDK

With your Project ID from the Reown Dashboard, initialise the SDK for your chosen framework. Reference the authentication docs for framework-specific setup — the configuration is consistent across supported stacks.

Step 3: Set your email and social options in the features object

Email and social logins are enabled by default — you don't need to write extra code to turn them on. The SDK ships with all providers active. If you want to restrict available providers or disable email or social login entirely, use the features object in your configuration:

code snippet

const modal = createAppKit({
adapters: [wagmiAdapter],
projectId,
networks: [mainnet, arbitrum],
features: {
email: true, // default: true. Set to false to remove email login.
socials: ['google', 'x', 'github', 'discord', 'apple', 'facebook', 'farcaster'] // remove any providers you don't want to offer
}
})

email controls whether the connection modal includes the email login option. It defaults to true, so you only need to set it explicitly if you want to disable it.

socials defines which social providers appear in the connection modal. Pass only the providers you want to enable. To disable social login entirely, pass an empty array: socials: [].

The full createAppKit() reference is in the Reown authentication docs.

Why Reown for Social & Email Logins?

Broad provider coverage out of the box

Reown supports Google, X, GitHub, Discord, Apple, Facebook, and Farcaster — the providers your users are most likely to already have an account with. There's no additional integration work required to enable any of them; they're part of the core SDK.

No additional tooling required

Social and email login are built into the Reown SDK, not added on top. You don't need to configure a separate OAuth provider, build a wallet provisioning layer, or stitch together third-party auth tools. The same SDK that handles wallet connections also handles email OTP and social OAuth — one integration, one dashboard, one set of analytics.

Non-custodial by default

Users own their keys. Reown manages the complexity of wallet provisioning without holding assets or keys on behalf of users. This is the correct model for Web3 authentication — and it's also the upgrade path if users eventually want to migrate to a fully self-custodial wallet.

Conclusion: Enable Social & Email Logins and Start Reaching More Users

Adding social and email login to your app removes the most common reason users don't get past your front door. Users who have never touched a crypto wallet can authenticate with Google, verify with an OTP, or connect with Discord — and your app handles the rest.

Reown's authentication tools make this a single integration decision rather than a multi-tool engineering project. Get started at dashboard.reown.com, or explore the full authentication docs to see framework-specific setup guides and advanced configuration options.

For more on what Reown's authentication layer can do — including SIWE and SIWX for onchain-native sign-in — visit reown.com/solutions/authentication.