Current network
Yokefellow's current production chain context is Base mainnet.
The production Yokefellow app is pointed at Base mainnet for live onchain activity.
Wallets and integrations should use chain ID 8453 for the live Base environment.
The repo deployment artifacts and production envs use the base-mainnet profile.
Core contract and wallet map
These are the current public addresses users and partners should use when checking Yokefellow's Base mainnet deployment. Addresses are shown directly and linked to BaseScan.
YES token
tokenYokefellow Empowerment Shekel. Native participation and economic rail for Yokefellow.
Base USDC
tokenOfficial USDC token used by the YES/USDC market on Base.
Bucket vault
contractCurrent bucket custody and accounting layer for bucket balances.
Settlement V2
contractCurrent market and bucket-side execution layer. This is the active settlement address.
Settlement V1
contractPrevious settlement address kept here so users can distinguish old wiring from the active V2 contract.
NFT registry
contractCanonical registry for recognized Yokefellow NFT collections.
721 collection factory
contractFactory for recognized ERC-721 style Yokefellow collections.
1155 collection factory
contractFactory for recognized ERC-1155 style Yokefellow collections.
Owner / deployer
walletCurrent owner/deployer wallet shown for transparency. Operational authority should be read with the trust-boundary documents.
Fee recipient
walletConfigured recipient for current settlement and vault fee routing.
Gas refund recipient
walletDedicated wallet configured for the gas-refund direction. Public gas abstraction should still be read as a hardening lane.
Fee and economic posture
Yokefellow fees and Base network gas should be read as separate layers. This page states the current configured launch posture, not a promise that fees can never change.
Current settlement-level taker fee. The deployed hard cap is 10%.
Current vault-level platform fee on bucket deposits. The deployed hard cap is 10%.
Base network gas is separate from Yokefellow fees. Gas abstraction remains an implementation direction, not a claim that gas disappears.
The gas-refund direction exists in the settlement design, but public sponsored-gas behavior should be checked by live configuration before relying on it.
Deployment transactions
These links let users inspect the main deployment and configuration transactions directly on BaseScan.
YES deployment
Deployment transaction for the YES token.
Vault deployment
Deployment transaction for the current bucket vault.
Settlement V2 deployment
Deployment transaction for the active settlement contract.
Vault operator grant
Grant connecting settlement authority to the vault layer.
Settlement V2 fee params
Fee-parameter update for the current settlement configuration.
Vault deposit fee params
Deposit-fee configuration for bucket deposits.
NFT registry deployment
Deployment transaction for the collection registry.
721 factory deployment
Deployment transaction for the 721 collection factory.
1155 factory deployment
Deployment transaction for the 1155 collection factory.
What users should verify
The app is meant to be readable, but users should still verify the important facts directly.
Indexer and app-state expectations
Some Yokefellow surfaces depend on an indexer to turn raw chain events into readable app state. That means the chain can be right while the app is briefly behind.
If a deposit, withdrawal, trade, mint, ownership update, or activity item confirmed onchain but does not appear immediately in the app, first check whether indexing has caught up. A missing row in the interface is not always a missing action onchain.
The practical reading rule is simple: BaseScan is the direct verification layer for confirmed transactions. Yokefellow's app, database, and indexer are the readability layer that makes those facts usable across buckets, profiles, activity feeds, and market surfaces.
Known live boundaries
Yokefellow is live, but it is still an early controlled deployment. These boundaries should stay visible until the system hardens further.
Live does not mean finished. Some app surfaces, public buckets, gas abstraction behavior, collection usage, and first-party app flows are still being hardened.
Control surfaces still exist. Fee configuration, minting, registry authorization, collection ownership, bucket operation, and queue handling should be read with the trust-boundary documents.
Legal review matters. Prize, raffle, charity, sale, proceeds, and operator-managed surfaces should not be treated as open public paths until their rules are ready.
Third-party infrastructure matters. Wallets, RPC providers, hosting, databases, indexers, explorers, and metadata surfaces can affect what users see even when contracts are functioning.
Related reading
Operational status should be read beside the deeper documents that explain the platform's risks, roles, and boundaries.
In plain terms
Yokefellow is live on Base mainnet. The addresses above are the public contract and wallet map users should check before relying on the app. The app should make the system easier to read, but users should still verify important chain actions directly and understand that indexing, wallet state, legal review, and operator-managed flows can affect what happens next.