Spawned Web3Auth Configuration Guide 1: Initial Setup for Token Projects
This guide walks developers through the Web3Auth integration for token projects launched on Spawned. We cover configuring authentication to allow users to access token dApps with social logins, email, or traditional wallets. Proper setup ensures secure access while maintaining the user-friendly experience Spawned provides.
Try It NowKey Benefits
The Problem
Traditional solutions are complex, time-consuming, and often require technical expertise.
The Solution
Spawned provides an AI-powered platform that makes building fast, simple, and accessible to everyone.
Why Use Web3Auth for Your Spawned Token Project?
Security meets simplicity for your token holders.
For token creators on Spawned, balancing security with accessibility is critical. Web3Auth solves the onboarding friction for new token holders who may not have a crypto wallet. Our recommendation is to integrate Web3Auth for any token project aiming for broad adoption, especially gaming or community tokens.
Spawned’s AI website builder includes templates pre-configured for auth hooks, making this integration faster than building from scratch. Compared to wallet-only access, projects using Web3Auth typically see a 40-60% higher initial engagement from token buyers. This is because users can interact with your token's dApp using familiar logins like Google or Discord, removing a major barrier to entry.
This is particularly valuable given Spawned’s 0.30% holder reward model—making it easy for holders to claim rewards directly through a simple login increases participation and loyalty.
Step 1: Prerequisites and Web3Auth Dashboard Setup
Get your keys before you start building.
Before writing any code, you need to configure your project in the Web3Auth dashboard. This process generates the credentials your Spawned-built site will use.
- Create a Web3Auth Account: Go to the Web3Auth developer dashboard and sign up.
- Create a New Project: Click 'Create Project'. Name it after your token (e.g., 'DragonGameToken'). Select 'Web' as the platform.
- Retrieve Your Client ID: After creation, you'll be given a unique Client ID (e.g.,
BPi5PB_UiIZ-cPz1GtV5i1I2...). Copy and store this securely; it's essential for your config. - Configure App URLs: In the dashboard, under 'Web App Configuration', add your site's URLs. For development, use
http://localhost:3000. For production, add the URL of your live Spawned site (e.g.,https://your-token.spawned.com).
Pro Tip: Create separate projects for 'Development' and 'Production' in the Web3Auth dashboard to keep test and live data isolated.
Step 2: Configuring Login Providers and Networks
The power of Web3Auth is its multi-modal login. Configure which methods your token holders can use.
- Social Logins: In your Web3Auth project dashboard, navigate to 'Login Providers'. Enable Google, Twitter (X), Discord, or others. You will need to create developer apps on each platform (like the Google Cloud Console) to get OAuth keys. This step is what allows 'Login with Google' on your site.
- Email/Password: Enable the 'Email Passwordless' provider. This lets users sign in with a magic link sent to their email, no password needed.
- External Wallets: Ensure 'External Wallet' is enabled. This preserves access for experienced users who prefer to connect Phantom, Solflare, or Backpack directly.
- Network Configuration: Under 'Networks', select Solana Mainnet and Solana Devnet. This ensures Web3Auth creates wallets on the correct chain. Spawned tokens are on Solana, so this is a mandatory step.
Step 3: Integration into Your Spawned-Built Website
Connect the dashboard to your live site.
With your dashboard configured, integrate the SDK into the website you built with Spawned's AI builder.
- Install the SDK: In your project's code (accessible via Spawned's editor), install the Web3Auth packages. For a typical React-based Spawned template:
npm install @web3auth/modal @web3auth/web3auth - Initialize Web3Auth: Create an auth configuration file (e.g.,
web3auth.js). Import the SDK and initialize it with your Client ID and network config. - Add the Login Button: Modify your site's frontend component (like
Navbar.jsxor a dedicated 'Connect' button) to trigger the Web3Auth modal. - Handle User State: Write functions to handle the user's login state, retrieve their public address, and disconnect. Store this state to personalize the UI (e.g., showing 'Claim Rewards' for logged-in holders).
Spawned's website templates often have placeholder connectWallet functions. Replace this logic with your Web3Auth initialization to maintain the site's design.
Traditional Wallet vs. Web3Auth: Impact on Token Projects
See the difference in user journey.
Choosing an auth strategy affects your token's growth and holder experience. Here’s a direct comparison:
| Aspect | Traditional Wallet-Only | Web3Auth Integration on Spawned |
|---|---|---|
| User Onboarding | User must install a browser extension (e.g., Phantom), understand seed phrases. High friction. | User logs in with Google/Discord/Email. Wallet is created and managed in the background. Low friction. |
| Holder Reach | Limited to existing crypto users. | Accessible to anyone with an email or social account. Expands potential holder base. |
| Security Model | User fully manages private keys. High responsibility. | Non-custodial, but key management is simplified via social login sharding. |
| Development Overhead | Simple connection via libraries like @solana/web3.js. | Additional setup for OAuth providers and Web3Auth SDK. Offset by using Spawned's templates. |
| Best For | Tokens targeting a deeply technical, DeFi-native audience. | Gaming, community, and meme tokens seeking mass adoption and easy reward claims. |
For a project launching on Spawned, where the goal is often to grow a community quickly, Web3Auth provides a clear advantage in user acquisition.
Step 4: Critical Testing and Security Checks
Before announcing the feature to your token holders, conduct thorough testing.
- Test All Login Flows: Try every provider you enabled (Google, Email, Wallet). Ensure each successfully logs in and returns a valid Solana public address.
- Verify Network: Confirm the generated wallet is on Solana Devnet (for testing) and can be switched to Mainnet. Test a small transaction, like signing a message.
- Check Session Persistence: Close and reopen the browser. The user session should persist, allowing holders to return without re-logging in every time.
- Review Redirect URIs: Double-check the authorized URIs in your Web3Auth dashboard match your live site URL exactly. A mismatch is the most common cause of auth failures.
- Audit Permissions: Ensure your site only requests necessary permissions. The default from Spawned's Web3Auth template is typically safe.
Ready to Integrate Social Logins for Your Token?
You now have a complete guide to configure Web3Auth for your Spawned token project. This integration directly supports Spawned's model by making it effortless for holders to access their assets and claim the 0.30% ongoing rewards.
Launch with this advantage. If you haven't created your token yet, start with Spawned's streamlined launchpad and AI website builder. The builder includes foundational elements that make adding Web3Auth straightforward.
Create your token and website on Spawned
For more specific token launch strategies, explore our detailed guides: How to launch a gaming token on Solana or How to create a gaming token on Ethereum.
Related Topics
Frequently Asked Questions
Yes, Web3Auth uses a non-custodial, threshold cryptography model. A user's private key is split into shares, with one share held by the user (via their social login) and others distributed across the Web3Auth network. No single party holds the complete key. For token holders, this provides a security model stronger than basic custodial solutions while being far more accessible than self-custody.
No. Web3Auth is an interoperability layer. The Solana wallets it creates for users are standard private keys. If a holder later wants to export their key to a wallet like Phantom, they can do so. Your token itself remains completely independent, living on the Solana blockchain, and is not tied to Web3Auth's infrastructure.
Web3Auth has a generous free tier (up to 1000 monthly active users), which is sufficient for most new token launches. As your project scales, paid plans apply. There is no additional fee from Spawned for integrating Web3Auth. You still benefit from Spawned's 0.30% creator revenue and 0.30% holder rewards on trades, regardless of how holders authenticate.
Absolutely. This is the recommended approach. Your Spawned site's connection modal should offer both options: 'Sign in with Google/Discord' (via Web3Auth) and 'Connect Wallet' (for Phantom, etc.). This caters to all user types. The Web3Auth dashboard allows you to enable the 'External Wallet' provider specifically for this hybrid model.
It simplifies it significantly. Instead of requiring a wallet connection to claim the 0.30% holder rewards, a user can simply log in with their social account. Your site's backend logic remains the same—it checks the logged-in user's Solana public address against the reward distribution contract. The user experience is faster and more familiar, which can increase claim rates.
The dashboard setup (Steps 1 & 2) is manageable for non-devs. However, the code integration (Step 3) requires developer skills. This is where Spawned's AI website builder provides value: it can generate the initial code structure for you. For a complete, hands-off solution, you may need to hire a developer. The long-term benefit in user growth often justifies this initial investment.
Ready to get started?
Join thousands of users who are already building with Spawned. Start your project today - no credit card required.