Community

Governance

Read power before trust breaks.

Open networks still need rules. This hub shows you who can act, what a badge or report can prove, where moderation happens, how votes gain meaning and why legal reality still belongs in the room.

Start with the question

Governance is the map of who gets to decide.

Use these entry points when a badge appears, a report starts moving, a client hides something, a relay rejects an event, a community vote opens or a public claim needs proof.

A governance room where public decisions are documented and accountable
Start with power iconStart with powerFind out which layer can act: protocol, client, relay, community, issuer or law. Moderate without a king iconModerate without a kingRelays, clients, communities and lists share the safety work instead of hiding it in one office. Read reputation by issuer iconRead reputation by issuerBadges and status only matter when you can inspect who made the claim. Treat reports as claims iconTreat reports as claimsA flag starts review. It does not become truth until context and action are visible. Use labels with provenance iconUse labels with provenanceWarnings, topics and categories are strongest when the labeler stays visible. Know what a vote means iconKnow what a vote meansA signed poll can show preference, but eligibility decides whether it governs. Make DAO talk concrete iconMake DAO talk concreteMembership, proposals, execution and accountability come before slogans. Bring law into the map iconBring law into the mapDSA duties, copyright, illegal content and app-store pressure affect real products.
Members preparing a public decision with rules, records and accountability.
A governance scene where documentation and accountability keep trust legible.
A Nostr badge and membership status visual for reputation and public context.
A focused table discussion about standards, membership and project rules.
A governance team working through operational decisions.

Read by consequence

Open the next page by the decision you need to understand.

A report, label, badge, list, vote or DAO proposal can all look like governance. The right page depends on what the signal changes for you.

01Standards create grammarA NIP coordinates software. It does not settle community values. 02Lists shape your roomMute lists, follow lists and relay lists are personal governance tools. 03Badges need contextDefinition, award, issuer and display rules all matter. 04Trust the software trailMaintenance, permissions and receipts matter more than polish. 05Exit can be healthyForks work better when public records survive the split. 06Awards need rulesCulture, votes and status become serious when money or access follows.
A Nostr badge and membership status visual for reputation and public context.
A focused table discussion about standards, membership and project rules.
A governance team working through operational decisions.
Project and partner discussion connected to a governance layer.
Partners discussing standards and project execution.

Standards and signals

Keep the NIP, the social meaning and the operator choice together.

These pages keep technical standards beside the social choices they enable: labels for context, reports for review, badges for status, lists for curation and polls for public preference.

NIP-32 Labels iconNIP-32 LabelsContext, warnings and categories need visible labelers. NIP-51 Lists iconNIP-51 ListsFollow, mute and relay lists shape what a room feels like. NIP-56 Reports iconNIP-56 ReportsFlags start a review path; they do not finish it. NIP-58 Badges iconNIP-58 BadgesPortable status needs an issuer you can evaluate. NIP-29 and NIP-72 iconNIP-29 and NIP-72Groups and moderated communities make room rules explicit. NIP-88 Polls iconNIP-88 PollsVoting only governs when eligibility and counting are clear.
A governance team working through operational decisions.
Project and partner discussion connected to a governance layer.
Partners discussing standards and project execution.
Members preparing a public decision with rules, records and accountability.
A governance scene where documentation and accountability keep trust legible.

Source trail

When a governance claim matters, open the document behind it.

Use the originals when the stakes rise: the NIP that defines the event, the legal text that frames operator duties, the Crays page that explains the association layer, or the product page that shows how status appears in practice.

Governance partners reviewing standards and project execution
NIP repository iconNIP repositoryOpen the standards that define Nostr event behavior. NIP-58 Badges iconNIP-58 BadgesCheck the badge model before using status as proof. NIP-56 Reports iconNIP-56 ReportsRead how reports point to events and people. Digital Services Act iconDigital Services ActRead the EU policy frame for online services and transparency. Crays Association iconCrays AssociationConnect Nostr governance to the real association layer. Crays Award iconCrays AwardFollow the award surface where voting, status and culture meet.