Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 807FDC002D for ; Sat, 28 Jan 2023 04:26:31 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 471F7821E8 for ; Sat, 28 Jan 2023 04:26:31 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 471F7821E8 Authentication-Results: smtp1.osuosl.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=gG+5GjTz X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: 0.157 X-Spam-Level: X-Spam-Status: No, score=0.157 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, MALFORMED_FREEMAIL=1.235, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C7T6w8ACKxJ0 for ; Sat, 28 Jan 2023 04:26:28 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 6A26E81F77 Received: from mail-yw1-x112e.google.com (mail-yw1-x112e.google.com [IPv6:2607:f8b0:4864:20::112e]) by smtp1.osuosl.org (Postfix) with ESMTPS id 6A26E81F77 for ; Sat, 28 Jan 2023 04:26:28 +0000 (UTC) Received: by mail-yw1-x112e.google.com with SMTP id 00721157ae682-4c131bede4bso92824107b3.5 for ; Fri, 27 Jan 2023 20:26:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=DN6h2VukxysAwH5OJ6y28thJWU7KiCkPE75gsuo9H6Q=; b=gG+5GjTz/Z8NLut/d/doy4HfXnYmGQSPF4i5rnAaq+XJJkASJJSGgaIz7btBZqyO4o YyTFcVFHUA0HQYzGpKx7CXgiKxM9klYE67S7z6NMQZB0MeCW/v9xauK2on8d+CyEv9Sy E/VMVXvjnTjWSumT9SFpX/s8t9uL1pzFRutorl/bB/d1MaE4I569CDr7wgUnW77OD4Va qozBMFxCObucac+7NMgX4s4HhvMNQs9DC1nYlIiqfYd2+uxl6J+c6HvLOwGU5V1NGrHd ixpbrW1gXXReqyD9ckRHO2rYpQzZBubEqEAhBn0I6Bs8W+Fb0GQS21QpCGBwu3CyJYS1 pB0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=DN6h2VukxysAwH5OJ6y28thJWU7KiCkPE75gsuo9H6Q=; b=fK/THJu2qzkvko/l/0zLX++HoT+DQAwBQ/+5FU9QUJZj+KupvBcUubAc9ADuNEKW32 myLd7gA9exRDmD3YVF0mvNqBr6dTVDULRre6QTXLFo8S+kBFOq/RCoMmnp1eGHUB6FD2 BDLcIGivg81t/5EBY7Tb2IzDr7cUxf8hIFnPaHmmZQ0kcwckylFlwKDa6ZCHBEOV8RtD HmsRK3lmipdj0ve3FJDmyBAnmbtv8wG/+dJX/2JwBAlWnX9n1GBWr5ZRDPa8UOSMcq8T ortvLHOh3yTGx6NZOkk7wsREogVhmzAXHH0NsRGYdp5uh13ITP9DCAw7LHTJYjGRKUsR SbMQ== X-Gm-Message-State: AFqh2kowrhFoH4+gaBMMKTRaRNQOnudbXyoggWjDX4d4N9IWb/51vkf3 4Ag5f8QM+wNjNDBcD/jBujH7J2ymH86y0GTRTiqr7NfqPg== X-Google-Smtp-Source: AMrXdXsoAl1ppo9Rhtpa8Tbx+SdWhSSziif+zG/w0C7Q6tCqfWqoSnhfJ6VrHVQgjKEdhozVNvJz29fR5ecjN9p6n14= X-Received: by 2002:a81:40f:0:b0:4fd:870d:b6ce with SMTP id 15-20020a81040f000000b004fd870db6cemr3567824ywe.318.1674879987141; Fri, 27 Jan 2023 20:26:27 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Robert Dickinson Date: Sat, 28 Jan 2023 01:26:15 -0300 Message-ID: Cc: Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Sat, 28 Jan 2023 09:02:50 +0000 Subject: Re: [bitcoin-dev] Ordinal Inscription Size Limits X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2023 04:26:31 -0000 On Fri, Jan 27, 2023 at 10:21 AM Andrew Poelstra 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.