Cybersecurity & Defence · Cyber Defence & Resilience

M30 · Fault-Tolerant Mesh

Keeps a network of D-COS nodes reliable: connectivity, revocation of compromised nodes and shared decisions.

Real Implemented

Level 1 · At a glance

Keeps a network of D-COS nodes reliable: connectivity, revocation of compromised nodes and shared decisions.

Benefits: A compromised node can be isolated quickly and safely.

Example of use: Find the nodes whose loss would split the network, and revoke a suspicious node.

Key capabilities

  • Network connectivity and critical points
  • Revocation of compromised nodes
  • Signed propagation to other nodes
  • Quorum decisions with signed votes
Level 2 · Technical detail

Fault-Tolerant Mesh. Epistemic ledger (registro_epistemico, registered only when the device has a ledger key) and contracts m30_mesh (15: connectivity, articulation points, critical bridges, min-cut via max-flow, load analysis, LAN transport limits with anti-replay, node revocation authorised by M01 with partition-aware, fail-secure propagation), m30_integra (5: real propagation of signed revocation packets to peers, M32/M17/M29 integrations) and m30_consenso (8: quorum consensus over signed votes from an M01-governed validator registry; crash-fault tolerant, detects equivocation; NOT open-membership BFT). A real multi-node mesh is not configured or verified here.

Prerequisites

Licence mesh_resiliente. Paired nodes for a real mesh.

Declared limits

Consensus assumes a correct validator registry (not open-membership BFT); no real multi-node mesh verified in this campaign.

Owner's note

The code of every module is fully present and the modules have been verified. Any status shown as “not verified” or “partially implemented” derives solely from test gaps in the laboratory environment (for example the physical absence of a device during the test campaign), not from software limitations. Declared simulations (decision D-24) are deliberate design choices.

Interconnections

The interconnections shown are documented functional relationships (code reuse and data flows) or derive from the architectural role; they are an editorial reconstruction.

Official texts: D-COS NEXUS V130 MASTERWORK Official Documentation and official V130 presentation (November 2026).

This module is part of the integrated ecosystem

D-COS NEXUS does not sell separate modules: every capability lives inside the ecosystem. Contact us to see how it applies to your context.