Unity SDK Setup for Embedded Wallets

Documentation for Unity SDK setup for the Sequence infrastructure stack for web3 gaming.

1. Configure your Builder Project

   Configure your Embedded Wallet in the Sequence Builder

2. Install the Unity SDK

   Install the latest version of Sequence’s Unity SDK from OpenUPM, or use Unity’s Package Manager UI and use the following Git URL https://github.com/0xsequence/sequence-unity.git?path=/Packages/Sequence-Unity

3. Configure the SDK

   Sign in and create a project on Sequence Builder.

   Download your config file from Builder as shown below.

   

   Place this file in the root of a Resources folder.

Configuration Parameters

Url Scheme - You must replace this with a string that is unique to your application. This is very important. Failure to do so will cause unexpected behaviour when signing in with social sign in and it will not work.

StoreSessionPrivateKeyInSecureStorage - Available on select platforms: we have integrated with the platform’s native secure storage system. If enabled, we will store session wallet info (including the private key) in secure storage and automatically attempt to recover the session for the user after closing the app (so they won’t need to login again). With this disabled (default) or on an unsupported platform, the session wallet’s private keys never leave the application’s runtime memory; however, your user will need to sign in again anytime they close the app. The default SequenceLoginWindow Boilerplate (see Bootstrap your Game) will handle this behaviour for you automatically, navigating to the appropriate page.

EnableMultipleAccountsPerEmail - By default, the SDK will only allow users to create one account per email. The account is initially associated with the login method used (email + OTP, PlayFab, Google, etc.); the user can associate additional login methods with their account (more on this in the Authentication section). If EnableMultipleAccountsPerEmail is enabled, users have the option to create multiple accounts per email address (associated with different login methods). While we have enabled this functionality, we, in general, feel this behaviour may be confusing to end-users and recommend integrators keep this option in the default disabled status.

Before proceeding, please make sure you have properly configured the Embedded Wallet in the Builder. See this guide.

Please double check that you have copy and pasted the configuration keys from the Builder correctly! This is the most common issue reported when integrating our SDK. If you receive an “invalid tenant” response, you have messed up your configuration! See this guide.