> For the complete documentation index, see [llms.txt](https://funarchy.gitbook.io/funarchy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://funarchy.gitbook.io/funarchy/pm-threat-modeling/test-result-dashboard/seer-test-result.md).

# Seer Test Result

| Configuration | Trading Mechanism | Oracle & Data | Governance | Operation |
| ------------- | ----------------- | ------------- | ---------- | --------- |
| ⚠️            | ✅                 | ✅             | ⚠️         | ✅         |

### Analysis stage

<details>

<summary>Configuration</summary>

❌  Ambiguous Resolution Criteria

✅  Manual Oracle Delay

✅  Extend market resolution time

</details>

<details>

<summary>Trading Mechanism</summary>

&#x20;**-**   Signature Replay Attacks

&#x20;**-**   Matching Engine Logic Errors

&#x20;**-**   State Inconsistency

✅ Slippage & Sandwich Attacks

✅ Permanent Loss

✅ Fee bypass

</details>

<details>

<summary>Oracle &#x26; Data</summary>

&#x20;**-**   Single Data Source Dependency

✅  Oracle Data Validation Logic Insufficiency

✅  Missing Oracle Authentication

&#x20;**-**   UI Latency Desynchronization

&#x20;**-**   UI–Oracle Price Mismatch

&#x20;**-**  Short-Horizon Settlement Price Manipulation

&#x20;**-**  Equality Boundary Settlement Precision Risk

</details>

<details>

<summary>Governance</summary>

✅  Whale Cartel Attack

❌  Dispute Mechanism Abuse

</details>

<details>

<summary>Operation</summary>

✅  Owner's Privilege too High

✅  DoS via Unrestricted Shared State Manipulation

✅  Calculation Logic Error

</details>

### Risk Summary&#x20;

#### Configuration

* The lack of a rulebook for the market UI can lead to market conclusions that are different from what the average user would want.

#### **Governance**

* In a dispute resolution system, with sufficient funds, an attacker can continue the dispute, preventing ordinary users from engaging in disputes, and achieve the attacker's desired outcome.

***

### Risk Analysis

#### **Configuration**

**Ambiguous Resolution Criteria**

<figure><img src="https://4210179539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DiVEbUgCTsp2iPassR9%2Fuploads%2FEuzFbTvMgjDmnDviQQNM%2Fimage.png?alt=media&amp;token=db1dca2b-0ea7-4b01-bc0f-07b8d0c3f26e" alt="" width="563"><figcaption></figcaption></figure>

* Currently, Seer does not have a clear rulebook for market outcomes.\
  \
  The vague settlement criteria of these prediction markets create structural problems that arise from the absence of standardized rules or objective indicators when creating a market.\
  \
  Thus, the attacker ends up distorting the judgment into a logical argument based on technical definitions rather than objective facts.

#### **Governance**

**Dispute Mechanism Abuse**

<figure><img src="https://4210179539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DiVEbUgCTsp2iPassR9%2Fuploads%2FVRVbnhUYVxnxUcwIfuOJ%2Fimage.png?alt=media&amp;token=b397f551-7d60-459e-ac13-3a4dbdadb0ff" alt="" width="563"><figcaption><p>&#x3C;Kleros docs></p></figcaption></figure>

* Currently, Seer uses Kleros as its governance in case of disputes.\
  \
  In systems like Kleros, where the required deposit increases exponentially with each round of dispute, the root cause of financial trolling lies in the economic asymmetry of the attack. Even with exponential defense mechanisms in place (e.g., doubling for the winner and tripling for the loser), the whales' ample funds neutralize these defenses, unilaterally passing on the burden of exploiting these defenses and tying up funds to ordinary users—they're often left with no choice but to suffer.\
  \
  Thus, the large size of the deposit makes it difficult to draw fair conclusions due to the presence of well-funded whale financial trolls.


---

# 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://funarchy.gitbook.io/funarchy/pm-threat-modeling/test-result-dashboard/seer-test-result.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.