From: AdamISZ <AdamISZ@protonmail.com>
To: Billy Tetrud <billy.tetrud@gmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Draft-BIP: Ordinal Numbers
Date: Fri, 25 Feb 2022 11:17:29 +0000 [thread overview]
Message-ID: <XdgBBHV0DwSOE9KMoCixmuFY1FpTLsoyhrPpE7zPI16nkUyGOAj_AMzi98jMCx8gAKYQdl4fodOIFFL8rpV7yCXT6XiiqvWk7bbFSyFaNUU=@protonmail.com> (raw)
In-Reply-To: <CAGpPWDbquYT4gm_eKTrtsHsCNRf2fU0gvHOz--jRVhVgUzFHYQ@mail.gmail.com>
> 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.
next prev parent reply other threads:[~2022-02-25 11:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 0:43 [bitcoin-dev] Draft-BIP: Ordinal Numbers 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 [this message]
2022-02-25 15:56 ` Billy Tetrud
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='XdgBBHV0DwSOE9KMoCixmuFY1FpTLsoyhrPpE7zPI16nkUyGOAj_AMzi98jMCx8gAKYQdl4fodOIFFL8rpV7yCXT6XiiqvWk7bbFSyFaNUU=@protonmail.com' \
--to=adamisz@protonmail.com \
--cc=billy.tetrud@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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