Migration to Lit and AA
  • Overview
  • Getting Started
    • Installation
    • Deployment
    • FAQ
  • Reference
    • Onboarding and Wallet SDK
      • Concepts
      • Wagmi config
      • @tria-sdk/core
        • Auth Controller [INTERNAL]
        • User Controller
      • @tria-sdk/web [INTERNAL]
        • Lit Controller
        • Keyring Controller
        • Wallet Controller
        • Gas Abstraction Wallet Controller ⛽️
        • Fee Controller
        • Solana Wallet
        • WalletConnect Controller
        • 🚂Execution Engine Controller
      • @tria-sdk/connect
        • TriaProvider
        • Actions
        • Hooks
          • Internal hooks
        • Constants [Internal]
      • @tria-sdk/authenticate
        • Application
      • @tria-sdk/authenticate-web
    • Supported Networks
    • How to create Debridge Solana Calldata
    • New concepts [Internal]
    • Gas Abstraction Integrations [Internal]
  • EIP1193 - Provider (WIP)
Powered by GitBook
On this page
  1. Reference
  2. Onboarding and Wallet SDK

Concepts

PreviousOnboarding and Wallet SDKNextWagmi config

Last updated 1 year ago

This SDK provides the functionality of handling all the API request, Transaction signing on the client side by storing the vault on the client side in encrypted form.

After successful login you just have to create the Keyring Object and using this object you can perform all the operation related to wallet. For more check .

Vault structure

This is the vault structure we are using to store users keys. This is stored at client side in encrypted form. For mobile we are using @react-native-async-storage/async-storage

{
    mnemonic: "",
    triaName: {
        ethereum: {
            publicKey: "",
            privateKey: "",
        },
        solana: {
            publicKey: "",
            privateKey: "",
        },
        ...
    },
    subTriaName: {
        solana: {
            publicKey: "",
            privateKey: "",
        },
    }
}
Keyring Controller