Trust nothing you cannot verify, especially a wallet asking for your recovery phrase.
Guardians make ZooBC harder to fool. They verify software before anyone puts a key into it, separate live network evidence from marketing claims, explain security limits honestly, and protect useful discussion without treating criticism as an enemy.
Why this symbol?
The meerkat watches the horizon and signals change. It represents people who verify information, identify risk early, educate others, and protect the quality of the community.
Decentralization does not remove the need for judgment.
ZooBC can remove a central intermediary from transactions and applications. It cannot stop a person from downloading a fake wallet, trusting an outdated claim, exposing a recovery phrase, or mistaking a failed data connection for an empty network. A Guardian closes that gap.
Verify software
Before a Wallet or node release is trusted, compute its SHA-256 fingerprint and compare it with the release record. An on-chain match means the release authority registered that exact file. A gateway-only match proves less because a compromised website could serve both a fake file and a matching fake fingerprint.
Protect keys
The ZooBC Wallet signs locally. A recovery phrase or secret key should never leave the page. That protection is meaningless if the page itself is counterfeit, so verification comes before entering a phrase, not after.
Separate fact from status
Chain height belongs in the Explorer. Release status belongs in the release registry. Mainnet dates and node eligibility belong on the Roadmap. Token allocation belongs on Tokenomics. A Guardian sends people to the maintained source and states when it was checked.
Keep criticism useful
Moderation protects people from impersonation, credential theft, spam, and fabricated claims. It does not erase a difficult technical question merely because the answer is uncomfortable. The FAQ explicitly invites harder questions; Guardians help those questions reach the right evidence.
Know the failure before you write the warning.
These are concrete failure modes already addressed by the Wallet manual, verifier, Explorer, security model, or site operating rules.
| Failure | What it looks like | What a Guardian does |
|---|---|---|
| Counterfeit Wallet | The page looks normal and may display the correct warnings, but sends the entered phrase somewhere else. | Verify the downloaded file before opening it. For anything involving funds, insist on an on-chain release match. |
| Revoked release | A file once published by the release authority was later withdrawn because it was compromised or faulty. | Delete it. A revoked match is a specific warning, not partial approval. Fetch and verify the current release. |
| Authority change | The verifier reports that a change to the release-authority key is pending. | Stop. Confirm the reason through a channel independent of the website serving the file. |
| False zero | An API outage is presented as zero balance, zero nodes, or an empty chain. | Report the connection as unreachable or stale. Never turn missing data into a factual network measurement. |
| Outdated promise | An old post is repeated as if its date, allocation, eligibility rule, or implementation status were current. | Link to the maintained Roadmap, Tokenomics, manuals, or live application and include the date checked. |
| Consensus myth | Someone claims participation score or stake gives a node a better chance to build the next block. | Correct it with the security page: selection is a uniform draw from the registry. Score controls whether a node remains registered; stake orders admission. |
Check the file before it can check you.
The browser verifier hashes the file locally; the file is not uploaded. For a check that does not trust the website serving the verifier, ask a node directly and compare the results.
- 01
Obtain the file
Download the Wallet, node package, or other release from the expected ZooBC location. Do not enter credentials or run it yet.
- 02
Calculate its fingerprint
Drop the file onto Verify a download, or calculate SHA-256 locally.
sha256sum "ZooBC Wallet.html" - 03
Ask the chain
Query a node you trust, or two nodes run by different people, and look for the exact fingerprint in the release list.
curl -s http://NODE:8080/api/v1/release/list curl -s http://NODE:8080/api/v1/release/authority - 04
Interpret the result
On-chain match: the authority registered this exact file. Gateway match only: useful against corruption, but not proof against a compromised site. Revoked: delete it. No match: do not put a recovery phrase into it.
If the fingerprint is missing, revoked, different, or accompanied by an unexplained authority change, stop the process. Do not solve uncertainty by trusting the warning shown inside the file being questioned.
Every claim has a proper home.
A useful answer names the source, the relevant section, and when it was checked. It also says whether the statement is a protocol fact, current status, published plan, or personal interpretation.
Blocks, transactions, accounts, nodes, gateways, releases, and current testnet activity.
↗PROTOCOL MECHANICSChain securityBuilder selection, registry share, censorship probability, admission timing, and attack-cost model.
↗RELEASE INTEGRITYVerifierLocal file hashing, release evidence, revocation state, and release-authority warnings.
↗DATES + ELIGIBILITYRoadmapMaintained milestones, mainnet path, node deadlines, and planned open-source timing.
↗SUPPLY + ALLOCATIONTokenomicsPublished supply, allocation, vesting, utility, and genesis participation information.
↗USER SECURITYWallet manualLocal signing, encrypted vault behavior, watch-only accounts, air-gap mode, and release checks.
↗Protect the conversation without controlling the conclusion.
A Guardian is not a project defender who wins arguments. The role is to make it harder for deception, credential theft, stale information, and manufactured certainty to survive.
- Ask for the exact URL, file hash, transaction, block, or claim being discussed.
- Link to the strongest maintained source, not a screenshot of it.
- State when live information was checked.
- Separate confirmed behavior from roadmap intentions.
- Escalate suspected credential theft, impersonation, compromised releases, and authority changes immediately.
- Ask anyone for a recovery phrase, secret key, PIN, or private backup.
- Treat a gateway's own statement as equivalent to an on-chain release record.
- Present unavailable data as zero.
- Promise returns, mainnet dates, security, or future functionality.
- Remove criticism simply because it challenges ZooBC.
Does this sound like you?
For privacy advocates, decentralization believers, educators, moderators, and careful skeptics.
You are skeptical of platforms, surveillance, middlemen, and quiet changes to the rules.
You want claims to be verifiable instead of accepted on authority.
You can educate, moderate, document, translate, or help people identify risk.
You value respectful disagreement, truth over hype, and long-term human autonomy.
Enter through a real door.
Each route below leads to an existing ZooBC page, tool, or current community destination.
Study chain security
Review how builders are selected, what attacks cost, and where the real risks sit.
↗QUESTIONRead the direct answers
Examine the purpose, design, funding, source-code, and continuity questions.
↗PROTECTVerify every release
Hash downloads locally and compare them with published or on-chain evidence.
↗Follow the evidence.
Use the source that matches the question instead of relying on a single marketing page.
From interest to participation.
- 01Read the claims and supporting technical pages
- 02Verify information against live or published evidence
- 03Help other people understand, question, and participate safely
Trust nothing you cannot verify, especially a wallet asking for your recovery phrase.
Guardians make ZooBC harder to fool. They verify software before anyone puts a key into it, separate live network evidence from marketing claims, explain security limits honestly, and protect useful discussion without treating criticism as an enemy.