# Introduction In the landscape of blockchain technology, transaction fees have been an integral yet controversial aspect. While necessary for the network's upkeep and security, they often act as a barrier to the integration of blockchain in everyday life, particularly in applications involving microtransactions or gamified experiences. VinuChain, developed by Vinu Ltd, emerges as a solution to this universal challenge. VinuChain is a unique fork of the Fantom blockchain protocol, designed to uphold the core advantages of its predecessor, including security, speed, and scalability, while introducing an innovative stake-based feeless transaction model, known as the Quota System. The Quota System allows stakers of VinuChain's native token (VC) to access a specific quota of feeless transactions based on their stake amount. The new system ensures equitable distribution of transaction capabilities while eliminating direct transaction costs for stakeholders. It also offers non-stakers the flexibility to conduct transactions traditionally, paying the gas fees, thereby accommodating diverse user preferences within the network. In addition, the Quota System integrates an inflation mechanism on VC to fund the cash-back to stakers, effectively making it a self-sustaining model. This system not only minimizes the friction associated with fees, but also opens the door to a range of real-world use-cases such as microtransactions, gamified experiences, and a more cost-effective DeFi landscape. With this innovative solution, VinuChain aspires to revolutionize the blockchain environment, making it more accessible, efficient, and user-friendly for all. --- # 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://vinu.gitbook.io/vinuchain/whitepaper/whitepaper/introduction.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.