@calimero-network/mero-js 23.6.0 → 23.8.1

package/dist/admin-api/admin-types.d.ts

@@ -1714,6 +1714,20 @@ export interface IssueOwnershipProofResponseData {
     signedPayload: string;
     /** Base64 64-byte ed25519 signature. */
     signature: string;
+    /**
+     * Namespace proofs only: what the namespace id was derived from. Not signed;
+     * the id commits to it. With {@link credential}, it is what lets the cloud
+     * check that the signer is a node of the account that FOUNDED the namespace
+     * (mdma refuses a namespace proof without both). Absent on nodes that predate
+     * it, and on context proofs.
+     */
+    founding?: NamespaceFounding;
+    /**
+     * Namespace proofs only: hex borsh `AccountProof<DeviceCert>` — the node's join
+     * credential, whose account root certifies `signerPublicKey`. See
+     * {@link founding}.
+     */
+    credential?: string;
 }
 export interface CreateGroupInvitationRequest {
     expirationTimestamp?: number;

package/dist/cloud/cloud-client.d.ts

@@ -176,6 +176,21 @@ export interface CloudAccountRelay {
     peerId: string;
     relayUrl: string | null;
     fresh: boolean;
+    /**
+     * The relay's own account id: 64 lowercase hex, the executor a delegated
+     * write through this relay names.
+     *
+     * Null when the server did not say (older servers omit it) or sent anything
+     * that is not 64 lowercase hex — an executor that cannot be named is the
+     * same as none, and a malformed one would only fail later, at the node.
+     */
+    executorAccount: string | null;
+    /**
+     * True when the cloud has just assigned this relay to an account that had
+     * none (the assignment is sticky); false for relays the account already
+     * used, and on older servers that omit the field.
+     */
+    assigned: boolean;
 }
 export interface CloudNamespaceNode {
     peerId: string;
@@ -656,7 +671,11 @@ export declare class CloudClient {
      * 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`.

package/dist/cloud/cloud-client.js

@@ -66,6 +66,10 @@ function teeRoleOf(row) {
 export function pickExecutingRelay(relays) {
     return (relays.find((r) => r.canExecute && r.relayUrl !== null && r.executorAccount !== null) ?? null);
 }
+const ACCOUNT_HEX = /^[0-9a-f]{64}$/;
+function accountHexOrNull(value) {
+    return typeof value === 'string' && ACCOUNT_HEX.test(value) ? value : null;
+}
 /**
  * The cloud's refusals of {@link CloudClient.enableHaAsAccount} that a
  * person can do something about. Both are `409`s with `{"error": code}`.
@@ -497,6 +501,8 @@ export class CloudClient {
             peerId: String(row.peer_id ?? ''),
             relayUrl: row.relay_url ?? null,
             fresh: row.fresh === true,
+            executorAccount: accountHexOrNull(row.executor_account),
+            assigned: row.assigned === true,
         }));
     }
     /**
@@ -567,7 +573,11 @@ export class CloudClient {
      * 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`.