@calimero-network/mero-js 23.6.0 → 23.8.1

package/dist/index.mjs

@@ -5925,6 +5925,10 @@ function teeRoleOf(row) {
 function pickExecutingRelay(relays) {
   return relays.find((r) => r.canExecute && r.relayUrl !== null && r.executorAccount !== null) ?? null;
 }
+var ACCOUNT_HEX = /^[0-9a-f]{64}$/;
+function accountHexOrNull(value) {
+  return typeof value === "string" && ACCOUNT_HEX.test(value) ? value : null;
+}
 var AccountHaRefusedError = class extends HTTPError {
   constructor(code, status, statusText, url, headers, bodyText) {
     super(status, statusText, url, headers, bodyText);
@@ -6315,7 +6319,9 @@ var CloudClient = class {
     return (body.relays ?? []).map((row) => ({
       peerId: String(row.peer_id ?? ""),
       relayUrl: row.relay_url ?? null,
-      fresh: row.fresh === true
+      fresh: row.fresh === true,
+      executorAccount: accountHexOrNull(row.executor_account),
+      assigned: row.assigned === true
     }));
   }
   /**
@@ -6393,7 +6399,11 @@ var CloudClient = class {
    * Pass merod's response object straight through. The cloud accepts core's
    * `signerPublicKey`/`signedPayload` casing as well as snake_case, so there is
    * no re-keying step — and getting that wrong used to surface as a `422`
-   * naming three missing fields.
+   * naming three missing fields. Passing it whole also carries the `founding`
+   * and `credential` merod attaches: the cloud accepts a namespace proof only
+   * from a node of the account that founded the namespace, checked with those
+   * two, and only when that account is linked to this login. A node that
+   * predates them, or an admin that did not found the namespace, gets a `422`.
    *
    * Idempotent for the same account. A namespace already claimed by someone
    * else is a `409`; a replayed proof nonce is a `403`.