From: DANIEL YIN <r8921039@hotmail.com>
To: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] bitcoin-dev Digest, Vol 27, Issue 10
Date: Tue, 22 Aug 2017 18:18:13 +0000 [thread overview]
Message-ID: <CY4PR1001MB2342A41F54C2309F2B130B1D85840@CY4PR1001MB2342.namprd10.prod.outlook.com> (raw)
In-Reply-To: <mailman.17549.1503424685.1678.bitcoin-dev@lists.linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
> Very true, if Moore's law is still functional in 200 years, computers will
> be 2^100 times faster (possibly more if quantum computing becomes
> commonplace), and so old wallets may be easily cracked.
>
> We will need a way to force people to use newer, higher security wallets,
> and turning coins to mining rewards is better solution than them just being
> hacked.
Even in such an event, my personal view is the bitcoin owner should have the
freedom to choose upgrade to secure his/her coins or to leave the door
open for the first hacker to assume the coins - yet the bitcoin network
that he/she trusts should not act like a hacker to assume his/her coins.
daniel
[-- Attachment #2: Type: text/html, Size: 2249 bytes --]
parent reply other threads:[~2017-08-22 18:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.17549.1503424685.1678.bitcoin-dev@lists.linuxfoundation.org>]
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=CY4PR1001MB2342A41F54C2309F2B130B1D85840@CY4PR1001MB2342.namprd10.prod.outlook.com \
--to=r8921039@hotmail.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