From: abdelhamid bakhta <abdelhamid.bakhta@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] RGB / Mimblewhimble: modularity of underlying ZK schemes
Date: Thu, 30 Jun 2022 14:27:44 +0200 [thread overview]
Message-ID: <CAOPkkH=5HWuPw=zvDFVpoB0c=KZmoBk=3BpmwSkMMu=g90Hw-g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
Hi,
I am wondering if there is some documentation about the modularity of the
underlying ZK schemes used to bring privacy on RGB. Specifically, seeing
that it currently uses Bulletproofs that are not Quantum Resistant, I am
wondering how hard it would be to switch to a Quantum resistant
alternative. Generally speaking, what is the design rationale for
cryptographic primitives used in the Bitcoin ecosystem?
What do people think about using ZK-Starks for some use cases like this?
Has anyone started to experiment something on that front ?
I am not sure about the most important criteria for RGB use cases between:
- proving time
- verification time
- size of proofs
- quantum resistance
- communication complexity
I am very curious about the particular choice of Bulletproofs in this
context and cannot find any useful information about it.
Thanks for your help.
[-- Attachment #2: Type: text/html, Size: 992 bytes --]
reply other threads:[~2022-06-30 12:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAOPkkH=5HWuPw=zvDFVpoB0c=KZmoBk=3BpmwSkMMu=g90Hw-g@mail.gmail.com' \
--to=abdelhamid.bakhta@gmail$(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