Skip to main content

Conduct and Governance Security

Last updated: August 21, 2026

Governance attracts two problems that ordinary community spaces do not. The first is that decisions have consequences, which raises the temperature of disagreement. The second is that participation runs through wallets, which makes the space attractive to people who want your credentials rather than your vote. Both are manageable, and neither is a reason to stay out — but they are worth naming before you connect anything.

Good faith in a deciding body

Argue the proposal rather than the proposer. Read the deliberations archive before asserting that something has never been considered. Accept outcomes you voted against as outcomes — a governance space in which losing is treated as illegitimate stops being one. And keep lore disputes in the Conclave, where they belong and where nothing is at stake.

The security rules that matter

  • Reach the Council by typing or bookmarking its address. Never from a link you were sent.
  • Read every signature request. Decline anything you did not initiate or cannot understand.
  • Never enter a recovery phrase or private key, anywhere, for any reason.
  • Treat urgency as a warning sign. Real governance has deadlines; it does not have emergencies that require you to approve something immediately.

If something looks wrong

A convincing copy of the Council that appears somewhere unexpected is the classic attack in this space. Stop, do not connect, and report it through the project's official contact channels rather than engaging with it.

No proposal, vote, airdrop, verification or recovery step in this Universe legitimately requires a seed phrase. Anything that asks is hostile, without exception.

Official source

Canonical source for this subject: the City Council. Checked 21 August 2026 — where this guide and the live service disagree, the service is right.