From: "John Light" <bitcoin-dev@lightco•in>
To: "Greg Sanders" <gsanders87@gmail•com>,
"Bitcoin Protocol Discussion"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Validity Rollups on Bitcoin
Date: Wed, 12 Oct 2022 11:40:10 -0400 [thread overview]
Message-ID: <224cf2f4-2577-4331-9977-ea71e9723ffe@app.fastmail.com> (raw)
In-Reply-To: <CAB3F3Dt5oy93duGvYb7SZ7wn7DCvn9FjVwRU9ENNa79yjzmdCQ@mail.gmail.com>
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 post about how those components would be used in a validity rollup, which was cited in my report and can be found here:
https://tr3y.io/articles/crypto/bitcoin-zk-rollups.html
But it'll take more research and design work to suss out those details you asked for and put them into a nice cheatsheet. I like this idea though!
next prev parent reply other threads:[~2022-10-12 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 15:40 John Light
2022-10-12 13:28 ` Greg Sanders
2022-10-12 15:40 ` John Light [this message]
2022-11-02 17:19 ` AdamISZ
2022-11-04 19:53 ` Trey Del Bonis
2022-11-04 20:29 ` Russell O'Connor
2022-11-04 23:07 ` ZmnSCPxj
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=224cf2f4-2577-4331-9977-ea71e9723ffe@app.fastmail.com \
--to=bitcoin-dev@lightco$(echo .)in \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gsanders87@gmail$(echo .)com \
/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