Skip to main content

Wallet Visibility

The Arcana wallet visibility mode setting governs the user experience for signing blockchain transactions. It allows the dApp developers to easily control when they want to show the wallet. Developers can choose between whether the Arcana wallet should be visible in the dApp browser window at all times or whether it is visible only when a blockchain transaction requires user approval through the wallet screen.

To manage the Arcana wallet visibility, the dApps must integrate with the Arcana Auth SDK. During integration, the dApp must specify the appropriate alwaysVisible input parameter while instantiating the AuthProvider to choose one of the modes:

  • Widget Mode
  • Full UI Mode

Full UI Mode -> alwaysVisible = true

By default, alwaysVisible is set to true ensuring that the wallet is always displayed on the dApp window after Auth SDK initialization and user login. Developers can choose to position the wallet widget on the screen using the position parameter. By default, it shows up on the bottom right of the screen. The wallet shows the user's account balance and provides the interface to add/switch networks and send/receive native/ERC20/custom tokens. Users can minimize and return to the wallet screen using this always-visible widget on the dApp screen.

wallet full ui mode

Widget Mode -> alwaysVisible = false

If alwaysVisible is set to false, then the wallet screen does not show up on the dApp window after Auth SDK initialization and user login, until a user action triggers a blockchain transaction.

Each blockchain transaction requires user review and approval. This review request is displayed using the wallet screen and stays visible until the user takes an action. Once the user approves or rejects, the request disappears and the user cannot access the wallet screen until another blockchain transaction is triggered. Users cannot add or switch networks or view their wallet balance or initiate send/receive of native/ERC20/custom tokens via the wallet in this mode.

wallet widget mode

User Experience

The table below summarizes how alwaysVisible parameter specified during Auth SDK initialization in the dApp code controls the user experience. For step-by-step instructions see how to configure Arcana wallet visibility mode guide.

alwaysVisibleUser Experience
Full UI1. Arcana Wallet is always visible on the dApp screen.
2. Users can minimize the wallet and it shows as a small widget on the dApp screen.
3. Users can access any of the supported wallet features using the Arcana wallet screen at any point in time.
4. When a user action triggers a blockchain transaction, the wallet screen switches to the notification screen, and the user can approve or reject the request. If the wallet is minimized, a red dot is shown and when the user selects it, the wallet notification screen comes up. It displays the current blockchain request waiting for user action. If the user was using the wallet screen to perform other operations such as switching the network, when a notification arrives, in that case, a red dot shows on the notification tab of the wallet. Other requests queue up until the user takes action on the first one.
Widget1. Arcana wallet is not visible on the dApp screen by default. It shows up only when a user action triggers a blockchain transaction. The user request notification screen is displayed for user action. Once the user takes an action, the wallet screen disappears.
2. Users cannot minimize the wallet if this mode is selected by the dApp.
3. Users cannot access any of the supported wallet features through the wallet.
4. When a user action triggers a blockchain transaction, the Arcana wallet screen pops up. It disappears after the user takes an action. If there are other blockchain transactions that show up while the user has not reviewed the current request, those will stay hidden and queued up. After the user action for the first action, subsequent actions will result in the Arcana wallet screen showing up for other requests one by one. For multiple blockchain transactions, the user will see a series of pop-ups, and then after a user action, those will disappear. There is no way for the user to ignore them or perform another action on the dApp.