From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id EB26AC002B for ; Sun, 29 Jan 2023 10:35:06 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id C44B560BA8 for ; Sun, 29 Jan 2023 10:35:06 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org C44B560BA8 Authentication-Results: smtp3.osuosl.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=jhNTOg1F 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 smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dmLq71nctnjP for ; Sun, 29 Jan 2023 10:35:06 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 1BC6460B46 Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by smtp3.osuosl.org (Postfix) with ESMTPS id 1BC6460B46 for ; Sun, 29 Jan 2023 10:35:05 +0000 (UTC) Received: by mail-yb1-xb2a.google.com with SMTP id x4so10924559ybp.1 for ; Sun, 29 Jan 2023 02:35:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=IbdhvfVsGvxipXtF8tl/SibX+R2RibgpBsnF1pgi82c=; b=jhNTOg1FdBovRmcE6ysN+QvNpQ/BSDHLZ1W8kM9cH/H42h38BFVHUyYUQSgxqUAWxQ zsxNvLCags7iBWLu34fGtp9ft+PXDI7sN6txNLYjhnlIzYy0pk77tp14ettNVXCPmKtY FAZWO9BPnTG2GTUkrRJKZ9nTWIiHN9D5ysvZxURjbp1Yuce97utoIBkqaGvDkVbI6AVr Fat7kFpUz2u6usikyntWMpiMQK5wOwOiEV3Sty1VTm/DXWlEOkFKW7QJMALfBN9Auh8h IuPqHSIQUDTqP/IddhNjOGg6zwBU42Xg4V4CWNjxlOIKGi0Gfu0CP1xKtBVYWXuDa5BA 7o2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding: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=IbdhvfVsGvxipXtF8tl/SibX+R2RibgpBsnF1pgi82c=; b=eTngywjSg1OnAbDGl02ZmxVdo19dEF2m0xhSPW3RFT4RdE4xxGKrD2k+bBE26D7/ZE Q9u5RxtRaXL121m1QA2OA1foLmPEzZEXOHzrAG8jsQGyYx1hoEsQPWrZhg7jRN0Tp0xX eYCZxnZDHXnIDUosz/hHdgasxqFGKjFcY7ZktIpQ9Tn7HufW6WxJfnPqCOpEb0SepWUs v84zUsiQWXnUF2vVX1iCZOYqOVMhWPLQkwJTE93/BlB2lMyUFN7TXqDt6Ce3KyTsfl9q eWiwMWfCW7/EPqA7SFaw5t6itIXISsV/eIKNwDsnvuZNwdGjhFQCZRcucdbzVPVTeZs0 1hMg== X-Gm-Message-State: AFqh2kpkS27JhOT7arPWJZhq0jCJ67qV4M/0zr5Wxfo0bxe+PKU9A9RE gkXyxeyMQC5zMGrXRfTuJSObEDKLOsdrZ4IEel76BRKDBQ== X-Google-Smtp-Source: AMrXdXvxe5bAEJ+QOa34C+WDnQbUYGeOdslj5Jv4Yo2tyrCqvgsCuwI2junkYjBmHQc51lUBpnva0JMK23IkrkULBsU= X-Received: by 2002:a5b:a8d:0:b0:707:3f66:a611 with SMTP id h13-20020a5b0a8d000000b007073f66a611mr7198908ybq.216.1674988504905; Sun, 29 Jan 2023 02:35:04 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Robert Dickinson Date: Sun, 29 Jan 2023 07:34:54 -0300 Message-ID: Cc: Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Sun, 29 Jan 2023 10:43:19 +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: Sun, 29 Jan 2023 10:35:07 -0000 On Sat, Jan 28, 2023 at 7:58 AM alicexbt wrote: > > Hi Bitcoin Developers, > > > Anyone who runs an unpruned bitcoin node should be capacity-planning th= eir disk space assuming that in the future blocks will be more full - as de= mand for blockspace increases, people will make better use of the space tha= t we already have and average block weight will trend upwards. If you=E2=80= =99re thinking about how much disk you will need when we have consistently = full blocks, ordinal inscriptions don=E2=80=99t change that number. > > I completely agree with this. I fully agree with this too. It was a sloppy remark on my part-- thanks for claifying. Underlying my remark was a bit of disgust from knowing that in the future, a (perhaps large) X number of GB of what should have been financial data will actually turn out to be something else entirely. Time/space on the Bitcoin blockchain is a shared limited resource and should be treated accordingly. We can say "no worries...the price and demand will sort everything out," but hopefully we all want Bitcoin to be the best financial tool it can be. =E2=80=9CIf the ax is not sharp and he does not make it sharp, then he must use more strength. Wisdom helps one to do well.=E2=80=9D