What is ZYNC?
A plain-language map of the Verified Growth Network, the four parties inside it, and the one lifecycle they share.
ZYNC is the Verified Growth Network. It coordinates Sponsors, Communities, Creators, and Members through funded Campaigns, verified contributions, transparent attribution, and auditable settlement.
In everyday terms: a community creates a Space and publishes Missions — clear actions its Members can complete. A Sponsor funds a Campaign around an outcome worth supporting. In the Planned Creator workflow, Creators publish trackable distribution that brings the right people to it. ZYNC records what was asked, what proof was provided, how it was checked, which contribution was accepted, and what reward followed.
ZYNC records whether accepted contributions were delivered, attributed, and settled. Whether they moved a Sponsor’s wider business stays the Sponsor’s own measurement.
The four roles in the system
- Members discover Missions, complete the action, and receive rewards.
- Community teams host the Space, design the experience, and review submissions.
- Creators (Planned workspace) accept a program’s disclosure and content terms, publish trackable distribution, and receive recognition and reporting for attributed contributions. A program may also define separate Sponsor-funded compensation in Credits.
- Sponsors fund Campaigns tied to verified action.
A Creator and a community operator can be the same person. The roles stay separate anyway, because their authority, terms, and dispute paths are different. Operators are not protocol payees. The Creator workspace, acceptance, publishing, and reporting flow remain Planned; read the Creator use cases for that contract.
Every role can be a Contributor. A Contributor is any person or organization whose meaningful participation creates value for a Member, a Space, or the network. Completing Missions, operating or funding healthy campaigns, verifying work, moderating, inviting retained Members, creating useful material, and maintaining ZYNC are different forms of contribution. Technical work is only one form.
Not every tap earns ZYNC. Local activity may earn Points or recognition. ZYNC follows separate, published rules for verified contribution.
Who runs the rails
ZYNC is the supporting control plane for the four Campaign parties. It provides the apps, coordination, search, record-keeping, safety controls, and shared rules they depend on.
Verification decisions come from validators, and today every validator is administered by ZYNC. The trust assumptions stay visible: the rule a decision was made under, and the record it produced, are meant to be inspectable by the parties it affects. Independently administered validation is a later stage, and no page here will describe it as present before it exists.
One shared program lifecycle
Every audience in these docs works on the same loop. Each stage names the role that owns it, and each audience guide links back to this section.
1. Fund: the Sponsor
A Sponsor decides which outcome it wants to support and funds a Campaign against it. The terms are settled before anything runs: the eligible audience, the Missions, the proof rules, the budget, the fees, and what happens to rejected, reversed, or unused funds. A funded Campaign is what makes every later stage payable rather than promised.
2. Distribute: the Community and the Creator
The Community hosts the program in its Space and decides how it reaches Members, because it owns that relationship. In the Planned Creator workflow, a Creator opts into the same program, accepts its disclosure and content terms, and publishes trackable distribution to its own audience. Both are named parties with their own terms; neither resells the other’s reach.
3. Act: the Member
A Member sees the action, the proof rule, the timing, and the reward before committing to anything. They complete the Mission in the real world and submit only the evidence the Mission asked for. Nothing about the qualifying rule changes once Members have begun.
4. Verify: validators, with Community review
The submission is judged against the policy that was published before the work began. Automated signals and human reviewers can both contribute to the decision, and where the policy allows one, a challenge path stays open. A case that cannot be settled on the published rule ends in an authorized review, not in silence.
5. Attribute: the shared record every party reads
An accepted contribution is recorded together with the Campaign, Community, Creator, and referral path it came from, so each party can see which part of the delivered work is theirs. Attribution is reproducible: the same accepted contributions produce the same assignment for everyone reading the report. It is a labeled observation of what the network saw, never a claim about what caused a Sponsor’s growth.
6. Settle: rewards and fees stay separate
Each accepted contribution settles once. The Campaign reward pool reaches the earning Members in full. In the Beta, separate fees use test Credits with no real-world value; the production model uses USD-pegged Credits. Those fees fund the platform, verifier costs, and any program-defined Creator or Community compensation. Attribution remains recognition and reporting, not a payout split. Rejections, holds, reversals, and refunds are part of settlement rather than exceptions hidden beside it. Fraud found inside the agreed window is reversed and restored; fraud found after it is measured and reported, not indemnified.
7. Report: the Community and the Sponsor close the loop
The Campaign closes with a record that keeps each event distinct: starts, submissions, approvals, payments, disputes, reversals, and refunds. The Sponsor receives the evidence the agreement defined, not unrelated Member activity, and the Community keeps ownership of its Member experience throughout. That record is what makes the next Campaign a decision rather than a guess.
Keep value and contribution separate
ZYNC keeps contribution history, local Points, Credits, funded rewards, and transferable token balance distinct. Beta Credits are test value; production Credits are cash-backed. Paying for access cannot mint ZYNC, manufacture contribution standing, or accelerate earning. After governed release, someone may acquire vested ZYNC from a holder, but they do not acquire the holder’s contribution history.
Start with ZYNC in three minutes, or choose a practical path in the use-case guide.