@moon-x/core 0.3.0 → 0.5.0

package/dist/chain-C9dvKXUY.d.ts

@@ -1,48 +0,0 @@
-type RpcUrls = {
-    http: readonly string[];
-    webSocket?: readonly string[];
-};
-type NativeCurrency = {
-    name: string;
-    symbol: string;
-    decimals: number;
-};
-type BlockExplorer = {
-    name: string;
-    url: string;
-};
-type Chain = {
-    id: number;
-    name: string;
-    network?: string;
-    nativeCurrency: NativeCurrency;
-    blockExplorers?: {
-        [key: string]: BlockExplorer;
-        default: BlockExplorer;
-    };
-    rpcUrls: {
-        [key: string]: RpcUrls;
-        default: RpcUrls;
-    };
-    testnet?: boolean;
-};
-type ChainLikeWithId = {
-    id: number;
-};
-type RpcConfig = {
-    rpcUrls?: {
-        [chainId: number]: string;
-    };
-    rpcTimeout?: number;
-};
-interface EthereumChainConfig {
-    defaultChain?: any;
-    supportedChains?: any[];
-    rpcs?: {
-        'ethereum:mainnet': {
-            rpc: string;
-        };
-    };
-}
-
-export type { BlockExplorer as B, Chain as C, EthereumChainConfig as E, NativeCurrency as N, RpcConfig as R, ChainLikeWithId as a, RpcUrls as b };

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 };