Get started
Overview
This page lists the initial steps for integrating your game with Lockbox. To get started, you need to request access to the MPC service and the Ronin Waypoint Account Service. Once you have access, you can implement the user authentication flow and deploy smart contracts that your game will interact with.
Prerequisites
Create an app in the Ronin Developer Console. For more information, see Create an app.
Steps
Step 1. Sign up for a Ronin Account
Your first step is to sign up for a Ronin Account as a developer:
- Go to the Ronin Developer Console.
- Create an account using an email and password or social login.
- Optionally, complete a short survey.
Your Ronin Account is ready to use.
Step 2. Create an app
Next, create an app in the Ronin Developer Console to get your client ID and API key:
- In the Ronin Developer Console, click Create application.
- Enter your app's name, then click Create.
- Select the app you created, then click Edit, and then fill in the app details, including the app description, website, and logo.
- Click Save.
Step 3. Request access to MPC service
Signing transactions with MPC requires permission. To obtain this permission, speak to your Sky Mavis point of contact.
Step 4. Implement user authentication with Ronin Account
- In the Ronin Developer Console, select your app, then App Permission > Waypoint Account Service > Request Access. When your request is approved, you see OAuth 2.0 under Products.
- With access to the Ronin Waypoint Account Service, configure your OAuth 2.0 settings. For more information, see Configure OAuth 2.0 settings.
- Implement the user authentication flow with Ronin Account. This flow lets you capture the users' access tokens, which are required for authenticating with Lockbox.
Step 5. Deploy and register smart contracts
Deploy smart contracts that your game will interact with. Share the addresses of these contracts with your Sky Mavis point of contact. This will allow the system to recognize and accept transactions to these contracts.
Calls to non-registered smart contracts are automatically rejected by the system.
For more information, see About transaction policies.