@moon-x/core 0.3.0 → 0.4.0

package/dist/web/index.mjs

@@ -81,6 +81,35 @@ var createWebAuthnPasskey = () => ({
       authenticatorAttachment: result.authenticatorAttachment
     };
     return sanitized;
+  },
+  assertForInternalPresence: async ({ optionsJSON }) => {
+    const result = await startAuthentication({
+      optionsJSON: {
+        ...optionsJSON,
+        allowCredentials: []
+      }
+    });
+    if (!result.response.userHandle) {
+      throw new Error("user_handle_missing");
+    }
+    const sanitized = {
+      id: result.id,
+      rawId: result.rawId,
+      type: result.type,
+      response: {
+        clientDataJSON: result.response.clientDataJSON,
+        authenticatorData: result.response.authenticatorData,
+        signature: result.response.signature,
+        userHandle: void 0
+      },
+      clientExtensionResults: result.clientExtensionResults,
+      authenticatorAttachment: result.authenticatorAttachment
+    };
+    return {
+      response: sanitized,
+      userHandleB64url: result.response.userHandle,
+      credentialIdB64url: result.rawId
+    };
   }
 });
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@moon-x/core",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "license": "UNLICENSED",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/dist/passkey-cache-B9PT3AWX.d.mts

@@ -1,47 +0,0 @@
-interface CachedAssertion {
-    userHandleB64url: string;
-    credentialIdB64url: string;
-}
-declare const setAssertCacheTtlMs: (ms: number) => void;
-declare const getAssertCacheTtlMs: () => number;
-declare const clearParentAssertCache: () => void;
-declare const readParentAssertCache: () => CachedAssertion | null;
-declare const writeParentAssertCache: (entry: CachedAssertion) => void;
-/**
- * Run `fn` inside a try/catch that clears the parent-side assertion
- * cache on failure. Used by every wallet-interaction SDK method
- * (sign / send / etc.) so that if the operation fails for any reason
- * — backend rejection, network error, MPC ceremony failure — the
- * next user attempt re-prompts biometric instead of silently reusing
- * a possibly-bad cached assertion.
- *
- * The cache is set inside the platform-specific `assertPasskeyInParent`
- * only on a successful ceremony, so cancellations / activation
- * failures don't pollute it. This wrapper specifically handles the
- * "assertion succeeded but downstream work failed" case where the
- * cache is set but the user is stuck — without the clear, the user
- * would have to refresh to escape.
- */
-declare const withClearOnFailure: <T>(fn: () => Promise<T>) => Promise<T>;
-/**
- * Generate fresh user.id bytes for a new WebAuthn credential. The
- * caller overrides `options.user.id` with these bytes before
- * navigator.credentials.create so the authenticator persists them as
- * the credential's user.id; on every subsequent assertion they come
- * back as response.userHandle and serve as the AES-GCM key for that
- * credential's DEK wrap.
- *
- * Returns the bytes both as base64url (what the WebAuthn options
- * accept and what we ship over postMessage) and as raw bytes (for
- * any caller that prefers direct binary).
- *
- * Requires a working `crypto.getRandomValues`. On RN this is provided
- * by the `react-native-get-random-values` polyfill that the SDK's
- * docs ask consumers to import at app entry.
- */
-declare const generatePasskeyUserId: () => {
-    userIdB64url: string;
-    userIdBytes: Uint8Array;
-};
-
-export { type CachedAssertion as C, getAssertCacheTtlMs as a, writeParentAssertCache as b, clearParentAssertCache as c, generatePasskeyUserId as g, readParentAssertCache as r, setAssertCacheTtlMs as s, withClearOnFailure as w };

package/dist/passkey-cache-B9PT3AWX.d.ts

@@ -1,47 +0,0 @@
-interface CachedAssertion {
-    userHandleB64url: string;
-    credentialIdB64url: string;
-}
-declare const setAssertCacheTtlMs: (ms: number) => void;
-declare const getAssertCacheTtlMs: () => number;
-declare const clearParentAssertCache: () => void;
-declare const readParentAssertCache: () => CachedAssertion | null;
-declare const writeParentAssertCache: (entry: CachedAssertion) => void;
-/**
- * Run `fn` inside a try/catch that clears the parent-side assertion
- * cache on failure. Used by every wallet-interaction SDK method
- * (sign / send / etc.) so that if the operation fails for any reason
- * — backend rejection, network error, MPC ceremony failure — the
- * next user attempt re-prompts biometric instead of silently reusing
- * a possibly-bad cached assertion.
- *
- * The cache is set inside the platform-specific `assertPasskeyInParent`
- * only on a successful ceremony, so cancellations / activation
- * failures don't pollute it. This wrapper specifically handles the
- * "assertion succeeded but downstream work failed" case where the
- * cache is set but the user is stuck — without the clear, the user
- * would have to refresh to escape.
- */
-declare const withClearOnFailure: <T>(fn: () => Promise<T>) => Promise<T>;
-/**
- * Generate fresh user.id bytes for a new WebAuthn credential. The
- * caller overrides `options.user.id` with these bytes before
- * navigator.credentials.create so the authenticator persists them as
- * the credential's user.id; on every subsequent assertion they come
- * back as response.userHandle and serve as the AES-GCM key for that
- * credential's DEK wrap.
- *
- * Returns the bytes both as base64url (what the WebAuthn options
- * accept and what we ship over postMessage) and as raw bytes (for
- * any caller that prefers direct binary).
- *
- * Requires a working `crypto.getRandomValues`. On RN this is provided
- * by the `react-native-get-random-values` polyfill that the SDK's
- * docs ask consumers to import at app entry.
- */
-declare const generatePasskeyUserId: () => {
-    userIdB64url: string;
-    userIdBytes: Uint8Array;
-};
-
-export { type CachedAssertion as C, getAssertCacheTtlMs as a, writeParentAssertCache as b, clearParentAssertCache as c, generatePasskeyUserId as g, readParentAssertCache as r, setAssertCacheTtlMs as s, withClearOnFailure as w };