@embarkai/ui-kit 0.4.128 → 0.6.9

package/README.md

@@ -1,6 +1,6 @@
 # @embarkai/ui-kit
 
-React UI components and hooks for EmbarkAI - a secure, user-friendly authentication and Account Abstraction wallet solution with MPC (Multi-Party Computation) key management.
+React UI components and hooks for embarkAI - a secure, user-friendly authentication and Account Abstraction wallet solution with MPC (Multi-Party Computation) key management.
 
 ## Features
 
@@ -165,7 +165,7 @@ function Root() {
   return (
     <QueryClientProvider client={queryClient}>
       <Provider
-        projectId="your-project-id" // Get from EmbarkAI Dashboard
+        projectId="your-project-id" // Get from embarkAI Dashboard
       >
         <YourDapp />
       </Provider>
@@ -297,7 +297,6 @@ The SDK uses the following priority for determining the active chain:
       mpcSecurity: true,
       strictMode: false,
       requestDeduplication: true,
-      kycNeeded: false,
       displayNameNeeded: false,
       showActiveBalanceAsFiat: false,
     },
@@ -357,7 +356,7 @@ The SDK uses the following priority for determining the active chain:
 
 ## Using Hooks
 
-> **Note:** The `useSession` hook is based on pure Zustand store so if you're already using useSession hook please consider 2 options: 1) refactor state extarction so it uses zustand state extraction feature. 2) consider using dedicated EmbarkAI shared store values hooks: `useAccountSession`, `useAddress` etc. Otherwise you might experience excessive re-rendering issues as EmbarkAI shares its internal store and might update some state values which should not affect app render.
+> **Note:** The `useSession` hook is based on pure Zustand store so if you're already using useSession hook please consider 2 options: 1) refactor state extarction so it uses zustand state extraction feature. 2) consider using dedicated embarkAI shared store values hooks: `useAccountSession`, `useAddress` etc. Otherwise you might experience excessive re-rendering issues as embarkAI shares its internal store and might update some state values which should not affect app render.
 
 ```tsx
 import { useAccountSession, useLoadingStatus } from '@embarkai/ui-kit'
@@ -384,7 +383,7 @@ function MyComponent() {
 }
 ```
 
-### EmbarkAI hared store values hooks
+### embarkAI hared store values hooks
 
 - **useActiveChainId** - Returns current ChainID
 - **useIsMobileView** - Returns boolean indicating if UI is in mobile view mode
@@ -786,9 +785,9 @@ function PrepareBatchExample() {
 }
 ```
 
-### useOpenPage - Programmatic EmbarkAI Dialog Control
+### useOpenPage - Programmatic embarkAI Dialog Control
 
-Control the EmbarkAI dialog programmatically.
+Control the embarkAI dialog programmatically.
 
 ```tsx
 import { PageKey, useOpenPage } from '@embarkai/ui-kit'

package/dist/iframe/_headers

@@ -32,18 +32,14 @@
   Access-Control-Allow-Methods: GET, OPTIONS
   Access-Control-Allow-Headers: Content-Type
 
-  # Cache control for HTML
+  # Every iframe asset (main.js, oauth/*.js, kyc/sumsub.js, dkls23_wasm_bg.wasm) is
+  # served under a fixed, unhashed name, so it must be revalidated on each load.
+  # A long-lived immutable cache keeps the previous build on auth.* after a deploy
+  # until someone purges the zone cache. Revalidation is cheap: Pages answers
+  # 304 Not Modified via ETag when the file has not changed.
+  # Do not add a second Cache-Control for a narrower path (e.g. /*.js): Pages
+  # appends it to this one and the edge then honours the longer max-age.
   Cache-Control: public, max-age=0, must-revalidate
 
-/*.js
-  # Cache JavaScript files for 1 year
-  Cache-Control: public, max-age=31536000, immutable
-
-/*.css
-  # Cache CSS files for 1 year
-  Cache-Control: public, max-age=31536000, immutable
-
 /*.wasm
-  # Cache WASM files for 1 year
-  Cache-Control: public, max-age=31536000, immutable
   Content-Type: application/wasm

package/dist/iframe/index.html

@@ -15,7 +15,7 @@
     <meta http-equiv="X-Content-Type-Options" content="nosniff" />
     <meta http-equiv="Referrer-Policy" content="strict-origin-when-cross-origin" />
 
-    <title>EmbarkAI Secure Wallet - iframe version 0.4.128</title>
+    <title>embarkAI Secure Wallet - iframe version 0.6.9</title>
 
     <!-- Styles will be injected by build process -->
     <style>

package/dist/iframe/kyc/sumsub.html

@@ -3,7 +3,7 @@
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Sumsub KYC - EmbarkAI</title>
+    <title>Sumsub KYC - embarkAI</title>
 
     <style>
       * {