From: Contact Team <contact@cypherock•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Removing Single Point of Failure with Seed Phrase Storage
Date: Wed, 26 Feb 2020 18:32:20 +0530 [thread overview]
Message-ID: <CAEcfjBRCA1sKcFC5M++WECsgYD-jDBYGuwxLfh0PSzRkCehEDA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1589 bytes --]
next reply other threads:[~2020-02-26 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 13:02 Contact Team [this message]
2020-02-26 19:56 ` Jeremy
2020-02-26 20:26 ` Christopher Allen
2020-02-28 13:10 ` ZmnSCPxj
2020-03-06 11:11 ` Russell O'Connor
2020-08-03 22:49 ` [bitcoin-dev] On the compatibility of Bech32 and Shamir's Secret Sharing Russell O'Connor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEcfjBRCA1sKcFC5M++WECsgYD-jDBYGuwxLfh0PSzRkCehEDA@mail.gmail.com \
--to=contact@cypherock$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox