From: CANNON <cannon@cannon-ciota•info>
To: Damian Williamson <willtech@live•com.au>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] NIST 8202 Blockchain Technology Overview
Date: Tue, 6 Feb 2018 02:08:24 +0000 [thread overview]
Message-ID: <bccd08e1-8fe5-dca8-bb04-2d5a77c43005@cannon-ciota.info> (raw)
In-Reply-To: <PS2P216MB0179F59241705B69BC88CFEF9DFB0@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 01/31/2018 11:16 AM, Damian Williamson wrote:
> I disagree with the correctness of the following statement:
>
>
>> Rather than implementing the SegWit changes, the developers of Bitcoin Cash decided to simply increase the blocksize.
>
>
> I would suggest "Rather than being satisfied with the implementation of SegWit changes alone, the developers of
> Bitcoin Cash decided to also increase the blocksize.
>
>
> Regards,
>
> Damian Williamson
You do realize that segwit includes many improvements of which are unrelated to scaling? These same improvements of which
simply increasing the blocksize alone would not fix or enable. Segwit is not just a blocksize increase.
Bitcoin Cash, while increasing the blocksize directly, from my understanding has yet to implement the
improvements and capabilities that segwit enables.
One example being, with transactions hashes being able to be calculated in advanced prior to signing
(due to the signature being in different section than that used
to calculate the transaction ID) it is possible to create transaction trees, enhanced smart contracts, trustless mixing protocols,
micropayment networks, etc...
Segwit also increases the security of signatures.
There are lots of other things segregated witness enables as well.
By saying "..segwit changes alone.... decided to also..." Bitcoin Cash has not implemented segwit. Bitcoin Cash only
increased the blocksize.
that wording above at least from the way I read it, seems to imply that Bitcoin Cash has segwit.
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJaeQ3IAAoJEAYDai9lH2mwKkQP/3dgYApq1qv2lGIyZIdeN9SE
D5AuXPqFQYAoMwhC0RPNQU/jUisKIyd6zm4XCIm6KPufCtXkjfH9FLhd0ThbCTcy
Gk+pYYRBzSuBZdPBKg0DHu7alRETtxbdtUI0zDfERt1FFZb+HmcDcGTfwdVci3fa
jBiFXq1R+myMW5xdB44dipSk5kBhcpx2zitr1bIA4rF11QbxKAmzU7iPdRpA+PXz
gB9NImc1Dbz+TEA50tdq3v9Ov3x7m7F+QtBnqyLAigJh6XKa6guCfwKIGoawRGwZ
v2ur7T+Qh3KGRXCBlHnxgtFte16wHagwvsVgE5EEmJR0yJUc/4XU2kCGANVNDZ/P
pphqk8pruQ5rjQ8S+s6i5XG8oHVSB2fDh56NvPY7msA72j+Gk+XneV2eJbEAdjhb
9Ci7u1uPJL3pb3c/ZOwQvpIRV3tRjlh0DertWkd3Li5RZLO3uFvBTxNxrni6+9bf
/cmAOwfHjoUp8BX/nvgMjpIDCoEu+Rv9IO/ok3s3mX300JbczAdGbXbsPTE5G+DI
RB1kSmszwst8wOlOAsdVqk/iKRJdN9daTGGN6aE/wjkpSg8rW9BOaoI2X9t4oXCU
+oe/WlgkxhxPcNyhKpLeeYVe6nFX2fjU+THyyiAq/LJ/qHU/brKpXc4NesCVHhQP
BBlxiN0E4gndMGs/Lx89
=+UCK
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-02-06 2:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 0:40 CANNON
2018-01-30 1:43 ` CANNON
2018-01-30 3:30 ` CANNON
2018-01-30 7:22 ` Peter Todd
[not found] ` <PS2P216MB0179F59241705B69BC88CFEF9DFB0@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM>
2018-02-06 2:08 ` CANNON [this message]
2018-02-06 7:07 ` Damian Williamson
[not found] <cad6fbdf-b826-41e8-f8ff-c37ec72193e9@cannon-ciota.info>
2018-01-29 1:08 ` CANNON
[not found] ` <BY1PR09MB09045CA927AB6A87BBB315D9E4E50@BY1PR09MB0904.namprd09.prod.outlook.com>
2018-02-18 16:20 ` CANNON
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=bccd08e1-8fe5-dca8-bb04-2d5a77c43005@cannon-ciota.info \
--to=cannon@cannon-ciota$(echo .)info \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=willtech@live$(echo .)com.au \
/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