@decentnetwork/peer 0.1.43 → 0.1.45

package/dist/peer.js

@@ -1537,6 +1537,16 @@ export class Peer {
                 if (!opened) {
                     continue;
                 }
+                // De-duplicate. The dual-send path delivers each lossless packet over
+                // BOTH the UDP and relay transports with the SAME packet number, so
+                // without this guard every chat message (and every file-data chunk) is
+                // dispatched — and stored / shown / appended — twice. Drop anything at or
+                // below the receive low-water mark, like toxcore net_crypto drops packets
+                // below buffer_start. Must run BEFORE the nonce advance below so a
+                // duplicate doesn't desync the receive nonce.
+                if (opened.packetNumber < (state.receiveBufferStart ?? 0)) {
+                    continue;
+                }
                 state.peerBaseNonce[state.peerBaseNonce.length - 2] = packet[1];
                 state.peerBaseNonce[state.peerBaseNonce.length - 1] = packet[2];
                 incrementNonce(state.peerBaseNonce);
@@ -2802,9 +2812,23 @@ export class Peer {
                 firstError = error;
             }
         }
-        // Fresh direct path → send over UDP only: no relay fan-out, no
-        // duplicates, no relay backlog. Applies to both data and control.
-        if (udpFresh && udpOk) {
+        // Fresh direct path → send over UDP only — but ONLY for bulk data.
+        // Bulk is high-volume and must avoid relay fan-out / backlog, so once
+        // the direct path is fresh it rides UDP exclusively.
+        //
+        // Low-volume traffic (chat 64 + control keepalives / endpoint offers /
+        // profile) instead ALSO goes over the relay even when the direct path
+        // looks fresh, because `udpFresh` is derived from INBOUND UDP
+        // (lastUdpRecvMs) and inbound reachability does NOT imply outbound
+        // reachability. On a symmetric / CGNAT peer (e.g. cellular T-Mobile
+        // 172.56.x) the peer's pings keep arriving — so udpFresh stays true —
+        // while our packets to the source port we observed are silently
+        // black-holed: the peer never received from us on that port, so its NAT
+        // has no inbound mapping for our endpoint. Returning UDP-only here would
+        // fire chat into a dead endpoint forever — the exact "peer can send to us
+        // but can't receive from us" one-way failure. net_crypto dedups by packet
+        // number, so the extra relay copy is harmless for sparse chat / control.
+        if (isBulkData && udpFresh && udpOk) {
             return;
         }
         // Tier 2: TURN relay (tokyo) — a fast (~280ms) stable fallback that

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@decentnetwork/peer",
-  "version": "0.1.43",
+  "version": "0.1.45",
   "description": "Pure TypeScript port of Elastos Carrier (toxcore-derived) P2P messaging. DHT, onion routing, TCP relay, FlatBuffers app payloads, Express offline relay. Wire-compatible with iOS Beagle and the Carrier C SDK.",
   "type": "module",
   "main": "./dist/index.js",