> 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/configuration.md).

# Configuration

The integration examples in this folder use [viem](https://viem.sh) with a **public client** (read-only) and a **wallet client** (signed transactions). Create both once and reuse them across Create a market, Resolve a market, Split, merge and redeem, Conditional market, and Futarchy markets.

**Note:** The viem configuration below is provided as an example. If your project already has `publicClient` and `walletClient` (e.g. from Wagmi, RainbowKit or another library), you can use them directly; the examples in this documentation only need clients compatible with viem’s interface for `readContract`, `simulateContract`, `writeContract`, and `waitForTransactionReceipt`.

***

### Dependencies

```bash
npm i viem
```

***

### Client helpers

Create two helpers that take a **chain** (from `viem/chains`) so the same code works on any network. The wallet client needs a **private key** (e.g. from `process.env.PRIVATE_KEY`).

```typescript
import { createPublicClient, createWalletClient, http } from "viem";
import type { Chain } from "viem";
import { privateKeyToAccount } from "viem/accounts";

export function getPublicClient(chain: Chain) {
  return createPublicClient({
    chain,
    transport: http(),
  });
}

export function getWalletClient(chain: Chain, privateKey: `0x${string}`) {
  const account = privateKeyToAccount(privateKey);
  return createWalletClient({
    chain,
    transport: http(),
    account,
  });
}

/** ERC20 `approve(spender, amount)` ABI. Use for collateral and outcome token approvals (split, merge, redeem, swaps). */
export const ERC20_APPROVE_ABI = [
  {
    inputs: [
      { name: "spender", type: "address" },
      { name: "amount", type: "uint256" },
    ],
    name: "approve",
    outputs: [{ type: "bool" }],
    stateMutability: "nonpayable",
    type: "function",
  },
] as const;

/** Market contract ABI: resolve, wrappedOutcome(index), parentMarket, parentOutcome, numOutcomes. Use for resolve and for reading outcome token addresses. numOutcomes() returns the count without INVALID_RESULT; use numOutcomes() + 1 if you need to include it. */
export const MARKET_ABI = [
  {
    inputs: [],
    name: "resolve",
    outputs: [],
    stateMutability: "nonpayable",
    type: "function",
  },
  {
    inputs: [{ name: "index", type: "uint256" }],
    name: "wrappedOutcome",
    outputs: [
      { name: "wrapped1155", type: "address" },
      { name: "data", type: "bytes" },
    ],
    stateMutability: "view",
    type: "function",
  },
  {
    inputs: [],
    name: "parentMarket",
    outputs: [{ type: "address" }],
    stateMutability: "view",
    type: "function",
  },
  {
    inputs: [],
    name: "parentOutcome",
    outputs: [{ type: "uint256" }],
    stateMutability: "view",
    type: "function",
  },
  {
    inputs: [],
    name: "numOutcomes",
    outputs: [{ type: "uint256" }],
    stateMutability: "view",
    type: "function",
  },
] as const;
```

**Usage (any chain):**

```typescript
import { gnosis } from "viem/chains"; // or mainnet, base, optimism, etc.

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

* **publicClient**: for `readContract`, `simulateContract`, `waitForTransactionReceipt`, etc.
* **walletClient**: for `writeContract` (sending transactions).
* **account**: use `account.address` when calling `simulateContract` with an explicit account.

***

### Deployed contracts by chain

Contract addresses per chain ID. Use the entry for your chain when calling the contracts (e.g. `SEER_CONTRACTS[chain.id]`).

| Chain ID | Chain            |
| -------- | ---------------- |
| 1        | Ethereum Mainnet |
| 10       | Optimism         |
| 100      | Gnosis           |
| 8453     | Base             |

Export the `SEER_CONTRACTS` object from your setup module so the integration docs can use it. Get addresses for the current chain with `SEER_CONTRACTS[chain.id]`:

```typescript
export const SEER_CONTRACTS = {
  100: {
    ConditionalRouter: "0x774284d5cDFeC3A0a0eBc7283aD4d5b33013c29c",
    FutarchyFactory: "0xe789e4A240d153AC55e32106821e785E71f6b792",
    FutarchyProposal: "0xec4fb999Db0e8cA28011D85EAD177810055b484c",
    FutarchyRealityProxy: "0x03E1fCfE3F1edc5833001588fb6377cB50A61cfc",
    FutarchyRouter: "0xE2996f6BC88ba0f2Ad3a6E2A71ac55884ec9F74E",
    GnosisRouter: "0xeC9048b59b3467415b1a38F63416407eA0c70fB8",
    Market: "0x8F76bC35F8C72E5e2Ec55ebED785da5efaa9636a",
    MarketFactory: "0x83183DA839Ce8228E31Ae41222EaD9EDBb5cDcf1",
    MarketView: "0x95493F3e3F151eD9ee9338a4Fc1f49c00890F59C",
    RealityProxy: "0xc260ADfAC11f97c001dC143d2a4F45b98e0f2D6C",
    Wrapped1155Factory: "0xD194319D1804C1051DD21Ba1Dc931cA72410B79f",
  },
  1: {
    ConditionalRouter: "0x1BA2dB142a69B2D0b0EDbe666A9Bd457E344D9b5",
    MainnetRouter: "0x886Ef0A78faBbAE942F1dA1791A8ed02a5aF8BC6",
    Market: "0x8bdC504dC3A05310059c1c67E0A2667309D27B93",
    MarketFactory: "0x1F728c2fD6a3008935c1446a965a313E657b7904",
    MarketView: "0xB2aB74afe47e6f9D8c392FA15b139Ac02684771a",
    Realitio_v2_1_ArbitratorWithAppeals: "0x2018038203aEE8e7a29dABd73771b0355D4F85ad",
    RealityProxy: "0xC72f738e331b6B7A5d77661277074BB60Ca0Ca9E",
    Wrapped1155Factory: "0xD194319D1804C1051DD21Ba1Dc931cA72410B79f",
  },
  10: {
    ConditionalRouter: "0x3124e97ebF4c9592A17d40E54623953Ff3c77a73",
    Market: "0xAb797C4C6022A401c31543E316D3cd04c67a87fC",
    MarketFactory: "0x886Ef0A78faBbAE942F1dA1791A8ed02a5aF8BC6",
    MarketView: "0x44921b4c7510Fb306d8E58cF3894fA2bc8a79F00",
    RealityProxy: "0xfE8bF5140F00de6F75BAFa3Ca0f4ebf2084A46B2",
    Router: "0x179d8F8c811B8C759c33809dbc6c5ceDc62D05DD",
    Wrapped1155Factory: "0xd194319d1804c1051dd21ba1dc931ca72410b79f",
  },
  8453: {
    ConditionalRouter: "0xF5ccbf74121edBa492725F325D55356D517723B9",
    Market: "0xC72f738e331b6B7A5d77661277074BB60Ca0Ca9E",
    MarketFactory: "0x886Ef0A78faBbAE942F1dA1791A8ed02a5aF8BC6",
    MarketView: "0x179d8F8c811B8C759c33809dbc6c5ceDc62D05DD",
    RealityProxy: "0xfE8bF5140F00de6F75BAFa3Ca0f4ebf2084A46B2",
    Router: "0x3124e97ebF4c9592A17d40E54623953Ff3c77a73",
    Wrapped1155Factory: "0xd194319d1804c1051dd21ba1dc931ca72410b79f",
  },
} as const;

// In your script: const addresses = SEER_CONTRACTS[chain.id];
// addresses.Market, addresses.MarketFactory, addresses.MarketView, ...
```

***

### Using in the integration docs

In the rest of the integration docs we obtain clients with `getPublicClient(chain)` and `getWalletClient(chain, process.env.PRIVATE_KEY!)`, use `SEER_CONTRACTS[chain.id]` for addresses, and import `ERC20_APPROVE_ABI` and `MARKET_ABI` from the same setup module (approve calls and market reads such as `wrappedOutcome`, `resolve`). Choose any chain from `viem/chains` (e.g. `gnosis`, `mainnet`, `base`); the examples are the same for all networks.


---

# 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/configuration.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.