Concepts
How an RFQ works
Every covr order is a short sealed-bid auction. A customer asks for a price. Desks bid. The best bid wins and signs a quote the customer can fill on chain.
The parties
| Party | What it does |
|---|---|
| Customer (writer) | Locks JitoSOL and sells a call at a strike and expiry. Signs and submits the fill transaction. |
| Desk (maker) | Buys the call. Pays the premium from its USDC vault. May exercise at expiry. |
| Gateway | covr's server. Broadcasts RFQs, runs the auction, checks every signature. |
| Program | covr's Solana program. Moves the money and enforces every rule again. |
| Keeper | Anyone. After the exercise window, anyone can return unexercised collateral to the customer. |
Timeline of one RFQ
Customer Gateway Desk Program
│ ask for quote │ │ │
├───────────────────►│ rfq (feed) │ │
│ ├───────────────────────►│ │
│ │◄───────────────────────┤ GET /api/rfqs/<id> │
│ │◄───────────────────────┤ bid_intent (signed) │
│ │ collect 3 s, rank │ │
│ ├───────────────────────►│ award (best price only) │
│ │◄───────────────────────┤ quote (signed, nonce) │
│◄───────────────────┤ executable quote │ │
├─────────────────────────────────────────────────────────────────────►│ fill_v3 (customer signs)
│ │ │ premium from desk vault, JitoSOL locked
│ │ no fill message: the desk watches its position account on chain| Time from the RFQ | What happens |
|---|---|
| 0 s | The RFQ appears on the feed. |
| 0 to 3 s | Bids are collected. Each desk sends at most one signed bid_intent. |
| 3 s | The highest price wins the award. |
| 3 to 6 s | The winner answers with a signed quote or an award_decline. |
| 6 s | Hard deadline. No quote means the customer gets "no quote". |
| up to 60 s later | A quote is valid for at most 60 s from when the gateway admits it. The customer reviews and signs within that time. |
Two signatures, two jobs
A desk signs twice per won order.
- Bid intent. A sealed bid: price and RFQ terms, signed with your quote key. It commits you to a price but cannot be filled.
- Quote. Only the winner signs this. It adds a nonce and a validity time and binds the customer's wallet. The program fills against this signature.
Both are EIP-712 typed data in a domain that belongs to that one market. A signature for one market never verifies on another. See Signing and nonces.
Answer every award
If you win, answer within the award window. Send either a quote or an award_decline.
- A decline, a disconnect or any failed quote passes the award to the next-best bid at once.
- A silent winner holds the award until the 6 s deadline. The customer then gets no quote.
"OK" is not a fill
When the gateway accepts your quote it replies "OK". That only means the customer can now see it. The customer may never sign. No fill message follows. A fill shows up only on chain, as your position account. See Fills and exercise.
Practice mode
Today covr's markets list only covr's own maker. For every other desk, the gateway checks each bid and then refuses it with:
Bid intent verified but not entered: this market does not list this maker yet| Practice mode proves | Practice mode does not test |
|---|---|
| Your token, connection and heartbeats | The 3 s bid deadline and the one-bid rule |
| Reading RFQs and market accounts | Awards, quotes and award declines |
| Your bid-intent signature, terms and asset | Your nonce journal |
| Fills, reconciliation and exercise |
Letting other desks win is planned engineering work at covr. It needs changes to the gateway's market listing and to covr's customer page, so it is not a setting covr can turn on for you.
Test the parts practice mode cannot reach yourself: replay awards against your own code, and rehearse exercise with the exercise guide. See also Gateway: practice mode.
Next
- Capital and settlement: what your vault pays, and when.
- Gateway messages: every field of every message.