Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 3DFA5C0032 for ; Thu, 26 Oct 2023 14:30:53 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 069846F65E for ; Thu, 26 Oct 2023 14:30:53 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 069846F65E X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 MsiptUkmg5yE for ; Thu, 26 Oct 2023 14:30:52 +0000 (UTC) Received: from mail-ej1-f42.google.com (mail-ej1-f42.google.com [209.85.218.42]) by smtp3.osuosl.org (Postfix) with ESMTPS id 231DD6143C for ; Thu, 26 Oct 2023 14:30:51 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 231DD6143C Received: by mail-ej1-f42.google.com with SMTP id a640c23a62f3a-9a6190af24aso163552166b.0 for ; Thu, 26 Oct 2023 07:30:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698330649; x=1698935449; 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=WzVcSyySpT5oLIwQ5WcRY3RmmmHgBLs3dK4Fbbc8ig4=; b=sHH1rG0jaGitHcJoDzlPmEiqk53Vg/+0PkWQw/ojqN3K960GHLU0+26XdKegoq7Npj YTvZp6pK5FeNIIrFVPBs+rPbL0twDwOBAM/JbBC2HNFIOU37sDDNBQ7eCdw/wP5UZc2K Z+aW5cI9Z2w1hHiO3Fr/QSdzBC02UUTXPvLrkpwxrosLX6cymdQqZP2MUDZRfzMmCQqL nGT3Q/GclA9qhmbo80WjBID7L/u8BthLgnZbFQemYr/hYICWFP8RnOs0hhdjEnkkf1sc JbU6kT/1HpdJqT3TF6Xr4PbNFi0eI+tZq9YFmJf4a2hly1B0T+ZAqkL5yC8+eL4tuUwK C1Ww== X-Gm-Message-State: AOJu0Yxzk6ZzfrxQNzPgBjxGKU9wh6GtL/jkfCCwXz3IQaPgM8r+RGo1 ct0iJIJ7B4u9JZWkI4vm8oqKqyPMhgN/AG3esF+bo2SJT8o9ZrkfxA4= X-Google-Smtp-Source: AGHT+IG53Kv91mbpmdxcPCou0AcXKQ2QC2jUH9RG8c0Kc6y7eHPwkgj3uBZd9yr6/0IVNUWfA7yqJqK7tOZZVeUgj4M= X-Received: by 2002:a17:906:c144:b0:9c4:4226:e4e6 with SMTP id dp4-20020a170906c14400b009c44226e4e6mr15576900ejc.66.1698330649217; Thu, 26 Oct 2023 07:30:49 -0700 (PDT) MIME-Version: 1.0 References: <194405691-79e11acd8b1dc1e2cdafc878b45b15c8@pmq3v.m5r2.onet> In-Reply-To: <194405691-79e11acd8b1dc1e2cdafc878b45b15c8@pmq3v.m5r2.onet> From: Ryan Grant Date: Thu, 26 Oct 2023 14:30:12 +0000 Message-ID: To: Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" Subject: Re: [bitcoin-dev] Proposed BIP for OP_CAT 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: Thu, 26 Oct 2023 14:30:53 -0000 I support OP_CAT, along with reasonable resource-consumption limiters. Implementation as a UASF would help build confidence in that method. I also support moving forward on other opcodes as soon as they are known to be safe and maintainable; whether for introspection, tx unpinning, or vaults.