From: vjudeu@gazeta•pl
To: damian@willtech•com.au, Casey Rodarmor <casey@rodarmor•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Draft-BIP: Ordinal Numbers
Date: Thu, 24 Feb 2022 08:02:06 +0100 [thread overview]
Message-ID: <157547153-6d2c3d68baafa7157fc9862342a73750@pmq4v.m5r2.onet> (raw)
In-Reply-To: <0642a5e59464779569f9d0aab452ee27@willtech.com.au>
> The system sounds expensive eventually to cope with approximately 2,100,000,000,000,000 ordinals.
What about zero satoshis? There are transactions, where zero satoshis are created or moved. Typical users cannot do that, but miners can, we currently have such transactions in the blockchain, for example 9f0b871e28fa19e2308e2fa74243bf2dcf23b160754df847d5f1e41aabe499d1 (check the last two inputs).
On 2022-02-24 01:53:36 user damian--- via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> Well done, your bip looks well presented for discussion. You say to
number each satoshi created? For a 50 BTC block reward that is
5,000,000,000 ordinal numbers, and when some BTC is transferred to
another UTXO how do you determine which ordinal numbers, say if I create
a transaction to pay-to another UTXO. The system sounds expensive
eventually to cope with approximately 2,100,000,000,000,000 ordinals. If
I understand ordinals 0 to 5,000,000,000 as assigned to the first
Bitcoin created from mining block-reward. Say if I send some Bitcoin to
another UTXO then first-in-first-out algorithm splits those up to assign
1 to 100,000,000 to the 1 BTC that I sent, and 100,000,001 to
5,000,000,000 are assigned to the change plus if any fee?-DA.
On 2022-02-23 11:43, Casey Rodarmor via bitcoin-dev wrote:
> Briefly, newly mined satoshis are sequentially numbered in the order
> in
> which they are mined. These numbers are called "ordinal numbers" or
> "ordinals". When satoshis are spent in a transaction, the input
> satoshi
> ordinal numbers are assigned to output satoshis using a simple
> first-in-first-out algorithm.
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists•linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2022-02-24 7:09 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
2022-02-24 7:02 ` vjudeu [this message]
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=157547153-6d2c3d68baafa7157fc9862342a73750@pmq4v.m5r2.onet \
--to=vjudeu@gazeta$(echo .)pl \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=casey@rodarmor$(echo .)com \
--cc=damian@willtech$(echo .)com.au \
/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