@calimero-network/mero-js 15.3.4 → 16.1.0

package/dist/namespace-op/namespace-op.js

@@ -51,12 +51,6 @@ function borshString(value) {
     const bytes = new TextEncoder().encode(value);
     return concat(u32le(bytes.length), bytes);
 }
-function encodeAdmitterHint(hint) {
-    if ('multiaddr' in hint) {
-        return concat(new Uint8Array([0]), borshString(hint.multiaddr));
-    }
-    return concat(new Uint8Array([1]), borshString(hint.url));
-}
 /**
  * Borsh-encode a `SignedGroupOpenInvitation`.
  *
@@ -70,7 +64,7 @@ function encodeAdmitterHint(hint) {
 export function encodeSignedInvitation(signed) {
     const body = signed.invitation;
     const admitters = body.admitters ?? [];
-    const hints = signed.admitter_hints ?? [];
+    const admitterAddrs = signed.admitter_addrs ?? [];
     return concat(
     // GroupInvitationFromAdmin.
     //
@@ -79,11 +73,17 @@ export function encodeSignedInvitation(signed) {
     // wrong way yields 32 bytes that encode cleanly and verify as nothing.
     bytes32(body.inviter_identity, 'inviter_identity'), bytes32(body.group_id, 'group_id'), u64le(body.expiration_timestamp), bytes32(body.secret_salt, 'secret_salt'), new Uint8Array([body.invited_role]), u32le(admitters.length), ...admitters.map((a, i) => fromHex(a, `admitters[${i}]`, 32)), 
     // ...then the enclosing SignedGroupOpenInvitation, in declaration order.
-    // `inviter_account` sits between the signature and the hints; putting it
+    // `inviter_account` sits between the signature and the addresses; putting it
     // anywhere else still encodes 32 bytes and still verifies as nothing.
     borshString(signed.inviter_signature), signed.inviter_account
         ? concat(new Uint8Array([1]), fromHex(signed.inviter_account, 'inviter_account', 32))
-        : new Uint8Array([0]), u32le(hints.length), ...hints.map(encodeAdmitterHint), optionalBytes32(signed.application_id, 'application_id'), 
+        : new Uint8Array([0]), 
+    // A `Vec<String>`, so each entry is a bare borsh string. This carried an
+    // enum until core dropped the URL variant, and an enum writes a
+    // discriminant byte ahead of each entry — encoding one here now would shift
+    // every following byte and fail as `invalid invitation signature`, pointing
+    // nowhere near this line.
+    u32le(admitterAddrs.length), ...admitterAddrs.map(borshString), optionalBytes32(signed.application_id, 'application_id'), 
     // Borsh order follows core's field order, where this is `bytecode_id`; the
     // JSON key is `app_key`, a rename covering both directions that core pins in
     // a test. Encoding by the Rust name would read `undefined` and emit a None

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@calimero-network/mero-js",
-  "version": "15.3.4",
+  "version": "16.1.0",
   "description": "Pure JavaScript SDK for Calimero",
   "type": "module",
   "exports": {