> For the complete documentation index, see [llms.txt](https://docs.kyte.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyte.sh/guides/sell-put.md).

# Sell a cash-secured put

Lock ETH, name your price for a token and earn the premium.

Page: [kyte.sh/sell](https://kyte.sh/sell) → **Cash-secured put**

Puts must be enabled for the token (`putsEnabled`). The form is the same as for [calls](/guides/sell-call.md). The difference is what you lock: **the total strike, in ETH**.

{% stepper %}
{% step %}

### Fill in the offer

Choose the token, amount, strike per token, expiry, fill window and premium, exactly as for a call.
{% endstep %}

{% step %}

### Sign one transaction

```solidity
Router.createPutOfferWithETH(token, amount, strike, premium, expiry, offerDeadline)
```

Send it with `value = strike`. The Router wraps your ETH to WETH and escrows it in the PutMarket on your behalf.
{% endstep %}
{% endstepper %}

## Outcomes

| What happens           | You receive                                                              |
| ---------------------- | ------------------------------------------------------------------------ |
| Filled                 | Premium − 3% fee, in WETH                                                |
| Exercised              | `amount` tokens from the holder. The holder receives your strike − 0.1%. |
| Expires unexercised    | Your WETH comes back                                                     |
| Not filled / cancelled | Your WETH comes back                                                     |

{% hint style="success" %}
**Worked example.** You lock 2 ETH as the strike for 1,000 tokens (0.002 ETH each), premium 0.05 ETH.

* A buyer fills: you get **0.0485 WETH**.
* The holder exercises: they deliver 1,000 tokens to you and receive **1.998 WETH**; 0.002 goes to the FeeVault.
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kyte.sh/guides/sell-put.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.