Skip to main content

Sidecar Transport Interfaces

Home · Generic Index · Chain Overlays

This document captures the transport layer between block builders and the sidecar in credible-sdk/crates/sidecar and credible-layer-besu-plugin.

Transport Topology​

Notes:

  • Besu selects HTTP or gRPC based on plugin configuration and available endpoints.
  • Shadow driver uses gRPC streams to replay blocks into the sidecar.
  • Both transports ultimately enqueue events into the same sidecar engine.
  • Health endpoints are intended for external monitoring, not used by the Besu plugin.
  • The Linea sequencer stack config uses gRPC endpoints in credible-sdk/docker/maru-besu-sidecar/config/linea-besu-sequencer/sequencer-credible-grpc.config.toml.

JSON RPC Flow (HTTP)​

gRPC Streaming Flow​

Key code paths:

  • HTTP transport: credible-sdk/crates/sidecar/src/transport/http/
  • gRPC transport: credible-sdk/crates/sidecar/src/transport/grpc/
  • Besu plugin transports: credible-layer-besu-plugin/src/main/java/net/phylax/credible/transport/