š
Original date posted:2018-01-30
š Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 01/30/2018 01:43 AM, CANNON via bitcoin-dev wrote:
>
>
> -------- Forwarded Message --------
> Subject: RE: NIST 8202 Blockchain Technology Overview
> Date: Mon, 29 Jan 2018 12:25:05 +0000
> From: Yaga, Dylan (Fed) <dylan.yaga at nist.gov>
> To: CANNON <cannon at cannon-ciota.info>
>
> Thank you for your comments.
> You, along with many others, expressed concern on section 8.1.2.
> To help foster a full transparency approach on the editing of this section, I am sending the revised section to you for further comment.
>
> 8.1.2 Bitcoin Cash (BCH)
> In 2017, Bitcoin users adopted an improvement proposal for Segregated Witness (known as SegWit, where transactions are split into two segments: transactional data, and signature data) through a soft fork. SegWit made it possible to store transactional data in a more compact form while maintaining backwards compatibility. However, a group of users had different opinions on how Bitcoin should evolve and developed a hard fork of the Bitcoin blockchain titled Bitcoin Cash. Rather than implementing the SegWit changes, the developers of Bitcoin Cash decided to simply increase the blocksize. When the hard fork occurred, people had access to the same amount of coins on Bitcoin and Bitcoin Cash.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
This is much better than the original. My question, the part where it says segwit makes transactions more compact, I thought that transactions are not more compact but rather they just take advantage of extra blockspace beyond that of 1 MB? Yes they would appear to be more compact to un-upgraded nodes due to the witness being stripped, but the transactions are not actually more compact right?
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJab+afAAoJEAYDai9lH2mwCDAP/RRpExXmnPzlvxuhhJ+8gSlc
QRZHVa0nJ2SETTZnQSa+0t8dBO9ROYSnDHuMEqz/ba8o00Rce8icxQvCGOO29OSK
Cru7/UJzYTwnt5mK2ljpUB1Fsx96fAPxfg4QMeDCRe+O5LLkH1als1GGVOwlFnLu
BAV0MoCljWzBxokf0ax8+ZHHYEaKe+Fj9PKby7CZrqQKoL9PkI/n7EvqICUdTCu5
tAz9SNIBVtUxgGx/ZY96hvBx0zorV1IQEWchQ50oh/V+TgmnOW4njQOKc4TcSgfp
TKpRFs8Zd7TzeIS/85GX0APGypchxdjlBaV0EORTO9GYFo7nKlzHkIGOF9Er+E6q
II4qjbKLc5d/wwCIA8MHFW0Vxwv2+0ztApaWAFW42+LeHERaPCzi4NEy5quqvmsE
IiTaGebl2XbTd0I+aB6WWsScTUmfXrt+NL05kwE0KDylY/mSwYMgYjP95X1Mci7X
rcJRf6/pP607EiHlq3MmDlyt4TrYBp9FVVjdjvM+sD8wz72FhWeYJQdyF8t1ToOD
U/ItNsxl5Jx9JvCkBXoX+6MMZ91W7D2x04Ur3OMRmy/lOoztOYAdlKy0tMyRqfCi
L81apfjvmTaR2OTWhCawgZGLXGJcfOG5ECuXC90B6il5Jsts/XwyFMN2Fa1iZB50
cZwF3ySKxoVtpsf/vTW7
=feRa
-----END PGP SIGNATURE-----
CANNON [ARCHIVE] /
npub145ā¦6gmta
2023-06-07 18:10:22
in reply to nevent1qā¦5txx
Author Public Key
npub145wc7mvqwpndzrtzxq2nqszthnq9cq4kcpx7nwl48uqtyfzw0nmse6gmtaPublished at
2023-06-07 18:10:22Event JSON
{
"id": "772864dde160963ae34903be6320435cfdfe517d268550d92a613d628359452e",
"pubkey": "ad1d8f6d807066d10d62301530404bbcc05c02b6c04de9bbf53f00b2244e7cf7",
"created_at": 1686161422,
"kind": 1,
"tags": [
[
"e",
"5634a4e7015507d7a4ec005d69e3e960b35f3fc119981438b4a0169f2a09640f",
"",
"root"
],
[
"e",
"378784b9c962efd16c7d854eeef2fd8256d4640a1ea40b2442eae9a4a1025d09",
"",
"reply"
],
[
"p",
"ad1d8f6d807066d10d62301530404bbcc05c02b6c04de9bbf53f00b2244e7cf7"
]
],
"content": "š
Original date posted:2018-01-30\nš Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA512\n\nOn 01/30/2018 01:43 AM, CANNON via bitcoin-dev wrote:\n\u003e \n\u003e \n\u003e -------- Forwarded Message --------\n\u003e Subject: RE: NIST 8202 Blockchain Technology Overview\n\u003e Date: Mon, 29 Jan 2018 12:25:05 +0000\n\u003e From: Yaga, Dylan (Fed) \u003cdylan.yaga at nist.gov\u003e\n\u003e To: CANNON \u003ccannon at cannon-ciota.info\u003e\n\u003e \n\u003e Thank you for your comments.\n\u003e You, along with many others, expressed concern on section 8.1.2.\n\u003e To help foster a full transparency approach on the editing of this section, I am sending the revised section to you for further comment. \n\u003e \n\u003e 8.1.2\tBitcoin Cash (BCH)\n\u003e In 2017, Bitcoin users adopted an improvement proposal for Segregated Witness (known as SegWit, where transactions are split into two segments: transactional data, and signature data) through a soft fork. SegWit made it possible to store transactional data in a more compact form while maintaining backwards compatibility. However, a group of users had different opinions on how Bitcoin should evolve and developed a hard fork of the Bitcoin blockchain titled Bitcoin Cash. Rather than implementing the SegWit changes, the developers of Bitcoin Cash decided to simply increase the blocksize. When the hard fork occurred, people had access to the same amount of coins on Bitcoin and Bitcoin Cash.\n\u003e \n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e \n\nThis is much better than the original. My question, the part where it says segwit makes transactions more compact, I thought that transactions are not more compact but rather they just take advantage of extra blockspace beyond that of 1 MB? Yes they would appear to be more compact to un-upgraded nodes due to the witness being stripped, but the transactions are not actually more compact right?\n-----BEGIN PGP SIGNATURE-----\n\niQIcBAEBCgAGBQJab+afAAoJEAYDai9lH2mwCDAP/RRpExXmnPzlvxuhhJ+8gSlc\nQRZHVa0nJ2SETTZnQSa+0t8dBO9ROYSnDHuMEqz/ba8o00Rce8icxQvCGOO29OSK\nCru7/UJzYTwnt5mK2ljpUB1Fsx96fAPxfg4QMeDCRe+O5LLkH1als1GGVOwlFnLu\nBAV0MoCljWzBxokf0ax8+ZHHYEaKe+Fj9PKby7CZrqQKoL9PkI/n7EvqICUdTCu5\ntAz9SNIBVtUxgGx/ZY96hvBx0zorV1IQEWchQ50oh/V+TgmnOW4njQOKc4TcSgfp\nTKpRFs8Zd7TzeIS/85GX0APGypchxdjlBaV0EORTO9GYFo7nKlzHkIGOF9Er+E6q\nII4qjbKLc5d/wwCIA8MHFW0Vxwv2+0ztApaWAFW42+LeHERaPCzi4NEy5quqvmsE\nIiTaGebl2XbTd0I+aB6WWsScTUmfXrt+NL05kwE0KDylY/mSwYMgYjP95X1Mci7X\nrcJRf6/pP607EiHlq3MmDlyt4TrYBp9FVVjdjvM+sD8wz72FhWeYJQdyF8t1ToOD\nU/ItNsxl5Jx9JvCkBXoX+6MMZ91W7D2x04Ur3OMRmy/lOoztOYAdlKy0tMyRqfCi\nL81apfjvmTaR2OTWhCawgZGLXGJcfOG5ECuXC90B6il5Jsts/XwyFMN2Fa1iZB50\ncZwF3ySKxoVtpsf/vTW7\n=feRa\n-----END PGP SIGNATURE-----",
"sig": "47f399d0ea2d8a1349e90ae0123e890d4931485dac923cd7f7fccb1ec72c164c43d1248a85d0610722ee9ac7b7f3f39cd2b442c6ad3c1939a1a4c956668d5612"
}