From: blk0 <blk0@protonmail•com>
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] ZeroSync: Introducing Validity Proofs to Bitcoin
Date: Mon, 28 Aug 2023 07:49:02 +0000 [thread overview]
Message-ID: <FWXh5Ug0jlXcbBMFSuClnPPz56fsgnZGjtBjV30rg0dZWELOytdxIvZyh1qzGyi1m9qBFrMBikc1NbEGye5hLuxXK_MPB0NVWAHdrcFt3Zk=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
Peter Todd wrote:
>Two serious issues with this proposal:
>1) You're creating an alternative implementation of the Bitcoin protocol. There
>is a _long_ history of such implementations failing to implement an exact copy
>of the consensus rules, leading to potential forks. Obviously, if only used by
>otherwise lite clients, there is less of a risk associated with this. But the
>risk is there and will expand as this tech is used for more sophisticated
>things.
There is a general purpose zkVM implementation for the RISC-V instruction set:
https://www.risczero.com/
Since Bitcoin Core can be compiled for RISC-V, and RiscZero can prove
execution traces of a RISC-V VM, this argument no longer applies: the exact
consensus rules would be applied and verified.
@blk014
[-- Attachment #2: Type: text/html, Size: 6117 bytes --]
next reply other threads:[~2023-08-28 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 7:49 blk0 [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-12 12:12 Robin Linus
2023-05-12 15:32 ` Weiji Guo
2023-05-12 16:03 ` Robin Linus
2023-06-05 18:47 ` Peter Todd
2023-06-05 18:59 ` Erik Aronesty
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='FWXh5Ug0jlXcbBMFSuClnPPz56fsgnZGjtBjV30rg0dZWELOytdxIvZyh1qzGyi1m9qBFrMBikc1NbEGye5hLuxXK_MPB0NVWAHdrcFt3Zk=@protonmail.com' \
--to=blk0@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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