# Overview EcoRound is an **onchain no-loss prediction market** for competitive esports matches, built on Base and powered by Chainlink's Compute Runtime Environment (CRE). It combines three primitives — **prediction markets**, **DeFi yield**, and **decentralized oracles** — into a single protocol where users can express opinions on match outcomes without ever risking their principal. *** ## What EcoRound Does Users deposit USDC to predict the winner of an esports match. While the match is underway, all deposited capital is put to work in a Morpho yield vault on Base. When the match ends: * **Winners** receive their deposit back plus a proportional share of the yield earned * **Losers** receive their full deposit back — no loss The yield comes from DeFi, not from other players. This makes EcoRound a **positive-sum** protocol. *** ## Who Is It For? **Esports fans** who want to engage more deeply with matches they already watch — without gambling away their money. **DeFi users** who want to put idle USDC to work while expressing a view on real-world events. **Protocols and platforms** who want to integrate prediction market infrastructure without exposing users to capital loss. *** ## Built on Base Base is Ethereum's leading Layer 2, offering low fees, deep USDC liquidity, and native access to Morpho's yield infrastructure. EcoRound is built natively for the Base ecosystem and uses real Base Mainnet state — USDC and Morpho — in a Tenderly virtual fork for safe development and demonstration. --- # 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://eco-round.gitbook.io/eco-round-docs/introduction/overview.md?ask= ``` 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.