Yokefellow - Blog
What Is YES?
A plain-English explanation of YES, the Yokefellow platform token: what it is, what it is used for, how it fits into buckets and the market, and what users should not assume.
What Is YES?
YES is the Yokefellow platform token.
Its full name is:
Yokefellow Empowerment Shekel
YES is used inside Yokefellow for participation, bucket activity, offerings, apps, market activity, and other platform-connected flows.
The simple version is:
Yokefellow = the platform
YES = the token used inside the platform
YES matters because Yokefellow is not only a website with posts and pages. It is a system where users, buckets, offerings, apps, NFTs, rights, and records can connect through real platform activity.
YES token details
YES is on Base.
Use these details when adding YES to your wallet:
Network: Base
Token name: Yokefellow Empowerment Shekel
Token symbol: YES
Token decimals: 18
YES contract address: 0xA8D0B69402f90e2A03640Df49a4D48304F38A15b
The contract address is the most important part. A fake token can copy a name or symbol. The address is what identifies the real token.
For setup instructions, read:
What YES is used for
YES is the token used across Yokefellow’s participation and economic flows.
Users may encounter YES when they:
- hold YES in a wallet
- buy or sell YES on the Yokefellow market
- deposit YES into a public bucket
- deposit YES into a personal bucket
- use YES in offerings
- interact with bucket-connected apps
- receive or use outputs connected to platform activity
YES is not just something to look at in a wallet. It is meant to move through the system.
YES and buckets
Buckets are the core participation surface on Yokefellow.
Some buckets may use YES directly.
A bucket may accept YES deposits, use YES in offerings, connect YES to participation, or use YES as part of a larger app or campaign flow.
That does not mean every bucket works the same way.
Some buckets capture deposits immediately. Some hold deposits as Bucket Credit. Some disable public deposits. Some are only previews. Some may be active later but not active now.
The bucket page should explain the current posture before users act.
For more detail, read:
YES and the market
Yokefellow includes a YES / USDC market.
That market gives users a place to buy or sell YES through the platform’s market surface.
YES = Yokefellow platform token
USDC = dollar-referenced token used as the other side of the market
The market helps YES move through and around the system.
The market is important, but it is not the whole point of Yokefellow.
Yokefellow is the broader platform. YES is the token. The market is one surface where YES can be traded.
For more detail, read:
YES and personal buckets
Users may have a personal bucket connected to their Yokefellow account.
A personal bucket helps support account-side balances and market activity.
For example, a user who wants to post a maker order on the market may need to deposit YES or USDC into their personal bucket first so those funds can be reserved behind the order.
Personal bucket balances are different from wallet balances.
Wallet balance = tokens held directly in your wallet
Personal bucket balance = tokens deposited into your Yokefellow account bucket
This matters because the market may use wallet funds or personal bucket funds depending on the action.
YES and public buckets
Public buckets are different from personal buckets.
A public bucket is tied to an initiative, project, app, campaign, concept, offering surface, or public participation path.
When YES enters a public bucket, the meaning depends on that bucket’s rules.
A public bucket may:
- capture the deposit immediately
- hold credit for later use
- connect the deposit to participation
- connect activity to an offering
- disable public deposits entirely
- require later operator action
- post proof or receipts after completion
Users should read the bucket before depositing.
YES and offerings
An offering is a structured participation path inside a bucket.
Some offerings may use YES.
An offering may be:
- a purchase path
- an earned path
- a request path
- an application path
- a grant path
- another configured path
YES may be used to enter or support one of those paths depending on how the bucket is designed.
The important distinction is:
YES = the token
Bucket = the public surface
Offering = the participation path
Output = what the path may lead to
Those pieces are connected, but they are not the same thing.
YES and NFTs or rights
YES can be part of a path that leads to an NFT, right, claim, proof, access, status, output, or redemption process.
That does not mean buying or holding YES automatically gives every possible right.
A right depends on the bucket, offering, terms, metadata, and platform state around it.
For more detail, read:
YES supply structure
YES is designed around a fixed yearly emission schedule.
The scheduled emission structure is:
39,674,006 YES per year
23 scheduled years
912,502,138 YES maximum scheduled emission
That means YES is not meant to have vague open-ended scheduled minting.
The emission schedule is meant to stay readable over time.
YES fees and gas
Yokefellow fees and network gas are separate.
Current platform fee layers include:
Market taker fee = 2%
Bucket deposit fee = 1%
Network gas = Base network cost
Gas is charged by the network, not by Yokefellow.
Users should review wallet confirmations before approving transactions.
What YES is not
YES is not the whole platform.
YES is not a promise that every bucket will succeed.
YES is not a guarantee of profit.
YES is not automatic ownership of Yokefellow.
YES is not automatic access to every app, bucket, right, NFT, offering, or redemption path.
YES is the platform token used inside Yokefellow. What it does in a specific situation depends on the bucket, market action, offering, app, or transaction involved.
Why YES matters
YES matters because Yokefellow needs a native token layer for participation.
Without a token layer, every bucket, offering, app, market action, and participation path would need to depend on disconnected payment tools or one-off accounting.
YES gives Yokefellow a common rail.
That rail can support:
- wallet holdings
- market activity
- personal bucket balances
- public bucket participation
- offering entry
- app-layer activity
- rights and output flows
- visible records around participation
The point is not to make everything about the token.
The point is to give the platform a working economic layer that can connect different surfaces.
What to check before using YES
Before using YES, check:
- you are on Base
- the token address is correct
- your wallet is connected
- you understand whether YES is in your wallet or personal bucket
- you understand whether a public bucket captures deposits or gives Bucket Credit
- you understand the market price and liquidity before trading
- you understand any fee or gas
- the wallet confirmation matches what you intended
Slow down before signing or confirming any transaction.
How YES fits into the full user path
A new user path may look like this:
Learn Yokefellow
→ add YES to wallet
→ buy or receive YES
→ use wallet or personal bucket
→ trade on the market if needed
→ enter a bucket or offering
→ receive an output, NFT, right, proof, or record
Not every user will follow every step. But this is the basic shape of how YES fits into the platform.
Current guides
Start here:
- Getting Started with Yokefellow
- How to Add YES to Your Wallet
- What Is a Bucket?
- Bucket Deposits, Captured Deposits, and Bucket Credit
- User Accounts and Yokefellow Market Basics
- NFTs, Rights, and Redemption
- Posts, Briefs, Updates, Policies, and Proof
More guides will be added as Yokefellow fills out.
Related posts
More to read next.