For the complete documentation index, see llms.txt. This page is also available as Markdown.

Blacklisting

To protect LP, malicious arbitrage that puts Native liquidity at risk will be profiled, and the user/swapper address will be added to the blacklist.

To avoid producing additional errors during the /firm-quote stage, any quotes submitted with from_address or beneficiary_address being blacklisted will be subject to a 50bps added spread due to increased risk.

We recommend that all upstreams query and cache a copy of the latest blacklisted addresses and apply pre-processing and filtering.

/v1/blacklist returns only the latest 140,000 records. To validate addresses outside that window, use /v1/is-black-address or maintain a local cache.

/blacklist Endpoint

## Request
curl "https://v2.api.native.org/swap-api-v2/v1/blacklist?page_size=35000&page_index=1" \
     -H "apiKey: $NATIVE_KEY"

Param:

  • page_size: entries per page, min 1, max 35000

  • page_index: page index

Normal return:

{
  "black_list": [ // latest first
    {
      "id": "466221",
      "address": "0x000000000000000000000000000000000000dead", // address
      "chainId": 1,
      "createTime": 1775026096 // unix timestamp
    }
  ],
  "total_count": 140000 // capped at 140000 (latest records only)
}

Upstream must contact the Native team through the existing communication channel to request permission for this endpoint.

No permission return:

/is-black-address Endpoint

Check whether a single address is on the blacklist. Use this for addresses that may fall outside the latest 140,000 records returned by /blacklist.

Param:

  • address: the address to check

Normal return:

Blacklist status on /firm-quote

Pass optional show_blacklist_status=true on /v1/firm-quote to include is_black_address in the response. Omit the parameter or pass false to keep the default response (field omitted).

Return when show_blacklist_status=true:

Return when omitted or false (field not included):

Last updated