Reasoning for Request structure

In general, this is NOT a traditional (Request-For-Quote) RFQ where the Solver specifies a volume and the Market Maker quotes a price. There are two main differences from common "private liquidity" RFQ APIs:

1. Solvers are encouraged to share the price they receive from a current source of liquidity they have, and Liquidity managers will attempt to beat this price.

   • This gives better guarantees to the Liquidity Manager that distributed Quotes will be executed, while also providing insight into other sources of available liquidity and real-time price discovery.

   • This allows solvers to easily replace specific parts of a computed solution without needing to re-recompute their solution. This is because the HOT Quote will be directly replacing a specific amount of volume at an improved price net of gas.

2. Solver requests have specified timeouts.

   • This allows solvers to utilize this API as a source of "Last Look Liquidity", where they already have a solution they wish to execute and have limited time to look for an improvement.

This system can be expanded to replace liquidity from a Solver's pre-computed liquidity cache, initially through the API. This enables Solvers to receive quotes before receiving order flow to execute. Rules and methodology for signing Quotes are at the discretion of Liquidity Managers.

Note: If amount_out_requested=0, then the Solver is not sharing any information about competing prices, and the Liquidity Manager returns a default price as it would in other RFQ APIs (though potentially less competitive).