ZYNC
Concept

Run a community

A mobile-first map for turning a community purpose into Spaces, Missions, verification, rewards, and repeat participation.

Running a community in ZYNC means creating reliable reasons for people to act together.

The intended operating loop is:

  1. define a Space with a clear identity and boundary;
  2. assign the smallest necessary team access;
  3. publish a Mission with explicit proof and reward terms;
  4. review submissions consistently;
  5. resolve disputes and safety issues;
  6. use results to improve the next Mission;
  7. build recurring rituals and Sponsor relationships around trustworthy evidence.

Your main responsibilities

Community teams shape the Member experience. They decide what action matters, which proof is proportionate, who may review it, and how moderation works. Sponsor funding does not remove those responsibilities.

Your team should be able to explain every Mission in plain language. Members need to know what counts before they begin. Reviewers need the same rule, not private improvisation. Sponsors need evidence tied to the agreed outcome, not unrestricted access to Member data.

Start with structure your Space, then read your first Mission.

If your Space is considering its own on-chain asset, treat it as a separate, opt-in decision. Read Plan a Community Launch before choosing a curve or making utility claims.