public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Devrandom <c1.bitcoin@niftybox.net>
To: James MacWhyte <macwhyte@gmail.com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Card Shuffle To Bitcoin Seed
Date: Mon, 4 Feb 2019 17:37:16 -0800	[thread overview]
Message-ID: <CAB0O3SUG5QbbdYphEkyRrbGfeeVF2L1UFKrg_wM+cxz5qdSdkg@mail.gmail.com> (raw)
In-Reply-To: <CAH+Axy5zB7GuS0Z6LCYibP81c0kk=uFk+t_uULCtwf-7xmnDfQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]

I would suggest 50+ 6-sided dice rolls, giving about 128 bits of entropy.
Compared to a shuffle, it's easier to be sure that you got the right amount
of entropy, even if the dice are somewhat biased.


On Mon, Feb 4, 2019 at 2:33 PM James MacWhyte via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

>
> James
>
>
> On Sun, Feb 3, 2019 at 10:27 AM Ryan Havar via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> Conveniently a shuffled deck of cards also can serve as a physical backup
>> which is easy to hide in plain sight with great plausible deniability.
>>
>
> To make sure someone doesn't play with your cards and mix up the order,
> use a permanent marker to draw a diagonal line on the side of the deck from
> corner to corner. If the cards ever get mixed up, you can put them back in
> order by making sure the diagonal line matches up.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 2055 bytes --]

  reply	other threads:[~2019-02-05  1:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-02 19:51 [bitcoin-dev] Card Shuffle To Bitcoin Seed rhavar
2019-02-04  6:49 ` Adam Ficsor
2019-02-04 21:05 ` James MacWhyte
2019-02-05  1:37   ` Devrandom [this message]
2019-02-06 13:48     ` Alan Evans
2019-02-06 13:51       ` Alan Evans
2019-02-07  2:42         ` James MacWhyte

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=CAB0O3SUG5QbbdYphEkyRrbGfeeVF2L1UFKrg_wM+cxz5qdSdkg@mail.gmail.com \
    --to=c1.bitcoin@niftybox.net \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=macwhyte@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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