Enhance UPlanet documentation by adding details for the Twin-Key exte…

…nsion, including SSSS-based authentication, geographic key delegation, and smart contract integration. Update event types and clarify implementation processes, increasing the total synchronized event types from 18 to 21.

10000-analytics-extension.md

@@ -4,6 +4,8 @@
 
 This NIP defines a standardized event kind (`kind: 10000`) for sending analytics data as NOSTR events. This allows analytics to be stored on decentralized NOSTR relays instead of centralized servers, providing users with control over their data and enabling queryable, verifiable analytics.
 
+**Both encrypted and unencrypted analytics use the same kind 10000.** The encryption status is determined by the content field and tags. Encrypted analytics have encrypted content (NIP-44) and may include `["t", "encrypted"]` tag.
+
 ## Motivation
 
 Traditional analytics systems rely on centralized servers that collect user data without user control. By using NOSTR events for analytics:
@@ -190,3 +192,4 @@ Analytics events can be queried using standard NOSTR filters:
 - [NIP-101](101.md): DID Document
 - [UPLANET_EXTENSIONS.md](UPLANET_EXTENSIONS.md): UPlanet NIP Extensions Overview
 
+

101-n2-constellation-sync-extension.md

@@ -10,7 +10,7 @@ This document describes the **N² (N-squared) constellation synchronization prot
 
 ## Overview
 
-The N² protocol extends [NIP-101](101.md) with a **peer-to-peer relay synchronization mechanism** that creates a "constellation" of interconnected Astroport nodes. Each relay automatically syncs **18 specific event kinds** across the network, ensuring data redundancy and censorship resistance.
+The N² protocol extends [NIP-101](101.md) with a **peer-to-peer relay synchronization mechanism** that creates a "constellation" of interconnected Astroport nodes. Each relay automatically syncs **21 specific event kinds** (including NIP-58 badges) across the network, ensuring data redundancy and censorship resistance.
 
 ## Motivation
 
@@ -115,7 +115,7 @@ Each Astroport node maintains a constellation registry:
       "umap": "43.60,1.44"
     }
   ],
-  "sync_event_kinds": [0, 1, 3, 5, 6, 7, 21, 22, 30023, 30024, 30312, 30313, 30500, 30501, 30502, 30503, 30800]
+  "sync_event_kinds": [0, 1, 3, 5, 6, 7, 8, 21, 22, 30008, 30009, 30023, 30024, 30312, 30313, 30500, 30501, 30502, 30503, 30800]
 }
 ```
 
@@ -199,7 +199,7 @@ Location: `~/.zen/tmp/${IPFSNODEID}/constellation.json`
     }
   ],
   "sync_config": {
-    "event_kinds": [0, 1, 3, 5, 6, 7, 21, 22, 30023, 30024, 30312, 30313, 30500, 30501, 30502, 30503, 30800],
+    "event_kinds": [0, 1, 3, 5, 6, 7, 8, 21, 22, 30008, 30009, 30023, 30024, 30312, 30313, 30500, 30501, 30502, 30503, 30800],
     "sync_interval": 900,
     "retry_attempts": 3,
     "retry_backoff": "exponential"