public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Michael Folkson <michaelfolkson@gmail.com>
To: Jeremy <jlrubin@mit.edu>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Is there a tool like Ethereum EVM at present for Bitcoin script?
Date: Thu, 26 Aug 2021 14:09:49 +0100	[thread overview]
Message-ID: <CAFvNmHQwifysNTumzoVj6+T8kTfj9Bcr3M1RZKuWRBQ7VRonCw@mail.gmail.com> (raw)

The "No Taproot" section of the Sapio docs need updating :) What are
your plans to take advantage of Taproot with Sapio? It would have been
interesting to see what a Taproot emulator would have looked like,
although no need for it now. It seems to me Taproot would have been
harder to emulate than CTV though I could be wrong.

https://learn.sapio-lang.org/ch05-02-taproot.html

Also there have been a number of people asking questions about Sapio
and CTV on the Libera equivalents of Freenode channels #sapio and
##ctv-bip-review over the past months. Do you plan to join and claim
those channels?

Date: Thu, 26 Aug 2021 03:26:23 -0700
From: Jeremy <jlrubin@mit.edu>
To: Andrew Poelstra <apoelstra@wpsoftware.net>, Bitcoin Protocol
        Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Is there a tool like Ethereum EVM at
        present for Bitcoin script?
Message-ID:
        <CAD5xwhgmAepA4jW3tK7nihMFsMEdgs0Z6UEs3k=3J1soDea0QQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

This has actually never been true (Sapio assumes extensions).

If the extensions are not present, you can stub them out with a signing
federation instead, configurable as flags, and you can also write many
contracts that do not use the ctv based components at all.

The protocol for emulation is a bit clever (if I do say so myself) since it
ensures that contract compilation is completely offline and the oracles are
completely stateless.

Relevant links:

https://learn.sapio-lang.org/ch05-01-ctv-emulator.html
https://learn.sapio-lang.org/ch03-02-finish.html

Cheers,

Jeremy

-- 
Michael Folkson
Email: michaelfolkson@gmail.com
Keybase: michaelfolkson
PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3


             reply	other threads:[~2021-08-26 13:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 13:09 Michael Folkson [this message]
2021-08-26 20:03 ` [bitcoin-dev] Is there a tool like Ethereum EVM at present for Bitcoin script? Jeremy
  -- strict thread matches above, loose matches on Subject: below --
2021-08-24  3:39 Null Null
2021-08-24  7:36 ` Gijs van Dam
2021-08-24 13:08   ` Andrew Poelstra
2021-08-26  8:12     ` Oleg Andreev
2021-08-26 10:26     ` Jeremy
2021-08-26  2:43   ` Null Null

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=CAFvNmHQwifysNTumzoVj6+T8kTfj9Bcr3M1RZKuWRBQ7VRonCw@mail.gmail.com \
    --to=michaelfolkson@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=jlrubin@mit.edu \
    /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