Enter ZooBC. Help shape what it becomes.
Participation is not limited to buying ZBC or operating hardware. ZooBC also needs people who test, document, translate, report problems, explain the project, organize the community, and take responsibility for meaningful work.
Why this symbol?
One firefly is a small signal; thousands become a visible field of activity. They represent the everyday contributions that make a participant-operated network feel alive.
Turn attention into work the project can inspect and use.
Participation is not measured by enthusiasm alone. A participant can exercise the current testnet, document a reproducible problem, improve an explanation, translate maintained material, help someone verify a release, organize a focused discussion, or take responsibility for a defined contribution.
Use the real product surface
Open the Wallet, Explorer, Faucet, manuals, and current testnet tools. Report what happened, on which page and network, with enough detail for someone else to reproduce it.
Bring a bounded contribution
Replace 'I want to help' with a specific output: a tested workflow, corrected paragraph, translation of a maintained page, issue report, event, tutorial, moderation shift, or named operational task.
Protect other participants
Never request recovery phrases, private keys, PINs, or backups. Mark testnet coins as valueless, link to maintained sources, and avoid turning a roadmap item into a promise.
Close the loop
A useful report includes the result after review: confirmed, corrected, deferred, unable to reproduce, or still open. Participation creates continuity when work does not disappear into chat.
Choose a path with a visible result.
The best first contribution matches what you can actually complete and names the evidence the project will receive.
| Path | Useful contribution | Evidence to return |
|---|---|---|
| Product testing | Exercise a Wallet, Explorer, Faucet, verifier, or manual workflow on the current testnet. | URL, device/browser, steps, expected result, actual result, time, and non-sensitive identifiers. |
| Documentation | Correct ambiguity, missing prerequisites, stale routes, inaccessible structure, or unclear technical explanation. | Exact page and section, proposed replacement, and the source used to verify it. |
| Translation | Translate a maintained source without changing technical meaning or security warnings. | Source version or date, complete translated section, and terms that need project review. |
| Community support | Answer questions with maintained links, route hard problems, and protect users from impersonation or credential requests. | Question, source provided, unresolved point, and escalation when safety is involved. |
| Organization | Run a focused test session, tutorial, working group, bounty task, or community event. | Purpose, owner, date, participants, output, decisions, and next action. |
| Founding contribution | Take responsibility for a defined technical, operational, product, content, or community function. | Scope, availability, relevant work, decision needs, deliverable, and review point. |
Start safely, then make yourself useful.
The current public environment is testnet. Treat it as a place to learn and test, not as proof of value or a substitute for current participation terms.
- 01
Read the status first
Review the Roadmap and FAQ so you know what is live, what is planned, what remains a risk, and which claims need verification.
- 02
Enter through testnet
Use the current Wallet and Explorer, obtain only valueless test coins through the Faucet, and never reuse a recovery phrase that protects real assets elsewhere.
- 03
Choose one deliverable
Select a test, documentation fix, translation, support task, event, role, or proposal that can be reviewed. Name the expected output before beginning.
- 04
Return evidence and ownership
Share the result with steps, links, identifiers, and open questions. State whether you can own the next action or whether it needs another person.
Stop any interaction that asks for a recovery phrase, secret key, PIN, private backup, payment to an unverified address, or certainty about value and returns. Confirm the route through maintained ZooBC channels before continuing.
Enter through maintained doors.
Use the product for experience, the Explorer for network evidence, the Roadmap for status, the FAQ for direct answers, and Join for current participation routes.
Genesis support, node operation, contribution paths, roles, community, and current next steps.
↗USEWalletThe current browser Wallet and the application surface available on testnet.
↗TEST COINSFaucetValueless testnet ZBC for learning and supported testing.
↗VERIFYExplorerLive testnet blocks, transactions, accounts, movements, services, and releases.
↗STATUSRoadmapMaintained milestones, completed work, planned releases, and mainnet path.
↗CONTEXTFAQDirect answers to the difficult questions about purpose, consensus, funding, code, and continuity.
↗Contribute without creating new uncertainty.
Good participation makes facts easier to find, problems easier to reproduce, and responsibility easier to locate.
- Name a specific deliverable and owner.
- Include exact pages, steps, times, and non-sensitive identifiers in reports.
- Mark testnet coins and activity as valueless test data.
- Link maintained sources when answering questions.
- Say when a task is finished, blocked, transferred, or still open.
- Ask anyone for private credentials or recovery material.
- Promise token value, returns, dates, eligibility, or future features.
- Submit vague feedback without a page, action, or expected result.
- Translate technical text by changing its meaning to sound smoother.
- Treat high message volume as a substitute for completed work.
Does this sound like you?
For community members, testers, contributors, ambassadors, organizers, and prospective founding collaborators.
You want identity, belonging, recognition, and a real role, not passive membership.
You can test, document, translate, organize, explain, moderate, or find problems.
You care about open source, truth over hype, and respectful discourse.
You can commit useful time and mental energy to something still being built.
Enter through a real door.
Each route below leads to an existing ZooBC page, tool, or current community destination.
Choose a contribution path
Support genesis, run infrastructure, or contribute skills and community work.
↗OPEN ROLESReview founding roles
Read the current role descriptions, expectations, and application route.
↗CONNECTJoin the conversation
Meet the current community, ask questions, and follow project activity.
↗Follow the evidence.
Use the source that matches the question instead of relying on a single marketing page.
From interest to participation.
- 01Find the path that matches your capabilities
- 02Review the project, expectations, and current status
- 03Enter the community with a specific way to help
Enter ZooBC. Help shape what it becomes.
Participation is not limited to buying ZBC or operating hardware. ZooBC also needs people who test, document, translate, report problems, explain the project, organize the community, and take responsibility for meaningful work.