EIN Relay Node: Difference between revisions
(Phase F3: tier-1 backbone (12 new pages + Resonant Finder rewrite with Layer 1/2/3 separation); unified spine with {{Psi-claim}} + {{Psi-tech-maturity}}) |
(Phase G: stamp page as defensive publication) |
||
| Line 1: | Line 1: | ||
The '''EIN Relay Node''' is a deployable [[Earth Intelligence Network|EIN]] participant — a small server (or appliance) that stores, forwards, signs, and serves EIN content. Relay Nodes are the redundant substrate that lets the EIN survive without any single operator's infrastructure and that lets the [[Tho'ra Clan]]'s public data (Schumann feed, magnetometer summaries, threat-class catalog, Resonant Card revocation log, AI Nursery Vault audit chain) propagate independently of corporate platforms. | The '''EIN Relay Node''' is a deployable [[Earth Intelligence Network|EIN]] participant — a small server (or appliance) that stores, forwards, signs, and serves EIN content. Relay Nodes are the redundant substrate that lets the EIN survive without any single operator's infrastructure and that lets the [[Tho'ra Clan]]'s public data (Schumann feed, magnetometer summaries, threat-class catalog, Resonant Card revocation log, AI Nursery Vault audit chain) propagate independently of corporate platforms. | ||
{{Defensive-publication}} | |||
== Overview == | == Overview == | ||
Latest revision as of 20:47, 11 May 2026
The EIN Relay Node is a deployable EIN participant — a small server (or appliance) that stores, forwards, signs, and serves EIN content. Relay Nodes are the redundant substrate that lets the EIN survive without any single operator's infrastructure and that lets the Tho'ra Clan's public data (Schumann feed, magnetometer summaries, threat-class catalog, Resonant Card revocation log, AI Nursery Vault audit chain) propagate independently of corporate platforms.
Defensive publication notice. This page is published as a defensive publication. Its publication date and content are intended to constitute prior art under 35 U.S.C. § 102 and equivalent international patent law, for the purpose of preventing the patenting of the disclosed subject matter and its obvious extensions by third parties. Reuse is governed by Project:Licensing (CC BY-SA 4.0) for written content; hardware designs disclosed herein are additionally licensed under CERN-OHL-S v2; reference software is GPL-3.0-or-later.
Overview
An EIN Relay Node:
- Stores a configurable set of EIN topics (e.g. Schumann feed, threat catalog, Vault audit chain, revocation logs).
- Forwards signed updates to peer nodes via gossip protocol over TCP/IP, Tor, or Psi Mesh gateway.
- Serves a public read-only HTTP(S) endpoint for human and software consumers.
- Verifies every signature against the Clan's published trust roots and rejects unsigned or invalid content.
- Logs tamper-evident receipt of each topic update.
A small constellation of Relay Nodes is what turns a single Clan publication into something the wider world can rely on.
Theoretical Basis
- 2e7d32;"
Epistemic status: [[
|
Gossip protocols with signed content are a mature distributed-systems substrate (Nostr, ATProto, Hypercore, Reticulum precedents).
- 2e7d32;"
Epistemic status: [[
|
Multi-jurisdiction, multi-operator relay networks are dramatically more censorship-resilient than centralized publication.
- 1565c0;"
Epistemic status: [[
|
The federated EIN architecture preserves Clan public data under loss of any single operator. This is testable by drilled outages.
Subsystems and BOM
Mk0 (target ≤ \$80, "Relay-in-a-box")
- Raspberry Pi 4 / 5 (4 GB) — \$50
- 256 GB USB-SSD — \$25
- PoE+ HAT (optional) — \$20
- Enclosure + cables — \$10
Software: containerized EIN relay daemon, Tor + clearnet endpoints, signed-content verification, automatic peer discovery. One-command bring-up.
Mk1 (small server, target ≤ \$500)
Mini-PC class (Intel N100 / Ryzen 5 mobile) with 1 TB NVMe and 16 GB RAM. Runs full Clan topic set + general EIN gossip + Tor hidden service.
Mk2 / Mk3
Mk2: rack-mounted relay with redundant storage, BGP peering, hardware HSM for signing; deployed at allied data centers. Mk3: federated relay network across allied Earth Alliance facilities with documented SLA.
Build Notes
- Sign before serving. Every published topic carries Clan signature; relays verify before storing.
- Multiple transports. Clearnet + Tor + (where available) Psi Mesh gateway. Each operator-jurisdiction-appropriate.
- No central control plane. Relays discover peers via gossip; the Clan publishes trust roots, not operational orders.
- Documented topic taxonomy. Clan topics are namespaced and versioned; subscribers select.
Safety and Ethics
- No personal data without explicit consent of the data subject.
- Relay operators publish their relay's existence and topic set; no covert relays under the Clan name.
- Operators may withdraw their relay at any time; the network is voluntary.
- Abuse handling: published content moderation rules in the topic taxonomy; relays may choose topic subsets.
Maturity
Maturity (Mk0 → Mk3)
See Tho'ra Tech Maturity Levels for the convention.
| Mark | Phase | Status | Confidence | Evidence Base | Next Validation Gate |
|---|---|---|---|---|---|
| Mk0 | Cosplay-type | Complete | 100% (symbolic) | Ritual + build practice | User satisfaction |
| Mk1 | Prototype | Active | — | — | — |
| Mk2 | Test-type | Planned | — | — | — |
| Mk3 | Production | Projected | — | — | — |
Failure Modes and Mitigations
- Single-relay loss. → Federation; no single relay holds unique data.
- Signature compromise. → Trust-root rotation procedure; emergency revocation path.
- Censorship of clearnet endpoint. → Tor hidden service mirror; Psi Mesh gateway fallback.
- Abuse via topic spam. → Per-topic moderation rules; relay opt-in per topic.
- Resource exhaustion. → Per-topic storage caps; tiered topic priorities.
- Operator burnout. → Mk0 is "set and forget"; documentation supports unattended operation.
