Network architecture
Spectre. Skyzai’s DLT.
Spectre is Skyzai’s distributed ledger technology, in development. Its design brings adaptive communication and shared event ordering together, while keeping permissions and authority distinct.
Connections have different shapes
One to one, one to many, many to one and many to many describe which endpoints communicate. They do not establish the truth of a message or who is allowed to read it.
Adaptive paths
Spectre’s proposed transport layer uses peer discovery, gossip and routing information such as latency and reliability to adapt communication paths. Efficient delivery must not be mistaken for proof, consent or consensus safety.
Shared event ordering
Spectre’s agreement layer is intended to establish a consistent order of ledger events. Its integration with adaptive routing, failure assumptions and safety properties require specification and verification; routing optimisation alone does not establish consensus guarantees.
Permission and settlement stay separate
Nexus governs which context a participant may receive. An available route does not override that boundary. Likewise, a connection or a consensus result does not authorize a payment or establish a commercial obligation.
The public material describes research and implementation targets. It does not establish an operational mesh, mainnet or settlement network. Each integration must identify its actual rail, responsibilities and evidence.
Technical details
Hashgraph lineage & upstream licensing
Spectre’s design builds on Hashgraph’s gossip-about-gossip and virtual voting, with additional routing telemetry. Spectre is the Skyzai DLT name; Hashgraph describes the underlying approach.
The upstream Hiero consensus-node implementation is licensed under Apache 2.0. Any Spectre release reusing that code must meet the applicable licence conditions, including licence copies, modification notices and relevant attribution/NOTICE requirements. The exact reused components and release compliance remain to be verified.