Wallet Connection and Profile
Last updated: August 21, 2026
- What connection is for
- The boundary worth holding
- Safety, stated once and meant
- Official source
- Related reading
Governance participation in the Council is tied to a Web3 wallet, connected through RainbowKit and Wagmi — a standard, widely used connection layer rather than anything bespoke. Connecting establishes who is speaking. It is an identity action, and it is worth being clear that it is a different kind of thing from signing into an account with an email and password: the credential is held by you, in software the Council does not control, and that is the point of the design.
What connection is for
It associates your participation with an address so that a vote can be attributed and a history can exist. Your profile in the Council is built around that association. Nothing about reading the Council requires it.
The boundary worth holding
A connected wallet in the Council is not the same identity as a Sanctum account, and neither is a login to any other vertical. Verticals may connect to a shared identity, but they are separate services with separate boundaries, and assuming that being signed in somewhere means being signed in here will produce confusing results.
Safety, stated once and meant
Start every connection from the Council's own interface, reached by typing or bookmarking the address — never from a link in documentation, a message or a search result. Read what a signature request says before approving it. And no part of this, ever, requires a seed phrase.
A page that asks for a recovery phrase is an attack, regardless of how exactly it reproduces the Council's design. There is no legitimate flow in this Universe that needs one.
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.
Related reading
- Voting and Vote History — What a vote means here, and where your own record of participation lives.
- Privacy, Accounts and Connected Services — The boundary between public browsing, authenticated areas and third-party flows.
- Accounts, Wallets and Authentication Boundaries — Which credential belongs to which vertical, and what never crosses between them.