charon-primary-sources-2026-05-12

Charon primary sources

Collected: 2026-05-12 UTC

Primary sources reviewed

• https://github.com/ObolNetwork/charon
  • Official Charon repository
  • Used to confirm Charon’s positioning as the distributed-validator middleware client rather than a generic staking app
• https://raw.githubusercontent.com/ObolNetwork/charon/main/README.md
  • Official repo README
  • Used to confirm the project’s self-description as an HTTP middleware client for Ethereum staking, the cluster model, launchpad linkage, and operator-facing docs surface
• https://docs.obol.org/learn/charon/intro
  • Official Charon introduction and architecture overview
  • Used to confirm the scheduler / fetcher / consensus / validator-API / partial-signature / aggregation / broadcast workflow and the BFT cluster assumptions
• https://raw.githubusercontent.com/ObolNetwork/charon/main/docs/architecture.md
  • Official architecture document from the Charon repo
  • Used to confirm the cluster and node workflow diagrams, duty-as-unit-of-work framing, batching logic, and the detailed component split
• https://docs.obol.org/advanced-and-troubleshooting/security/overview.md
  • Official Obol security overview
  • Used to confirm Charon-specific audit and assessment references plus operational-security posture around the middleware
• https://github.com/ObolNetwork/distributed-validator-specs
  • Official distributed-validator specifications repository
  • Used to confirm that Charon sits beside a broader spec surface for QBFT consensus, partial-signature exchange, DKG, cluster files, validator API behavior, and duty scheduling
• https://raw.githubusercontent.com/ObolNetwork/distributed-validator-specs/main/README.md
  • Official specs README
  • Used to map the subspecs and verify that the source of truth includes formal protocol definitions, not just product docs

Notes

• Charon clears the intake bar because it exposes a distinct validator-coordination control plane inside the broader Obol stack.
• The key analytical split is between validator-client UX on one side and the hidden coordination layer on the other: duty timing, unsigned-data consensus, validator-API mediation, partial-signature transport, and threshold aggregation.
• No standalone whitepaper surfaced in this pass; the strongest material was architecture-heavy docs plus the public repository and specs.