Henosis

Open governance for communities, NGOs and movements

A voice for every person. Not for every coin.

Henosis lets a community prove that each member is one real human and vote in secret, without anyone learning who voted how. No names, no numbers, no profiles. Decisions are taken where they belong: as close to the people as possible.

There is no token. Ever.

Who it is for How it works

Drag to turn. Click a node or a module below.

Who it is for

Any group that needs to decide together without exposing its members. Henosis grew out of the Shib community and was first conceived as the governance layer for SHIB OS; it is built for everyone.

  • Minorities and persecuted communities

    Organise and vote without a membership list that could be seized. Only proofs go on chain, never personal data. Nobody, not even the organisers, learns who voted how.

  • NGOs and aid organisations

    Let the people you serve decide for themselves: record mutual aid as karma, allocate scarce goods by a verifiable lottery, and keep decisions at the local level where the knowledge is.

  • Diaspora and cross-border communities

    Scopes from local to global let a community spread across countries decide at each level, with a passport of any issuing state as proof of personhood.

  • Movements that refuse money power

    One human, one vote. Influence cannot be bought, staked, delegated to a whale or inherited through a token. The rules are open, the code will be public, and there is no owner.

How it works

A layered design. Four core modules sit on a scope registry and a constitution; an off-chain AI layer can only advise.

M1 Identity
The phone reads the chip of a passport or ID card over NFC and proves in zero knowledge, on the phone, that the document is genuine. On chain there is only the proof, a nullifier and a commitment. No name, number or date of birth leaves the phone. Other admission paths (vouching by verified members, presence events) are designed for people without an electronic document.
M2 Karma
Karma records help and community service. It is granted only when both sides confirm, capped per person and epoch, and decays over time. It cannot be transferred, sold or delegated. Externally only threshold proofs are shown, never an individual history.
M3 Lottery
One base entry per person, extra tickets from karma, a public randomness beacon and a verifiable draw. Used for allocations between equally qualified people and for choosing reviewers and verifiers at random.
M4 Voting
Members join an epoch group with their identity and vote with a group membership proof. One nullifier per member and proposal stops double voting; a vote can be changed while the window is open. Release 1 brings a commit-reveal secret ballot; later stages add encrypted tallies and a design in which a bought or coerced vote cannot be proven.
M5 Scopes
A scope has a parent, an identity group, its own parameters and a list of competences. Competences move only upwards, ceded from below, and can never be taken from above. Four guarantees cannot be configured away: one person one vote, anonymity of the vote, unilateral exit, and decisions only about oneself.
M6 Constitution
Fundamental rights are immutable in the protocol. Other rules change only with a supermajority across several scopes and a time lock. A randomly selected, time-limited body can pause single modules in an emergency; it can never move funds or change rules.
M7 AI advisory
The advisory layer runs off-chain with models from different operators, at least one with open weights. Each side of a decision gets its own argument; facts with sources are kept apart from evaluation. Prompts, model versions and outputs are hashed and referenced on chain. No keys, no execution rights, no payment access.
M8 Operations
Threshold signatures or MPC for every operator role, external audits and formal verification before mainnet, upgrades only through the constitutional procedure with a time lock. Signature and proof systems are swappable so post-quantum schemes can be adopted. Users need no gas: a relayer funded from a community pool submits transactions.

Money stays separate

Henosis has no token, no fee, no treasury and no owner. Voting weight can never be bought, staked or delegated to the richest wallet. That is a rule of the protocol, not a promise.

A community that uses Henosis may still need money: for donations, for paying people who do the work, for aid that must reach someone quickly. It can use a currency of its choice for that, including a cryptocurrency on a chain such as Shibarium, as a second option next to bank money. That choice is the community's own, taken through its own governance, and it never touches the vote.

Open to other chains

Henosis is built first for Shibarium. Its interfaces are chain-neutral and are proposed as a draft ERC, so any chain that shares the decentralised vision of Ryoshi and the cypherpunks, with no owner, no gatekeeper and privacy by default, can run it.

Results are read across chains by state proofs, never by asset bridges or relayers with a veto.

Principles

  1. P1

    One human, one vote

    Voting weight is tied to a verified person, never to token ownership.

  2. P2

    Influence is not for sale

    Karma and lottery tickets are soulbound; there are no transferable governance tokens.

  3. P3

    Subsidiarity

    Every decision sits at the lowest level that can resolve it.

  4. P4

    Homeostasis instead of maximisation

    Caps, decay and saturation are mandatory parameters of every module.

  5. P5

    Decentralisation and redundancy

    No single keys, no central authority, several independent operators.

  6. P6

    Privacy by default

    Only proofs and nullifiers go on chain, never personal data in plain text.

  7. P7

    Constitution before majority

    Fundamental rights are not subject to a vote.

  8. P8

    AI advises, never decides

    AI components hold no keys and have no execution rights.

  9. P9

    Shibarium, SHIB OS and Zama first

    Every technology choice checks a Shibarium-, SHIB OS- or Zama-based solution first.

  10. P10

    Whoever bears the risk decides

    A risk that falls on one person is that person's choice; a risk that falls on everyone is decided by binding governance.

  11. P11

    No home-made cryptography

    Only standardised or publicly reviewed building blocks, combined, implemented and audited externally.

Fixed rules

  • No admin keys, no owner in any contract. Upgrades only through the constitutional procedure.
  • No token-weighted voting, no staking or validator coupling, no burn logic or fee hooks in the protocol.
  • No bridges as a required component. Results are read across chains by state proofs, not by asset bridges or relayers with a veto.

Status October 2026

ModuleState
M1 IdentityBuilt Zero-knowledge registration for the common passport signature schemes, chip authentication upgrades, certificate registries with time lock and objection. Phone app in development.
M4 Voting, stage 1Built Anonymous membership per epoch, proposals and revoting; a cleartext-tally and an FHE-encrypted variant (Zama). Next: commit-reveal secret ballot.
M5 Scope registryPrototype
M2, M3, M6, M7, M8Design only No code yet.

Not ready for real use

  • Demonstrated on a testnet only: the full flow (register, join, propose, vote, tally) ran on Celo Sepolia with synthetic documents.
  • All proving keys so far come from local single-party setups. A multi-party ceremony is still needed.
  • No external audit yet, no relayer and no released phone app.
  • Nothing is deployed on Shibarium mainnet or on the Puppynet testnet. Mainnet only after an external audit.

First use case: a non-binding, person-based shadow vote for the Shib community, until the community chooses otherwise.

Roadmap to Release 1

  1. Nov 2026

    Chain-scoped nullifier (v2), all instances re-keyed, blind review

  2. Nov 2026

    Voting v2: commit-reveal secret ballot, abstention, enforced quorum, rules changeable by vote, private join

  3. Nov–Dec 2026

    Reference relayer, key hosting, app end-to-end on testnet

  4. Dec 2026

    Freeze, audit package, audits start

  5. Jan–Feb 2027

    Audit remediation, trusted-setup ceremony

  6. Feb–Mar 2027

    Release 1 on Shibarium mainnet, ERC submitted, code public

After Release 1: encrypted tally (FHE), karma, lottery, constitution and AI advisory.

Documentation

Contact

General

[email protected]

Security

Found a vulnerability? Please write to [email protected] before disclosing it publicly. See security.txt.