Weave documentation
Weave Dht Daemon

Protocol

The daemon mounts the following HTTP routes alongside its DHT node:

HTTP endpoints

The daemon mounts the following HTTP routes alongside its DHT node:

MethodPathPurpose
GET/healthzProcess health response
GET/readyzCurrent readiness handler response
GET/metricsPrometheus metrics
GET/v1/admin/store/metricsStore metrics
GET/v1/admin/storeStore state
GET/v1/node/infoNode identity, listener, peer, and store summary
GET/v1/did/resolve?did=...Resolve an envelope/document with local-cache fallback
POST/v1/did/publishPublish a JSON body containing an envelope
GET/v1/peersPeer inspection

There is no generic /rpc put/get endpoint. Use the configured authentication mode for protected operations. Publication calls envelope validation, limits the encoded envelope to 256 KiB, and the router additionally limits request bodies to 512 KiB. A dummy proof or placeholder key is not a valid DID envelope.

The health/readiness handlers currently return static ok responses; they do not independently demonstrate DHT peer convergence, successful persistence, or cross-node resolution. Inspect node/store state and verify the intended lookup path separately.

Source: network/weave-dht-daemon/src/main.rs, especially run_http, resolve_handler, and publish_handler. Envelope contract.

On this page