From: Zheming Lin <heater@gmail•com>
To: Eric Voskuil <eric@voskuil•org>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal: Demonstration of Phase in Full Network Upgrade Activated by Miners
Date: Sat, 22 Jul 2017 11:58:21 +0800 [thread overview]
Message-ID: <CAJVXTPm2HZ989j3HiRXxJWoaT_r61ySF=v3xptdoyOUvhWPhqA@mail.gmail.com> (raw)
In-Reply-To: <8999832B-BD81-415A-9CA5-0DE397A1A904@voskuil.org>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
I think we should not switch to Proof of Stake system.
in Proof of Stake system, the one with more voting power tend to protect
their investment and that will stop others from competing with them. they
will use the voting power to make entering barrier, limiting the
competition is bad for bitcoin economy (I believe).
Miners are not centralized, they just grow bigger and be industrialized,
but there's still a lot of competition. The competition is the main
security model of bitcoin system.
When we are talking about "security" in bitcoin system, we are talking
about the probability that a transaction revert or change. We can not be
100% sure under 3 confirmations, but in 6 or more confirmations, we think
the cash received is safe and can't be taken away. That's the security
provided by bitcoin system.
Hard fork is not dangerous, when hard fork happens, people can wait for a
short time (like maintenance of a POS/CreditCard system). When the chain
with most hashrate wins (with high enough probability), we can then safely
assume that the longest chain can't be reverted.
Regards,
LIN Zheming
[-- Attachment #2: Type: text/html, Size: 1607 bytes --]
next prev parent reply other threads:[~2017-07-22 3:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 2:23 Zheming Lin
2017-06-13 5:44 ` James Hilliard
2017-06-13 6:50 ` Zheming Lin
2017-06-13 7:19 ` James Hilliard
2017-06-13 8:13 ` Zheming Lin
2017-06-13 8:37 ` James Hilliard
2017-06-13 19:35 ` Jared Lee Richardson
2017-06-14 0:23 ` James Hilliard
2017-06-14 1:08 ` Jared Lee Richardson
2017-06-13 8:24 ` Zheming Lin
2017-06-13 10:20 ` James Hilliard
2017-06-13 18:11 ` Gregory Maxwell
2017-06-14 16:39 ` Zheming Lin
2017-06-14 17:20 ` Jameson Lopp
2017-06-14 18:29 ` Zheming Lin
2017-06-14 18:55 ` Jameson Lopp
2017-06-14 19:04 ` Zheming Lin
2017-06-14 20:11 ` Jameson Lopp
2017-06-16 14:39 ` Zheming Lin
2017-06-15 5:04 ` Eric Voskuil
2017-06-15 18:38 ` Erik Aronesty
2017-06-16 3:09 ` Eric Voskuil
2017-07-22 3:58 ` Zheming Lin [this message]
2017-06-14 18:30 ` Zheming Lin
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='CAJVXTPm2HZ989j3HiRXxJWoaT_r61ySF=v3xptdoyOUvhWPhqA@mail.gmail.com' \
--to=heater@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=eric@voskuil$(echo .)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