From: Jeremy <jlrubin@mit•edu>
To: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] [Bitcoin Advent Calendar] Composability in Sapio Contracts
Date: Mon, 13 Dec 2021 10:25:33 -0800 [thread overview]
Message-ID: <CAD5xwhhj+tF-oqOw6v4apPdP2OVB1Rb5+kiYpSmR0rc8cRQvcg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
Devs,
Here's today's post: https://rubin.io/bitcoin/2021/12/13/advent-16/
It covers how you can use Sapio modules composably. This is an active area
of research for the Sapio platform, so definitely welcome and appreciate
ideas and feedback.
One area I'm particularly happy with but also unhappy with is the
"JSONSchema Type System". It is remarkably flexible, which is useful, but a
better type system would be able to enforce guarantees more strongly. Of
course, comparing to things like ERC-20, Eth interfaces aren't particularly
binding (functions could do anything) so maybe it's OK. If you have
thoughts on better ways to accomplish this, would love to think it through
more deeply. I'm particularly excited about ways to introduce more formal
correctness.
Cheers,
Jeremy
p.s. -- feel free to send me any general feedback on the series out
of band. There's a couple posts in the pipeline that are a bit less
development focused like the earlier posts I excluded, and I could filter
them if folks are feeling like it's too much information, but I'd bias
towards posting the remaining pieces as they come for continuity. Let me
know if you feel strongly about a couple posts that might be a topical
reach for this list.
--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>
[-- Attachment #2: Type: text/html, Size: 3071 bytes --]
reply other threads:[~2021-12-13 18:25 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=CAD5xwhhj+tF-oqOw6v4apPdP2OVB1Rb5+kiYpSmR0rc8cRQvcg@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