# Stablecoins Zeebu's rewards are derived entirely from real-world transactions and are offered for active participation in and services to the protocol. Unlike many protocols that rely on inflationary tokenomics (emissions), all rewards generated through Zeebu are paid out exclusively in stablecoins to active contributors. How can we do this? The telecoms prepayment market, valued at $120 billion annually, forms the backbone of Zeebu's rewards. By disrupting the traditional payment rail standard of 4-5% transaction fees, Zeebu charges 2% while decreasing settlement times. This cost reduction has attracted over 130 merchants to date, while processing over $4 billion in total transactions. This web2 B2B adoption enables Zeebu to distribute stablecoin rewards according to invoices and settlements from telecom B2B transactions, completely avoiding token emissions. Zeebu's reward model is the opposite of the inflationary tokenomics prevalent in many blockchain projects. Instead of minting new tokens to reward participants, Zeebu's reward comes directly from fees generated by Telecom businesses and is paid to active contributors to the protocol. Additionally, the ZBU token itself is designed to be deflationary, incorporating a burn mechanism([phoenix protocol](/zeebu/protocol/tokenomics/burn-mechanics.md)) that gradually to drastically reduces the total supply over time. This combination of B2B stablecoin generation and deflationary token economics creates a uniquely sustainable and highly deflationary ecosystem for all participants. --- # 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://zeebu-1.gitbook.io/zeebu/protocol/tokenomics/stablecoins.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.