From cf9c1df03df8a746bcfb221467f6591d13ff1874 Mon Sep 17 00:00:00 2001 From: Satoshi Qazi Muhammed Date: Thu, 8 Oct 2026 09:00:46 +0400 Subject: [PATCH] Generate new mnemonics with wasm-crypto again mnemonicGenerate was forced onto the JavaScript path because wasm-crypto 7.5.18 had no bip39Generate. 7.5.20 has it: 1000 phrases of 12 to 24 words generated through wasm were all valid and distinct, and wasm and JavaScript derive the same mini secret from each. The call is back to the upstream form, which uses wasm when it is ready. --- packages/extension-base/src/background/handlers/Extension.ts | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/packages/extension-base/src/background/handlers/Extension.ts b/packages/extension-base/src/background/handlers/Extension.ts index c2adca2..c415e12 100644 --- a/packages/extension-base/src/background/handlers/Extension.ts +++ b/packages/extension-base/src/background/handlers/Extension.ts @@ -325,8 +325,7 @@ export default class Extension { } private seedCreate ({ length = SEED_DEFAULT_LENGTH, seed: _seed, type }: RequestSeedCreate): ResponseSeedCreate { - // Use onlyJs=true because wasm-crypto doesn't implement bip39Generate - const seed = _seed || mnemonicGenerate(length, undefined, true); + const seed = _seed || mnemonicGenerate(length); return { address: keyring.createFromUri(getSuri(seed, type), {}, type).address,