1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
Return-Path: <jlrubin@mit.edu>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
by lists.linuxfoundation.org (Postfix) with ESMTP id D40B3C0012
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 18 Dec 2021 21:14:32 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id B4C1C605A4
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 18 Dec 2021 21:14:32 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3,
RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 6OoVvQbJKD4W
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 18 Dec 2021 21:14:31 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])
by smtp3.osuosl.org (Postfix) with ESMTPS id B193860596
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 18 Dec 2021 21:14:30 +0000 (UTC)
Received: from mail-lj1-f181.google.com (mail-lj1-f181.google.com
[209.85.208.181]) (authenticated bits=0)
(User authenticated as jlrubin@ATHENA.MIT.EDU)
by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 1BILESx0019133
(version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT)
for <bitcoin-dev@lists.linuxfoundation.org>; Sat, 18 Dec 2021 16:14:29 -0500
Received: by mail-lj1-f181.google.com with SMTP id b19so9063735ljr.12
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 18 Dec 2021 13:14:29 -0800 (PST)
X-Gm-Message-State: AOAM5313YzmcVpxbFG7PqDvW3QP0bjhT6ER6FwEup3S65YszFN40JoSo
otYvF8S+f2lZBMLg4eMq0ZA6gULFA/hs7EyJsQQ=
X-Google-Smtp-Source: ABdhPJx3pWYT5FTqMhYUpYook3K9EPxSTKBEnjEkbZWwxoZvrEUP2hI3CbqK+C+E+gT3UrsFwtMYoV55VcBDvgbJzdQ=
X-Received: by 2002:a2e:7a06:: with SMTP id v6mr8151405ljc.198.1639862067900;
Sat, 18 Dec 2021 13:14:27 -0800 (PST)
MIME-Version: 1.0
From: Jeremy <jlrubin@mit.edu>
Date: Sat, 18 Dec 2021 13:14:16 -0800
X-Gmail-Original-Message-ID: <CAD5xwhjquyfecaoL_K723EQ=7Gvp9UCs382mH8f01e4KuewnKg@mail.gmail.com>
Message-ID: <CAD5xwhjquyfecaoL_K723EQ=7Gvp9UCs382mH8f01e4KuewnKg@mail.gmail.com>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="00000000000009b6c805d372243f"
Subject: [bitcoin-dev] [Bitcoin Advent Calendar] Packaging Sapio Applications
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Dec 2021 21:14:32 -0000
--00000000000009b6c805d372243f
Content-Type: text/plain; charset="UTF-8"
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>
--00000000000009b6c805d372243f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small;color:#000000">hi devs,</div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small;color:#000000"><br></div><div class=3D"gmail_default" style=3D"font=
-family:arial,helvetica,sans-serif;font-size:small;color:#000000">today'=
;s topic is packaging Sapio applications. maybe a bit more annoying than us=
ual, but important.</div><div class=3D"gmail_default" style=3D"font-family:=
arial,helvetica,sans-serif;font-size:small;color:#000000"><br></div><a href=
=3D"https://rubin.io/bitcoin/2021/12/18/advent-21/">https://rubin.io/bitcoi=
n/2021/12/18/advent-21/</a><br clear=3D"all"><div><div dir=3D"ltr" class=3D=
"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><br><=
/div><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:ari=
al,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div cl=
ass=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-=
size:small;color:rgb(0,0,0)">I think WASM is really really cool! It's d=
efinitely been very helpful for Sapio. It'd be kinda neat if at some po=
int software like Bitcoin Core could run Sapio modules natively and offer u=
sers 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 bitcoin=
ers (in particular, the rust-bitcoiners & rust-lightning) who like WASM=
for shipping stuff to browsers!</div><div class=3D"gmail_default" style=3D=
"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)"><=
br></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,=
sans-serif;font-size:small;color:rgb(0,0,0)">WASM is also something I'v=
e been thinking about w.r.t. how we ship consensus upgrades. It would be ki=
nda 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 compile=
d to and run through a WASM system, it would help guarantee that those piec=
es of the code are entirely deterministic. Maybe something for Simplicity t=
o consider WASM being the host language for JET extensions!</div><br></div>=
<div dir=3D"ltr"><br></div><div dir=3D"ltr"><div class=3D"gmail_default" st=
yle=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0=
,0)">Cheers,</div><div class=3D"gmail_default" style=3D"font-family:arial,h=
elvetica,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small;color:rgb(0,0,0)">Jeremy</div><br></div><div dir=3D"ltr">--<br><a h=
ref=3D"https://twitter.com/JeremyRubin" target=3D"_blank">@JeremyRubin</a><=
a href=3D"https://twitter.com/JeremyRubin" target=3D"_blank"></a></div></di=
v></div></div>
--00000000000009b6c805d372243f--
|
