From: Jeremy Rubin <jeremy.l.rubin@gmail•com>
To: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] CTV Meeting #6 Agenda (Tuesday, March 22nd, 12:00 PT / 7PM UTC)
Date: Mon, 21 Mar 2022 14:32:14 -0700 [thread overview]
Message-ID: <CAD5xwhhjnLG-TGnHs09HZn44gavd-vymkhLZLCuapFa=PVB5MA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1410 bytes --]
Hi devs,
The 6th fortnightly CTV meeting will be held tomorrow March 22nd at noon
pacific 7 utc. *Note the Daylight Savings Time Change, 7PM UTC. Before it
was 8 UTC. Now it is not.*
The agenda for tomorrow will be a tutorial on using Sapio Studio, and it
will be building on the knowledge from the 4th meeting (so please review
the notes / that tutorial as well). Minimally, you will be expected to be
able to build a sapio WASM blob and the CLI, but everything else will be
covered in detail in this meeting. If you don't like running NPM
dependencies and don't want to trust me, please have a VM/burner set up
where you can do so (although not sure how well that will work?).
The culmination of the tutorial will be trying out different contracts,
including one similar to James O'Beirne's vault.
After the tutorial, we can have a discussion about tooling and
infrastructure.
for meeting #4, see:
tutorial:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-February/019973.html
notes:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-February/019974.html
logs (helpful if stuck in tutorial):
https://gnusha.org/ctv-bip-review/2022-02-22.log
I will try to post by later tonight basic steps to follow for setting
things up from start to finish.
A preview of the software you'll play with.
[image: image.png]
Cheers,
Jeremy
--
@JeremyRubin <https://twitter.com/JeremyRubin>
[-- Attachment #1.2: Type: text/html, Size: 4815 bytes --]
[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 496599 bytes --]
reply other threads:[~2022-03-21 21:32 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='CAD5xwhhjnLG-TGnHs09HZn44gavd-vymkhLZLCuapFa=PVB5MA@mail.gmail.com' \
--to=jeremy.l.rubin@gmail$(echo .)com \
--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