@decentnetwork/lan 0.1.37 → 0.1.38

package/dist/config/loader.js

@@ -9,16 +9,32 @@ const DEFAULT_CONFIG_FILE = resolve(DEFAULT_CONFIG_DIR, "config.yaml");
 // Mirrored from peer SDK's legacy-bootstraps.mjs
 // 45.207.220.155 omitted — observed timing out repeatedly during testing,
 // causing relay#2 to flap which knocks the friend connection offline.
+// Ordered with US relays first so a US↔US session (the common case)
+// doesn't land on a China relay just because it was first in the list.
+// Observed in the wild: both Vultr (US public IP) and a Mac (US
+// residential) connected to 47.100.103.201 (Alibaba Cloud Shanghai)
+// as their sole TCP relay — every packet between them transited
+// China, ~600ms RTT, and net_crypto handshakes often dropped because
+// the path was lossy. Reordering puts AWS US-East/US-West first so
+// the SDK's "connect to top-N relays" path naturally picks closer
+// nodes. The China + Singapore nodes stay in the list as fallback for
+// peers actually in those regions.
 const DEFAULT_BOOTSTRAP_NODES = [
-    { host: "47.100.103.201", port: 33445, pk: "CX1XH419p4xJ5SV4KvDxBeKYSRdMJW9QpdWJY8owUxHd" },
-    { host: "154.64.235.176", port: 33445, pk: "GdNtV2N74fZnLjhH7NhQ18nGdxb1k8jRM9dQaK7WnxmL" },
-    { host: "52.83.171.135", port: 443, pk: "5tuHgK1Q4CYf4K5PutsEPK5E3Z7cbtEBdx7LwmdzqXHL" },
-    { host: "52.83.191.228", port: 33445, pk: "3khtxZo89SBScAMaHhTvD68pPHiKxgZT6hTCSZZVgNEm" },
+    // US-East — closest for typical North-American peers.
     { host: "13.58.208.50", port: 33445, pk: "89vny8MrKdDKs7Uta9RdVmspPjnRMdwMmaiEW27pZ7gh" },
     { host: "18.216.102.47", port: 33445, pk: "G5z8MqiNDFTadFUPfMdYsYtkUDbX5mNCMVHMZtsCnFeb" },
     { host: "18.216.6.197", port: 33445, pk: "H8sqhRrQuJZ6iLtP2wanxt4LzdNrN2NNFnpPdq1uJ9n2" },
+    // US-West.
     { host: "54.193.141.205", port: 33445, pk: "7TfZWZNV8vnBxxWzJXuvKgX2QyKkLpg2oXx3LQ5tg8LW" },
+    // Unknown / global.
+    { host: "154.64.235.176", port: 33445, pk: "GdNtV2N74fZnLjhH7NhQ18nGdxb1k8jRM9dQaK7WnxmL" },
+    // Asia-Pacific (Singapore + China). Kept as fallback so peers
+    // actually in CN/SG can use a nearby relay. Peers in the US should
+    // not be hitting these for normal traffic.
     { host: "52.74.215.181", port: 33445, pk: "Xv6d34WaUw9bPn7YihzVAFw7D2igbQJZ3jwmzzfYVFV" },
+    { host: "47.100.103.201", port: 33445, pk: "CX1XH419p4xJ5SV4KvDxBeKYSRdMJW9QpdWJY8owUxHd" },
+    { host: "52.83.171.135", port: 443, pk: "5tuHgK1Q4CYf4K5PutsEPK5E3Z7cbtEBdx7LwmdzqXHL" },
+    { host: "52.83.191.228", port: 33445, pk: "3khtxZo89SBScAMaHhTvD68pPHiKxgZT6hTCSZZVgNEm" },
 ];
 const DEFAULT_EXPRESS_NODES = [
     { host: "lens.beagle.chat", port: 443, pk: "ECbs4GxwGzxGerNkmqDJFibEmevu8jAXqAZtikccvD95" },
@@ -153,7 +169,16 @@ export class ConfigLoader {
             },
             carrier: {
                 dataDir: config.carrier?.dataDir || defaults.carrier.dataDir,
-                bootstrapNodes: config.carrier?.bootstrapNodes || defaults.carrier.bootstrapNodes,
+                // ALWAYS use the latest DEFAULT_BOOTSTRAP_NODES, even if the
+                // user's config.yaml has an older list. Bootstrap nodes are
+                // shared public infrastructure — operators who want a private
+                // mesh point at their own dora (which handles peer discovery
+                // entirely); they don't customize Carrier bootstraps. Without
+                // this auto-update, a stale config.yaml from an early install
+                // pins a US peer to a China relay forever even after we
+                // reorder defaults, and every install upgrade keeps the bad
+                // first-relay landing pattern.
+                bootstrapNodes: defaults.carrier.bootstrapNodes,
                 expressNodes: config.carrier?.expressNodes || defaults.carrier.expressNodes,
             },
             network: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@decentnetwork/lan",
-  "version": "0.1.37",
+  "version": "0.1.38",
   "description": "Private virtual LAN for self-hosted services and AI agents, built on Elastos Carrier. NAT-traversal, name service, ACL, all over a peer-to-peer mesh — no public IP required.",
   "type": "module",
   "main": "./dist/index.js",