HTTP request parameters
Solvers send requests for HOT Quotes to the Valantis HOT API. A Solver’s request includes information about the current price they are getting at alternate venues, along with volume, and estimates about gas costs (optional).
The request parameters are described as follows:
authorized_recipient - the address to send tokenOut to.
authorized_sender - the authorized executor of the Signed Quote to be returned
chain_id - network chain ID
token_in - address of the input token
token_out - address of the output token
expected_gas_price - (Optional) the solver's gas price estimate in gwei. Note that it can also be in decimals, for example, "0.01" gwei.
expected_gas_units - (Optional) the solver's estimate of the amount of gas consumed by the venue they are replacing HOT swap with.
amount_in - input token amount being requested
amount_out_requested - minimum output token expected to receive. Note that the price that the solver is requesting for, is calculated as amount_in/amount_out_requested or amount_out_requested/amount_in depending upon the direction of the swap. Exception: If 0 is passed, the HTTP request will still work and the response will return the default price that the Liquidity Manager can offer (similar to RFQ APIs).
request_expiry - Unix timestamp in seconds after which the HTTPS request times out and the request is considered expired.
quote_expiry - Unix timestamp in seconds after which the signed HOT quote expires and is rejected by the pool. Note: quote_expiry gets capped at a maximum value, in order to ensure that excessively delayed HOT AMM price updates are not applied.
Liquidity Managers analyze incoming requests and construct Signed Quotes which match or beat the price a Solver currently has. The Liquidity Manager attaches an AMM state update to the requests they choose to fulfil.
Last updated
Was this helpful?