ciris-edge

What it is and what it does

ciris-edge is the transport substrate of the CIRIS Epistemic Web, a Rust crate that replicates signed claims (one of 14 envelope kinds) between federation peers over multiple mediums: Reticulum mesh networks, HTTPS, or packet radio. It enforces two core principles: fail-secure (missing keys or unresolved consent deny access rather than degrade silently) and integrity through structure (privacy and authenticity are properties the wire format cannot violate).

The package sits between host application code and ciris-persist, handling cryptographic attribution of inbound frames at the wire before any handler processes them, consent-gated routing for attestations, and anti-entropy replication across peer cohorts. Every claim's scope (self, family, community, affiliations, species, biosphere, or federation) resolves to a projection (SelfOwn, Cohort, or Global) that determines how it replicates. The library is not a sidecar but an embedded transport layer; key seeds never cross the FFI boundary, and verification happens before any application code runs.

Use it for:

• Build a federated mesh network where claims replicate between peers with cryptographic attribution and consent-based access control.
• Integrate CIRIS Epistemic Web transport into applications requiring fail-secure, structure-enforced privacy and authenticity guarantees.
• Deploy hybrid transport topologies combining Reticulum mesh, HTTPS, and packet radio for resilient claim distribution.
• Implement anti-entropy replication for distributed attestation and trace storage across a federation of peers.
• Enforce consent-gated fan-out of claims where recipients must hold both infra:serve capability and producer consent grants.

Worth the install?

AI-flagged interpretation of the facts on this page — verify before relying

A Rust-based transport and replication layer for the CIRIS Epistemic Web that moves signed envelopes between federation peers over Reticulum mesh, HTTPS, or packet radio, with cryptographic attribution and consent-based access control enforced at the wire before any handler sees data.

Yes, if you are building on the CIRIS stack and need federated transport with cryptographic attribution and consent-based routing. The package is actively maintained, has no known vulnerabilities, and is production-ready for CEG-native transport. The AGPL-3.0-or-later license requires open-source compliance; proprietary projects should verify licensing compatibility. Medium install friction (Rust wheel, Python 3.10+ required) is acceptable for projects already committed to CIRIS.

Install

ciris-edge on PyPI

pip install ciris-edge

uv add ciris-edge

poetry add ciris-edge

Installing ciris-edge

Before you install

Active maintenance with a recent release (17 days old). Medium install friction due to the Rust-compiled wheel; requires Python 3.10 or later and depends on ciris-persist. Suitable for projects already committed to the CIRIS stack.

License in practice

Licensed under AGPL-3.0-or-later, which requires derivative works and modifications to be open-sourced under the same license. Suitable for open-source projects; proprietary applications would need explicit licensing negotiation.

Quickstart

pip install ciris-edge

from ciris_edge import Transport
# Register handlers and initialize transport for federation peers
transport = Transport()

Requires Python 3.10 or later; ciris-persist must be installed and configured for key and attestation storage.

Verify before relying

• Whether the package provides Python bindings directly or requires FFI setup for the Rust crate.
• Specific API surface and handler registration patterns beyond the Transport trait abstraction.
• Performance characteristics and throughput limits for different transport mediums (Reticulum vs. HTTPS vs. packet radio).
• Deployment requirements for the anti-entropy replication engine and state machine reconciliation.

Package facts

Evidence: ciris_edge-15.0.0-cp310-abi3-macosx_11_0_arm64.whl

Tags

More Networking packages