Good morning Trey,
> * something like OP_PUSHSCRIPT which would remove the need for the
> introspection the the prevout's script and avoids duplicating data in
> the witness
> * some kind of OP_MERKLEUPDATEVERIFY which checks a merkle proof for a
> leaf against a root and checks if replacing the
On Fri, Nov 4, 2022 at 4:04 PM Trey Del Bonis via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> Instead of that approach, I assume we have fairly granular transaction
> introspection opcodes from a list in Elements [2] (which seem like they
> aren't actually used in mainnet
Hi all, I figured I could answer some of these rollup questions,
There's a few different possibilities to make rollups work that have
different tradeoffs. The core construction I worked out in [1] involves
a quine-ish recursive covenant that stores some persistent "state" as
part of the
Hi John,
Sorry for late feedback. Very much appreciated the in depth report!
So, I second Greg's main question, which I've really been thinking about a bit
myself since starting to research this area more: it feels like the Bitcoin
protocol research community (or, uh, some of it) should focus
On Wed, Oct 12, 2022, at 9:28 AM, Greg Sanders wrote:
> Is there a one page cheat sheet of "asks" for transaction
> introspection/OP_ZKP(?) and their uses both separately and together for
> different rollup architectures?
We do not have this yet. Trey Del Bonis wrote a more detailed technical
Thanks for the writeup John,
Is there a one page cheat sheet of "asks" for transaction
introspection/OP_ZKP(?) and their uses both separately and together for
different rollup architectures?
On Tue, Oct 11, 2022 at 11:52 AM John Light via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org>
Hi all,
Today I am publishing "Validity Rollups on Bitcoin", a report I produced as
part of the Human Rights Foundation's ZK-Rollup Research Fellowship.
Here's the preface:
> Ever since Satoshi Nakamoto first publicly announced bitcoin, its supporters,
> critics, and skeptics alike have
