From: Billy Tetrud <billy.tetrud@gmail•com>
To: AdamISZ <AdamISZ@protonmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Draft-BIP: Ordinal Numbers
Date: Fri, 25 Feb 2022 09:56:24 -0600 [thread overview]
Message-ID: <CAGpPWDZxynGhOE7PpQ0sChvBODrM2k47KP6dRDu06oNUFJGyKA@mail.gmail.com> (raw)
In-Reply-To: <XdgBBHV0DwSOE9KMoCixmuFY1FpTLsoyhrPpE7zPI16nkUyGOAj_AMzi98jMCx8gAKYQdl4fodOIFFL8rpV7yCXT6XiiqvWk7bbFSyFaNUU=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
> El Gamal commitments, for example, are perfectly binding but only
computationally hiding.
That's very interesting. I stand corrected in that respect. Thanks for the
information Adam!
On Fri, Feb 25, 2022, 05:17 AdamISZ <AdamISZ@protonmail•com> wrote:
> > I really don't see a world where bitcoin goes that route. Hiding coin
> amounts would make it impossible to audit the blockchain and verify that
> there hasn't been inflation and the emission schedule is on schedule. It
> would inherently remove unconditional soundness from bitcoin and replace it
> with computational soundness. Even if bitcoin did adopt it, it would keep
> backwards compatibility with old style addresses which could continue to
> use ordinals.
>
> Nit: it isn't technically correct to say that amount hiding "inherently
> removes unconditional soundness". Such commitments can be either perfectly
> hiding or perfectly binding; it isn't even logically possible for them to
> be both, sadly. But we are not forced to choose perfect binding; El Gamal
> commitments, for example, are perfectly binding but only computationally
> hiding.
>
[-- Attachment #2: Type: text/html, Size: 1619 bytes --]
next prev parent reply other threads:[~2022-02-25 15:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 0:43 Casey Rodarmor
2022-02-23 7:02 ` damian
2022-02-23 7:10 ` Casey Rodarmor
2022-02-23 7:24 ` damian
2022-02-23 7:31 ` Casey Rodarmor
2022-02-24 2:34 ` damian
2022-02-24 15:55 ` Billy Tetrud
2022-02-24 21:03 ` Casey Rodarmor
2022-02-25 4:59 ` Billy Tetrud
2022-02-25 11:17 ` AdamISZ
2022-02-25 15:56 ` Billy Tetrud [this message]
2022-02-24 7:02 ` vjudeu
2022-02-24 7:17 ` Casey Rodarmor
2022-02-24 17:52 vjudeu
2022-02-24 21:02 ` Casey Rodarmor
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=CAGpPWDZxynGhOE7PpQ0sChvBODrM2k47KP6dRDu06oNUFJGyKA@mail.gmail.com \
--to=billy.tetrud@gmail$(echo .)com \
--cc=AdamISZ@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