From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 95DC3C002B for ; Tue, 31 Jan 2023 08:59:00 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 7DFD2813F4 for ; Tue, 31 Jan 2023 08:59:00 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 7DFD2813F4 Authentication-Results: smtp1.osuosl.org; dkim=pass (2048-bit key) header.d=q32-com.20210112.gappssmtp.com header.i=@q32-com.20210112.gappssmtp.com header.a=rsa-sha256 header.s=20210112 header.b=AvwZXSo3 X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.399 X-Spam-Level: X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, 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 1_n-04MMKlCo for ; Tue, 31 Jan 2023 08:58:59 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 48402813F3 Received: from mail-vk1-xa32.google.com (mail-vk1-xa32.google.com [IPv6:2607:f8b0:4864:20::a32]) by smtp1.osuosl.org (Postfix) with ESMTPS id 48402813F3 for ; Tue, 31 Jan 2023 08:58:58 +0000 (UTC) Received: by mail-vk1-xa32.google.com with SMTP id i38so6660936vkd.0 for ; Tue, 31 Jan 2023 00:58:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=q32-com.20210112.gappssmtp.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=bX0GPphpZ2v/CaerQtBKu8L9ehZNjX91aXwMZDEWSN4=; b=AvwZXSo3ESCSi2lnnYIBIXvG0Ix5uGOR0/k6ERVQjW9TkAMyjsYDC143ha/WnUPOrk qVHd+MFoMIDg680lCu9CQ58/7zspRRbB2JEm5CpwBsDNkvcwzJcNF0IiIj2w/sRAJmM7 qEkM15N+KhjeM2VfgNm9bDSAGI+t2TnnWYuKyRs7EsDLnpl8jVcjULq4mItx2VvqKw/o 8uu6KWMdhJr7lvKURKjAoxpa924l7cGFzGy7RPcR0MxwbeBV8hqM0inAzdyt1+rO3z6Q k7SnNpIEj1Oq/steT68QGbHjFKrlJ1Y5i+UNLm19ptoIkbpaKHBtyhVgMP88+9MWCs2C NtAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to: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=bX0GPphpZ2v/CaerQtBKu8L9ehZNjX91aXwMZDEWSN4=; b=wvc/SniDEGXKr0frsphO3TuFEzsrJp8FHDu05J8GPuewdfs0YmY6skC4SmSuy0PGl/ RP9fBdmhGGICm7b24wMCkrlBwk05nCdCRjZVvZSRh3hi4z6WiPhqkpx2FKOsgwTQDDMF NppFRk9mUgGA1adTVAzB0W5H+1ukfvDP43MJzow9X9Ro/yyETs5XIKYU8gs2gKR1cKqo tuTtq+TSUOF3vUmXlg2fG7eS6t4sKMemwQT170Sam6pgrw1JVxs+0ULkIMEIQl/kiATl +wBql9p1EmTpjnnt+gc9yfIJbbHglpXAGp6yEj1kPx2UQ5aBhtp3csUvdyWfCLQCHil1 t8Rw== X-Gm-Message-State: AFqh2kpo2mEdGsQQcsrov+zEr2vZuChsl4ywmVEjVKoMDwiAOorCtE5v PQJEMJe4keXVAFYehA9XZkU+JUMGARiF92s+Oaz+3f0= X-Google-Smtp-Source: AMrXdXuA5JwYPCnjH6hMLV1cqZCUTAOT3ApEmDC/+PRd+0S1MzVg0A0SML29aG4EBailj5eASiCMM8tUUXAzFksvkJw= X-Received: by 2002:a1f:14c1:0:b0:3d5:9b32:7ba4 with SMTP id 184-20020a1f14c1000000b003d59b327ba4mr6264630vku.15.1675155537758; Tue, 31 Jan 2023 00:58:57 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Erik Aronesty Date: Tue, 31 Jan 2023 03:58:46 -0500 Message-ID: To: Robert Dickinson , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000c5bb0a05f38b8aa0" X-Mailman-Approved-At: Tue, 31 Jan 2023 09:08:16 +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: Tue, 31 Jan 2023 08:59:00 -0000 --000000000000c5bb0a05f38b8aa0 Content-Type: text/plain; charset="UTF-8" my only concern is that as block space gets limited the likelihood of soft fork opcode tech improvement proposals getting accepted by the community goes down schnorr sigs are extremely useful to me (anon, cheap multisig) and some sort of vault tech would be very helpful as well --000000000000c5bb0a05f38b8aa0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
my only concern is that as block space gets limited the l= ikelihood of soft fork opcode tech improvement proposals getting accepted b= y the community goes down

schn= orr sigs are extremely useful to me (anon, cheap multisig)

and some sort of vault tech would be ver= y helpful as well



--000000000000c5bb0a05f38b8aa0--