public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Robin Linus <robin@zerosync.org>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] BitVM: Compute Anything on Bitcoin
Date: Mon, 9 Oct 2023 15:46:24 +0200	[thread overview]
Message-ID: <CCA561B6-A2DE-46FD-A2F8-98E0C34A3EEE@zerosync.org> (raw)

Abstract. BitVM is a computing paradigm to express Turing-complete Bitcoin contracts. This requires no changes to the network’s consensus rules. Rather than executing computations on Bitcoin, they are merely verified, similarly to optimistic rollups. A prover makes a claim that a given function evaluates for some particular inputs to some specific output. If that claim is false, then the verifier can perform a succinct fraud proof and punish the prover. Using this mechanism, any computable function can be verified on Bitcoin. Committing to a large program in a Taproot address requires significant amounts of off-chain computation and communication, however the resulting on-chain footprint is minimal. As long as both parties collaborate, they can perform arbitrarily complex, stateful off-chain computation, without leaving any trace in the chain. On-chain execution is required only in case of a dispute.

https://bitvm.org/bitvm.pdf

             reply	other threads:[~2023-10-09 14:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 13:46 Robin Linus [this message]
2023-10-10  1:06 ` [bitcoin-dev] BitVM: Compute Anything on Bitcoin Lloyd Fournier
2023-10-10  1:12 ` symphonicbtc
2023-10-10  1:27 ` Anthony Towns
2023-10-15 15:15 ` ZmnSCPxj
2023-10-17 18:00 ` Russell O'Connor

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=CCA561B6-A2DE-46FD-A2F8-98E0C34A3EEE@zerosync.org \
    --to=robin@zerosync.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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