AsyncAPI channel · EigenLayer · EigenDA Streaming Surface

disperser.Disperser/DisperseBlobAuthenticated

Bidirectional streaming gRPC method. The client opens the stream with a DisperseBlobRequest, the disperser replies with a BlobAuthHeader containing a challenge parameter, the client signs and returns an AuthenticationData message, and the disperser closes by sending a DisperseBlobReply with the assigned request_id.

Open source AsyncAPI → All EigenLayer channels EigenLayer provider profile
Provider: EigenLayer AsyncAPI: v3.0.0 Spec: EigenDA Streaming Surface Operations: 2 Messages: 2

Channel address

disperser.Disperser/DisperseBlobAuthenticated

Operations

send
sendAuthenticatedRequest
Client-to-disperser frames on the DisperseBlobAuthenticated stream.
receive
receiveAuthenticatedReply
Disperser-to-client frames on the DisperseBlobAuthenticated stream.

Messages

AuthenticatedRequest
Client frame on the DisperseBlobAuthenticated stream.
Content-Type:
AuthenticatedReply
Disperser frame on the DisperseBlobAuthenticated stream.
Content-Type:

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.