# ZooBC Ecosystem Creators

Canonical page: https://zoobc.com/roles/creators/
Audience: Long-term supporters, application teams, service providers, partners, sponsors, and community builders
Symbol: The Coral, a durable structure that supports many other forms of activity
Last reviewed: 2026-08-18

Ecosystem creators turn protocol capability into maintained applications, infrastructure services, integrations, economic programs, partnerships, and communities with named owners. They are responsible for the gap between a demonstration and a service another participant can depend on.

## Required operating brief

1. Define the user, problem, action, outcome, and explicit non-goals.
2. Map every protocol dependency: routes, transaction types, signing, tokens, fees, storage, applications, gateways, releases, and roadmap items.
3. Mark each dependency as live, planned, or external.
4. Name product, technical, security, operations, support, content, and commercial ownership.
5. Prove one complete testnet outcome, including a failure and recovery path.

An application needs a verified user action through confirmed state. Infrastructure needs a verified release, health evidence, and an incident owner. An integration needs duplicate, delayed, rejected, unavailable, and confirmed-state tests. A partnership needs named deliverables and owners, not only an announcement. A community program needs rules, moderation, reward source, review, and measurable output.

Do not recruit, sell, or announce around a capability that is only planned, economics that cannot be reconciled, an unsafe custody or signing boundary, or a service with no maintainer.

Primary action: Explore ways to support: https://zoobc.com/join/#support-genesis
Related: https://zoobc.com/tokenomics/ | https://zoobc.com/roadmap/ | https://zoobc.com/developer/ | https://zoobc.com/manuals/transactions/ | https://zoobc.com/manuals/apps-manual/ | https://zoobc.com/join/