> For the complete documentation index, see [llms.txt](https://midashand-1.gitbook.io/midaspredict/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://midashand-1.gitbook.io/midaspredict/developers/technical-overview.md).

# Technical Overview

MidasPredict is deployed on LitVM with smart contracts written in Solidity (EVM-compatible).

## Architecture

* **Execution:** Arbitrum Nitro stack (EVM-compatible, high throughput)
* **ZK proofs:** Succinct zkVM for ZK-grade economic finality
* **Sequencing:** Espresso decentralized sequencer (sub-100ms pre-confirmations)
* **Bridging:** BitcoinOS / Charms (trustless LTC bridge)
* **Settlement:** Litecoin L1 (phased; initially Ethereum)
* **Oracle layer:** Multi-source (Chainlink, Pyth, or alternatives available on LitVM)

## Fee Routing Pipeline

On every trade, the 1% protocol fee is split on-chain 

`protocolFee = V × 0.01` : 

* `toEcosystemFund = V × 0.005`
* `toTreasury = V × 0.0025`
* `toPointsPool = V × 0.00125` (accumulated per epoch)
* `toReferralPool = V × 0.00125` (distributed per trade to uplines)

## Oracle and Data Layer

Automated resolution uses multi-source oracle aggregation with median/threshold reconciliation. Price-based Daily Markets aggregate from at least two independent oracle networks. Non-price events use API-based resolution with cryptographic attestation, falling back to dispute-based resolution.


---

# 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://midashand-1.gitbook.io/midaspredict/developers/technical-overview.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.