@metamask-previews/profile-sync-controller 29.0.0-preview-e57e5c3dc → 29.0.0-preview-c34a16a37

package/dist/shared/utils/entropy-source.mjs

@@ -0,0 +1,32 @@
+import { KeyringTypes } from "@metamask/keyring-controller";
+/**
+ * Reads HD keyring entropy source IDs (metadata IDs) from KeyringController
+ * keyrings, primary first. Returns an empty array when none are available
+ * (e.g. the wallet is locked, where `keyrings` is cleared).
+ *
+ * @param keyrings - Keyrings from `KeyringController:getState`.
+ * @returns The HD keyring metadata IDs, primary first.
+ */
+export function getHdKeyringEntropySourceIds(keyrings) {
+    return (keyrings ?? [])
+        .filter((keyring) => keyring.type === KeyringTypes.hd.toString())
+        .map((keyring) => keyring.metadata.id);
+}
+/**
+ * Resolves the primary SRP's entropy source ID (the first HD keyring's
+ * metadata ID). The ID is randomly regenerated whenever the vault is
+ * recreated (e.g. on restore).
+ *
+ * @param keyrings - Keyrings from `KeyringController:getState`.
+ * @returns The primary HD keyring metadata ID.
+ * @throws If no HD keyring is available; callers must only resolve while
+ * the wallet is unlocked.
+ */
+export function getPrimaryHdKeyringEntropySourceId(keyrings) {
+    const [primaryEntropySourceId] = getHdKeyringEntropySourceIds(keyrings);
+    if (!primaryEntropySourceId) {
+        throw new Error('getPrimaryHdKeyringEntropySourceId - no HD keyring available');
+    }
+    return primaryEntropySourceId;
+}
+//# sourceMappingURL=entropy-source.mjs.map

package/dist/shared/utils/entropy-source.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"entropy-source.mjs","sourceRoot":"","sources":["../../../src/shared/utils/entropy-source.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,YAAY,EAAE,qCAAqC;AAG5D;;;;;;;GAOG;AACH,MAAM,UAAU,4BAA4B,CAC1C,QAA4C;IAE5C,OAAO,CAAC,QAAQ,IAAI,EAAE,CAAC;SACpB,MAAM,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,IAAI,KAAK,YAAY,CAAC,EAAE,CAAC,QAAQ,EAAE,CAAC;SAChE,GAAG,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,QAAQ,CAAC,EAAE,CAAC,CAAC;AAC3C,CAAC;AAED;;;;;;;;;GASG;AACH,MAAM,UAAU,kCAAkC,CAChD,QAA4C;IAE5C,MAAM,CAAC,sBAAsB,CAAC,GAAG,4BAA4B,CAAC,QAAQ,CAAC,CAAC;IACxE,IAAI,CAAC,sBAAsB,EAAE,CAAC;QAC5B,MAAM,IAAI,KAAK,CACb,8DAA8D,CAC/D,CAAC;IACJ,CAAC;IACD,OAAO,sBAAsB,CAAC;AAChC,CAAC","sourcesContent":["import { KeyringTypes } from '@metamask/keyring-controller';\nimport type { KeyringObject } from '@metamask/keyring-controller';\n\n/**\n * Reads HD keyring entropy source IDs (metadata IDs) from KeyringController\n * keyrings, primary first. Returns an empty array when none are available\n * (e.g. the wallet is locked, where `keyrings` is cleared).\n *\n * @param keyrings - Keyrings from `KeyringController:getState`.\n * @returns The HD keyring metadata IDs, primary first.\n */\nexport function getHdKeyringEntropySourceIds(\n  keyrings: KeyringObject[] | null | undefined,\n): string[] {\n  return (keyrings ?? [])\n    .filter((keyring) => keyring.type === KeyringTypes.hd.toString())\n    .map((keyring) => keyring.metadata.id);\n}\n\n/**\n * Resolves the primary SRP's entropy source ID (the first HD keyring's\n * metadata ID). The ID is randomly regenerated whenever the vault is\n * recreated (e.g. on restore).\n *\n * @param keyrings - Keyrings from `KeyringController:getState`.\n * @returns The primary HD keyring metadata ID.\n * @throws If no HD keyring is available; callers must only resolve while\n * the wallet is unlocked.\n */\nexport function getPrimaryHdKeyringEntropySourceId(\n  keyrings: KeyringObject[] | null | undefined,\n): string {\n  const [primaryEntropySourceId] = getHdKeyringEntropySourceIds(keyrings);\n  if (!primaryEntropySourceId) {\n    throw new Error(\n      'getPrimaryHdKeyringEntropySourceId - no HD keyring available',\n    );\n  }\n  return primaryEntropySourceId;\n}\n"]}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metamask-previews/profile-sync-controller",
-  "version": "29.0.0-preview-e57e5c3dc",
+  "version": "29.0.0-preview-c34a16a37",
   "description": "The profile sync helps developers synchronize data across multiple clients and devices in a privacy-preserving way. All data saved in the user storage database is encrypted client-side to preserve privacy. The user storage provides a modular design, giving developers the flexibility to construct and manage their storage spaces in a way that best suits their needs",
   "keywords": [
     "Ethereum",