> For the complete documentation index, see [llms.txt](https://seer-3.gitbook.io/seer-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seer-3.gitbook.io/seer-documentation/developers/interact-with-seer/resolve-a-market.md).

# Resolve a market

To resolve a market, the user calls the <mark style="color:red;">`resolve`</mark> function on the <mark style="color:red;">`Market`</mark> contract.

***

### Prerequisites

Before resolution can succeed:

* The Reality question(s) must be **answerable**: `block.timestamp >= openingTime` (opening time is set at market creation).
* The question(s) must be **answered** on Reality.eth (someone called `submitAnswer` with sufficient bond).
* The question(s) must be **finalized** (e.g. timeout passed, no reopen), so that `realitio.resultForOnceSettled(questionId)` returns a settled result.

If these are not met, the resolution transaction will revert.

***

### After resolution: redeeming

Once the market is resolved, users can redeem winning position tokens for the underlying collateral via the <mark style="color:red;">`Router`</mark> contract (merge and redeem flow).

***

### Viem examples

We use the Viem setup: `getPublicClient(chain)` and `getWalletClient(chain, process.env.PRIVATE_KEY)`.

#### Shared: ABI and address

```typescript
import { getPublicClient, getWalletClient, MARKET_ABI } from "./viem-setup";
import { gnosis } from "viem/chains"; // or mainnet, base, etc.

const chain = gnosis;
const publicClient = getPublicClient(chain);
const walletClient = getWalletClient(chain, process.env.PRIVATE_KEY! as `0x${string}`);
const account = walletClient.account!;

const marketAddress = "0x..."; // Market contract address
```

#### Resolve the market

Call `resolve()` on the Market contract:

```typescript
const hash = await walletClient.writeContract({
  address: marketAddress,
  abi: MARKET_ABI,
  functionName: "resolve",
  args: [],
});

const receipt = await publicClient.waitForTransactionReceipt({ hash });
```

#### Simulate before sending

To avoid reverts (e.g. question not yet settled), simulate first:

```typescript
const { request } = await publicClient.simulateContract({
  account: account.address,
  address: marketAddress,
  abi: MARKET_ABI,
  functionName: "resolve",
  args: [],
});

const hash = await walletClient.writeContract(request);
const receipt = await publicClient.waitForTransactionReceipt({ hash });
```


---

# 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://seer-3.gitbook.io/seer-documentation/developers/interact-with-seer/resolve-a-market.md?ask=<question>&goal=<endgoal>
```

`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.