@waaskey/sdk 0.3.1 → 0.3.2

package/dist/node.d.ts

@@ -80,7 +80,11 @@ interface DeviceSignParams extends CeremonyParams {
 }
 /** Result of the device half of sign. */
 interface DeviceSignResult {
-    /** The cggmp24 signature (JSON). */
+    /**
+     * The signature as LOW-S–normalized compact `r ‖ s` hex (128 chars, no `0x`) — byte-identical to
+     * what the platform's own party produces, so the backend can cross-check the two before embedding
+     * one into a transaction, and chain adapters can slice `r`/`s` by offset.
+     */
     signature: string;
 }
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@waaskey/sdk",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "WAASKey — embedded, non-custodial MPC wallets for your app. Official TypeScript SDK.",
   "license": "MIT",
   "author": "Waaskey",
@@ -63,7 +63,7 @@
   },
   "peerDependencies": {
     "@simplewebauthn/browser": "^13.0.0",
-    "@waaskey/client-wasm": "0.2.1"
+    "@waaskey/client-wasm": "0.2.2"
   },
   "peerDependenciesMeta": {
     "@simplewebauthn/browser": {
@@ -73,7 +73,7 @@
       "optional": true
     }
   },
-  "//peerDependencies-note": "@waaskey/client-wasm (the wasm MPC engine) is loaded via an indirect dynamic import (see mpc/load-wasm.ts) and pinned to the EXACT version in CLIENT_WASM_VERSION — never a floating range (issue #40). The SDK now requires 0.2.0, which adds the ed25519 (FROST) keygenEddsa/signEddsa exports (waas-core #110) the ed25519 wallet path drives. Add it here as an exact, OPTIONAL peerDependency (\"@waaskey/client-wasm\": \"0.2.0\" + peerDependenciesMeta.optional) ONLY AFTER 0.2.0 is published — pnpm resolves even optional peers, so declaring an unpublished version 404s `pnpm install`. Publish it via waas-core's `Publish @waaskey/client-wasm` workflow (bump the client-wasm Cargo version to 0.2.0, push a `client-wasm-v0.2.0` tag), then add the entry + refresh the lockfile.",
+  "//peerDependencies-note": "@waaskey/client-wasm (the wasm MPC engine) is loaded via an indirect dynamic import (see mpc/load-wasm.ts) and pinned to the EXACT version in CLIENT_WASM_VERSION — never a floating range (issue #40). The SDK requires 0.2.2, which awaits the relay close (an unpolled close left the party's role registered, so a sign right after keygen was rejected) and emits signatures as low-s normalized compact r‖s hex — the wire form the platform party produces and the chain adapters slice by offset. Bump BOTH this pin and CLIENT_WASM_VERSION together, and only AFTER the new client-wasm is on npm: pnpm resolves optional peers, so an unpublished pin 404s `pnpm install`. Publish it from waas-core by bumping client-wasm/Cargo.toml and pushing a `client-wasm-v<version>` tag.",
   "scripts": {
     "build": "tsup",
     "start": "tsup --watch",