public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Robert Dickinson <robert.lee.dickinson@gmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Ordinal Inscription Size Limits
Date: Sat, 28 Jan 2023 01:26:15 -0300	[thread overview]
Message-ID: <CABHetKxtRMgKC2myYd04UQQ3T2AvVSC7kpN_4_2p4MnHVnANRA@mail.gmail.com> (raw)
In-Reply-To: <Y9PPvBiWOXpBefmD@camus>

On Fri, Jan 27, 2023 at 10:21 AM Andrew Poelstra
<apoelstra@wpsoftware.net> wrote:

8<

> Unfortunately, as near as I can tell there is no sensible way to prevent
> people from storing arbitrary data in witnesses without incentivizing
> even worse behavior and/or breaking legitimate use cases.

8<

> There's a reasonable argument that this sort of data is toxic to the
> network, since even though "the market is willing to bear" the price of
> scares blockspace, if people were storing NFTs and other crap on the
> chain, then the Bitcoin fee market would become entangled with random
> pump&dump markets, undermining legitimate use cases and potentially
> preventing new technology like LN from gaining a strong foothold. But
> from a technical point of view, I don't see any principled way to stop
> this.
>
>
>
> --
> Andrew Poelstra
> Director of Research, Blockstream
> Email: apoelstra at wpsoftware.net
> Web:   https://www.wpsoftware.net/andrew
>
> The sun is always shining in space
>     -Justin Lewis-Webster
>

Thank you for your reply and explanations. If it be so, then I think
the principled route would be to make it a priority to continuously
educate people on the morals of the matter. Rather than for fads and
scams, the world would be a better place if ordinal inscriptions were
used for enduring, practical, and universally beneficial purposes,
such as for domain name inscription to solve the DNS centralization
problem.


  parent reply	other threads:[~2023-01-28  4:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 12:44 [bitcoin-dev] Ordinal Inscription Size Limits Robert Dickinson
2023-01-27 12:58 ` rot13maxi
2023-01-28 10:58   ` alicexbt
2023-01-29 10:34     ` Robert Dickinson
2023-01-31  8:58       ` Erik Aronesty
2023-01-27 13:21 ` Andrew Poelstra
2023-01-27 15:43   ` Aymeric Vitte
2023-01-28 16:47     ` Aymeric Vitte
2023-01-28  4:26   ` Robert Dickinson [this message]
2023-12-29 12:27   ` Greg Tonoski
2023-12-29 19:01     ` Nagaev Boris
2023-12-30  9:58     ` Erik Aronesty
2024-01-01 13:33       ` Brad Morrison
2024-01-01 16:08         ` Erik Aronesty
2024-01-03  9:11           ` Brad Morrison
2024-01-03 13:05             ` Erik Aronesty
2023-02-03 19:56 ` Melvin Carvalho
2023-02-04 14:25   ` Kostas Karasavvas
2023-02-06 16:39     ` Erik Aronesty
2023-02-06 17:31 ` Claus Ehrenberg
2023-02-06 18:05   ` Erik Aronesty
2023-02-07 12:17     ` Aymeric Vitte

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=CABHetKxtRMgKC2myYd04UQQ3T2AvVSC7kpN_4_2p4MnHVnANRA@mail.gmail.com \
    --to=robert.lee.dickinson@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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