How To Implement Crypto Wallets That Web2 Players Will Use

Properly constructed and implemented wallets don’t need to be complex or intimidating. With simple onboarding flows and web2-like logins, non-custodial wallets can be made as simple as ever.

If you’re developing or have developed a web3 game you probably know that a critical aspect of the game itself is how and where players store NFT items acquired in-game. Conventional crypto wallets can be intimidating for web2 players, providing web3 game developers yet another obstacle to reaching the larger gaming market of 3 billion players.

Many web3 games require players to open a wallet before they start playing. This is because most web3 games use wallet connection as a means of player sign-in and authentication, progress tracking, in-game NFT or virtual land payments, and NFT storage.

“Wallets shouldn’t be forced on players as a requirement, they should be offered as an added benefit to unlock enhanced player functionality” — KJ Mercer, Lead Game Designer

Player-Friendly Wallets

Ready employs a separate sign-in and authentication mechanism which is distinct from their wallets, allowing players to sign in and track their game progress without the need to connect a wallet. This eliminates undue pressure associated with the requirement to connect a wallet before playing.

Furthermore, in games built on Ready, NFTs are purchased using in-game hard currency rather than cryptocurrencies, allowing players to fully engage in gameplay before they introduce a wallet. In fact, players don’t actually need to create a crypto wallet until they purchase their first NFT virtual item to store in it. Ready’s SDK enables developers to implement wallet creation pop-ups prompting players to create a wallet as soon as they acquire their first NFT.

Wallet creation is as simple as creating a password. It is designed to be as intuitive as possible for web2 users.

Implementing Ready Wallets consists of three simple steps.

1. Check if user has an existing wallet
2. If yes, retrieve existing wallet
3. If no, create new wallet

Each step is simple to implement, and Ready includes all of the code in its documentation. To provide an idea of the simplicity of Ready wallet integration and implementation, here is the API call for creating a new player wallet:

using RGN.Modules.Wallets;

namespace SomeNamespace
{
    internal sealed class CreateNewWallet
    {
        public async void CreateWalletAsync()
        {
            string password = "123456abcdefABCDEF";
            CreateWalletResponseData result =
                await WalletsModule.I.CreateWalletAsync(password);
            UnityEngine.Debug.Log(result.address);
            UnityEngine.Debug.Log(result.wallet_created);
            UnityEngine.Debug.Log(result.success);
            UnityEngine.Debug.Log(result.error);
        }
    }
}

New wallet creation is recorded on the blockchain as follows:

{
    "success": {
        "code": 200,
        "message": "Success",
        "status": "WALLET_CREATED",
        "details": [
            {
                "wallet_public_key": UUID,
            }
        ]
    }
}

One-Time Setup for All Games

Since Ready Games is an ecosystem of connected games through a web of technological integrations, once a player creates a wallet in one game, their wallet will automatically connect to any other games they play in the ecosystem. This one-time setup makes for an incredibly smooth user experience and provides an incentive for players to play games within the ecosystem.

Non-Custodial

Ready’s wallets are entirely non-custodial. This allows players exclusive control over their assets without risking breaches by centralized custodial authorities. It also means that the password used to create a player wallet must be stored and safeguarded by the players; neither Ready Games nor the game’s developers store wallet passwords.

Recent events in the world of crypto, including the FTX bust, have taught that the only safe place to keep digital assets is in a personal, self-custodial wallet, away from centralized exchanges and custodial wallets. Ready’s security-first approach means that wallets are entirely non-custodial and it is therefore crucial for developers to explain clearly during player wallet creation that the password must be safeguarded by the player. Since neither the game developers nor Ready Games store player wallet passwords, if lost, the password cannot be recovered.

External Wallet Compatibility

Ready’s wallets are compatible with external wallets, enabling players to effortlessly transfer their assets to external wallets like Metamask as they wish. This gives existing web3 players the flexibility to store their assets in existing wallets for ease of use and organizational purposes.

Start Building Web3 for Web2

Ready’s wallets are just one piece of the puzzle that makes Ready Games the leading solution for web3 game development. Ready Games has built the infrastructure for web3 developers to make their games accessible to the entire player market. Ready’s public SDK is full of web2-friendly web3-native tools, including compliance with App Store listing requirements, an intermediate in-game currency, seamless NFT item integration, player profiles, authentication flows, and more.

Read the documentation and start building today free of charge.