White Paper

Roles in the Marketplace

Module Developers

Neighbourhoods provides developers a pathway to experiment with Holochain development in a meaningful way. By creating small, pluggable modules for the low-code marketplace, developers can iterate on ultra-slim stacks with and for early web 3.0 adopters. They can do all this without having to create a company of their own or spend time “white labeling” a platform per community.
Developers can
  • take advantage of Holochain’s open source libraries.
  • integrate components of rep_lang into Rust modules.
  • earn credits for modules used by specific neighbourhoods.

Community Activators

Community activators are those seeking generic tools to promote group coordination, resource sharing, and the advancement of common interest, whatever that may be, in their communities. An activator may be a leader or a whole group acting together to bundle tools with intentionally designed reputation, culture, guidelines, entry criteria, and cross-neighbourhood data porting.
Community activators can
  • use and contribute to libraries containing useful ways to calculate reputation, foster engagement, incent behavior that benefits the collective, and penalize bad actors.
  • localize sense-making of members’ actions.
  • build bridges between neighbourhoods to multiply the utility of the reputation scores of their neighbourhood.


Members of specific neighbourhoods benefit from the advantages associated with decentralized web technology. They are the sole holders of the sensitive data they generate across all neighbourhoods, evading centralized surveillance and hacks that target central data stores. Additionally, they can leverage reputation from one community to facilitate activity in another.
Users can
  • participate in the design of the reputation systems they opt into (assuming this is coordinated by community activators).
  • contest and revoke data pertaining to their own reputation by re-calculating scores based on their perspective.
  • enjoy a community-focused web experience designed with data sovereignty and user/collective autonomy in mind.