Native Documentation
  • introduction
    • What is Native
    • About Native V2
    • Benefits for Key Players
  • SOLUTION
    • Native Credit Pool
    • Native Swap Engine
  • CONCEPTS
    • Orderbook
    • Firm Quote Orders
    • Auto Sign Orders
    • Swap Fees
    • Slippage
    • Base and Listed Assets
    • Single-Sided Liquidity Pools
    • Total Available Liquidity
    • Liquidity Pairing
    • Liquidity Bootstrapping
    • Health Ratio
    • Earning Fees and Incentives
    • Credit-Based Swap
      • Collateral Factor
      • PMM Credit
      • Settlement and Liquidation
    • Market-Responsive Pricing
    • Risks
  • USER GUIDE
    • Add Liquidity
    • Pair Liquidity
    • Claim Rewards
    • Swap with Native
  • Build with Native
    • Swap Aggregators
      • Guide
      • FirmQuote Swap APIs
        • GET Orderbook
        • GET Indicative quote
        • GET Firm quote
    • Asset Issuers
      • For Pegged Assets
      • For General Assets
  • Resources
    • Addresses
    • Audits
    • Github
    • System Status
    • Business Source License
    • Media Kit
Powered by GitBook
On this page
  • Pre-requisite
  • Firm-Quote
  • Signing the order
  • Orderbook
  1. Build with Native
  2. Private Market Makers[june]
  3. Guide

Using Native Credit Pool

Pre-requisite

This section assumes you have already integrated with Native as a market maker.

Firm-Quote

When Native requests a Firm-Quote from the market maker, it will pass the availableBorrowBalance parameter, indicating the amount of available tokens you can borrow to fulfil the quote.

If you wish to use Native Credit Pool to fulfil the order, respond with isBorrowing: true in your Firm-Quote response.

Signing the order

If you are using Native Credit Pool to fulfil the order, the buyer and verifyingContract fields when signing the order should be the Native Credit Pool address.

If you are using your own inventory, use the address of your own RfqPool.

Orderbook

Market makers can publish a different orderbook for using Native Credit Pool versus their own inventory. This can be done by using different endpoints or the same endpoint with a different field in the response to distinguish between the two inventory sources.

Last updated 9 months ago