Release Notes Arcana Auth (Mainnet)
Release Date: February 21st, 2023
This release of the Arcana Auth product consists of the following components:
- Arcana Auth SDK v1.0.2
- Arcana Developer Dashboard
- Arcana wallet UI
New Product Features
Fiat On-ramp Providers
Arcana wallet supports fiat on-ramping that allows wallet users to buy cryptocurrency (native and ERC20 tokens) easily from any of the supported providers:
App Address -> Client ID
Each registered Web3 app is associated with a unique Arcana identifier. Earlier, it was referred to as App Address. Now it is referred to as Client ID in the documentation and on the Arcana Developer Dashboard screen.
The format of the Client ID has also changed but it does not impact Arcana Auth SDK usage. Developers can continue to use the existing App Address with the new Arcana Auth SDK. If the app is integrated using the following Arcana Auth SDK versions, there is no need to re-register the app:
If the app is using an older version of the Arcana Auth SDK, refer to the migration guide and upgrade to the latest version.
Minimized Wallet Widget Update
The circular widget displayed when a wallet was minimized by clicking the 'x' icon on the top right of the wallet in its maximized state has changed. In the current release, the minimized wallet state is displayed in the form of a smaller widget.
|Minimized Wallet Widget v1.0.1||Minimized Wallet Widget v1.0.2|
Arcana Auth SDK package additions: Wagmi & RainbowKit support
Typical React/NextJS apps integrate with the Arcana Auth SDK by installing the
auth-react npm packages and instantiating the
ProviderAuth before using them in the app. See how to integrate a React app for details.
The React/NextJS apps that use Wagmi can be integrated with the Arcana Auth SDK by simply installing the
auth-wagmi package and instantiating the
ArcanaConnector wrapper component. For details, see how to integrate a React app that uses Wagmi guide.
Earlier, to integrate the Arcana Auth SDK with a Web3 app that uses Wagmi or RainbowKit wallet connectors, developers were required to directly install the
auth-wagmi package and create the
ArcanaConnector. This has changed for auth-wagmi v0.0.5 onward. Developers are now required to also install the
auth package along with the
Securing Local/Session store partition
In the previous release, the embedded wallet UI displayed for an authenticated user in the context of an application was also accessible in a different app's context, if the same tab was used to browse a different app.
Once a user authenticates and logs in to an app, say app A, using a browser and then before logging out of app A, simply types a new app URL in the same browser tab for accessing app B, the user was able to access the wallet associated with app A in the context of app B without explicit sign-in into app B.
This issue is fixed in the current release. The user will have to log in to the new app before they can access the wallet UI.
Ready to dive in?
Migrate to v1.0.2
Are you using an older version of the Arcana Auth? Use the Migration Guides and upgrade to the latest version.