Genesis Mesh
Genesis Mesh is a protocol for sovereign communities to establish, delegate, recognize, and revoke trust across organizational boundaries. It gives AI agents, edge systems, and distributed infrastructure a portable trust fabric: cryptographic identity, signed attestations, delegated authority, cross-sovereign recognition, revocation propagation, and auditable trust state — without a central authority.
Status
Genesis Mesh 1.0 is ready for an independently operated pilot. The surfaces
listed as stable in the public contract
follow DEPRECATION_POLICY.md for the whole 1.x line,
and upgrades from 0.59 onward are rehearsed in CI. Independent federation in
production is not yet proven: a second independently implemented sovereign and
an operator outside Genesis Core are pending and expected from the pilot.
Installation
pip install genesis-mesh
Requires Python 3.12 or later.
The Network Authority and the gateway also ship as signed container images,
ghcr.io/genesismeshlabs/genesis-mesh and
ghcr.io/genesismeshlabs/genesis-mesh-gateway, for linux/amd64 and
linux/arm64. Verify them before deploying: see
Container Images.
Quick start
# Initialize keys, genesis block, and CLI config (run once).
genesis-mesh init
# Start the Network Authority.
genesis-mesh na start
# In a second terminal — create an invite and join.
INVITE_TOKEN=$(genesis-mesh admin invite --role anchor)
genesis-mesh join --na http://127.0.0.1:8443 --token "$INVITE_TOKEN"
# Inspect trust state.
genesis-mesh status
Or run the full local smoke test in one command:
genesis-mesh dev up
Trust API (v0.52.0+)
The Network Authority exposes all stable protocol operations over HTTP — agreement negotiation, boundary decisions, trust evidence, selective disclosure, consensus proofs, and data-usage intents. SDK clients use these endpoints rather than reimplementing the cryptography.
Full HTTP reference: docs/api/trust-http.md
Documentation
Full documentation, operator guides, protocol RFCs, and example walkthroughs:
Contributing
See CONTRIBUTING.md for development setup, branch naming, commit style, and the protocol-change process.
Security
Vulnerability reports: github.com/GenesisMeshLabs/genesismesh/security/advisories/new
See SECURITY.md for the threat model and disclosure policy.
License
1 maintainer
Metadata
1 maintainer
Release files for genesis-mesh 1.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| genesis_mesh-1.7.0.tar.gz | 678.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| genesis_mesh-1.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.5 MB
Release files / genesis_mesh-1.7.0.tar.gz
| Download URL | genesis_mesh-1.7.0.tar.gz |
|---|---|
| Size | 678.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eb7d07466debcbaf3b789a97493e2784b13052298d6495750056d6f9b92b640a
|
|
BLAKE2b-256 checksum How to use checksums |
5c8fa52722ffe25c09e12d9f90093cbf82052165d794887081d8968e1622d699
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency logRelease files / genesis_mesh-1.7.0-py3-none-any.whl
| Download URL | genesis_mesh-1.7.0-py3-none-any.whl |
|---|---|
| Size | 835.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a3ba90da28173f3926b25dc3fd25999245b02d3112f10f451f3aa6d6d6d34992
|
|
BLAKE2b-256 checksum How to use checksums |
ac5fe757df0403c573d739a0f614a45cc0415363c1219f3350da369fa7761fe1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency log
