> For the complete documentation index, see [llms.txt](https://wherls.gitbook.io/wherls/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wherls.gitbook.io/wherls/the-challenge.md). # The Challenge While the blockchain industry has seen tremendous growth in NFTs, DeFi, and decentralized marketplaces, it continues to face major limitations that prevent widespread adoption. Wherls was conceived as a solution to the following systemic challenges: ⚠️ **1. Fragmented Ecosystem** Most platforms specialize in one feature — NFT trading, staking, or payments — forcing users to juggle multiple apps and wallets, complicating the user journey. ⚠️ **2. High Fees and Poor Scalability** Ethereum-based platforms suffer from gas spikes and slow confirmation times. These issues hinder microtransactions, discourage experimentation, and alienate budget-conscious users. ⚠️ **3. Technical Barriers for Newcomers** From complicated wallet setups to poor UI/UX, many Web3 platforms require a steep learning curve. This limits accessibility and discourages mainstream adoption. ⚠️ **4. Centralized Control in Decentralized Platforms** Despite claims of decentralization, many projects are still governed by small, centralized teams with opaque decision-making and limited user governance. ⚠️ **5. Lack of Real Utility for Tokens** Many tokens offer little beyond speculation, with weak ecosystems and no long-term incentives for holding or using the token. These challenges have created a market gap: users want an all-in-one, low-cost, decentralized platform that is usable, rewarding, and transparent. Wherls is built to fill that gap — and go further. --- # 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://wherls.gitbook.io/wherls/the-challenge.md?ask=&goal= ``` `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.