Release Notes - v0.208.1

v0.208.1

Title: Strengthen protocol validation and compatibility

Version: v0.208.1

This release improves connection reliability, separates proposal validation concerns, strengthens transaction submission checks, expands era compatibility, and standardizes gOuroboros branding.

Features

• Improved connection reliability by processing incoming messages in smaller steps, applying byte limits to each protocol state, admitting peer initiated and pipelined messages only when permitted, and checking message submission request counts and windows. Deployments can set MaxUnacknowledgedMessageIDs; it defaults to 100.
• Refined proposal handling so generic checks and decoding accept protocol-only proposals whose system tags fall outside ledger-state length or ASCII rules. ByronUpdateProposal.Validate now checks only metadata shape and no longer enforces system-tag length or ASCII rules. For software-update registrations, callers that previously relied on Validate must invoke ValidateSystemTags at the appropriate point with ledger state.

Compatibility and Breaking Changes

• Strengthened transaction submission reliability by checking transaction IDs, matching requests with replies, validating transaction eras and body sizes, allowing the stated tolerance for advertised sizes, preserving request ordering, controlling concurrent work, and respecting shutdown state.
• Verified compatibility with 12-field Dijkstra and Leios extended headers, corrected the required transaction body CBOR keys from Shelley through Babbage, and encoded an empty metadata set as {}.

Additional Changes

• Standardized gOuroboros branding across agent guides and corrected the README logo alt text.

Release: v0.208.1

Compare: v0.208.0…v0.208.1

---

Docs authored by Doc Holiday