From: Jeremy <jlrubin@mit•edu>
To: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] [Bitcoin Advent Calendar] Packaging Sapio Applications
Date: Sat, 18 Dec 2021 13:14:16 -0800 [thread overview]
Message-ID: <CAD5xwhjquyfecaoL_K723EQ=7Gvp9UCs382mH8f01e4KuewnKg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]
hi devs,
today's topic is packaging Sapio applications. maybe a bit more annoying
than usual, but important.
https://rubin.io/bitcoin/2021/12/18/advent-21/
I think WASM is really really cool! It's definitely been very helpful for
Sapio. It'd be kinda neat if at some point software like Bitcoin Core could
run Sapio modules natively and offer users extended functionality based on
that. For now I'm building out the wallet as Sapio Studio, but a boy can
dream. I know there are some bitcoiners (in particular, the rust-bitcoiners
& rust-lightning) who like WASM for shipping stuff to browsers!
WASM is also something I've been thinking about w.r.t. how we ship
consensus upgrades. It would be kinda groovy if we could implement the
semantics of pieces of bitcoin code as WASM modules... e.g., imagine pieces
of consensus being able to be compiled to and run through a WASM system, it
would help guarantee that those pieces of the code are entirely
deterministic. Maybe something for Simplicity to consider WASM being the
host language for JET extensions!
Cheers,
Jeremy
--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>
[-- Attachment #2: Type: text/html, Size: 2790 bytes --]
reply other threads:[~2021-12-18 21:14 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='CAD5xwhjquyfecaoL_K723EQ=7Gvp9UCs382mH8f01e4KuewnKg@mail.gmail.com' \
--to=jlrubin@mit$(echo .)edu \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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