πŸ“’
Native Docs
  • 🦎About Native
    • πŸ—ΊοΈRoadmap
    • πŸ“žContact Us
    • πŸ”Security Audit
    • πŸ–ΌοΈBrand Assets
  • πŸŽ‰Campaigns
    • πŸ–ΌοΈOfficial NFTs
  • INTRODUCTION
    • πŸ”€Flexible Market Making
      • Pricing Models
        • On-chain Pricing
          • Constant Sum
          • Uniswap V2
        • Off-chain Pricing
          • Fixed Price
          • RFQ - Private Market Maker
    • πŸŽ’Self Custody
      • Externally Owned Account (EOA)
      • Hardware Wallet
      • Multi-signature Wallet
    • πŸ’ΉProject Owned DEX
  • GETTING STARTED
    • πŸš€Product Overview
    • πŸŽ“Tutorial
      • Accessing Native Portal
      • Creating A Private Pool
      • Adding Allowance
      • Creating A Public LP Pool
      • Adding LP Rewards
      • Getting Started with the Swap Widget
      • Changing Swap Widget Settings
    • πŸ™‹β€β™‚οΈFAQ
  • DEVLOPERS
    • 🧩Native V1
    • πŸ“±Widget
Powered by GitBook
On this page
  1. INTRODUCTION
  2. Self Custody

Hardware Wallet

Hardware wallets keep a crypto user’s private keys offline, meaning they are not connected to the internet, except when a user must briefly connect them to a computer to complete a transaction.

Hardware wallets are offline, so they are considered one of the safest ways to safeguard private keys. However, a hardware wallet doesn’t replace the usual crypto safety practices. If a user is careless with their keys or seed phrase, it won’t matter what kind of wallet they use.

Users can use a hardware wallet as the Treasury of the pool created with Native. No private keys are shared with Native. The only connection between the hardware wallet and the Native pool contracts is the allowance given by the user.

Common hardware wallets

  1. Trezor

  2. Ledger

  3. Safepal

Use a different hardware wallet from your main wallet where you store all your assets for the Treasury of your Native pool for better security

PreviousExternally Owned Account (EOA)NextMulti-signature Wallet

Last updated 2 years ago

πŸŽ’