From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from whitealder.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 452EFC0177 for ; Wed, 26 Feb 2020 13:09:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by whitealder.osuosl.org (Postfix) with ESMTP id 33E2F85A46 for ; Wed, 26 Feb 2020 13:09:28 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from whitealder.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RiNUB92OQyr0 for ; Wed, 26 Feb 2020 13:09:23 +0000 (UTC) X-Greylist: delayed 00:06:46 by SQLgrey-1.7.6 Received: from mail-wm1-f68.google.com (mail-wm1-f68.google.com [209.85.128.68]) by whitealder.osuosl.org (Postfix) with ESMTPS id 5345B86DAF for ; Wed, 26 Feb 2020 13:09:23 +0000 (UTC) Received: by mail-wm1-f68.google.com with SMTP id f15so2205958wml.3 for ; Wed, 26 Feb 2020 05:09:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cypherock-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=Kqz2y3G3OmMJ1QbnLxI5KZswhrgT+uyFOF6LSKsdrYg=; b=zLfPkjWsbHitYPaY6JvONc4c4YDBu5NhMj5QqdkHXTXOewjPasCZQpKensnfsLkAHO oeiIunP6+9uEbu1CIL8/mUkZxruT3lpqWHmwlNWLs6UFbTpgA8EIo7Dq8wumEGwZNZEz 2ggfdpbXqhOUYiJ4yKp5iND+dSb2LkqfRzCFozIkJm/YSxQ4V82RZrAzPJUxXi0BRgPX Cc6cYbm77q0igU4AaLoDaJc7ynWMssqAqTsUYIA3uMU1IvdaFzlkI15lzNUUoHPFglie eCMdvubeiFnvTmW9x0QHZVc6B6ARehw+LhHbCF7DzRhBsqMP1Jf3eb3ZjJf8DOrPi807 dUJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Kqz2y3G3OmMJ1QbnLxI5KZswhrgT+uyFOF6LSKsdrYg=; b=mYnG0PwK3O6G0DW+6djHa25ULMCE5RUkY6DXzXmiJ4NFOKyMUVKONNQQZcO4lhMmqt vcvt/KWzVT4VRXbkM1yf0ao2HJxno2z6FYMNGCEegR2U9xpVr3q6E3VwTj12j+d7NraG k6+DxaYTfbksQ1v9Zb0Js3FexsGf147TNBBGHhT33Cnn6g6bLkDspH4t3OAT+IVnyeY/ dqJhdHaLPYgjyog6CqL7NgZAlBicyHbD1zncatpKwsJqc13ygzIYiXH15g+Pm59f3Yew 1sB8kb0CeJ8ZrKlBRuAWloQGr3zlZPWi2pNKJJTaKsQ1dZv9lxdGlHDLgipUSXb+Q8fU LK6A== X-Gm-Message-State: APjAAAWc9Q6yAZMeXLy4KDyDpj3lkDZmbCkWFpKkG86ih7/pSgOpTtTF mN3eRhl/L3a7hpc/R7vEFDIxXUqdCzL+AqIt5KARCiWe X-Google-Smtp-Source: APXvYqzfR79wJ5gBG1p54FZqKKW/Bp5SQ85+9cbPiN/W6DrAi178x5G0LhCEeq4A7AcGl4NtHvg+xXpAWnKRRPW9cAA= X-Received: by 2002:a7b:c1d0:: with SMTP id a16mr5538891wmj.175.1582722151393; Wed, 26 Feb 2020 05:02:31 -0800 (PST) MIME-Version: 1.0 From: Contact Team Date: Wed, 26 Feb 2020 18:32:20 +0530 Message-ID: To: bitcoin-dev@lists.linuxfoundation.org Content-Type: multipart/alternative; boundary="000000000000c2fb8c059f7a373c" X-Mailman-Approved-At: Wed, 26 Feb 2020 17:14:23 +0000 Subject: [bitcoin-dev] Removing Single Point of Failure with Seed Phrase Storage X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2020 13:09:28 -0000 --000000000000c2fb8c059f7a373c Content-Type: text/plain; charset="UTF-8" Hi Everyone, Seed phrase security has been a subject of discussion for a long time now. Though there are varying opinions on the subject but the conflict usually arises due to different security models used by different individuals. The general practice in the space has been to use paper or metal engraving options to secure seed phrase but those too act as a single point of failure when secure storage is concerned. The hardware wallets, no matter whether use a secure element or not can be hacked either through basic glitching or through bigger schemes state enforced backdoors in the closed soured SE used. The option that Cypherock (Cypherock X1 Wallet) is working on removes a single point of failure when it comes to storage of seed phrases. It uses 2 of 4 (with the option of setting up custom threshold limit) Shamir Secret Sharing to split the seed phrase into 4 different shares. Each share gets stored in a PIN ( hardware enforced ) Card with an EAL 6+ secure element. The user would need any 2 of these 4 cyCards to recover the seed or make a transaction. Ideally they should all be stored at different locations and this added security through distribution makes losing seed phrase highly improbable. We have decoupled storage and computation aspect of a hardware wallet. More information can be obtained from cypherock.com. The purpose of this mail is to get feedback from the community. Let us know if there is any feedback, we would love it. Thanks --000000000000c2fb8c059f7a373c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Everyone,
Seed phrase security has been a subject o= f discussion for a long time now. Though there are varying opinions on the = subject but the conflict usually arises due to different security models us= ed by different individuals. The general practice in the space has been to = use paper or metal engraving options to secure seed phrase but those too ac= t as a single point of failure when secure storage is concerned. The hardwa= re wallets, no matter whether use a secure element or not can be hacked eit= her through basic glitching or through bigger schemes state enforced backdo= ors in the closed soured SE used.

The option that = Cypherock (Cypherock X1 Wallet)=C2=A0 is working on removes a single point = of failure when it comes to storage of seed phrases. It uses 2 of 4 (with t= he option of setting up custom threshold limit) Shamir Secret Sharing to=C2= =A0 split the seed phrase into 4 different shares. Each share gets stored i= n a PIN ( hardware enforced ) Card with an EAL 6+ secure element. The user = would need any 2 of these 4 cyCards to recover the seed or make a transacti= on. Ideally they should all be stored at different locations and this added= security through distribution makes losing seed phrase highly improbable. = We have decoupled storage and computation aspect of a hardware wallet. More= information can be obtained from cypheroc= k.com. The purpose of this mail is to get feedback from the community. = Let us know if there is any feedback, we would love it.

Thanks
--000000000000c2fb8c059f7a373c--