πŸ“’
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

Multi-signature Wallet

PreviousHardware WalletNextProject Owned DEX

Last updated 2 years ago

Multi-signature wallets are contract accounts that require multiple parties to confirm a transaction before it can be executed. These parties, each represented by a unique Ethereum account address, are defined as multi-signature wallet owners in the smart contract. Only when a predefined number of these owners confirm a transaction, will the transaction be executed. Hence, the single point of failure associated with private key-controlled accounts is removed; losing or compromising a private key will no longer automatically result in a loss of all funds controlled by the account. A popular multi-signature wallet is .

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

Using a multi-signature wallet is recommended for the Treasury because multiple confirmations by different owners are required for a transaction; this lowers the risk of loss of assets due compromising of a single private key.

πŸŽ’
Gnosis Safe
More than 1 owners need to sign before a transaction can go through.