@terminal3/t3n-sdk 0.3.0 → 0.4.0

package/dist/index.d.ts

@@ -591,19 +591,30 @@ declare function eth_get_address(privateKey: string): string;
  * from `${baseUrl}/status` on first invocation and caches the encoded
  * response for subsequent calls.
  *
- * @param baseUrl - Optional explicit node URL. If omitted, falls back to the
- *                  current environment default (see `getNodeUrl()`).
+ * @param baseUrl - **Required**. The node URL whose `/status` endpoint should
+ *                  serve the ML-KEM public key. Must be the same URL the
+ *                  T3nClient is constructed with — otherwise the handshake
+ *                  encrypts to one node and sends ciphertext to another.
+ *
+ *                  Was optional in 0.3.x, where omitting it caused the lazy
+ *                  fetch to silently fall back to `NODE_URLS[currentEnv]` and
+ *                  hit the wrong node. Three downstream consumers (demo.ts,
+ *                  t3-apps dev wallet hooks, t3n-mcp session manager) all
+ *                  hit this trap before we tightened the type.
  */
-declare function createMlKemPublicKeyHandler(baseUrl?: string): GuestToHostHandler;
+declare function createMlKemPublicKeyHandler(baseUrl: string): GuestToHostHandler;
 /**
  * Create Random handler backed by crypto.getRandomValues
  * Note: The Rust Vec<u8> type serializes as an array of bytes, not a base64 string
  */
 declare function createRandomHandler(): GuestToHostHandler;
 /**
- * Create the default handler set required by the T3n handshake
+ * Create the default handler set required by the T3n handshake.
+ *
+ * @param baseUrl - **Required**. Forwarded to `createMlKemPublicKeyHandler`
+ *                  so the lazy /status fetch hits the right node.
  */
-declare function createDefaultHandlers(baseUrl?: string): GuestToHostHandlers;
+declare function createDefaultHandlers(baseUrl: string): GuestToHostHandlers;
 
 /**
  * Cryptographic utilities for T3n SDK