⚙️
Native Developers
  • Native V1
    • Overview
    • Operations
      • Single-Hop Transaction: Off-chain Pricing
      • Single-Hop Transaction: On-chain Pricing
      • Multi-Hop Transaction
      • L1 Token Swap
      • Creating a Pool
      • Updating a Pool
    • System Components
      • GUI
      • Native Backend
      • Pricer
      • Registry
      • Signer
      • Pool
      • Pool Factory
      • Treasury
      • Router
    • Smart Contracts
      • Core
        • Registry
        • NativePool
        • NativePoolFactory
        • NativeRouter
      • Liquidity Pools
    • Contract Address
    • API References
      • GET /v1/indicative-quote
      • GET /v1/orderbook
      • GET v1/firm-quote
      • GET v1/firm-quote/calldata
    • Guide
      • Get quote for ETH to USDT
      • Execute ETH to USDT swap on Native
    • Routing
  • Market Maker Integration
    • WebSocket Connection
Powered by GitBook
On this page
  1. Native V1
  2. System Components

Treasury

The Treasury is the source of liquidity. It is where the assets for Pool are stored. This can be any EVM compatible wallet: hardware wallets, EOA wallets or smart contract wallets. The only linkage between the Treasury and the Pool is the allowance given by the wallet owner to the Pool for the specific tokens.

The Treasury is assigned by user setting "Liquidity address" in the Pool creation flow. Only the Treasury can give allowance to the Pool.

NOTE: The Treasury (Liquidity address) cannot be changed after pool creation

If you are want to supply L1 tokens for your swap, please fill the Treasury with the wrapped L1 tokens instead of the L1 tokens. The Router will handle the wrapping and unwrapping of the wrapped tokens.

PreviousPool FactoryNextRouter

Last updated 2 years ago