From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 04 Mar 2025 19:26:28 -0800 Received: from mail-yb1-f191.google.com ([209.85.219.191]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tpfOt-0000CL-MY for bitcoindev@gnusha.org; Tue, 04 Mar 2025 19:26:28 -0800 Received: by mail-yb1-f191.google.com with SMTP id 3f1490d57ef6-e54d9b54500sf9200540276.3 for ; Tue, 04 Mar 2025 19:26:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1741145181; x=1741749981; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:sender:from:to:cc:subject:date :message-id:reply-to; bh=MbdG3wi7KLXp39yv8IzC6HGK4YIpFfE7Y1voDqocF5c=; b=q5mA66tzWd1J+oiVJlUflwfR7Egj48OtI06Bxm4V6xLWO6U7H2czRLN1QtzZizXbDX nqSVW8xjCWze8Lv9ltJF+xG3Id06H0nygG8gXkpNUu+URBt141e6l0BjOCRMPaenyJb3 Q6LRYYVKRCW8t9Zuu6EnTEs9RKmscFrAHzlodoZDeI5BNbRffxJukyYXsILLI6TGT/z3 89JDX5N0AGQ92kKPVAazJGM4+VEHTg8PEsaCcZ+pKwXK0cBjKSGLy+VAG6PuifhPOwVg kDrxBZ/EmEi6zaLjIkgs1eQ7y4g++HzGHOR2fb+DsGe0cMXOE/Pzlw+WOLt1tWd+Al3Q zCyg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741145181; x=1741749981; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:from:to:cc:subject:date:message-id :reply-to; bh=MbdG3wi7KLXp39yv8IzC6HGK4YIpFfE7Y1voDqocF5c=; b=koj6YOD4AulGqb08fMZj/huxuX8nUydpSG9yJV0VC3cQHQOmCMb+r+n3dVdzuOhTUc 73tCJGKDM45KbVTQ4gH1u4jTwgCZVHWidgzT3iHfN2u5pVRrg5CcAE+DgZlrk/e8YmJw nX8Gah7crXqaOe4klwt9EUqiUdM5ykg44bteXYpeMy8y7p2fNwraMT1TeJ0J2o3I1GJy XZSBQeaDSy9lch44eU0AZfgQKxyDe5yxoZjgPNgcM84RvKugKYMyYfkyF63KxgERVRbP N8EGB5Rj+HFrB3hWRFS7gZv0iJ+WmukUxofD4mBY/JKxlCuTSJMwhNcRjXnH2L/405Wm NgBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741145181; x=1741749981; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:x-beenthere:x-gm-message-state :sender:from:to:cc:subject:date:message-id:reply-to; bh=MbdG3wi7KLXp39yv8IzC6HGK4YIpFfE7Y1voDqocF5c=; b=o1OtBkBJb9HJNpBU+roR7bavRzdXYg6hZydn+mzqYBCdwCI352TRldc5kuRPBOcbPV U2LmLIMUyHnKmaGIFIMtTkmLqKGU4InhsJMTfTNQmax3sKY7cwFoyg/nzEhPNsK7Y7Fk +DeiUK1AAeLNJTbEhB4jvRjWhRiq9g4JPsVJpsc/eydotZty6+r1UvmZYba8M2qyGkg8 1HUQEmT5zKMTXYjsmcrRaeoMsXp/69YcYu/kXKCLQP6rxghl+U3SEcSJGyrm7JvVWh8y pVc7P52yqWSH6mTMww+ACnbZd7Ypwew+3BD+7ih/9hHLMPO285KDCq0DDpCcwL3tBrnA aOUw== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCXXFpoPmwc/WSlKAA0pwIdCKvwHfuM+NBtk2JAEI3sUEue/sSy53n6o0UHoW/3X84iXHs0lPa6Ua1tG@gnusha.org X-Gm-Message-State: AOJu0YzXaEbN6Sp19GnKswbu6KTs+FSWy9BjHSMbr0d3luOgY6HXV3rJ dDico980DcnlInZegMxLa0lQNsC/uz+vRCnUs1GO86Xpp850s9Fa X-Google-Smtp-Source: AGHT+IEsTRuV93mrN6NgmkKxoLqigQRBo65/AIEqrVt0Hkh1vD9KDMuF/L09/6KWvucddLcjsmrewQ== X-Received: by 2002:a05:6902:1244:b0:e5d:d128:e6cc with SMTP id 3f1490d57ef6-e611e35f2d5mr1884051276.37.1741145181510; Tue, 04 Mar 2025 19:26:21 -0800 (PST) X-BeenThere: bitcoindev@googlegroups.com; h=Adn5yVGcl76jv/FVd/CtqQq6G2lIeMg4JyUxca/NnHZS5EO58Q== Received: by 2002:a25:dccb:0:b0:e5b:423e:3be6 with SMTP id 3f1490d57ef6-e60cebfc5d2ls2477094276.1.-pod-prod-08-us; Tue, 04 Mar 2025 19:26:18 -0800 (PST) X-Received: by 2002:a05:690c:64c1:b0:6f9:45de:408f with SMTP id 00721157ae682-6fda30f8de1mr27722457b3.35.1741145178134; Tue, 04 Mar 2025 19:26:18 -0800 (PST) Received: by 2002:a05:690c:3388:b0:6ef:590d:3213 with SMTP id 00721157ae682-6fda287d365ms7b3; Tue, 4 Mar 2025 19:23:00 -0800 (PST) X-Received: by 2002:a05:690c:708d:b0:6f2:9533:8fba with SMTP id 00721157ae682-6fda2fe2f79mr23327067b3.1.1741144979477; Tue, 04 Mar 2025 19:22:59 -0800 (PST) Date: Tue, 4 Mar 2025 19:22:59 -0800 (PST) From: Sergio Demian Lerner To: Bitcoin Development Mailing List Message-Id: <3e49d257-7d44-4c19-a157-eb479ca0a4b9n@googlegroups.com> Subject: [bitcoindev] ESSPI: ECDSA/Schnorr Signed Program Input for BitVMX MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_13936_515486276.1741144979230" X-Original-Sender: sergio.d.lerner@gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) ------=_Part_13936_515486276.1741144979230 Content-Type: multipart/alternative; boundary="----=_Part_13937_1551497950.1741144979230" ------=_Part_13937_1551497950.1741144979230 Content-Type: text/plain; charset="UTF-8" Hello! I'd like to present to bitcoin-dev an improvement to the BitVMX protocol that enables the optimistic verification of long proofs (i.e. STARKs) on Bitcoin without soft forks. Here is the abstract and paper links: https://bitvmx.org/files/esspi-ecdsa-input-bitvmx.pdf *Abstract* The BitVM and BitVMX protocols have long relied on inefficient one-time signature (OTS) schemes like Lamport and Winternitz for signing program inputs. These schemes exhibit significant storage overheads, hindering their practical application. This paper introduces ESSPI, an optimized method leveraging ECDSA/Schnorr signatures to sign the BitVMX program input. With Schnorr signatures we achieve an optimal 1:1 data expansion, compared to the current known best ratio of 1:200 based on Winternitz signatures. To accomplish this we introduce 4 innovations to BitVMX: (1) a modification of the BitVMX CPU, adding a challengeable hashing core to it, (2) a new partition-based search to detect fraud during hashing, (3) a new enhanced transaction DAG with added data-carrying transactions with a fraud-verifying smart-contract and (4) a novel timelock-based method for proving data availability to Bitcoin smart contracts. The enhanced BitVMX protocol enables the verification of uncompressed inputs such as SPV proofs, NiPoPoWs, or longer computation integrity proofs, such as STARKs. Best, Sergio. -- You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/3e49d257-7d44-4c19-a157-eb479ca0a4b9n%40googlegroups.com. ------=_Part_13937_1551497950.1741144979230 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello!
I'd like to present to bitcoin-dev an improvement to the BitVMX= protocol that enables the optimistic verification of long proofs (i.e. STA= RKs) on Bitcoin without soft forks.

Here is the abstract and pap= er links: https://bitvmx.org/files/esspi-ecdsa-input-bitvmx.pdf

A= bstract

The BitVM and BitVMX protocols have long relied on i= nefficient one-time signature (OTS) schemes like Lamport and Winternitz for= signing program inputs. These schemes exhibit significant storage overhead= s, hindering their practical application. This paper introduces ESSPI, an o= ptimized method leveraging ECDSA/Schnorr signatures to sign the BitVMX prog= ram input. With Schnorr signatures we achieve an optimal 1:1 data expansion= , compared to the current known best ratio of 1:200 based on Winternitz sig= natures. To accomplish this we introduce 4 innovations to BitVMX: (1) a mod= ification of the BitVMX CPU, adding a challengeable hashing core to it, (2)= a new partition-based search to detect fraud during hashing, (3) a new enh= anced transaction DAG with added data-carrying transactions with a fraud-ve= rifying smart-contract and (4) a novel timelock-based method for proving da= ta availability to Bitcoin smart contracts. The enhanced BitVMX protocol en= ables the verification of uncompressed inputs such as SPV proofs, NiPoPoWs,= or longer computation integrity proofs, such as STARKs.

Best, S= ergio.

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoind= ev/3e49d257-7d44-4c19-a157-eb479ca0a4b9n%40googlegroups.com.
------=_Part_13937_1551497950.1741144979230-- ------=_Part_13936_515486276.1741144979230--