> 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/usdwherls-protocol.md). # $WHERLS Protocol The $WHER Protocol is the underlying infrastructure that powers the Wherls ecosystem, built on Binance Smart Chain (BEP-20) and designed to support smart contracts, decentralized finance features, NFT operations, and governance logic. It acts as the connective tissue between users, validators, smart contracts, and the $WHERLS token. 🧩 **Core Protocol Components** **1. Smart Contract Layer** Smart contracts manage all core platform functions: * NFT creation, buying/selling, and royalties * Token minting, burning, staking, and vesting * Transaction validations * Affiliate/referral tracking Contracts are audited, modular, and upgradeable — ensuring both security and adaptability. **2. Super Masternode Validation Layer** The protocol supports a permissionless masternode system, where nodes validate blocks and earn rewards based on uptime and performance. Super Masternodes enhance scalability by: * Reducing bottlenecks * Managing parallel validations * Participating in governance (future DAO) **3. Liquidity & Staking Pools** The $WHER Protocol includes automated staking and liquidity management: * Users lock tokens for fixed periods and receive dynamic APY * Liquidity providers receive LP tokens and trading rewards * Smart contracts manage auto-compounding and reward distribution **4. Governance Module (Planned)** The protocol is designed to support decentralized governance: * Community members vote on proposals * Voting power is proportional to token holdings * Future support for DAO frameworks like Snapshot or Tally 🔐 **Security Framework** All protocol operations are protected by: * Multi-signature treasury wallets * On-chain risk monitors * Immutable transaction records * Third-party smart contract audits By combining automation, decentralization, and security, the $WHER Protocol forms a future-ready framework that drives both the technology and economy of the Wherls platform. --- # 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/usdwherls-protocol.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.