Yokefellow - Start Here
YES Tokenomics Paper
The YES emission schedule, platform role, fee structure, market role, and gas-fee boundary.
1. What This Paper Is
This paper explains the economic structure of YES. It defines what YES is, how much can be minted, how long that schedule lasts, what YES is used for, how fees work in the system, and how gas should be understood alongside those fees.
2. What YES Is
YES is the platform token used across Yokefellow’s participation and economic flows. It is used in buckets, offerings, apps, and related market activity. Yokefellow is the platform. YES is the token used within it. It supports the system’s economic layer, but it is not the whole identity of the platform.
3. Fixed Emission
YES has a fixed yearly emission schedule.
39,674,006 YES may be minted per year. That emission may occur only once per year. That schedule lasts for 23 years. The total maximum scheduled emission is 912,502,138 YES. After year 23, scheduled emission ends.
YES is not designed for open-ended minting. The supply schedule is fixed, bounded, and meant to remain readable over time.
4. Why the Emission Is Structured This Way
The yearly cap exists so YES does not become a token with vague or casually expandable supply. A native participation token should have readable issuance, not discretionary inflation.
The 23-year duration exists because Yokefellow is being built as a long-term system rather than a short token cycle. Buckets, offerings, apps, and the wider participation rails need time to grow through real use. YES is meant to support that longer expansion, not only an initial launch window.
The emission structure is designed to do three things:
keep supply controlled
keep issuance readable
give the system a long runway to grow
5. What YES Is Used For
YES is used across Yokefellow’s participation flows.
That includes:
bucket activity
offering entry
app-layer participation
platform funding movement
market activity around the system
YES is not only held. It is used as part of the system’s working participation rail across buckets, offerings, apps, and related economic activity.
6. YES in Buckets and Offerings
YES is not only held. It is used directly.
Offerings can be:
free
fixed in YES
dynamically anchored to a USD target that resolves into a YES amount
This makes YES a real participation rail rather than a symbolic ecosystem token. A fixed YES offering states the entry amount directly in YES. A dynamic USD-target offering still resolves into YES through the platform’s pricing model. That keeps the participation rail native to Yokefellow while allowing offerings to be configured against a more stable reference where needed.
7. Market Role
The market exists so YES can be priced, traded, and discovered in a way the wider Yokefellow system can use. Yokefellow needs a live economic layer around participation. It is not enough to issue a token and leave it static. YES has to be able to move through the system and around the system.
But the market is not the whole point of Yokefellow. It supports the platform rather than replacing it.
8. Fee Structure
The fee structure should be stated plainly.
Market takers pay a 2% fee. Bucket deposits carry a 1% platform fee.
These are Yokefellow fees and part of the platform’s economic structure.
The 2% taker fee belongs to the market layer. The 1% deposit fee belongs to the bucket-entry layer. Charging the platform fee on deposit places it at the point of entry into the bucket rail rather than later on exit, which keeps the participation model cleaner once funds are already inside the system.
9. Gas Fees Are Separate
Chain gas is not the same thing as a Yokefellow fee.
When a user performs an onchain action, the network charges gas. That cost belongs to the chain, not to Yokefellow.
The economic structure should therefore be read in three separate layers:
2% taker fee on market activity
1% deposit fee on bucket deposits
chain gas charged by the network itself
These are separate costs and should not be described as if they were the same thing.
10. Gas Abstraction Direction
Yokefellow intends to reduce the need for users to manage base gas assets directly.
The goal is to use a bridge or gas-abstraction layer so normal participation does not require users to hold Base ETH in the usual way. The intended direction is to let users cover gas through USD rails first, and potentially YES later, instead of managing base-gas assets directly for ordinary system use.
This does not mean gas disappears. Chain gas still exists. The point is to abstract it from the user experience so Yokefellow feels cleaner and more self-contained as an economic system.
11. Controlled Minting
YES minting is controlled, not open.
Minting is access-controlled and bounded by the token’s fixed issuance structure. YES is designed to follow a defined emission policy rather than loose discretionary minting.
That matters because a token that powers participation across a long-term system should not have a vague supply posture. The supply rule should be something people can actually read and understand.
12. What YES Is Not
YES is not the whole product. YES is not the whole value of Yokefellow. YES is not a justification for open-ended minting. YES is not detached from real system use. YES does not by itself represent equity, ownership, control, or profit rights in Yokefellow, the platform, or the apps, tools, or other surfaces built on it.
The hierarchy is simple:
Yokefellow is the system. YES is the token used within that system.
13. Closing Frame
YES has a fixed yearly emission of 39,674,006 for 23 years, for a total maximum scheduled emission of 912,502,138 YES. It is used across Yokefellow’s participation flows, offerings, apps, and related market activity. The economic structure is meant to be readable: supply is controlled, platform fees are stated directly, and chain gas is treated separately from Yokefellow fees. Over time, Yokefellow aims to make gas handling cleaner for users by abstracting network costs through USD first, and potentially YES later, instead of requiring direct base-gas management for normal participation.