From: Bryan Bishop <kanzure@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>,
Bryan Bishop <kanzure@gmail.com>
Subject: Re: [bitcoin-dev] ChainWallet - A way to prevent loss of funds by physical violence
Date: Fri, 4 Oct 2019 05:02:59 -0500 [thread overview]
Message-ID: <CABaSBayF+nq+MdK3TY4_0Wkgn4qNMAWJub+q8e9amuig6gRE0Q@mail.gmail.com> (raw)
In-Reply-To: <4E84E4B0-7354-4681-985F-3DBFAA4E856F@astrotown.de>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
Since the user can't prove that they are using this technique, or
petertodd's timelock encryption for that matter, an attacker has little
incentive to stop physically attacking until they have a spendable UTXO.
I believe you can get the same effect with on-chain timelocks, or
delete-the-bits plus a rangeproof and a zero-knowledge proof that the
rangeproof corresponds to some secret that can be used to derive the
expected public key. I think Jeremy Rubin had an idea for such a proof.
Also, adam3us has described a similar thought here:
https://bitcointalk.org/index.php?topic=311000.0
- Bryan
On Fri, Oct 4, 2019, 4:43 AM Saulo Fonseca via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hi everyone
>
> If you are a hodler, I like to propose the creation of a key stretching as
> a new layer of protection over your current wallet.
>
[-- Attachment #2: Type: text/html, Size: 1581 bytes --]
prev parent reply other threads:[~2019-10-04 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 9:15 [bitcoin-dev] ChainWallet - A way to prevent loss of funds by physical violence Saulo Fonseca
2019-10-04 10:02 ` Bryan Bishop [this message]
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=CABaSBayF+nq+MdK3TY4_0Wkgn4qNMAWJub+q8e9amuig6gRE0Q@mail.gmail.com \
--to=kanzure@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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