User wallet interactions
This guide is aimed at providing clarity on the minimum requirements when implementing user wallet connections and interactions.
Previously, applications using the Link SDK did not have to worry about this because the Link SDK provided an opinionated UI that implemented our best practices. Now, when using the Typescript SDK with the Wallet SDK, applications may need to implement their own design. Other than the must-haves outlined in this guide, the rest is up the application.
Interactions:
- Connect wallet
- Disconnect wallet
- List asset
- Buy asset
- L1 to L2 deposit
- L2 to L1 withdrawals
- Fiat onramp
- Crypto to fiat offramp
- Error states
- Transaction history
Connect wallet
Flow | Link UI / Immutable marketplace example | Requirements |
---|---|---|
Provider list |
| |
Email login | If an application chooses to provide the email wallet (provided by Magic) as an option, it must:
| |
MetaMask + GameStop | Not mandatory, but useful to include:
| |
Wallet connected | Not mandatory, but useful to include:
|
Disconnect wallet
Flow | Link UI / Immutable marketplace example | Requirements |
---|---|---|
Disconnect wallet |
|
List asset
Buy asset
L1 to L2 deposit
L2 to L1 withdrawals
Flow | Link UI / Immutable marketplace example | Requirements |
---|---|---|
Withdraw flow | Partner must
|
Fiat onramp
Fiat onramp is still under development and not available in the SDK yet.
Flow | Link UI / Immutable marketplace example | Requirements |
---|---|---|
Fiat onramp |
|
Crypto to fiat offramp
Crypto to fiat offramp is still under development and not available in the SDK yet.
Error states
Flow | Link UI / Immutable marketplace example | Requirements |
---|---|---|
Error states |
|
Transaction history
Transaction history is still under development and not available in the SDK yet.