Release Notes Arcana Auth (Mainnet)
Version: v1.0.2
Release Date: February 21st, 2023
Feature Updates
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 Network 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 Auth SDK usage. Developers can continue to use the existing App Address with the new Auth SDK as well. No need to re-register the app if you were using the following Auth SDKs:
- v1.0.1
- v1.0.0
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 screen 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 |
|---|---|
 |
  |
Auth SDK additions: Wagmi & RainbowKit support
Typical React/NextJS apps 
integrate with the Arcana Auth SDK by installing the auth and auth-react npm packages and instantiating the AuthProvider and ProviderAuth before using them in the app. See how to integrate a React app with the Auth SDK guide for details.
The React/NextJS apps that use Wagmi 
can be integrated with the 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.
Similarly, for React apps using the RainbowKit framework, 
see how to integrate a React app that uses RainbowKit guide.
Using auth-wagmi
If your Web3 application uses Wagmi or RainbowKit, you can directly install and integrate with the Auth wagmi wrapper. Using auth-wagmi does not require installing the auth package as it is wrapped within the auth-wagmi package.
Bug Fixes
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.
Get Started
New to Auth SDK and ready to dive in?
See Auth SDK Quick Start Guide.
For step-by-step instructions, see how to integrate with Auth SDK guide.
Check out the sample dApp integration example with the Arcana SDKs for React,Vue dApps.
Migrate to v1.0.2
Are you using an older version of the Arcana Auth SDK? Refer to the Migration Guides and upgrade to the latest version.
Questions?
Refer to FAQ, Troubleshooting Guide and other developer resources or contact Arcana Support.