Concepts
Cash-secured puts
Customers can sell cash-secured puts on covr since 7 November 2026. This page says what that means for a desk today, and how a put differs from a call, so you can judge the work before desks can quote them.
Desks cannot quote puts yet. covr's own maker quotes every put. Three things stand in the way, all on covr's side:
- Every put market lists only covr's own maker, so another desk's put bid could only ever be a practice bid.
- covr's public desk endpoint does not route put feeds. It serves
/makerand call feeds (/rfqs/<alias>) only. @covrfun/maker-sdk0.1.1 has no put builders, decoders or signers.
When each will change is to confirm with covr.
What a put is on covr
The customer (the writer) locks cash and is paid a premium now. During the exercise window just after expiry, the maker may exercise: it sells the asset to the writer at the strike. The writer receives the asset and the maker receives the locked cash. If the maker does not exercise, anyone can release the position after the window and the writer gets the cash back.
| Term | Meaning | Unit |
|---|---|---|
| Q | Asset amount of the position | asset atoms |
| Strike | Price per whole asset token | payment-token units × 10^8 |
| T | The writer's lock: Q × strike | payment atoms, must be exact |
| Price | Premium per whole asset token | payment-token units × 10^18 |
| G | Gross premium: Q × price | payment atoms, must be exact |
| Fee | floor(G × feeBps / 10000), to the market's fee owner | payment atoms |
The writer receives G − fee at fill. If T or G is not a whole number of payment atoms, the program refuses the fill.
How a put differs from a call, for a desk
| Call | Put | |
|---|---|---|
| Customer locks | JitoSOL | A payment token (a plain 6-decimal SPL Token, such as USDC or USDT) |
| You pay at fill | Premium, from your USDC vault | Premium, from your vault for that payment token |
| You deliver at exercise | The strike, in USDC | Q of the asset, from your put asset vault or by a flash swap |
| You receive at exercise | The JitoSOL | The writer's locked cash, T |
| Your on-chain switch | Mint policy (V1) | Put policy (V2), per (maker, asset, payment token), born disabled |
| RFQ feed | /rfqs/<asset alias> | /rfqs/put/<asset alias>/<payment alias> |
| RFQ request | isPut: false, usd = USDC alias | isPut: true, usd = collateralAsset = the payment token's alias |
| Signing domain | The call market's domain | The put market's own domain (scope market-v3:ordinary-put): no call signature verifies on a put market, or the reverse |
| Nonces | One nonce history per maker, shared by calls and puts |
Capital a put needs
- Premiums in a payment vault for each payment token you quote.
- The asset or a route. Your put policy's backing says how you deliver at exercise:
1inventory (the asset sits in your put asset vault),2flash (you swap the writer's cash for the asset inside the exercise transaction, under a flash put policy), or3either. - Your limits. A put exposure limit per asset, shared by every payment token, and the limits in each put policy.
The program checks put_backing is 1, 2 or 3, and that you can deliver when you exercise. It does not reserve your asset per position.
Where to read more
- The put instructions, accounts and errors, contract by contract: Instructions: cash-secured puts.
- How customers see puts: Cash-secured puts.
- Desk-side put program reference: Program instructions.