@calimero-network/mero-js 23.6.0 → 23.7.0

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

@@ -656,7 +656,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

@@ -567,7 +567,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`.