> They could have just as easily used OP_RETURN
outputs or any number of other data encoding techniques.
But doesn't OP_RETURN render the UTXO unspendable, thereby making it impossible
to "trade" the minted BTC-20 tokens?
Moth
Sent from Proton Mail for iOS
On Mon, May 8, 2023 at 7:55 PM, Peter Todd <[p...@petertodd.org](mailto:On Mon,
May 8, 2023 at 7:55 PM, Peter Todd <<a href=)> wrote:
> On Mon, May 08, 2023 at 08:16:41PM +0000, Moth via bitcoin-dev wrote:
>> From what I understand, things like inscriptions can only be inserted
>> between two specific flags - OP_FALSE and OP_IF.
>
> That's just an artifical limitation of the current inscription protocol. There
> are endless ways to embed arbitrary data in Bitcoin transactions. Blocking
> them
> all is a hopeless task.
>
>> Having a validation check to reject witness scripts that have arbitrary data
>> between these two flags could be used to reject inscriptions while still
>> allowing all the benefits of taproot. This will prevent people from
>> overloading the network with txns geared solely for ordinals and brc-20
>> tokens.
>>
>> Is there a reason such a validation check is a bad idea? We already have
>> OP_RETURN to store arbitrary data that is limited to 80kb. Was it an
>> oversight that arbitrary data can be inserted between OP_FALSE and OP_IF
>> when the size limit for witness scripts was lifted as part of taproot?
>
> It's pointless to even try.
>
> The current flood of inscription txs are very small, about 150vB, and embed
> very little data in the chain. They could have just as easily used OP_RETURN
> outputs or any number of other data encoding techniques. Blocking that kind of
> use-case is hopeless.
>
> The _purpose_ of the current flood of BRC-20 inscriptions - tl;dr the creation
> of a new set of assets via an auction - is something that doesn't even require
> any data to be embedded in the chain at all. They could have implemented them
> with perfectly normal transactions indistinguishable from any other
> transaction. Blocking that is truly hopeless.
>
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
