Pulse hash
Deterministic epoch coordination without a central clock.
SOVEREIGN LAYER 1 / TEMPORAL HARMONIC CONSENSUS
A Substrate-based L1 research architecture coordinating validators through deterministic time windows, distributed physical entropy, reputation dynamics and quorum finality.
At every slot, the protocol reasons about its pulse, entropy root, validator matrix and peer topology as one global network state.
Deterministic epoch coordination without a central clock.
Latency, drift, jitter and physical telemetry aggregation.
Stake, liveness, eligibility and reputation state.
Network reachability and active connection graph.
Ωₜ = (Pₜ, Eₜ, Vₜ, Nₜ)Every state transition must resolve against the same coordinated view.
Network jitter, clock drift and validated telemetry contribute to a distributed entropy root.
Validator stake, uptime and reputation are evaluated against the current pulse threshold.
The proposer commits pulse hash, entropy root, state root and parent hash.
Eligible validators replay deterministic runtime execution and sign the result.
A block finalizes after a greater-than-two-thirds eligible quorum accepts the state transition.
Sliding windows widen under anomalous delay conditions rather than forcing unsafe timing assumptions.
Orbital validator eligibility can incorporate altitude, Doppler shift, attenuation and line-of-sight state—turning measured conditions into verifiable scheduling inputs.
Eₜ = H(L ∥ D ∥ O ∥ Sᵗᵉˡ)L: latency variance · D: clock drift · O: jitter · S: orbital telemetry
PULSE · ENTROPY · VALIDATOR · FINALITY
BYZANTINE · DRIFT · DOUBLE PROPOSAL · SPOOF
INK! SMART-CONTRACT PATH
LOCAL · DOCKER · KUBERNETES BLUEPRINTS
Rust modules, simulator, telemetry oracle, visual dashboard and deployment blueprints exist in the repository.
400 ms finality and 48k+ TPS are design targets requiring reproducible public testnet benchmarks.
Flight hardware, frequency coordination, radiation testing and hosted-payload qualification remain milestone work.
The updated filing and development guide makes security a release gate rather than a later audit. These controls are commitments for production readiness; they are not presented as completed certification.
Critical source changes require verified signing and protected developer authentication.
Production validators are designed for private addressing and encrypted links to explicitly trusted peers.
Administrative, treasury and validator authority is kept outside application processes and online operator consoles.
Runtime, networking and storage dependencies remain inside the audit scope—not assumed safe because they are upstream.
Versioned runtime upgrades require explicit authorisation, reproducible artefacts and rollback planning.
Consensus, cryptography and custom runtime logic require external security review before any production mainnet claim.
Explore the thermal, power, communications, shielding and capital architecture behind the orbital data-centre thesis.
Operate the original PoP model, inspect the optional ARSE gate and compare the controlled benchmark outputs in the primary simulator platform.
Open simulator platform ↗