From: Casey Rodarmor <casey@rodarmor•com>
To: vjudeu@gazeta•pl,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: Billy Tetrud <billy.tetrud@gmail•com>
Subject: Re: [bitcoin-dev] Draft-BIP: Ordinal Numbers
Date: Thu, 24 Feb 2022 13:02:05 -0800 [thread overview]
Message-ID: <CANLPe+ND4u76QxL4c4wy-=t-B4sCeB1G-_X1QBGa8aUCgy=kGg@mail.gmail.com> (raw)
In-Reply-To: <157676573-26d876ec3baac7f177731a4fa956fb25@pmq3v.m5r2.onet>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
> When we talk about future improvements, there could be even bigger
problem with ordinal numbers: what if/when we introduce some Monero-like
system and hide coin amounts? (for example by using zero satoshi, because
we have to use something that will be backward-compatible). Zero is quite
interesting amount, because it means "skip amount checking for old
clients". That can be used in many ways to introduce many protocols (and
also to add fractional satoshis on-chain, because 0.4 satoshis could be
represented as zero), so if that amounts will be simply ignored, then I
wonder how it would be possible to connect some future protocol based on
that with ordinal numbers.
Ordinal numbers are inherently public, so it seems reasonable that they
don't work with transactions that are private or have obfuscated values.
[-- Attachment #2: Type: text/html, Size: 953 bytes --]
next prev parent reply other threads:[~2022-02-24 21:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 17:52 vjudeu
2022-02-24 21:02 ` Casey Rodarmor [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2022-02-24 7:02 ` vjudeu
2022-02-24 7:17 ` 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='CANLPe+ND4u76QxL4c4wy-=t-B4sCeB1G-_X1QBGa8aUCgy=kGg@mail.gmail.com' \
--to=casey@rodarmor$(echo .)com \
--cc=billy.tetrud@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=vjudeu@gazeta$(echo .)pl \
/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