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 6C0EAC0037 for ; Fri, 29 Dec 2023 19:03:42 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 370338378A for ; Fri, 29 Dec 2023 19:03:42 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 370338378A Authentication-Results: smtp1.osuosl.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20230601 header.b=JhrMF94t X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 4AQMfnX7I0rz for ; Fri, 29 Dec 2023 19:03:40 +0000 (UTC) Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) by smtp1.osuosl.org (Postfix) with ESMTPS id 85F8F83D56 for ; Fri, 29 Dec 2023 19:02:31 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 85F8F83D56 Received: by mail-il1-x12a.google.com with SMTP id e9e14a558f8ab-35ff53a78a3so16432635ab.3 for ; Fri, 29 Dec 2023 11:02:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703876550; x=1704481350; darn=lists.linuxfoundation.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=sMzl9jrU/pp7BE6nEsgcfPhMFwhO2pe9bPktI5uVgbk=; b=JhrMF94tPzBfiD7djf7QgL4JBBO5cbaR0ZVc8xZpeaf3fJI9m7EAqEZ6p6v34qZK/a yz6ZR5vY+7L2daqfQ8F2y/84b4tTXrs0vLcrWCdLTRBVF267pqCoyJAb3fBrwqa4wxXq eD3lBp5L7AqT0ignnXtXXlZi8vd3R29HHIcpbuHJbUe70nqxlsVlgW1s5dl/99TASCAb gk8r5FCxNJlh46kjftwZYAIgVc7WtGwI84CMzY8vN7wdLBh08sFNgnYYgluxVnb1wh0a h02yylcZ/3MQr6lAG8RdT4HhwU/P6TTEyaNXBicB2mIJc16a9VYZ373I+DvZIwx/+4m3 XOtA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703876550; x=1704481350; h=content-transfer-encoding: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=sMzl9jrU/pp7BE6nEsgcfPhMFwhO2pe9bPktI5uVgbk=; b=tTdHM+aVGv+8MFzXuVSv8ZnAMducNbts06nd1KchXoOGKr4knxbUWL8AjKxlbiWPOg WyqzdfS5aAyJOP9WIijA+/B9eSZxHtwyMdLL/8unROm/y4jrIBFR3mobNqakDNt7YSZ1 uSGjlBrR8hXndpbWLSfkpsF74o7yD/GdpuRLblFlD+MDO10K4mQE7ciRRmoggbuJWSv8 T255rvD0qA7X+zq9g4VMRNp2n4TL93b7/lVLIrmFoF9sAcUHDZkFe1EjsoWJ89LrmeAp CGgIV+scdP34q6sJgw7AUGcLqssCXAYTS0PeKBeoq4YKY+D9Mz24wWuMHTHjy3/ZoRec +wrg== X-Gm-Message-State: AOJu0YwJTLpcOxHPsQCOr70ggxq18eKcs6HnFIhRlobsHbn/QOkA6+zd KLbDYGZpjLDCHtDQGQ3E4dpJjkBie5aNY1ObSKw= X-Google-Smtp-Source: AGHT+IFpx6AqmyIjDtYxUQGS8EySWA1l+u9WqoE/EvEXMit/nmdkvD2mx0A0iE+EJ7BsBV6t0kxqE21i3WIYJn/ly4Q= X-Received: by 2002:a05:6e02:17cd:b0:360:fa:2a6a with SMTP id z13-20020a056e0217cd00b0036000fa2a6amr9563912ilu.36.1703876550351; Fri, 29 Dec 2023 11:02:30 -0800 (PST) MIME-Version: 1.0 References: <980df778-cc94-4f98-8eb1-cbb321883369@gmail.com> In-Reply-To: <980df778-cc94-4f98-8eb1-cbb321883369@gmail.com> From: Nagaev Boris Date: Fri, 29 Dec 2023 16:01:52 -0300 Message-ID: To: Greg Tonoski , Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Sat, 30 Dec 2023 15:58:26 +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: Fri, 29 Dec 2023 19:03:42 -0000 On Fri, Dec 29, 2023 at 1:34=E2=80=AFPM Greg Tonoski via bitcoin-dev wrote: > There is significant difference when storing data as dummy signatures > (or OP_RETURN) which is much more expensive than (discounted) witness. > Witness would not have been chosen as the storage of arbitrary data if > it cost as much as alternatives, e.g. OP_RETURN. Hi Greg! How about storing data in multisig signatures? Make a 1/n multisig and store the data in (n-1) dummy public keys. It is stored in witness and is quite efficient and hard to filter out only if together with legitimate multisigs. Another smart place for hidden data is Merkle proof in Taproot. The depth is limited to 128 levels, so put 1 valid leaf and add data to 127 fake elements to calculate the Merkle root. I think there are more ways like this. If the current place is banned, they can always waste money in other parts of bitcoin transactions. It is impossible to stop someone who can afford to waste money from doing it. (Well, it is, but not in a decentralized voluntary way of Bitcoin.) My approach is just to wait for them to run out of money and use Lightning Network for payments meanwhile. --=20 Best regards, Boris Nagaev