Skip to main content

​
Overview

The wallet is the user’s on-chain identity entry point in ArtStar. It is also the foundation for subsequent login, KYC, approvals, subscriptions, and portfolio display. The network, in turn, determines whether those interactions occur on the correct chain. As a result, wallet connection and network switching are not just technical prerequisites. They are the first checkpoint that determines whether a user can participate in the platform smoothly. If wallet state is unstable, every downstream flow can be affected.

​
Access Mechanism and Functions

In ArtStar, the wallet serves at least the following purposes: * Identifies the user’s on-chain address * Works with signatures to complete login authentication * Retrieves stablecoin balances and approval status * Initiates on-chain transactions such as Approve and Mint * Displays the user’s holdings and asset history
ArtStar’s core interactions run on a designated blockchain. To prevent asset-reading errors or transaction failures caused by the wrong network, the frontend typically needs to: * Detect the current chain ID and determine whether it matches the target network * Block critical write operations when the user is on the wrong network * Guide the user through one-click network switching * Resume the interaction flow automatically after a successful switch

​
Basic Access Flow

From a product perspective, the goal of this step is not simply to “connect a wallet,” but to allow the platform to identify and serve the current user correctly:
1

Connect Wallet

The user clicks Connect Wallet, which invokes the wallet extension or app.
2

Get Address

The wallet authorizes the connection and returns the active address.
3

State Initialization

The frontend initializes UI state associated with that address.
4

Signature Login

If required, the user completes signature verification to establish a backend session.
5

Data Loading

The frontend continues by reading balances, network details, and permission-related data before entering the core business flow.

​
Common Exceptions and Troubleshooting

Users may run into the following issues during wallet connection and network switching. The frontend should provide clear, actionable guidance rather than generic error messages:

Common Errors

  • The wallet extension is not installed or cannot be launched * The user rejects the wallet connection request * The active address cannot be retrieved
  • The current network is incorrect, such as not being on BNB Chain * The automatic network-switch request does not respond * The in-app browser of a mobile wallet has compatibility issues

​
Pitfall Guide

Wallet connection only provides the address. If the platform also requires a signature-based backend session, the user may still be “connected but not signed in,” and the frontend should guide them accordingly.
Some wallets, browsers, or mobile environments do not support reliable automatic switching. Do not assume a single switch call completes successfully. Always validate the result against the actual chain ID afterward.
When the user disconnects the wallet, the platform should clear page state, cached data, and session information tied to that address to prevent issues caused by stale data.