@derec-alliance/nodejs 0.0.5 → 0.0.6

package/index.js

@@ -6,12 +6,30 @@ const wasm = require("./derec_library.js");
 const DeRecProtocol = wasm.DeRecProtocolWasm;
 const DeRecProtocolBuilder = wasm.DeRecProtocolBuilder;
 
+// A second `free()`, or one after `build()` consumed the builder, finds the
+// handle already released; it returns instead of passing a null handle to the
+// library, the same as .NET `Dispose` and Go `Close`.
+function releaseOnce(Class) {
+  const release = Class.prototype.free;
+  Class.prototype.free = function free() {
+    if (this.__wbg_ptr !== 0) release.call(this);
+  };
+  Class.prototype[Symbol.dispose] = function dispose() {
+    this.free();
+  };
+}
+
+releaseOnce(DeRecProtocol);
+releaseOnce(DeRecProtocolBuilder);
+
 const SenderKind = Object.freeze({ Owner: 0, Helper: 1, ReplicaSource: 3, ReplicaDestination: 4 });
 
 const ContactMode = Object.freeze({ InlineKeys: 0, HashedKeys: 1, NoKeys: 2 });
 
 const FlowKind = Object.freeze({ Pairing: 0, Discovery: 1, ProtectSecret: 2, VerifyShares: 3, RecoverSecret: 4, Unpair: 5, UpdateChannelInfo: 6, ReplicaDiscovery: 7, UnpairReplica: 8 });
 
+const StatusEnum = Object.freeze({ Ok: 0, Partial: 1, Fail: 2, SizeLimitExceeded: 3, TooFrequent: 4, UnknownSecretId: 5, UnknownShareVersion: 6, DecryptionFailed: 7, VerificationFailed: 8, FormatError: 9, Rejected: 10, IncompatibleParameterRange: 11, UnsupportedTransportProtocol: 12, VersionConflict: 13, ReplicaIdConflict: 14, RequestToClose: 99 });
+
 const primitives = {
   discovery: {
     request: {
@@ -41,7 +59,10 @@ const primitives = {
       produce_pre_pair: wasm.pairing_response_produce_pre_pair,
       extract_pre_pair: wasm.pairing_response_extract_pre_pair,
       process_pre_pair: wasm.pairing_response_process_pre_pair,
+      produce_pre_pair_no_keys: wasm.pairing_response_produce_pre_pair_no_keys,
+      process_pre_pair_no_keys: wasm.pairing_response_process_pre_pair_no_keys,
     },
+    fingerprint: wasm.pairing_fingerprint,
   },
   recovery: {
     request: {
@@ -121,9 +142,15 @@ function channelFilterMatches(filter, id, status, role) {
 
 function advertisedEndpoints(message) {
   if (!message) return [];
-  const offers = message.supported_transports ?? [];
-  if (offers.length > 0) return offers;
-  return message.transport_protocol ? [message.transport_protocol] : [];
+  return message.supported_transports ?? [];
+}
+
+function protocol_version() {
+  return wasm.protocol_version();
+}
+
+function generate_replica_id() {
+  return wasm.generate_replica_id();
 }
 
 function sequentialFailover(dialer) {
@@ -161,6 +188,8 @@ module.exports = {
   primitives,
   channelFilterMatches,
   advertisedEndpoints,
+  protocol_version,
+  generate_replica_id,
   sequentialFailover,
   singleEndpointTransport,
   envelope,
@@ -169,4 +198,5 @@ module.exports = {
   SenderKind,
   ContactMode,
   FlowKind,
+  StatusEnum,
 };

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@derec-alliance/nodejs",
   "description": "Node.js WebAssembly bindings for derec-library, the Rust SDK for the DeRec protocol.",
-  "version": "0.0.5",
+  "version": "0.0.6",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",

package/proto/contact.proto

@@ -68,13 +68,13 @@ package org.derecalliance.derec.protobuf;
 //  against the hash before sending `PairRequestMessage`. The hash binding
 //  gives the OOB-shared contact the same MITM resistance as inline-keys
 //  mode despite the keys traveling over the (unauthenticated) transport.
-//  Because the `PrePair*` messages are plaintext, the `transportProtocol`
+//  Because the `PrePair*` messages are plaintext, the `supportedTransports`
 //  carried in this mode MUST be ephemeral — see the security note on
 //  `PrePairRequestMessage` for the required ephemeral-then-swap discipline.
 //
 // - `NO_KEYS`: all of `mlkemEncapsulationKey`, `eciesPublicKey`, and
 //  `contactBindingHash` are absent. The contact carries only
-//  `channelId`, `nonce`, and `transportProtocol` — small enough to be
+//  `channelId`, `nonce`, and `supportedTransports` — small enough to be
 //  hand-typed or dictated over the phone. There is no cryptographic
 //  binding: the recipient's `PrePairRequest` triggers on-the-fly key
 //  generation on the contact creator, and the returned keys are used
@@ -112,7 +112,7 @@ enum ContactMode {
   // `PrePairRequest` / `PrePairResponse` and verified against the hash.
   HASHED_KEYS = 1;
   // No key material and no hash are inlined. The contact carries only
-  // `channelId`, `nonce`, and `transportProtocol`; the contact creator
+  // `channelId`, `nonce`, and `supportedTransports`; the contact creator
   // generates key material on the fly when the corresponding
   // `PrePairRequest` arrives. Only appropriate when the out-of-band
   // delivery channel is fully trusted, and the channel stays unusable
@@ -190,37 +190,9 @@ message ContactMessage {
   // out-of-band authentication has taken place.
   uint64 nonce = 6;
 
-  // Transport information used to reach the creator of this contact.
-  //
-  // This specifies both:
-  //
-  // - the endpoint to which the first protocol message should be sent
-  // - the transport protocol that determines how that endpoint is interpreted
-  //  and used
-  //
-  // The initiating party uses this field to deliver the initial pairing
-  // request. Subsequent protocol exchanges may continue using the same
-  // transport information or updated transport details, depending on the
-  // protocol and application behavior.
-  //
-  // Deprecated: superseded by `supportedTransports`, which carries every
-  // endpoint rather than one.
-  //
-  // **Reading this field directly is now incorrect.** Its meaning narrowed
-  // from "the endpoint" to "one entry of a list, and possibly absent": a
-  // creator that has moved past this field advertises only
-  // `supportedTransports`. A reader that was correct before this release is
-  // a bug now — it rejects, or fails to reach, a peer that is offering it a
-  // perfectly good endpoint. Resolve both spellings instead of reading
-  // either: `advertised_endpoints()` (Rust and TypeScript),
-  // `AdvertisedEndpoints()` (Go), `AdvertisedEndpoints()` (.NET).
-  //
-  // Senders still populate it: a sender that sets `supportedTransports`
-  // MUST also set this to a single best-compatibility choice, so
-  // implementations predating the list still pair.
-  //
-  // **Scheduled for removal in v0.0.5.**
-  TransportProtocol transportProtocol = 7 [deprecated = true];
+  // Formerly the singular `transportProtocol`, superseded by `supportedTransports`.
+  reserved 7;
+  reserved "transportProtocol";
 
   // Timestamp indicating when the sender created this message.
   //
@@ -243,22 +215,17 @@ message ContactMessage {
   // preference rather than the sender's. The order here expresses
   // availability, not a ranking the recipient must honor.
   //
-  // # Compatibility
-  //
-  // Absent means "only `transportProtocol` is offered", which is how every
-  // implementation predating this field behaves. A sender populating this
-  // list MUST also set `transportProtocol` to a single best-compatibility
-  // choice so those implementations still pair.
+  // A contact MUST carry at least one entry: it is the only way the
+  // recipient learns where to send its first message.
   //
   // # Security
   //
-  // `contactBindingHash` does not cover this field, exactly as it does not
-  // cover `transportProtocol`. An attacker able to rewrite an
-  // out-of-band contact can therefore remove entries. Removing the secure
-  // ones leaves only plaintext, which the recipient's transport policy
-  // refuses unless plaintext has been explicitly opted into. DeRec messages
-  // are signed and encrypted at the application layer on every transport,
-  // so substituting one secure transport for another is not a loss of
-  // confidentiality or authenticity.
+  // `contactBindingHash` does not cover this field. An attacker able to
+  // rewrite an out-of-band contact can therefore remove entries. Removing
+  // the secure ones leaves only plaintext, which the recipient's transport
+  // policy refuses unless plaintext has been explicitly opted into. DeRec
+  // messages are signed and encrypted at the application layer on every
+  // transport, so substituting one secure transport for another is not a
+  // loss of confidentiality or authenticity.
   repeated TransportProtocol supportedTransports = 9;
 }

package/proto/getshare.proto

@@ -70,24 +70,14 @@ message GetShareRequestMessage {
   // - timeout handling
   google.protobuf.Timestamp timestamp = 3;
 
-  // Ephemeral transport endpoint at which the requester wants to receive
-  // the response to *this exchange*, overriding the channel's stored peer
-  // endpoint for this round-trip only.
-  //
-  // See `StoreShareRequestMessage.replyTo` for full semantics.
-  //
-  // Superseded by `replyToTransports`, which carries every endpoint rather
-  // than one. Kept, and still populated with the list's first entry, so
-  // implementations predating that field still receive a reply.
-  // **Scheduled for removal in v0.0.5.** Reading this field directly is now
-  // incorrect — resolve it against `replyToTransports`.
-  optional TransportProtocol replyTo = 4 [deprecated = true];
+  // Formerly the singular `replyTo`, superseded by `replyToTransports`.
+  reserved 4;
+  reserved "replyTo";
 
   // Every ephemeral endpoint the requester wants this exchange's response
   // delivered to, in its own preference order.
   //
-  // See `StoreShareRequestMessage.replyToTransports` for full semantics,
-  // including why this is a new tag rather than a widened `replyTo`.
+  // See `StoreShareRequestMessage.replyToTransports` for full semantics.
   repeated TransportProtocol replyToTransports = 6;
 
   // Identity of the replica-group member this message concerns.

package/proto/pair.proto

@@ -139,33 +139,9 @@ message PairRequestMessage {
   // whether pairing is possible and which parameters to use.
   ParameterRange parameterRange = 7;
 
-  // Transport information for reaching the initiator.
-  //
-  // This specifies:
-  //
-  // - the endpoint where the initiator can receive messages
-  // - the protocol required to deliver those messages
-  //
-  // After pairing, the responder uses this information to send responses
-  // and all subsequent protocol messages to the initiator.
-  // Deprecated: superseded by `supportedTransports`, which carries every
-  // endpoint rather than one.
-  //
-  // **Reading this field directly is now incorrect.** Its meaning narrowed
-  // from "the endpoint" to "one entry of a list, and possibly absent": an
-  // initiator that has moved past this field advertises only
-  // `supportedTransports`. A reader that was correct before this release is
-  // a bug now — it rejects, or fails to reach, a peer that is offering it a
-  // perfectly good endpoint. Resolve both spellings instead of reading
-  // either: `advertised_endpoints()` (Rust and TypeScript),
-  // `AdvertisedEndpoints()` (Go), `AdvertisedEndpoints()` (.NET).
-  //
-  // Senders still populate it: a sender that sets `supportedTransports`
-  // MUST also set this to a single best-compatibility choice, so
-  // implementations predating the list still pair.
-  //
-  // **Scheduled for removal in v0.0.5.**
-  TransportProtocol transportProtocol = 8 [deprecated = true];
+  // Formerly the singular `transportProtocol`, superseded by `supportedTransports`.
+  reserved 8;
+  reserved "transportProtocol";
 
   // Timestamp indicating when this message was created.
   //
@@ -177,8 +153,8 @@ message PairRequestMessage {
   // initiator's own preference order.
   //
   // Same semantics as `ContactMessage.supportedTransports`: the responder
-  // selects by its own preference, and absent means "only
-  // `transportProtocol` is offered".
+  // selects by its own preference, and the list MUST carry at least one
+  // entry.
   repeated TransportProtocol supportedTransports = 10;
 }
 

package/proto/prepair.proto

@@ -41,17 +41,17 @@ package org.derecalliance.derec.protobuf;
 //
 // # Security: transport endpoint is observable
 //
-// Because the envelope is plaintext, the `transportProtocol` field in both
-// `PrePairRequestMessage` and `PrePairResponseMessage` is visible to any
-// passive observer on the network path. The same applies to the
-// `transportProtocol` carried in the `HASHED_KEYS`-mode `ContactMessage`
-// itself if its out-of-band channel can be observed.
+// Because the envelope is plaintext, the endpoints carried in
+// `PrePairRequestMessage` are visible to any passive observer on the
+// network path. The same applies to the `supportedTransports` carried in
+// the `HASHED_KEYS`-mode `ContactMessage` itself if its out-of-band channel
+// can be observed.
 //
 // The protocol relies on this contract from the application to preserve
 // the security guarantees of `HASHED_KEYS` mode:
 //
-// - The `transportProtocol` used during pairing (the one advertised in the
-//  `ContactMessage` and echoed in `PrePairRequestMessage`) MUST be
+// - The endpoints used during pairing (those advertised in the
+//  `ContactMessage` and in `PrePairRequestMessage`) MUST be
 //  ephemeral and short-lived — bound to the pairing attempt, not to the
 //  long-term identity of either peer.
 // - Once pairing completes, the application MUST swap to a long-term
@@ -70,27 +70,9 @@ message PrePairRequestMessage {
   // and the receiver MUST refuse to serve the keys.
   uint64 nonce = 1;
 
-  // Transport endpoint at which the sender expects to receive the
-  // `PrePairResponseMessage`.
-  //
-  // Deprecated: superseded by `supportedTransports`, which carries every
-  // endpoint rather than one.
-  //
-  // **Reading this field directly is now incorrect.** Its meaning narrowed
-  // from "the endpoint" to "one entry of a list, and possibly absent": a
-  // sender that has moved past this field advertises only
-  // `supportedTransports`. A reader that was correct before this release is
-  // a bug now — it rejects, or fails to reply to, a peer that is offering it
-  // a perfectly good endpoint. Resolve both spellings instead of reading
-  // either: `advertised_endpoints()` (Rust and TypeScript),
-  // `AdvertisedEndpoints()` (Go), `AdvertisedEndpoints()` (.NET).
-  //
-  // Senders still populate it: a sender that sets `supportedTransports`
-  // MUST also set this to a single best-compatibility choice, so
-  // implementations predating the list still receive a reply.
-  //
-  // **Scheduled for removal in v0.0.5.**
-  TransportProtocol transportProtocol = 2 [deprecated = true];
+  // Formerly the singular `transportProtocol`, superseded by `supportedTransports`.
+  reserved 2;
+  reserved "transportProtocol";
 
   // Timestamp indicating when this message was created.
   //
@@ -111,22 +93,15 @@ message PrePairRequestMessage {
   // preference rather than the sender's. The order here expresses
   // availability, not a ranking the recipient must honor.
   //
-  // # Compatibility
-  //
-  // Absent means "only `transportProtocol` is offered", which is how every
-  // implementation predating this field behaves. A sender populating this
-  // list MUST also set `transportProtocol` to a single best-compatibility
-  // choice so those implementations still reply.
-  //
-  // At least one of the two MUST be present: a request naming no endpoint
+  // The list MUST carry at least one entry: a request naming no endpoint
   // gives the recipient nowhere to send the response.
   //
   // # Security
   //
   // PrePair traffic is plaintext — no shared key exists yet — so these
-  // endpoints are visible to a passive observer, exactly as
-  // `transportProtocol` already was. The recipient's transport policy still
-  // refuses plaintext entries unless plaintext has been opted into.
+  // endpoints are visible to a passive observer. The recipient's transport
+  // policy still refuses plaintext entries unless plaintext has been opted
+  // into.
   repeated TransportProtocol supportedTransports = 4;
 }
 

package/proto/secretidsversions.proto

@@ -68,24 +68,14 @@ message GetSecretIdsVersionsRequestMessage {
   // - timeout handling
   google.protobuf.Timestamp timestamp = 1;
 
-  // Ephemeral transport endpoint at which the requester wants to receive
-  // the response to *this exchange*, overriding the channel's stored peer
-  // endpoint for this round-trip only.
-  //
-  // See `StoreShareRequestMessage.replyTo` for full semantics.
-  //
-  // Superseded by `replyToTransports`, which carries every endpoint rather
-  // than one. Kept, and still populated with the list's first entry, so
-  // implementations predating that field still receive a reply.
-  // **Scheduled for removal in v0.0.5.** Reading this field directly is now
-  // incorrect — resolve it against `replyToTransports`.
-  optional TransportProtocol replyTo = 2 [deprecated = true];
+  // Formerly the singular `replyTo`, superseded by `replyToTransports`.
+  reserved 2;
+  reserved "replyTo";
 
   // Every ephemeral endpoint the requester wants this exchange's response
   // delivered to, in its own preference order.
   //
-  // See `StoreShareRequestMessage.replyToTransports` for full semantics,
-  // including why this is a new tag rather than a widened `replyTo`.
+  // See `StoreShareRequestMessage.replyToTransports` for full semantics.
   repeated TransportProtocol replyToTransports = 4;
 
   // Identity of the replica-group member this message concerns.

package/proto/storeshare.proto

@@ -131,10 +131,13 @@ message StoreShareRequestMessage {
   // Used for observability, replay detection, and timeout handling.
   google.protobuf.Timestamp timestamp = 7;
 
-  // Ephemeral transport endpoints at which the requester wants to receive
-  // the response to *this exchange*, in its own preference order,
-  // overriding the channel's stored peer endpoints for this round-trip
-  // only.
+  // Formerly the singular `replyTo`, superseded by `replyToTransports`.
+  reserved 8;
+  reserved "replyTo";
+
+  // Every ephemeral endpoint the requester wants this exchange's response
+  // delivered to, in its own preference order, overriding the channel's
+  // stored peer endpoints for this round-trip only.
   //
   // # When to use
   //
@@ -146,45 +149,11 @@ message StoreShareRequestMessage {
   //
   // # Semantics
   //
-  // - Absent (the default): the responder routes to the endpoints stored on
+  // - Empty (the default): the responder routes to the endpoints stored on
   //  its `Channel` record for this `channelId`.
-  // - Present: the responder routes this exchange's response here, and
-  //  leaves the stored endpoints unchanged.
-  //
-  // Superseded by `replyToTransports`, which carries every endpoint rather
-  // than one. Kept, and still populated with the list's first entry, so
-  // implementations predating that field still receive a reply.
-  // **Scheduled for removal in v0.0.5.**
-  //
-  // **Reading this field directly is now incorrect** for the same reason it
-  // is on `transportProtocol`: it is one entry of a list and may be absent.
-  // Resolve it against `replyToTransports` instead.
-  optional TransportProtocol replyTo = 8 [deprecated = true];
-
-  // Every ephemeral endpoint the requester wants this exchange's response
-  // delivered to, in its own preference order.
-  //
-  // # Semantics
-  //
-  // - Empty, and `replyTo` absent: the responder routes to the endpoints
-  //  stored on its `Channel` record for this `channelId`.
-  // - Empty, `replyTo` present: that one endpoint, which is how every
-  //  implementation predating this field asks.
   // - Non-empty: the responder routes the response to any one of these, in
   //  the order given, and leaves the stored endpoints unchanged. Delivery
   //  to any one is success.
-  //
-  // # Why this is a new field rather than a wider `replyTo`
-  //
-  // `replyTo` was singular through 0.0.2. Re-tagging it `repeated` would
-  // have been wire-compatible in the read direction only: protobuf merges a
-  // repeated submessage into a singular reader field-by-field, so a 0.0.2
-  // peer decoding a multi-entry list sees the **last** entry, while the
-  // first entry is what every other compatibility rule in this release
-  // designates as the legacy-readable one. One list cannot be ordered to
-  // satisfy both. A new tag lets the singular field keep meaning exactly
-  // what it did — the same shape `supportedTransports` (contact.proto tag 9)
-  // uses beside `transportProtocol` (tag 7).
   repeated TransportProtocol replyToTransports = 10;
 
   // Identity of the replica that authored this update.

package/proto/unpair.proto

@@ -68,24 +68,14 @@ message UnpairRequestMessage {
   // - timeout handling
   google.protobuf.Timestamp timestamp = 2;
 
-  // Ephemeral transport endpoint at which the requester wants to receive
-  // the response to *this exchange*, overriding the channel's stored peer
-  // endpoint for this round-trip only.
-  //
-  // See `StoreShareRequestMessage.replyTo` for full semantics.
-  //
-  // Superseded by `replyToTransports`, which carries every endpoint rather
-  // than one. Kept, and still populated with the list's first entry, so
-  // implementations predating that field still receive a reply.
-  // **Scheduled for removal in v0.0.5.** Reading this field directly is now
-  // incorrect — resolve it against `replyToTransports`.
-  optional TransportProtocol replyTo = 3 [deprecated = true];
+  // Formerly the singular `replyTo`, superseded by `replyToTransports`.
+  reserved 3;
+  reserved "replyTo";
 
   // Every ephemeral endpoint the requester wants this exchange's response
   // delivered to, in its own preference order.
   //
-  // See `StoreShareRequestMessage.replyToTransports` for full semantics,
-  // including why this is a new tag rather than a widened `replyTo`.
+  // See `StoreShareRequestMessage.replyToTransports` for full semantics.
   repeated TransportProtocol replyToTransports = 5;
 
   // Identity of the replica-group member that initiated this unpair.

package/proto/updatechannelinfo.proto

@@ -17,7 +17,7 @@ package org.derecalliance.derec.protobuf;
 //
 // # Context
 //
-// Both `communication_info` and `transport_protocol` are exchanged at pairing
+// Both `communication_info` and the transport endpoints are exchanged at pairing
 // time only. This message lets either party (Owner or Helper) propagate
 // post-pairing changes without re-pairing.
 //
@@ -31,16 +31,16 @@ package org.derecalliance.derec.protobuf;
 //  stored map with the supplied one." Updates, additions, and deletions
 //  are all expressed by the difference between the receiver's current map
 //  and the supplied one.
-// - `transport_protocol` absent means "do not modify the transport endpoint
-//  stored for the sender." Presence means "the sender's transport endpoint
-//  is now this value." The receiver MUST route subsequent messages on this
-//  channel to the new endpoint, including the
+// - `supported_transports` empty means "do not modify the transport
+//  endpoints stored for the sender." Non-empty means "the sender's transport
+//  endpoints are now these." The receiver MUST route subsequent messages on
+//  this channel to the new endpoints, including the
 //  UpdateChannelInfoResponseMessage for this request.
 //
 // # Endpoint changeover
 //
-// When `transport_protocol` is updated, the receiver sends its response to
-// the new endpoint. The sender's application is therefore responsible for
+// When `supported_transports` is updated, the receiver sends its response to
+// the new endpoints. The sender's application is therefore responsible for
 // ensuring the new endpoint is reachable BEFORE this request is issued, and
 // for keeping the old endpoint operational long enough for in-flight
 // messages from other peers (and any concurrent operations) to drain.
@@ -52,49 +52,20 @@ message UpdateChannelInfoRequestMessage {
   // stored map for this channel. Absence leaves it untouched.
   optional CommunicationInfo communicationInfo = 1;
 
-  // Updated transport endpoint for the sender, or absent to leave unchanged.
-  //
-  // Presence updates both the URI and protocol enum. The receiver routes
-  // the response to this new endpoint.
-  //
-  // Deprecated: superseded by `supportedTransports`, which carries every
-  // endpoint rather than one.
-  //
-  // **Reading this field directly is now incorrect.** Its meaning narrowed
-  // from "the endpoint" to "one entry of a list, and possibly absent": a
-  // sender that has moved past this field announces only
-  // `supportedTransports`. A reader that was correct before this release is
-  // a bug now — it records the wrong address, or none, for a peer that
-  // announced a perfectly good one. Resolve both spellings instead of
-  // reading either: `advertised_endpoints()` (Rust and TypeScript),
-  // `AdvertisedEndpoints()` (Go), `AdvertisedEndpoints()` (.NET).
-  //
-  // Senders still populate it: a sender that sets `supportedTransports`
-  // MUST also set this to a single best-compatibility choice, so
-  // implementations predating the list still learn the new address.
-  //
-  // **Scheduled for removal in v0.0.5.**
-  optional TransportProtocol transportProtocol = 2 [deprecated = true];
+  // Formerly the singular `transportProtocol`, superseded by `supportedTransports`.
+  reserved 2;
+  reserved "transportProtocol";
 
   // Every transport endpoint the sender can now be reached on, in its own
   // preference order, replacing the receiver's stored set for this channel.
   //
   // # Semantics
   //
-  // - Empty, and `transportProtocol` absent: the sender's endpoints are
-  //  left unchanged. An update that changes only `communicationInfo` says
-  //  nothing about transports.
+  // - Empty: the sender's endpoints are left unchanged. An update that
+  //  changes only `communicationInfo` says nothing about transports.
   // - Non-empty: replaces the stored set outright. Unlike a request's
-  //  `replyTo`, this **is** persisted — it is how a peer announces it has
-  //  moved.
-  //
-  // # Compatibility
-  //
-  // Empty with `transportProtocol` present means "only that one endpoint is
-  // offered", which is how every implementation predating this field
-  // behaves. A sender populating this list MUST also set
-  // `transportProtocol` to a single best-compatibility choice so those
-  // implementations still learn the new address.
+  //  `replyToTransports`, this **is** persisted — it is how a peer
+  //  announces it has moved.
   repeated TransportProtocol supportedTransports = 4;
 
   // Timestamp indicating when this message was created.
@@ -112,8 +83,8 @@ message UpdateChannelInfoRequestMessage {
 // On success (`result.status == OK`):
 //
 // - the receiver has persisted the supplied updates
-// - subsequent messages from the receiver MUST use the new endpoint, if
-//  `transport_protocol` was updated
+// - subsequent messages from the receiver MUST use the new endpoints, if
+//  `supported_transports` was updated
 //
 // On failure:
 //

package/proto/verify.proto

@@ -74,24 +74,14 @@ message VerifyShareRequestMessage {
   // - timeout handling
   google.protobuf.Timestamp timestamp = 4;
 
-  // Ephemeral transport endpoint at which the requester wants to receive
-  // the response to *this exchange*, overriding the channel's stored peer
-  // endpoint for this round-trip only.
-  //
-  // See `StoreShareRequestMessage.replyTo` for full semantics.
-  //
-  // Superseded by `replyToTransports`, which carries every endpoint rather
-  // than one. Kept, and still populated with the list's first entry, so
-  // implementations predating that field still receive a reply.
-  // **Scheduled for removal in v0.0.5.** Reading this field directly is now
-  // incorrect — resolve it against `replyToTransports`.
-  optional TransportProtocol replyTo = 5 [deprecated = true];
+  // Formerly the singular `replyTo`, superseded by `replyToTransports`.
+  reserved 5;
+  reserved "replyTo";
 
   // Every ephemeral endpoint the requester wants this exchange's response
   // delivered to, in its own preference order.
   //
-  // See `StoreShareRequestMessage.replyToTransports` for full semantics,
-  // including why this is a new tag rather than a widened `replyTo`.
+  // See `StoreShareRequestMessage.replyToTransports` for full semantics.
   repeated TransportProtocol replyToTransports = 6;
 }