fiber-network-primary-sources-2026-05-11

Fiber Network primary sources

Collected: 2026-05-11 UTC

Primary sources reviewed

• https://fiber.chainbound.io/
  • Official Fiber landing page
  • Used to confirm project identity and current product framing
• https://fiber.chainbound.io/docs/intro/
  • Official introduction / architecture overview
  • Used to confirm the global node mesh, private internal network, execution- and consensus-layer connectivity, and the source-latency / target-latency framing
• https://fiber.chainbound.io/docs/use-cases/
  • Official use-case documentation
  • Used to confirm the target user set (searchers, builders, validators, HFT firms, researchers), mempool / payload streaming claims, transaction broadcast path, and FiberBoost / FiberGuard positioning
• https://fiber.chainbound.io/docs/fiberdb/
  • Official indexing / analytics documentation
  • Used to confirm the centralized observation pipeline, ClickHouse-backed storage, message-observation schema, and the distinction between Fiber-origin and p2p-origin observations
• https://fiber.chainbound.io/docs/usage/json-rpc/
  • Official interface documentation
  • Used to confirm Ethereum-style subscription interfaces for block headers and pending transactions and to ground the project as an API-facing integration layer
• https://chainbound.io/
  • Official company site
  • Used to confirm Chainbound’s broader positioning around optimized infrastructure and networking for Ethereum
• https://raw.githubusercontent.com/chainbound/fiber-proto/main/README.md
  • Public proto repository README
  • Used to confirm published protobuf definitions for the Fiber gRPC API and the existence of supported client implementations
• https://raw.githubusercontent.com/chainbound/fiber-ts/main/README.md
  • Public TypeScript client README
  • Used to confirm external client integration for transaction streams, execution payloads, beacon blocks, and transaction submission

Notes

• Fiber’s key mechanism is not only faster message delivery. It is the packaging of geographically distributed p2p visibility, private rebroadcast, and propagation analytics into a single API-mediated service layer.
• FiberDB matters because it reveals an additional control surface beneath the latency pitch: whoever operates the observation layer gets privileged visibility into origin geography, propagation timing, and public-versus-private transaction paths.
• Validator services such as FiberBoost and FiberGuard make Fiber useful as more than a searcher feed; they push the project into the broader validator-performance and execution-supply-chain cluster.
• This entry belongs in the active corpus because it gives a cleaner comparison point for low-latency infrastructure than generic mempool API labels and helps separate transport, observation, and rebroadcast power from later builder / proposer commitment layers.