Skip to content

HIVE v1.1.0 — Direct mode

Choose a tag to compare

View all tags
@capybarist capybarist released this 10 Jun 15:31
· 4 commits to main since this release
v1.1.0
435ed01

Direct mode (bee → queen HTTP ingest)

An additive alternative transport for centralized / closed deployments. HIVE_TRANSPORT defaults to p2p — existing nodes and deployments are untouched.

  • Direct transport (bee): HIVE_TRANSPORT=direct + HIVE_QUEEN_URL + HIVE_INGEST_TOKEN — same pipeline (forage → chunk → embed → sign), publish step POSTs gzipped signed batches (≤500) to the queen; no swarm. Whole-batch retry with exponential backoff, safe by deterministic fragment ids.
  • Ingest endpoint (queen): POST /internal/ingest behind HIVE_INGEST_ENABLED + bearer token + HIVE_TRUSTED_BEES ed25519 allowlist; one bad signature rejects the whole batch; LanceDB mergeInsert reports { upserted, unchanged }.
  • HIVE_SWARM=off: fully closed queen — joins no Hyperswarm topic; ingest is its only fragment source.
  • CatalogSource (kind: 'catalog'): authoritative-listing sources with verifiable sweep completeness and content_hash change detection.
  • FragmentV08.meta: extensible signed metadata, stored + returned verbatim.
  • direct.sh: one-command local sandbox (wired queen+bee pair, allowlist handshake automated).
  • /api/status reports transport / ingest_enabled / swarm_enabled; UI badge shows bee · direct / queen · ingest.

Docs: docs/direct-mode.md — contract, idempotency invariant, docker-compose example.
Tests: npm run test:direct -w @hive/api (offline suite) + untouched P2P regression suites.

Assets 2
Loading