@calimero-network/mero-js 19.11.0 → 19.13.0

package/dist/index.mjs

@@ -1378,6 +1378,20 @@ var AdminApiClient = class {
       )
     );
   }
+  /**
+   * Name a device of this account, for a listing to render.
+   *
+   * Run on the node holding the account root to name any device; a paired
+   * node is accepted only for that device's own id.
+   */
+  async labelAccountDevice(deviceId, request) {
+    return unwrap(
+      await this.httpClient.put(
+        `/admin-api/account/devices/${encodeURIComponent(deviceId)}/label`,
+        request
+      )
+    );
+  }
   /**
    * Every device of this account, as this node sees them - its own included.
    *
@@ -5072,6 +5086,61 @@ var CloudClient = class {
     const challenge = await this.getRoutingChallenge(namespaceId);
     return routingProofHeaders(challenge, this.routingCredential);
   }
+  /**
+   * Ask the cloud for a challenge bound to one ACCOUNT.
+   *
+   * Public and unauthenticated like {@link getRoutingChallenge}: an account id
+   * is `H(genesis(root_pk))` and travels in the clear in every device-link op,
+   * so naming one here reveals nothing and authorises nothing. MDMA re-derives
+   * the account from the certificate and refuses a mismatch.
+   */
+  async getAccountRelaysChallenge(accountId) {
+    const body = await this.request("GET", `/api/cloud/accounts/${encodeURIComponent(accountId)}/challenge`, {
+      anonymous: true
+    });
+    return {
+      accountId: String(body.account_id ?? accountId),
+      nonce: String(body.nonce ?? ""),
+      expiresAtMs: Number(body.expires_at_ms ?? 0)
+    };
+  }
+  /**
+   * Which relays serve this account — the bootstrap, and nothing more.
+   *
+   * A device holding a certificate can resolve a namespace it can *name*
+   * ({@link getNamespaceRouting}) and can ask a node it can *reach* what its
+   * account belongs to. It starts with neither. This closes that one gap.
+   *
+   * **It does not return namespaces, deliberately.** The node answers that from
+   * the governance DAG, scoped to the calling account: log in at one of these
+   * relays with an account proof and read its namespace listing. A cloud-side
+   * copy would be a second source of truth built from rows that linger for an
+   * account which left a namespace.
+   *
+   * So the sequence is: this → log in at a relay → ask it what you are in.
+   *
+   * Proven with the **device certificate**, not a cloud session, so it needs a
+   * `routingCredential` and throws without one rather than returning an empty
+   * list — "you configured no credential" and "you have no relays" are
+   * different answers and must not look alike.
+   */
+  async getAccountRelays(accountId) {
+    if (!this.routingCredential) {
+      throw new Error(
+        "getAccountRelays needs a routingCredential: construct the client with the device certificate and its signing secret, since this read is proven by the device, not by a session."
+      );
+    }
+    const challenge = await this.getAccountRelaysChallenge(accountId);
+    const body = await this.request("GET", `/api/cloud/accounts/${encodeURIComponent(accountId)}/relays`, {
+      anonymous: true,
+      headers: await routingProofHeaders(challenge, this.routingCredential)
+    });
+    return (body.relays ?? []).map((row) => ({
+      peerId: String(row.peer_id ?? ""),
+      relayUrl: row.relay_url ?? null,
+      fresh: row.fresh === true
+    }));
+  }
   /**
    * The node to send a signed join to, chosen from those an invitation names.
    *