From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Wed, 17 Jun 2026 07:12:19 -0700 Received: from mail-oa1-f64.google.com ([209.85.160.64]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1wZr06-0000tl-D9 for bitcoindev@gnusha.org; Wed, 17 Jun 2026 07:12:19 -0700 Received: by mail-oa1-f64.google.com with SMTP id 586e51a60fabf-43d10d3f8c7sf7622988fac.0 for ; Wed, 17 Jun 2026 07:12:18 -0700 (PDT) ARC-Seal: i=3; a=rsa-sha256; t=1781705532; cv=pass; d=google.com; s=arc-20240605; b=VazV8cJfk0GQ/hmBsV5Zn3LkB8NY20hNofsFWNkIscZg/+dvaUkxpByAKZJysc7a3Q XzEuzsLwHyFzPWEzvDcZF+RKk0sucuSeso3I88ngOK35O/cHm9lXbEMXsnJiZ7fYdhWx w10zu91AwM1pFNepVHERkp+BUbn3dGhrJNbkY5nMH8I5dorhbFC0nxcAKoj+zcAm+/df w6laC8M2yO5aQrwDeGdOLRgAs95SKWBbK6amiIoE70j7p6Bv4qOxAywITZ8L43kUXDXA bX15Cu2miiXIl//5mT34G2Xcuen5Bvhzshd5UN0pd9AB00xh/Y1MnCVutxKGrmCXi7vy dnqA== ARC-Message-Signature: i=3; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:sender:dkim-signature :dkim-signature; bh=0npRGH4ub9NtliG3LqCYOfTEkPObLR+KIxL6d4Y/TDs=; fh=/Lq1euBN+uYcapKhvCJZiyP8il7+9Yrm8th419XShKQ=; b=CdceYjyZGo7XIiXXWZeNCVuugBfscVQxoMNvRHw9bhRCFdeJlWB1jvmY/E+lz/64na wsub2UQ9QF4/TncyBCmcTM/KzeHfg5WNaE/MnAJszku+yhPh42R/Zqt6HIq57s9oAZnS ozB9T+zzUFmpGRu9tlgRLkm3A1kiDtDBgZvranwIpEB5U2UXn+dFDwHzvxnsI51bS/fa TXUyEzTha0d+EBn8DonWjUlUTY2HJwNlPtgDQOFWCWbK/mbmepjmR06Z5QCDEG9llrcb Vx5EEtQyxjqr/ODqKtV++x28+fy9lu9RHFHs6xO9Z3qT3E/oPeNZzBtJxdDGRb8fM2EN Tihg==; darn=gnusha.org ARC-Authentication-Results: i=3; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20251104 header.b=MADX83pV; arc=pass (i=1); spf=pass (google.com: domain of daniosemberg@gmail.com designates 2a00:1450:4864:20::52c as permitted sender) smtp.mailfrom=daniosemberg@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1781705532; x=1782310332; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:sender:from:to:cc:subject:date:message-id :reply-to; bh=0npRGH4ub9NtliG3LqCYOfTEkPObLR+KIxL6d4Y/TDs=; b=UPj3J/wqSLLyGNyFXByO04autWlutBQrzbZaQdUAGbtvLhjNr8voWQCmFy24RTmGY/ 8ki+deuYZEVaFhDe3sgXNhdseDZDOTCN3tKNL1+8mYfECYQ0xYbfJaNELtiR3RD2hOIz Ul681eqgcoshQpglBkSJ/kheOFljWKiQo716NlrJp7GNi/WXDznfcE8hDDNduFIIFdmQ 4RXACCeEOmlZ48k9HxoBa3F+CTuzZwwyYPfHQcUQ8ws2w2lx8VtdhhcqzfOlTIMLXRIL Ni39UY2suFWJBqBBxvNyqnvcaVEvVRFMZNmZ33ACA/s5/Wb6eBcSApj8Fs/5Tyd7zP75 ZSLA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1781705532; x=1782310332; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to; bh=0npRGH4ub9NtliG3LqCYOfTEkPObLR+KIxL6d4Y/TDs=; b=O/aAUDszK6Y4Svb6CqxxLHDEVnmHMw+IKR5NKrYHJSZuu3Bc64PQxu7J3mjwC6CtxV S2HfMeZQPjUKgI4ZIKKSHEfP9w1cvbnt2n6pGQPKjdJUZwzvlqKNh7cM/xsWUtwlzdZa t0dvevu6W3cGFOGvOcK+v2cYDds9MODjOoSPbwkb863cOkLzL2wwjnIsBeLD4/kE6KvQ z/UUY4GM1nMPJA0GTcBMoZyG3g3SOW6zxUzZ5zKUL7wWPva3aJ+ZIbf6PgTo3ZNC7AIM JwETP6ObOyBgY30z117tDJyrrtLhGeHKNYIaCxcGcPeOnACNXSWpXLI2PfaPVh7zQGTJ h/HA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1781705532; x=1782310332; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-beenthere:x-gm-message-state :sender:from:to:cc:subject:date:message-id:reply-to; bh=0npRGH4ub9NtliG3LqCYOfTEkPObLR+KIxL6d4Y/TDs=; b=k7Gckra1OpI9VHHIhHBPG8IPgUyfc2ygoVYoo/Ws8T38GHp3BFk3++iYcucILRZOcS MuG6Ky84Ihriie8UO3VWdal39TIjfclZV0GhOW8me99PsXrMMjlb3CmvPbVuG4dsner9 SrsDPkZDkU2opS0Ug7oSn5LafZTJGsK9bjnO5TL4mhPftqVLVyFyXzdTfWEr71p26M4M hQcEtDyVvuW4e0g5FLlMlp6cVtAocJOEWfMegkb3anzFM8xHCPaAww9cu0qI9kUuCpCK 7x+F0xlqmLDzXVokcXiIysCP7CsLvHKgyCpoOZbIIl19gCAVOFtQAfTRCrS6Y3yUzxj1 nZWw== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=3; AFNElJ8GMcEA0G72dA1o24zajH0BzWQ0Dl36aFCDn24RDxkgPkbVqzNEgzS1lRum/jE6HmdqRFinslSyc4oG@gnusha.org X-Gm-Message-State: AOJu0YwNVSmiYkliYodiQxjFvarXasE821A4PDwgQWFCGxjrQRjx2hhV wNhrqSWo824eJy/6PqgyE/5M7MC9gPXl4fVMu9Ps1ZtE4O60yUuxPbv7 X-Received: by 2002:a05:6820:1525:b0:69d:9e9d:b000 with SMTP id 006d021491bc7-6a0b5f2ee88mr2846317eaf.23.1781705532078; Wed, 17 Jun 2026 07:12:12 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="AX0PUUfAaAGK89CyXAbfIGHHYPwq3gM5tNc+Raz9RKon2OEjIQ==" Received: by 2002:a05:6820:80c8:b0:69e:5564:72c2 with SMTP id 006d021491bc7-69ed792d3e9ls4136703eaf.0.-pod-prod-01-us; Wed, 17 Jun 2026 07:12:06 -0700 (PDT) X-Received: by 2002:a05:6808:11cd:b0:486:79ad:96e9 with SMTP id 5614622812f47-48942bac334mr3155560b6e.37.1781705525922; Wed, 17 Jun 2026 07:12:05 -0700 (PDT) Received: by 2002:a05:6402:a2cd:20b0:68c:16a8:bd1b with SMTP id 4fb4d7f45d1cf-695469b008bmsa12; Wed, 17 Jun 2026 07:05:49 -0700 (PDT) X-Received: by 2002:a05:6402:3217:b0:695:4649:ca62 with SMTP id 4fb4d7f45d1cf-69547477cdamr2359898a12.21.1781705147779; Wed, 17 Jun 2026 07:05:47 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1781705147; cv=pass; d=google.com; s=arc-20240605; b=kkzdL8I9EaDV6nWYE1arfbKzUfQnHG16b6BPhp69qsni6p3j4vF4qkcrZaxVEOxx3X rauYTL9cWczIAy+6F8eaOzAuDslUxa4VQlLJEQJjuOQPpZ9WBYpE01APVugH63YoYpQN uXPndpzdTREwXEevWQ5nqWLgesO7JmobkwHeTyueCtaA383cWXYfwv+PJSZvpy/OBs60 SAwKeUtBoCYysOLLoZ/0+t2onITZGsq0YpdP03mN26oPqMUSQZ8eyctH+HV6AxgunpiI 0RSFoe8j8gj4Vzn0Mod7ZJm1FoflGHvHbYTvZVHy2sB/0ZjZaiGPOrjoVOP+PVFnUtNd IvvA== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=1xy9vuDf0/E4QNGCO4aYTlTtz1GxTYnjDiZHIjuQHXw=; fh=wikqFOI1zoGPUut9KlLwNBRJKbR3nAGdzgzIIebuWgs=; b=cvZiqqEjfn1UGZL9Pe4oc6HR4Kf6SaTRrwe9RiBpwcFjtOpb/0Wor8XpUeANNA/XPM z2LqvASuIHph9OfBupVllx+A6TJwGkm3tUyEz0PhXcbpruVk9V5msyIMOpcGagWRz8PB u3q8XcGT3gUd6GmK9ivq4vqhNptWSvtZAcZcW9PJCx9jAx6h7IqDbGgwwe9vRz+ArbSX oXEvO3L9a4omAmeR7RAxeJFJNeE57qD94W9DoQBj59iONYZ4IMTflwc4qQSlsGYazrH7 B8ZUtChUse4xmiIAztF1nzwmrkJ2Sg0Qo+7Xo7lfV3/JJ9cg9MOw/vH12sWCPdrnmwzG HoCQ==; dara=google.com ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20251104 header.b=MADX83pV; arc=pass (i=1); spf=pass (google.com: domain of daniosemberg@gmail.com designates 2a00:1450:4864:20::52c as permitted sender) smtp.mailfrom=daniosemberg@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com. [2a00:1450:4864:20::52c]) by gmr-mx.google.com with ESMTPS id 4fb4d7f45d1cf-6953559fb56si82262a12.7.2026.06.17.07.05.47 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 17 Jun 2026 07:05:47 -0700 (PDT) Received-SPF: pass (google.com: domain of daniosemberg@gmail.com designates 2a00:1450:4864:20::52c as permitted sender) client-ip=2a00:1450:4864:20::52c; Received: by mail-ed1-x52c.google.com with SMTP id 4fb4d7f45d1cf-6957b74472dso1249327a12.0 for ; Wed, 17 Jun 2026 07:05:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1781705147; cv=none; d=google.com; s=arc-20240605; b=KRynha5XxvWjDss37w6sN09qiuvrywaEBaCOZ2huo4hhfr5aCINWzF3L9mXReaXNSA bb6dOua2+lqUuhUUmkUmTZlq4b38RMjSsKbHNWQlhWqzNnEN7q5vVggO+oHnK6DQERaY rdgiYcB8+aMkkH7FoBSOGA7rz8ZRnkZUm8zxsKbFF4OOuHqoz+WrISJ/1L4O34CQnYtc urFW9Hqo1O76zMVPSgjHcWHt59m8aR044HYwd91Z8qSigDknFje6WXsVXFUCXcBhQx+5 FSWUZ3d5oFT08nUcvXCYBTP5ylssX19MKN96KCZnfyMTrJhcwRaF/RG0W5fuH/7ZG5Z4 WAXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=1xy9vuDf0/E4QNGCO4aYTlTtz1GxTYnjDiZHIjuQHXw=; fh=wikqFOI1zoGPUut9KlLwNBRJKbR3nAGdzgzIIebuWgs=; b=NCORJOcSEWqm25EWs7akhfudhDkj8m6tS3t8ELrmgC+COjC03Al0dZxARKbHNOexLe 9o/1tCRMVf/Pxdg7vb80eDmEJ7dXcg/nphHUWBbsd3TD0//Zf71H77OHMA0S3Zg02Eui uHdiWSOdUy85KgiFDxxR1fS+OPPZObrqMuvw1uH90DXAfExcioU5QL1syXQk9REGKCk6 CFESHVOmg/sgamPclw2+b12Y3GSV4SllYyipuTFHwwpKHG98YPCmJPyhi+yhZDpNKTgL vadcZLZl0oQZozxmQ6Tw+hGawiIFIOdZhho1C8FNKbOfL0rkjuj3DWYpZteJE4E1OspC 0wfA==; dara=google.com ARC-Authentication-Results: i=1; mx.google.com; arc=none X-Gm-Gg: AfdE7clScnrOkykeUbhzMiKBN+XfIsHjeRWSS/KnlnhjsQd7y3fN3sP21ERTUoQueuf 6BGb4s2WUGuHTZzyLsgvBtv44/xEGW3c4FpfQlATGdo+apevqm3GQNYZIXPOWeOsgyc8EoH7sc5 G7AWcfQEoMFJgym4jrryt5bc5cDFpFd7sgC9X7ngshlXkkwOA2KrYlLonUnjA5qI4yjCIH3g4B0 uyEw5FmlvVYMZUv2/QUq4pJvNermPSh5P1/eMtronke4tZYnAFl14k6A6hqgRJCo2EZVFOi4GQj m4Liue4dtCPtVmNySkWyv3vEKbQeG7H1WwHSnSvTFV9JyBQB0cCQAHZeKsYWG8a6J7MWduffTzw 2909SrhWhovrPJ0ZXSISB0sin9dQ2WTj7GRwgFzsfWCTpgVvAPhiwCKXmmoG7Trr+WdkOi8BCXg KvFPGO X-Received: by 2002:a05:6402:43c3:b0:691:a8bd:981f with SMTP id 4fb4d7f45d1cf-69547464467mr2316589a12.19.1781705147075; Wed, 17 Jun 2026 07:05:47 -0700 (PDT) MIME-Version: 1.0 References: <7fe5fea8-ae9d-4081-a94f-fa9be0677012n@googlegroups.com> In-Reply-To: From: Daniel Osemberg Date: Wed, 17 Jun 2026 17:06:26 +0300 X-Gm-Features: AVVi8CdeK_Ub26TQb8hhUPoEe_3X4mqUy4pNuymPM4jUyV1PNI5ss7HGL-ATJic Message-ID: Subject: Re: [bitcoindev] [bitcoin-dev] Proposal discussion: BIP39 native-language display wordlists To: Randy McMillan Cc: Bitcoin Development Mailing List Content-Type: multipart/alternative; boundary="00000000000062cec60654738ef5" X-Original-Sender: daniosemberg@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20251104 header.b=MADX83pV; arc=pass (i=1); spf=pass (google.com: domain of daniosemberg@gmail.com designates 2a00:1450:4864:20::52c as permitted sender) smtp.mailfrom=daniosemberg@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com; dara=pass header.i=@googlegroups.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) --00000000000062cec60654738ef5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, I understand the point, but I think this misses the practical issue the proposal is trying to address. Yes, BIP39 is an application-layer specification, and yes, wallet developers can theoretically offer locale options. But in practice, most wallets do not provide full localization of the recovery experience, and they do not provide a standardized way to map native-language input back to the canonical English BIP39 flow. That is the gap this proposal is addressing. My own work started with BlockSight, a free Bitcoin block explorer available in 31 languages. TZUR Wallet came later as a Bitcoin-only self-custody wallet that integrates BlockSight natively inside the app. It does not offer trading, conversion, buying, selling, custody, brokerage, or any financial service. It only uses Bitcoin standards for wallet creation, backup, receiving, and sending. The reason this issue became obvious to me is that localization of Bitcoin tools is still very incomplete. I am from Israel, and there are no mainstream Bitcoin wallets with a fully Hebrew-native recovery experience, and there is no Hebrew seed phrase experience that remains compatible with the standard English BIP39 flow. So while the responsibility is indeed on wallet developers to implement good UX, there is currently no common convention for doing this safely and interoperably across wallets. The proposal is not saying that BIP39 itself is broken. It is saying that the current ecosystem around BIP39 leaves many non-English users dependent on English recovery words, and that creates a real UX and recovery-risk problem. This proposal tries to define a simple, optional, wallet-level convention: English BIP39 remains canonical. The localized words are fixed independent display/input lists. The localized phrase maps deterministically by index back to the English BIP39 wordlist. The localized words are not passed directly into PBKDF2. Wallets must always allow export of the canonical English BIP39 phrase. In that sense, TZUR Wallet is simply one implementation of the proposal. The broader contribution is the methodology and the prepared wordlists, which are already available for review, testing, and potential adoption by other wallet developers. No one is asking for compensation for this work. The intent is to contribute something useful back to the Bitcoin ecosystem, especially for users who do not think, read, or back up critical financial information naturally in English. So I agree that wallet developers are responsible for implementation. But that is exactly why a shared convention can be useful: it gives wallet developers a common way to support native-language recovery UX while preserving compatibility with English BIP39. Best, Daniel On Wed, Jun 17, 2026 at 4:58=E2=80=AFPM Randy McMillan wrote: > =E2=80=9CMany users around the world are asked to back up and restore Bit= coin > wallets using English recovery words, even when English is not their nati= ve > language. This creates UX risk, spelling mistakes, misunderstanding, and > lower confidence during backup and recovery.=E2=80=9D > > Note: Bip39 is categorized as an Applications layer specification - the > concern in your motivation falls on the wallet developer and IMO isnt a > short coming of the specification itself. Many applications give the user > the ability to select locale - a wallet UI should offer wordlist options > based on user locale preference. > --=20 You received this message because you are subscribed to the Google Groups "= Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/= CAFS8eiVN2WmJi0gpRFR%2Bab_C6VOFi6oPBx-g_EULwMDvaF%3DEtQ%40mail.gmail.com. --00000000000062cec60654738ef5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi,

I understand the point, but I think this miss= es the practical issue the proposal is trying to address.

Yes, BIP39 = is an application-layer specification, and yes, wallet developers can theor= etically offer locale options. But in practice, most wallets do not provide= full localization of the recovery experience, and they do not provide a st= andardized way to map native-language input back to the canonical English B= IP39 flow.

That is the gap this proposal is addressing.

My own = work started with BlockSight, a free Bitcoin block explorer available in 31= languages. TZUR Wallet came later as a Bitcoin-only self-custody wallet th= at integrates BlockSight natively inside the app. It does not offer trading= , conversion, buying, selling, custody, brokerage, or any financial service= . It only uses Bitcoin standards for wallet creation, backup, receiving, an= d sending.

The reason this issue became obvious to me is that localiz= ation of Bitcoin tools is still very incomplete. I am from Israel, and ther= e are no mainstream Bitcoin wallets with a fully Hebrew-native recovery exp= erience, and there is no Hebrew seed phrase experience that remains compati= ble with the standard English BIP39 flow.

So while the responsibility= is indeed on wallet developers to implement good UX, there is currently no= common convention for doing this safely and interoperably across wallets.<= /p>

The proposal is not saying that BIP39 itself is broken. It is saying = that the current ecosystem around BIP39 leaves many non-English users depen= dent on English recovery words, and that creates a real UX and recovery-ris= k problem.

This proposal tries to define a simple, optional, wallet-l= evel convention:

English BIP39 remains canonical.

The localized= words are fixed independent display/input lists.

The localized phras= e maps deterministically by index back to the English BIP39 wordlist.

The localized words are not passed directly into PBKDF2.

Wallets mus= t always allow export of the canonical English BIP39 phrase.

In that = sense, TZUR Wallet is simply one implementation of the proposal. The broade= r contribution is the methodology and the prepared wordlists, which are alr= eady available for review, testing, and potential adoption by other wallet = developers.

No one is asking for compensation for this work. The inte= nt is to contribute something useful back to the Bitcoin ecosystem, especia= lly for users who do not think, read, or back up critical financial informa= tion naturally in English.

So I agree that wallet developers are resp= onsible for implementation. But that is exactly why a shared convention can= be useful: it gives wallet developers a common way to support native-langu= age recovery UX while preserving compatibility with English BIP39.

Be= st,
Daniel


On Wed, Jun 17, 2026 at 4:58=E2=80= =AFPM Randy McMillan <ra= ndy.lee.mcmillan@gmail.com> wrote:
=E2=80=9CMany users ar= ound the world are asked to back up and restore Bitcoin wallets using Engli= sh recovery words, even when English is not their native language. This cre= ates UX risk, spelling mistakes, misunderstanding, and lower confidence dur= ing backup and recovery.=E2=80=9D

Not= e: Bip39 is categorized as an Applications layer specification - the concer= n in your motivation falls on the wallet developer and IMO isnt a short com= ing of the specification itself. Many applications give the user the abilit= y to select locale - a wallet UI should offer wordlist options based on use= r locale preference.

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/= d/msgid/bitcoindev/CAFS8eiVN2WmJi0gpRFR%2Bab_C6VOFi6oPBx-g_EULwMDvaF%3DEtQ%= 40mail.gmail.com.
--00000000000062cec60654738ef5--