November 27, 2023
Fixed
- Code example in the integration guide.
- Code example in the rnsjs library reference.
- Command to install dependencies in the integration guide and rnsjs library reference.
Webhooks, a developer tool that enables apps to automatically get notified upon the occurrence of various events, such as transactions, address activities, and smart contract events. For more information, see Webhooks.
Developer documentation for Ronin Name Service (RNS). Integrate RNS in your dApp, try a quickstart guide.
isVerified
search.Consolidated previously separate explanation topics into one integration guide: Integrate using the API.
The API integration guide stated that in the identify
events, the user_id
should be sent before identifying the user. This could lead to a double-count of the daily active users (DAU). This has been fixed.
Ronin REST API documentation: Ronin RESTful API.
A link to download the Unity package for the App Tracking Unity SDK.
The Ronin Wallet provider object is now explicitly referred to as "the window.ronin.provider
object" in the following guides:
origins-beta
path in Origins API.
Added gas
in the code example in Send a transaction request.
Documentation for implementing the flow that lets you link a user's Ronin Wallet to their Sky Mavis Account or their account in your app.
A guide for implementing the flow that lets your users link Ronin Wallet to their account in your app. The user's account can be their Sky Mavis Account or the account in your app's system. When the wallet is connected to the account, the user can sign transactions using the Ronin Wallet browser extension or mobile app. For more information, see Link Ronin Wallet with Sky Mavis Account.
In addition, you can also earn commission from every wallet that is linked to your app. For more information, see About Ronin Wallet Referral program.
Improvements across the API documentation and the site's information architecture.
Documentation about authentication, rate limits, and errors in the API tab: see Authentication, Rate limits, and Status codes.
A new wallet version has been released for desktop (v1.26.0) and mobile (v1.14.0) clients.
To make it easier to integrate Ronin wallet into dApps, we decided to remove the wallet domain allowlist. Instead we're moving to a combination of session management and trusted domain system.
Following the EIP-1102 standard, from now on the Ronin wallet extension won't expose the user's wallet and addresses by default. Developers have to call eth_requestAccounts
to connect to the wallet and the user can select the addresses he wants to expose to the dApp or he can completely reject the request.
For an example of the updated request flow, see Get user's wallet addresses.
With the removal of the domain allowlist system, the trusted domain system, that was already introduced with wallet version v1.24.0 (desktop) and v1.13.0 (mobile), becomes an important feature of the wallet.
For more information about the trusted domain system, see About trusted domain system.
This release brings a flurry of developer features to Ronin and introduces our revamped developer documentation site.
Ronin VRF (Verifiable Random Function) is now available to developers in our ecosystem. This creates the opportunity to experiment with random value generation backed by cryptographic proof.
For more information, see Integrate with Ronin VRF.
We removed the previous allowlist requirement for the Ronin Wallet Javascript SDK, and released a public version that will empower developers to tap into Ronin’s infrastructure and user base.
For more information, see Ronin Wallet JS SDK.
For more information, see Ronin RPC.
We’ve migrated the website from ReadMe to Docusaurus—an open-source documentation site generator. This migration retains familiar sections like Docs, API, and Changelog while enabling our team to contribute to the documentation through a docs-as-code workflow.
The developer documentation layout has also been restructured using the Diataxis framework. This is a way to organize technical documentation that anticipates developers’ needs.
Together, these updates to our developer documentation make it easier than ever for developers to access the content they’re looking for and contribute to our ecosystem.
For more information, see Documentation structure.