Cardano Proposes Block Producer Software Registry

Josh Marchand don propose one shared registry wey go allow Cardano explorers track which node clients dey produce blocks. Dem submit am on September 24, CIP-0203 build on top signaling method wey Dingo and Gerolamo don already dey use. Dem still dey review the proposal.

Software Identifiers for Cardano Blocks

Each node client wey participate go receive one identifier wey link to im name, maintainers and public repository. Block producers go record that identifier inside the block header, so explorers fit match am to the registered software.

The proposal dey use the existing minor protocol version field, wey no dey determine whether block valid. This one allow identification without changing consensus rules or needing hard fork. Extra space go fit hold information like software versions, using formats wey the respective development teams document.

Identifiers wey dem retire go still remain inside the registry and dem no go reassign am inside the same scheme, to preserve the meaning of historical blocks.

Measuring Cardano Client Diversity

Node clients na the software implementations wey allow computers validate network data and produce blocks. As independently developed clients begin enter use, explorers need one consistent way to measure how dem dey contribute to block production.

The earlier CPS-0036 problem statement identify fragmented signaling conventions as obstacle to that measurement. The authors describe client diversity as relevant measure of network resilience. Without agreed format, explorers and researchers must interpret each implementation own conventions separately.

CIP-0203 go provide that common format. According to Marchand, the core identifier go allow observers calculate each client share of produced blocks regardless of any extra data wey e publish.

From Registry to Explorer Support

Participation go be voluntary, and e include explicit option to withhold software information. Statistics go reflect producers self-reported identifiers, without independent verification of the programs wey dem run.

Reviewers still dey discuss how tools suppose decode optional information like version numbers. The proposal leave those formats to individual teams but e require make dem document the meaning.

The proposed path to Active status require adoption from both sides: at least two independent clients wey dey produce blocks with registered identifiers for mainnet or public testnet, and at least one public explorer or dashboard wey dey decode those identifiers.