Building block · Groups
Hives
Groups with membership, proposals and their own chain.
What a person notices
Joining a Hive means accepting a real invitation, not tapping an open link. Someone with the right standing in the group sends it, the invite can be checked, and it can be taken back before it's used.
Inside a Hive, a person sees membership, proposals and shared content as separate, organized areas rather than one long mixed feed. A chat channel inside a Hive behaves like its own space too, kept apart from the group's other activity.
A Hive defaults to a cap of 150 members. That's a starting policy the group can raise, not a wall a person suddenly hits.
Messages move member to member through the group's live connections rather than bouncing through a company's servers. For everyday-sized groups this is fast; for very large groups NAOMS is upfront that the exact reach time is an engineering estimate, not something proven under real load yet.
What you get as a developer
A Hive is a real group type, not a table of rows tagged with a group id. Membership, governance and shared content each live on their own dedicated part of the group's chain, kept separate from one another, and a channel inside the Hive (for example, chat) gets its own separate chain again rather than being folded into the Hive's chain.
Membership has its own history
Who is in the Hive, and when they joined or left, is tracked on its own part of the chain, not inferred from application state.
Governance is structural, not a setting
Proposals and decisions live on their own part of the chain too, so a decision the group made is provable, not just remembered by one app.
Channels are separate chains
A chat channel, or any other activity stream inside a Hive, gets its own chain. Different kinds of activity don't get tangled into one growing log.
Members sync directly, with no server
Devices belonging to Hive members gossip directly with each other, deduplicated against the group's own signed history. No server holds or relays the Hive's data.
Local-first: a Hive's data lives across its members' own devices. There is no company server a Hive depends on to exist or to stay in sync.
How it connects
Governance
How a Hive decides things is one of five modes the group picks, and its own chain enforces the threshold once picked.
Group tokens
A Hive can define and issue its own token, with minting that can be routed through the group's governance.
Sharing & permissions
What members can see and do inside a Hive is controlled by the same structural boundaries as membership and governance.