Quote from: franky1 on Today at 07:47:37 AM

you will have to move the meme into each TX to show its current owner.
also it takes up space AGAIN due to lack of using just hashes of a meme instead of full meme data

No. This is incorrect. I don't know why you keep repeating this misinformation. I pleaded with you to actually look at a bitcoin transaction where one ordinal (inscribed ordinal) was sent from the minting address to another address. You obviously didn't do it because if you had you would realize that the transaction does not contain the bloated witness data associated with the transcription. This is because it is not necessary for the protocol to function.

The transcribing process only happens once. The transcription is forever associated with the resulting ordinal output, which is tracked by the protocol from owner to owner.

Let's pull a new example at random.

This is a Bitcoin Punk for sale on OpenSea via Emblem Vault (an Ethereum wrapper for bitcoin assets):

https://opensea.io/assets/ethereum/0x82c7a8f707110f5fbb16184a5933e9f78a34c6ab/17050183900261431

Looking at the bottom of the NFT description we see two block explorer links:

Pulling up the BTC Explorer link first we see two transactions. The older transaction is not related to the ordinal, but the newer one is, which is:

https://mempool.space/tx/5bff0c943a04f4320bdc1cd6d55407ce6e952bcb4c2be6866eb159c0c85a3536

(I like to use this explorer b/c it contains detailed info about witness data)

Its a 153 byte transaction from

bc1pme4kpyy7cmzz9gd5f6wdpsxlxk5qqwz3zx8mj7wjrsukcdpljggsxal4xz to
1PUY4ugnZ3oFtke6YU4LqpZeJhUNjyssjM, which is the address that currently holds the inscribed ordinal.

The witness data in this transaction is normal-sized.

Going backward to bc1pme... we see 2 transactions: a send and a receive. Looking at the receive transaction,

https://mempool.space/tx/b7a5cffd28b6c2db37880ac0321b18b4985c2ae4d75584a264d1334320ef532f

we see a much bigger size:

This is because the inscription happened in this transaction.

Putting the above tx ID into the ordinals explorer (+ "i0" per ordinal ID standard) yields the following:

https://ordinals.com/inscription/b7a5cffd28b6c2db37880ac0321b18b4985c2ae4d75584a264d1334320ef532fi0

You can see the ordinals explorer recognizes 1PUY4ugnZ3oFtke6YU4LqpZeJhUNjyssjM as the current owner of the Bitcoin Punk.

Here is a side-by-side comparison of the witness data of the minting transaction and first send transaction:

Ergo, the inscription data attached to an ordinal does not need to be re-inscribed upon each transfer.

Quote from: larry_vw_1955 on Today at 06:02:52 AM

everytime a bitcoin nft gets sold another copy of that same jpeg or whatever content it is gets duplicated. how inefficient! Huh

peoples' hard drives are gonna fill up real fast if that's the case.

Except that's not what happens regardless of what franky has to say about it. Anyone who is capable of logically following what I demonstrated above will realize this.