> 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/transaction-cost.md). # Transaction Cost One of the key advantages of the Wherls ecosystem is its commitment to affordability and accessibility — achieved in part through its use of the Binance Smart Chain (BEP-20), which enables **low-cost, high-speed transactions** across the platform. Whether users are buying NFTs, staking tokens, or transferring assets, Wherls ensures that costs are kept minimal without compromising on speed or security. ⚙️ **Transaction Fee Structure** * **NFT Transactions:** A minimal fee (e.g., 1–2%) is applied to marketplace transactions, a portion of which is redistributed to creators and Super Masternode validators. * **$WHERLS Token Transfers:** Near-zero fees for on-chain transfers using the native BEP-20 standard. * **Staking Operations:** Staking and unstaking transactions incur standard BSC gas fees, with no additional platform markup. * **Masternode Rewards:** Fees collected across the ecosystem contribute to masternode and staking pools, promoting decentralization. 🔄 **Cost Optimization Features** * **Gas Fee Discounts for $WHERLS Holders:** Users who pay in $WHERLS receive discounts on platform fees, incentivizing token utility. * **Batching Transactions (Planned):** Future updates may include batch processing to further reduce per-action gas consumption. * **Deflationary Mechanics:** A portion of all collected transaction fees may be burned or allocated to liquidity pools to support long-term token value. By prioritizing low fees and efficient settlement, Wherls ensures that users of all experience levels — from first-time NFT buyers to power stakers — can participate in the Web3 economy without prohibitive costs. --- # 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/transaction-cost.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.