From: Aymeric Vitte <aymeric@peersm•com>
To: Christopher Allen <ChristopherA@lifewithalacrity•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Moth <moth_oshi@proton•me>
Subject: Re: [bitcoin-dev] Witness script validation to reject arbitrary data
Date: Tue, 9 May 2023 19:45:11 +0200 [thread overview]
Message-ID: <39514580-3d3e-d633-8270-952caab73b1e@peersm.com> (raw)
In-Reply-To: <CACrqygCN-LLttNks-MpBKErZauZyx8hpV=MCgvACRoOcRxETOQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
Le 08/05/2023 à 23:43, Christopher Allen via bitcoin-dev a écrit :
> There was a recent thread discussing raising the limit on
> OP_RETURN https://github.com/bitcoin/bitcoin/issues/27043
Indeed we already discussed all of this, and the conclusion was: there
are no reasons to impose limits, because people will find some deviant
(or not) workarounds (like Stamps), and fees will regulate this
And how to control the value of what is stored? If I store e=mc2, the
way I like since as many said it's super easy to find plenty of ways to
store in bitcoin, this one is short and supposed to have more value than
bitcoin, no?
Personnally I think of course that you should store a reference to
something and not the something, so a few hashes and/or signatures which
you cannot do with OP_RETURN today (80B Moth, not 80kB)
I don't see very well what can be done against the freeriders, except
avoiding that they impact the whole network (a bit à la bittorrent),
maybe the issue is more about decentralization rather than trying to
impose limitations, so the decentralized miners can't have the whole
image of the whole txs and hold low fees txs, which is not the case at
all today, but it seems a bit utopic right now
Or maybe when the ordinal meme stuff/BRC20 will be proven to have
finally zero value the market will self regulate
[-- Attachment #2: Type: text/html, Size: 2208 bytes --]
next prev parent reply other threads:[~2023-05-09 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 20:16 Moth
2023-05-08 21:33 ` angus
2023-05-08 21:43 ` Christopher Allen
2023-05-09 17:45 ` Aymeric Vitte [this message]
2023-05-08 23:55 ` Peter Todd
2023-05-09 12:20 ` Moth
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=39514580-3d3e-d633-8270-952caab73b1e@peersm.com \
--to=aymeric@peersm$(echo .)com \
--cc=ChristopherA@lifewithalacrity$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=moth_oshi@proton$(echo .)me \
/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