From 59e889254b1fda2dcc8e3e6d596635d1b77f589f Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 17:44:03 +0000 Subject: transport: wire versions spoken side by side A build speaks wire versions OLDEST to VERSION and writes each node the newest both speak (wire::choose), as the node's SPEAKS says; the oldest until it says. The identity layer keeps that per address (Book::speaks): a SPEAKS from an address sets it for the address, and for every address of the node proven there, and a new address of a node takes it over. Paths encodes each message for an address in its version (Transport::encode_in; Transport::encode is the newest). So that two nodes know what the other speaks once they have proven themselves to each other, before any other message goes between them, a SPEAKS goes ahead of every WHO and ME, and WHO and ME are read in every version from 52 on (wire::PROOFS): their tags and layout never change. Without that, a node whose oldest version is past the other's couldn't read its proofs, and the two would never get to the handshake that says what each speaks. A SPEAKS naming no version this build speaks is logged as a message of another version is, naming the node to upgrade, the versions as ranges. A 0.0.1 node takes a SPEAKS from an address not yet proven for any other message from there: it drops it, and asks WHO. This build speaks 52 alone, so nothing it sends changes but the SPEAKS ahead of the proofs. A release adding a version encodes and decodes the older ones from their own, frozen, types. --- CHANGELOG.md | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'CHANGELOG.md') diff --git a/CHANGELOG.md b/CHANGELOG.md index 2d531c8..7754a3d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,14 @@ it from the release before ([`docs/operations.md`](docs/operations.md), ## Unreleased +* A node speaks several wire versions side by side and writes each peer the newest both + speak, as the peer's SPEAKS says; SPEAKS goes ahead of each WHO and ME now, and WHO + and ME read alike in every version. So a release adding a wire version and keeping + the older rolls out node by node ([`docs/operations.md`](docs/operations.md), + [Upgrading](docs/operations.md#upgrading); + [`src/transport/wire.rs`](src/transport/wire.rs), + [`src/transport/identity.rs`](src/transport/identity.rs)). + * `scripts/release` makes a release: it checks the tree, says from the last release's wire versions, Automerge and revisions whether it rolls out node by node, and commits and tags it, pushing nothing ([`docs/development.md`](docs/development.md), -- cgit v1.3.1