Module hashiverse_server 

Top-level server orchestrator

HashiverseServer is the server-binary analogue of [hashiverse_lib::client::hashiverse_client::HashiverseClient]: the single struct that wires together every subsystem the node needs to operate and hands them to the inbound-request handler.

What it owns:

• Identity — a persisted [hashiverse_lib::tools::server_id::ServerId] is loaded from the crate::environment::environment::Environment or minted fresh with proof-of-work on first start.
• Transport — built via a TransportFactory (TLS in production, plain TCP or in-memory in tests) and bound to the port from crate::server::args::Args.
• DHT — a crate::server::kademlia::kademlia::Kademlia populated from the persisted peer buckets at startup and kept up to date by the handler dispatch.
• Caches — crate::server::post_bundle_caching and crate::server::post_bundle_feedback_caching plus per-connection reply-salt and heal caches, all backed by moka with TTL/TTI eviction.
• Replay protection — a short-window set of observed request salts so an attacker can’t replay a valid signed request back at us.

Structs

HashiverseServer