# 🍸Dive Bar

{% hint style="info" %}
The Dive Bar uses the protocol's [smart contract architecture](/technical-reference/smart-contract-architecture.md), with custom oracle contracts retrieving off-chain data feeds. These markets are introduced as pilots, and are created for those brave enough for a dive. With sufficient community interest,  and the support of third-party oracle networks, they can be integrated as staples of options offerings. Interested community members can [request](mailto:contact@divergence-protocol.com) new prediction markets to be added to the Dive Bar.  
{% endhint %}

<figure><img src="/files/QJ8dCbdt7uLintadMqjH" alt=""><figcaption></figcaption></figure>

The prediction markets primarily adhere to the [options specs](/overview/protocol-basics/options-specs.md), with a few distinctions:

* The markets trade on the outcomes of unknown future events. They can also be configured to trade on prices of assets, including those that are not yet publicly offered.
* Each market uses one ERC20 collateral token to long and short <mark style="color:green;">YES</mark> or <mark style="color:red;">NO</mark> event outcomes
* <img src="/files/KICz5vyFPAdeSYRkSpjw" alt="" data-size="line">Spear tokens settles profitably when the event outcome is  '<mark style="color:green;">YES</mark>'.
* <img src="/files/EeXCAlrfMMmuGv4ObKLb" alt="" data-size="line">Shield tokens settles profitably when the event outcome is '<mark style="color:red;">NO</mark>'.
* The interface is designed with some similarity to orderbooks, with each liquidity position (aka sell orders) set to a minimum interval of 30 ticks.
* As is the case with [shorting options](/user-guide/short-options.md),  liquidity positions must be finalized under "Open Orders", before the shorts in <mark style="color:green;">YES</mark> or <mark style="color:red;">NO</mark>  can be [closed](/user-guide/short-options/close-shorts.md).  To close shorts, simply click "Close", approve and confirm sending the pool the prompted amount of <mark style="color:green;">YES</mark> or <mark style="color:red;">NO</mark> from holdings, and receive the reserved collateral. Note that the open shorts can only be closed in full. &#x20;

<figure><img src="/files/PjaiwYLa96TEWZE5AwMA" alt=""><figcaption><p>After finalizing a liquidity position under "Open Orders", go to "Positions" to close it. </p></figcaption></figure>

* Markets expire at custom timestamps specified as a pool's `BattleKey`. An hour after settlement,  winning long <mark style="color:green;">YES</mark> or <mark style="color:red;">NO</mark> positions can exercise for profit.  Liquidity providers who have opened shorts in losing  <mark style="color:green;">YES</mark> or <mark style="color:red;">NO</mark> positions can reclaim reserved collateral, keeping the premiums as profit.
* To [close longs](/user-guide/long-options/close-longs.md) in <mark style="color:green;">YES</mark> or <mark style="color:red;">NO</mark>,  click "Earn", select a limit price to sell your holdings and confirm adding liquidity. Don't forget to finalize these in "Open Orders" to withdraw your sale proceeds! &#x20;
* Alternative [fee](/overview/protocol-basics/fees.md) structures for the markets can be enabled.
* Last but not least, **these markets enable everyone to voice their opinions**. Click on the "Yes" or "No" button and share your views on X 🤿\_🤿

<figure><img src="/files/AzjNAHSowfJRuENKsN7a" alt=""><figcaption><p>You've got it. Just say it.</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.divergence-protocol.com/user-guide/dive-bar.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.