Overview
Last updated
Last updated
The wallet is the first gateway for users to enter Web3. Unlike the widely used email addresses or social accounts in Web2, Web3 requires a private key to directly manage assets. The blockchain architecture for managing ownership of user assets, such as coins, tokens, and NFTs, ensures complete ownership for users but can also be a barrier to entering desired Web3 applications in an unfamiliar environment. Moreover, project teams focused on creating apps may face difficulties in decentralizing resources, such as contemplating wallet integration to prevent user drop-off during on-boarding and addressing customer requests that arise in the process.
Wepin is a Web3 wallet that dramatically reduces the concerns and costs associated with developing a wallet. By utilizing the SDK provided by Wepin, you can easily and conveniently build wallet on-boarding into your app in a built-in format. This enables numerous project teams developing apps to save time and resources that would otherwise be spent on wallet developments, allowing them to focus on the core value of their app.
To achieve this goal, Wepin has been developed as a wallet with the following features.
Developers can integrate a wallet with their web/app in just 10 minutes by installing the SDK provided by Wepin. Through the widget built into the app, users don't need to go through the cumbersome process of leaving the app to copy their wallet address or check their assets or transaction history. By using Wepin, users can simply click the supported floating button within the app to access their wallet transactions history. Additionally, when the app requires the user's address information, it can easily retrieve the address from the activated wallet within the app, providing an integrated experience to the users. Additionally, by utilizing the widget designs provided by Wepin, you can easily offer a UI that seamlessly integrates with your app.
Refer to how to easily set up widget designs.
One of the biggest difficulties users face during the on-boarding process is the mnemonic phrase. A list of 12-24 words guarantees complete ownership but also brings concerns about loss and management difficulties to the users. Above all, the process of memorizing and verifying the correct words delays the time it takes for users to enter the app. This can implant a negative user experience such as difficulty and annoyance in users, posing a serious problem that could negatively affect the value of the app.
To solve this problem, Wepin supports creating wallets and managing private keys through the user-friendly email and social login methods. By guiding users through the sign-up and login process in a way they have already experienced, it is easier for them to create wallets and accounts, reducing the time it takes to transition to the core value within the app.
Check out the currently supported login providers.
The future is a multi-chain era. Already, numerous blockchain mainnets are in operation, and users do not stay on a single blockchain. In other words, users are traveling between blockchains, holding assets across various mainnets. Developers only need to worry about the environment of the mainnet on which they try to deploy their app, but users have to navigate through various apps and manage different wallets with each change of mainnet. This adds confusion for users.
As a result, there is a need for a multi-chain environment that can manage users' assets in an integrated manner, and a wallet capable of supporting this. It's more convenient for users to have one wallet that supports all the blockchain environments apps A and B are deployed on, rather than having an wallet A for app A and a wallet B for app B. Wepin supports this environment by supporting over 20 blockchains, allowing users to manage most of their assets from a single wallet.
Check out all the blockchains currently supported by Wepin.
One of the core values of Web3 is the ownership of assets. Assets not owned are not truly the user's. The private key information, which guarantees the user's ownership, should only be known by the user, and the user should be able to control their assets without entrusting their authority to others.
Wepin understands these requirements well and is designed in a non-custodial manner. Wepin only executes commands based on user requests and does not have access to the user's private key information. Only the user who created it can access the private key, and all private key communications are encrypted during transmission.
For more detailed architecture of Wepin, check the linke below.
