Expand description
§Top-level client API
The one thing every external consumer of hashiverse-lib ends up holding: a
HashiverseClient instance. The server binary’s cache role, the WASM browser client,
the Python wrapper, and the integration-test harness all build on top of this struct.
HashiverseClient wires together the rest of the client module — peer tracking,
post/feedback bundle management, timelines, the meta-post system, the key locker — and
exposes the small set of verbs a social-network client actually performs:
- submit posts, submit feedback, fetch URL previews, fetch trending hashtags;
- walk per-user / per-hashtag / per-mention timelines;
- manage the logged-in account (via
crate::client::key_locker); - read and update the profile (
crate::client::meta_post).
Every dependency that varies by environment (clock, network, PoW engine, storage, key
locker) is injected through crate::tools::runtime_services::RuntimeServices and
pluggable traits so the same struct works unchanged on native, in the browser (WASM),
and in deterministic in-memory integration tests.
Structs§
- Hashiverse
Client - The top-level client API for participating in a hashiverse network.