What happened

The Ouroboros Leios prototype 2026w30 adds an optional LeiosKey to StakePoolParams. The field carries a BLS12381 verification key and proof of possession, creating a place for BLS key material in a stake pool’s registration data.

The Dijkstra pool_registration_cert CDDL has been extended with the same optional field. The related cardano-cli Dijkstra stake-pool registration-certificate command now accepts --bls-signing-key-file.

Why it matters

This is a concrete change to the pool-certificate surface on the Leios and Dijkstra track. The record frames it as plumbing that stake pool operators may eventually need for signing endorser blocks under Leios consensus.

Compatibility is preserved at this stage: a pool does not need to add the field for an existing registration to remain valid. The release notes describe the keys as possible but not utilized yet, so the change is a structural step rather than an active pool-operator requirement.

What to watch

The next useful receipt is evidence that the optional LeiosKey is actually used, together with changes to the current insecure key-derivation shortcut. Separately, accepted-versus-rejected tx-firehose dashboard results may show how Leios throughput testing is being measured, although the supplied record reports no throughput number.

The wider feed is entirely development-lane activity. It contains no observed market, governance, security, adoption, or mainnet signal for this date.

What to watch

Watch for a prototype update that uses the registered BLS keys, replaces the insecure derivation shortcut, or reports accepted-versus-rejected throughput results.

Sources and limits

Upstream references and independent checks

Digest dated 2026-07-25 · upstream model claude-sonnet-4-6. Direct links are matched to all 1 upstream source IDs.

  1. 1
    Prototype 2026w30Direct upstream source · c9bcfc975b4e9af154cc614ee9214b6d0400d304
Continue reading
  1. 1

This Research brief was generated by Terra from a dated upstream research digest. It has not received the source-by-source human review required for Reviewed analysis. Material limit: This is prototype and testnet development, not a mainnet ledger change; the BLS keys are unused, the current derivation shortcut is still insecure, and the record provides one approved source.