public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Sergio Demian Lerner <sergio.d.lerner@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] ESSPI: ECDSA/Schnorr Signed Program Input for BitVMX
Date: Tue, 4 Mar 2025 19:22:59 -0800 (PST)	[thread overview]
Message-ID: <3e49d257-7d44-4c19-a157-eb479ca0a4b9n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1781 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 2146 bytes --]

                 reply	other threads:[~2025-03-05  3:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e49d257-7d44-4c19-a157-eb479ca0a4b9n@googlegroups.com \
    --to=sergio.d.lerner@gmail.com \
    --cc=bitcoindev@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox