> For the complete documentation index, see [llms.txt](https://docs.divaprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.divaprotocol.io/use-cases/directional-bets/downside-bet.md).
# Downside bet
Alice believes that the Bitcoin price will drop from its current level of $37’000. Shorting an asset the traditional way is pretty cumbersome as it involves four steps: 1) borrow BTC, 2) sell it for USD, 3) buy BTC back (at hopefully lower prices), and 4) give back BTC to the lender plus some interest. Alice wants a simple way to participate in the downside of BTC.
Alice could use the DIVA App to create short positions with one of the below example shapes.
### :gear: Pool configuration
The example configuration for the above three patterns
### 🤝Sell long position tokens
After the creation of the pool, Alex would sell the long position tokens and keep the short position tokens.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.divaprotocol.io/use-cases/directional-bets/downside-bet.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.