From: damian@willtech•com.au
To: Casey Rodarmor <casey@rodarmor•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Draft-BIP: Ordinal Numbers
Date: Thu, 24 Feb 2022 13:34:39 +1100 [thread overview]
Message-ID: <a54b2632d9b20f9330cf129706f5c886@willtech.com.au> (raw)
In-Reply-To: <CANLPe+Nc6ehatESSuS5jFXU-wammBSOe5GRjn45n8BAr90TPOg@mail.gmail.com>
Not all people who have been stolen from believe that they have lost the
right and title to what has been stolen and in many cases they have not.
I do not excuse Bitcoin that it is impossible to have any individual
Bitcoin identified but also I do not care, if I receive Bitcoin honestly
I do not care what their history was. What if they were taken from a
brothel? It is not a matter for an ordinal to determine if a satoshi is
fungible. It is truth in effect that each satoshi is newly created to
the new UTXO and the old satoshi destroyed. -DA.
On 2022-02-23 18:31, Casey Rodarmor wrote:
>> The least reasonable thing I could expect is some claimed former
>> holder of some ordianls turning up to challenge me that it was their
>> stolen Bitcoin was some of what I received.
>
> I think it's unlikely that this would come to pass. A previous owner
> of an ordinal wouldn't have any particular reason to expect that they
> should own it after they transfer it. Similar to how noting a dollar
> bill's serial number doesn't give you a claim to it after you spend
> it. From the BIP:
>
>> Since any ordinal can be sent to any address at any time,
>> ordinals that are transferred, even those with some public history,
>> should be considered to be fungible with other satoshis with no such
>> history. [1]
>
>
>
> Links:
> ------
> [1]
> https://github.com/casey/ord/blob/master/bip.mediawiki#backward-compatibility
next prev parent reply other threads:[~2022-02-24 2:34 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 [this message]
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
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=a54b2632d9b20f9330cf129706f5c886@willtech.com.au \
--to=damian@willtech$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=casey@rodarmor$(echo .)com \
/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