Mainnet status
Yokefellow is operating as a live public platform on mainnet. That means wallet-connected actions, public bucket surfaces, profiles, activity, offerings, NFT-linked behavior, and other core flows may involve real onchain state, real user activity, and real consequences. Some parts of the platform update immediately. Others depend on indexing, sync, cache refresh, or third-party infrastructure before they are fully reflected across every surface.
Live does not mean finished.
Live does not mean instant everywhere.
Live does mean actions should be treated seriously.
Current operating context
Yokefellow runs as a public web platform connected to live blockchain activity. Core platform behavior may depend on wallet connections, onchain transactions, indexer freshness, derived activity views, balance and ownership sync, NFT metadata and collection visibility, public content and proof surfaces, and connected infrastructure such as RPC, hosting, and storage providers.
Some delays are visual. Some delays are indexing-related. Some issues are true failures. This page exists to help users tell the difference.
Indexer status matters
Some Yokefellow surfaces depend on an indexer to reflect what already happened onchain. That means the chain can be correct while parts of the app are temporarily behind. When that happens, the indexer status becomes one of the first things to check.
If the indexer is healthy, recent deposits, trades, mints, transfers, and related activity should appear in platform views after normal sync delay. If the indexer is delayed or stale, you may see missing recent activity, balances that look behind, NFTs or ownership displays lagging, or bucket and profile surfaces that do not yet match chain explorers.
The chain is the source of truth for completed onchain actions. The indexer is what helps Yokefellow reflect that truth across the app.
How indexer health is measured
Yokefellow treats the indexer as healthy when it is continuing to process recent chain activity within an acceptable lag window and the platform is receiving fresh indexed state. The public indexer check is built around a few simple signals.
Last indexed block
The most recent block the indexer has fully processed.
Last indexed time
The last time the indexer successfully moved forward.
Freshness lag
How long it has been since the indexer last advanced. Yokefellow currently treats the indexer as stale when that freshness window falls behind the platform threshold.
Indexer state
Whether the indexer is healthy, delayed, stale, or failing based on freshness and recent processing errors.
Under the hood, Yokefellow's indexer check also tracks whether the last run reported an error and whether the indexer is still producing fresh state within the stale threshold. That is the difference between a brief display delay and a real indexing problem.
Public indexer states
Live: the indexer is advancing normally and recent activity should appear after ordinary sync delay.
Delayed: the indexer is still moving, but it is behind enough that recent activity, balances, or ownership displays may lag.
Stale: the indexer has not advanced recently enough to be trusted as current. Onchain activity may be correct while app surfaces are behind.
Offline: the indexer is not processing correctly or is unavailable.
What the indexer check should show
A useful public indexer block should expose enough to explain app behavior without dumping raw internals. At a minimum, Yokefellow should surface:
- Indexer status: Live, Delayed, Stale, or Offline
- Last indexed block
- Last updated time
- Freshness lag from the most recent indexed state
- A short note explaining that onchain state may be ahead of app surfaces while indexing catches up
What can lag or look wrong
Activity delay: a completed transaction may not appear in the activity feed immediately if indexing has not caught up.
Balance or ownership mismatch: a wallet may already hold an asset onchain while parts of Yokefellow still show an older state.
Wallet mismatch: if the wrong wallet is connected, or if the wallet state is stale, the platform can appear broken even when the underlying system is fine.
NFT display issues: an NFT may exist onchain and still not appear where expected right away due to metadata refresh, ownership sync, wallet app behavior, or collection visibility quirks.
Profile, proof, or content delay:public content changes may appear in one place before every derived or cached surface updates.
Before reporting a problem
Confirm the transaction succeeded onchain.
Confirm you are connected with the expected wallet.
Refresh the page and reconnect if needed.
Check whether the issue is display-only or onchain.
Check whether the indexer appears current.
Give recent actions a short window to sync before assuming failure.
A missing row in the app is not always a missing action onchain.
Known limitations
Yokefellow is live on mainnet, but it is still evolving. Some surfaces are stronger than others, some flows are still being sharpened, and some parts of the app may occasionally fall out of sync with the chain before catching up again.
Short delays between onchain action and UI reflection can happen.
Ownership and activity lag can happen when indexing is behind.
Wallet-dependent NFT display quirks can still show up.
Permissions, offerings, and linked surfaces are still evolving.
Need help
If something looks broken, delayed, missing, or out of sync, use the contact page. When reporting an issue, it helps to include the page you were on, the wallet you were using, what action you took, whether the transaction succeeded onchain, the transaction hash if there is one, and screenshots if useful.
Go to contactIn plain terms
Yokefellow is live on mainnet. Some things update immediately. Some depend on indexing. Some depend on wallet state. Some depend on the app catching up to the chain.
The chain may already be right even when the interface is briefly behind. That is why the indexer check belongs here, and why this page exists at all.