# Why Betcha ## What's Wrong? The current prediction market landscape suffers from limitations in UX and incentive structure. Users must lock up their funds for long periods, earn no yield on the value which they do lock up, and are not adequately rewarded for their activity and success on the platform. ## Our Solution Betcha leverages Edgeless' native yield bearing asset structure, fee-less nature, and powerful community to be able to solve these issues. * **Yields** Assets locked in markets like Presidential Elections (which can take months to resolve) accrue rewards. Betcha emits these rewards back to users, providing competitive yields in addition to event exposure. Users can earn % APR and have exposure to the upside of these native yields while also locking in predictions! * **Fees** Other leading prediction markets charge usage fees on all actions, lowering the expected value of user interactions and harming the overall user experience. Edgeless provides users a zero application fee experience, and enables Betcha to drip gas refunds from user actions directly back to users through our rewards program! * **Rewards** Betcha's rewards program (learn more [here](https://betcha.gitbook.io/betcha-markets/interstellar-insights-initiative-iii)) is designed to reward the most engaged! We seek to reward those who use prediction markets with airdrops, free predictions, and redeemable unlocks based upon their points earned on our platform. --- # 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://betcha.gitbook.io/betcha-markets/why-betcha.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.