Skip to main content

Becoming a Core Protocol Contributor

This section is for systems engineers, compiler writers, protocol researchers, formal methods practitioners, and developers who want to contribute to the core of Cardano: not build applications on top of it.

This is a parallel track, not a destination you reach after shipping a dApp. If your background is in programming languages, distributed systems, cryptography, or formal verification, this is your entry point.

Start Here: The Cardano Blueprint

Before choosing a language path, read the Cardano Blueprint.

The Blueprint is implementation-independent documentation explaining how the Cardano protocol works: node architecture, ledger state machine, consensus mechanics, and networking: written in accessible Markdown with diagrams and test data, not dense academic LaTeX. It applies equally to every language path below. Reading it first will make every codebase significantly easier to navigate.

Choose Your Path

LanguageNode / ProjectStageGuide
Haskellcardano-node: the reference implementationProductionHaskell Core Contributor
RustAmaru (Pragma), Pallas / Dolos (TxPipe)Active developmentRust Core Contributor
GoDingo (Blink Labs)Testnet / active developmentGo Core Contributor

None of these paths requires the others as a prerequisite. Choose based on your background and the kind of work you want to do.

Shared Resources

These apply to all three paths:

Contributing to Protocol Direction

Core protocol work doesn't require writing code to participate. Intersect's Technical Steering Committee (TSC) working groups shape which CIPs get prioritized and which protocol changes get funded: across all node implementations.

See Contributing to Intersect for how to find and join working groups. See the Intersect Membership Guide for membership access.

For contributing to this documentation site, see the Contributing Guidelines.