Browse Source

Fix typo

- Add acknowledgement of the typo finder
main
John Light 2 years ago
committed by GitHub
parent
commit
07d36d5062
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
  1. 4
      validity_rollups_on_bitcoin.md

4
validity_rollups_on_bitcoin.md

@ -35,7 +35,7 @@ Contact the author: <https://lightco.in/contact>
This report is the product of the author's participation in the Human Rights Foundation's [ZK-Rollup Research Fellowship](https://hrf.org/zkrollups). Financial support for the ZK-Rollup Research Fellowship was provided by Starkware and CMS Holdings. The author thanks these organizations for their support.
The author also thanks the following individuals for answering questions, providing insights and ideas, and/or giving feedback that contributed to the production of this report: Trey Del Bonis, Louis Guthmann, Patrick Dugan, Vitalik Buterin, Eli Ben-Sasson, Olaoluwa Osuntokun, Jeremy Rubin, Jameson Lopp, Alberto Garoffolo, Matt Corallo, Francis Corvino, Eric Wall, Dario Sneidermanis, Ruben Somsen, and Alex Gladstein. (Name order has been [randomized](https://www.random.org/lists/).)
The author also thanks the following individuals for answering questions, providing insights and ideas, and/or giving feedback that contributed to the production of this report: Trey Del Bonis, Francis Corvino, Jeremy Rubin, Sebastián Gustavo Reca, Eric Wall, Louis Guthmann, Matt Corallo, Patrick Dugan, Dario Sneidermanis, Alberto Garoffolo, Eli Ben-Sasson, Alex Gladstein, Olaoluwa Osuntokun, Ruben Somsen, Vitalik Buterin, and Jameson Lopp. (Name order has been [randomized](https://www.random.org/lists/).)
Please note that inclusion in this acknowledgements section should not be interpreted as an endorsement of the contents of this report. Any claims, conclusions, opinions, errors, _et cetera_ belong to the author alone, unless explicitly stated otherwise.
@ -217,7 +217,7 @@ Today, there are two ways that these programming languages could be used in a bi
In both cases, these alternative programming languages would not be able to operate on BTC natively. Instead, a bridge (also referred to as a "two-way peg" in the literature) would need to be built that would lock BTC on the bitcoin mainchain, release an equivalent amount of BTC IOUs inside the new execution environment, and implement some mechanism for converting the IOUs back into BTC on the mainchain.[^70] Today, the types of bridges that can be built to and from arbitrarily complex execution environments are limited by bitcoin consensus rules and generally considered less secure than using the bitcoin mainchain directly.[^71][^72]
If it were possible to build validity rollups with alternative execution environments on bitcoin, then bitcoin users could experiment with these alternative execution environments while retaining the full "self-custodial" ownership security of bitcoin L1. Validity rollups would eliminate the need for BTC IOUs, since validity rollups built on bitcoin would be able to operate on BTC nativelyAdditionally, because bitcoin full nodes would only have to verify a proof of correct computation, and not actually replay the full computation needed to execute rollup transactions, implementing these alternative execution models in a validity rollup would impose little-to-no additional computational burden on bitcoin full nodes.
If it were possible to build validity rollups with alternative execution environments on bitcoin, then bitcoin users could experiment with these alternative execution environments while retaining the full "self-custodial" ownership security of bitcoin L1. Validity rollups would eliminate the need for BTC IOUs, since validity rollups built on bitcoin would be able to operate on BTC natively. Additionally, because bitcoin full nodes would only have to verify a proof of correct computation, and not actually replay the full computation needed to execute rollup transactions, implementing these alternative execution models in a validity rollup would impose little-to-no additional computational burden on bitcoin full nodes.
### Section 3.2 New privacy protections

Loading…
Cancel
Save