public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andrew Poelstra <apoelstra@wpsoftware.net>
To: Rama Gan <ganrama@proton.me>
Cc: "bitcoindev@googlegroups.com" <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Penlock, a paper-computer for secret-splitting BIP39 seed phrases
Date: Thu, 16 May 2024 17:24:26 +0000	[thread overview]
Message-ID: <ZkZBSriGn96GDLg-@camus> (raw)
In-Reply-To: <ZkYJ21cloqyvT93G@camus>

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

On Thu, May 16, 2024 at 01:27:55PM +0000, Andrew Poelstra wrote:
> >
> > [3]: The 2-of-M wheel "Recovery" window shows the distance between two shares:
> > https://beta.penlock.io/2ofm-wheel.html
> >
> 
> Ah, I understand. Looking again at your wheel, I see that it's a
> combination slide wheel (for addition/subtraction) and slide chart (for
> "recovery windows").
> 
> What I'm saying is that you don't need to have extra cutout windows for
> the recovery windows. You should be able to just label the characters on
> the inner wheel with them, similar to how you have already labeled =
> with (1).
>

Ah, I am incorrect. You can put the recovery windows on a slide wheel
but it needs to use a different ordering than the one used for addition.
So you would need a second wheel and possibly some relabelling of
recovery windows.

I don't see why this is ... it seems that the recovery windows, being
differences of characters, should follow exactly the same pattern as
addition (possibly in the opposite direction). So worth investigating.

But assuming that it isn't possible and would require you introduce
another wheel, it's probably not worth the extra "simplicity". After
all, you only need to look up the windows once per share (so volvelle
ergonomics are not so important) and you only need to cut out as many
windows as you have shares (so setup/construction time is not bad).


-- 
Andrew Poelstra
Director, Blockstream Research
Email: apoelstra at wpsoftware.net
Web:   https://www.wpsoftware.net/andrew

The sun is always shining in space
    -Justin Lewis-Webster

-- 
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 email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/ZkZBSriGn96GDLg-%40camus.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-05-16 17:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-12 18:04 [bitcoindev] Penlock, a paper-computer for secret-splitting BIP39 seed phrases 'Rama Gan' via Bitcoin Development Mailing List
2024-05-13 13:40 ` Andrew Poelstra
2024-05-14 12:03   ` 'Rama Gan' via Bitcoin Development Mailing List
2024-05-14 13:42     ` Andrew Poelstra
2024-05-16  7:43       ` 'Rama Gan' via Bitcoin Development Mailing List
2024-05-16 13:27         ` Andrew Poelstra
2024-05-16 17:24           ` Andrew Poelstra [this message]
2024-05-24 10:39             ` 'Rama Gan' via Bitcoin Development Mailing List
2024-05-24 14:14               ` Andrew Poelstra
2024-05-24 15:02                 ` 'Rama Gan' via Bitcoin Development Mailing List
2024-05-14 12:43 ` 'Rama Gan' via Bitcoin Development Mailing List

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=ZkZBSriGn96GDLg-@camus \
    --to=apoelstra@wpsoftware.net \
    --cc=bitcoindev@googlegroups.com \
    --cc=ganrama@proton.me \
    /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