What a participant does, then the mechanism behind it, then the accounts that enforce it — and what is not built yet.
What each one actually costs or produces — not a funnel
YUID never holds a key and has no account system. Your wallet is your identity, and every signature happens inside it — this app builds transactions and shows them to your wallet, which is the only thing that can sign.
Open the appActivation creates your participant account: your node in the economic graph. It costs a fixed amount of SOL, read from the protocol's own settings rather than converted from a price, and that fee is split four ways to destinations the program controls. Nothing is attributed to a wallet that has not activated.
See the cost and the splitEvery participant is a node and the one edge the chain records is who referred whom. Influence is a bounded measure of sustained economic significance, computed per epoch — it is not YUID, not a balance, and not a rating. Where no value has been computed for you, the graph says so rather than showing a zero.
Open the economic graphYour referral link carries your wallet. When somebody activates through it, the referral share of their fee is paid to you at that moment, and the relationship is written permanently onto their participant account. Beyond that share, introductions alone earn nothing: rewards follow measured activity.
Get your linkStaking is custody with a lock. Tokens move into a vault whose authority is your own stake position, and no key in this protocol can move them out except by your own withdrawal. Whether staking pays a reward is a separate switch, and it is off.
See the termsRewards are published per epoch as a Merkle root the protocol commits to on chain. If an epoch allocated you something, you claim it against that root; if it allocated nothing, the page says so rather than showing an empty balance that looks like a failure.
Check your allocationA Solana-native economic network. Participants activate once, their economic activity forms weighted relationships with other participants, and those relationships are measured each epoch to determine what each participant contributed. Settlement is on Solana; the measurement runs off-chain and commits to the chain as a Merkle root that anyone can recompute.
One flat lamport price, read from a protocol parameter — not an oracle, and not a USD target. It creates a Participant account keyed to the wallet, once, and it cannot be repeated. The fee divides four ways and the panel below reads the live division rather than describing it.
500,000,000 YUID, all of it minted at genesis, and the SPL mint authority permanently set to None. That is not a policy the protocol promises to keep — it is a property of the mint account, so no key, no governance vote and no program upgrade can create another unit of YUID. Any holder may burn, so the supply can fall and can never rise.
300,000,000 Community, 150,000,000 Treasury, 50,000,000 Team, summing to the cap exactly — the program refuses to build if they do not. Each sits in a vault the program itself controls — a program-derived address — so no private key holds any allocation. The team's 50,000,000 is 10,000,000 released at launch and 40,000,000 vesting on a 12-month cliff followed by 24 months linear.
An epoch opens, accrues activity, and closes. The engine computes an allocation off-chain and publishes a Merkle root that commits to the parameters, the engine version and the previous epoch's state — so a root cannot be swapped for one computed under different rules. A guardian may challenge a published root inside its window, and no instruction lets anyone force a challenged root to finalize. Participants claim against a proof; a receipt account makes a second claim impossible.
Money does not leave on one signature. A withdrawal is proposed against a destination that must already be on an allowlist, becomes executable only after a timelock, and is re-checked against the allowlist at execution — so removing a destination during the window actually stops the payment. A guardian may cancel it or pause the treasury, and a pause suspends the timelock rather than running beside it.
A share of each activation accrues to the LSR. It is not a reward pool and never pays a participant for contributing: capital leaves it only toward a programme that was named, budgeted and allowlisted beforehand, inside per-action, per-epoch and floor limits the program enforces. It ships disarmed and is disarmed today.
YUID never holds participant funds, never operates a custodial wallet and never asks for a seed phrase. Phantom is the primary wallet. Every reward and every fee settles on Solana, and the client in your browser reads the chain directly rather than trusting this site's API for anything that gates a transaction.
The fee and its four shares, read from the protocol’s own settings at a known slot. Every destination is an address the program itself controls; no person holds a key to any of them.
The fee and its four shares, read from the protocol's own settings. Every destination is an address the program itself controls — no person holds a key to any of them.
Waiting on the chain.
The ledger records what each allocation has released; the vaults hold what has not. Both are read from chain, and they answer different questions.
What exists, what has been released against each allocation, and what has been retired.
Until initialize_token_config has run there is no ledger to report — a different thing from one reporting zero.
The three allocation vaults, read from the accounts themselves. Every one is held by a program-derived address — no key can move them.
The vault addresses derive from the mint, and the supply ledger has not reported one yet.
Read from the treasury's own config account. Who may move funds, and what an outflow has to pass through first.
Waiting on the chain.
Every claim above is a claim about one of these accounts. The addresses are derived from the program IDs this build is configured with, so a link here lands on exactly the account the panels above read.
Named rather than gestured at. A reference that lists only what works is not a reference.
The release limit is settled and now enforced on this cluster: at most 577,000 YUID of the 300,000,000 community allocation may leave the reserve in any 1,512,000-slot window, roughly a week — counted across every epoch at once, so a backlog of unpaid epochs queues rather than discharging together. That is a ceiling and never a target; a healthy week may release nothing. Unused capacity expires at the end of a window, while an epoch's unpaid entitlement carries forward. What is still unchosen is where inside that ceiling a week should land: the reward ratio r, the bootstrap size and the eligibility thresholds are open decisions, so the figure an operator authorizes is today a judgement rather than a formula's output.
This is no longer an open item and is kept because it changed. The producer is deployed, the policy is armed, and 577,000 YUID has left the community reserve into two epoch escrows on a test cluster — the full window ceiling, refused at one atomic unit beyond it. The reserve reads 299,423,000 YUID rather than 300,000,000, and the canonical mint's supply did not move while that happened, because an emission is a transfer of YUID that already exists. One epoch is still owed 123,000 YUID, deferred until the window rolls.
Not to be confused with the community reserve above, which is armed and has released. The LSR's policy account has not been created on this cluster: its four roles, its limits and its staged permissions are implemented and tested, and none of them is live. Nothing has been deployed from it and nothing has been bought back or retired.
Implemented and tested in the program, not initialized on this cluster. Staking rewards ship disabled.
Protocol authorities are single keys today. The thresholds they are intended to sit behind are decided and documented; they are not yet implemented, and this site will not describe a multisig before one exists.
Anything denominated in dollars on this site is sample data. Pricing a balance needs a SOL price the protocol deliberately does not carry, and a plausible figure beside a real one makes both look equally authoritative.
Figures in the panels above are read from Solana at the slot each panel reports. Prose describes the deployed programs. Anything denominated in dollars elsewhere on this site is sample data and is labelled as such.
