yakmesh 1.5.0 → 1.5.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -0,0 +1,45 @@
|
|
|
1
|
+
# Yakmesh v1.5.0 - Network Identity Unification
|
|
2
|
+
|
|
3
|
+
**🦬 Yakmesh v1.5.0 is here!**
|
|
4
|
+
|
|
5
|
+
This release introduces **Network Identity Unification** - a fundamental improvement to how nodes identify themselves and verify they're running the same code.
|
|
6
|
+
|
|
7
|
+
## 🔑 What's New
|
|
8
|
+
|
|
9
|
+
### Network Identity Unification
|
|
10
|
+
Node IDs now contain TWO components:
|
|
11
|
+
- **Network Name** - Derived from codebase hash (SAME for all nodes on network)
|
|
12
|
+
- **Instance ID** - Derived from public key (UNIQUE per node)
|
|
13
|
+
|
|
14
|
+
Format: `node-[network-name]-[instance-id]`
|
|
15
|
+
Example: `node-grid-carbide-reveal-pq-QHZx`
|
|
16
|
+
|
|
17
|
+
**Why this matters:**
|
|
18
|
+
✅ Nodes running identical code share the same network name
|
|
19
|
+
✅ Visual verification: same network name = same code = can trust peer
|
|
20
|
+
✅ Each node still has a unique instance identifier
|
|
21
|
+
✅ Human-readable verification phrases for extra confirmation
|
|
22
|
+
|
|
23
|
+
### Automatic Port Fallback
|
|
24
|
+
No more "port in use" crashes! If default ports (3000, 9001) are occupied, the node automatically finds the next available port.
|
|
25
|
+
|
|
26
|
+
### Process Management Script
|
|
27
|
+
New `scripts/start.sh` for proper background process management:
|
|
28
|
+
```bash
|
|
29
|
+
./scripts/start.sh start # Start in background
|
|
30
|
+
./scripts/start.sh stop # Clean shutdown
|
|
31
|
+
./scripts/start.sh restart # Stop + start
|
|
32
|
+
./scripts/start.sh status # Check if running
|
|
33
|
+
./scripts/start.sh logs # View logs
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
## ⚠️ Breaking Change
|
|
37
|
+
Existing `node-key.json` files will trigger identity regeneration on first v1.5.0 startup. This is expected - the new format ensures network name derivation from codebase hash.
|
|
38
|
+
|
|
39
|
+
## 📦 Install/Upgrade
|
|
40
|
+
```bash
|
|
41
|
+
npm install yakmesh@1.5.0
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
---
|
|
45
|
+
🔗 https://yakmesh.dev | 💬 Discord: https://discord.gg/8mSPfbJB8N
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
🦬 Yakmesh v1.5.0 Released
|
|
2
|
+
|
|
3
|
+
Network Identity Unification - nodes now share network names when running identical code.
|
|
4
|
+
|
|
5
|
+
New ID format: node-[network-name]-[instance-id]
|
|
6
|
+
|
|
7
|
+
• Same network name = same codebase = can peer
|
|
8
|
+
• Automatic port fallback
|
|
9
|
+
• Process management script
|
|
10
|
+
|
|
11
|
+
npm install yakmesh@1.5.0
|
|
12
|
+
|
|
13
|
+
https://yakmesh.dev
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
🦬 Yakmesh v1.5.0: Network Identity Unification
|
|
2
|
+
|
|
3
|
+
Node IDs now tell you if peers run the same code:
|
|
4
|
+
|
|
5
|
+
node-grid-carbide-reveal-pq-QHZx
|
|
6
|
+
^^^^^^^^^^^^^^^^^ unique
|
|
7
|
+
network name instance
|
|
8
|
+
|
|
9
|
+
✅ Same network name = same codebase = trustable peer
|
|
10
|
+
✅ Auto port fallback when ports busy
|
|
11
|
+
✅ Process management script included
|
|
12
|
+
|
|
13
|
+
Breaking: Nodes regenerate identity on first run (expected)
|
|
14
|
+
|
|
15
|
+
npm install yakmesh@1.5.0
|
|
16
|
+
|
|
17
|
+
#PostQuantum #P2P #DecentralizedWeb #OpenSource
|
package/package.json
CHANGED