MIME-Version: 1.0
Date: Fri, 27 May 2016 16:24:36 -0500
Message-ID: <CABaSBaxyR=emQa0+ford3mxSz6hAQm9o_A3iTDspTzsNf8-MPw@mail.gmail.com>
From: Bryan Bishop <kanzure@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>,
	Bryan Bishop <kanzure@gmail.com>
Content-Type: multipart/alternative; boundary=001a113d50689720790533d988b7
Subject: [bitcoin-dev] Zurich engineering meeting transcript and notes
	(2016-05-20)
Precedence: list

--001a113d50689720790533d988b7
Content-Type: text/plain; charset=UTF-8

It has occurred to me that some folks may not have seen the link floating
around the other day on IRC.

Transcript:
https://bitcoincore.org/logs/2016-05-zurich-meeting-notes.html
https://bitcoincore.org/logs/2016-05-zurich-meeting-notes.txt

Meeting notes summary:
https://bitcoincore.org/en/meetings/2016/05/20/

Topics discussed and documented include mostly obscure details about
segwit, segwit code review, error correcting codes for future address
types, encryption for the p2p network protocol, compact block relay,
Schnorr signatures and signature aggregation, networking library, encrypted
transactions, UTXO commitments, MAST stuff, and many other topics. I think
this is highly useful reading material.

Any errors in transcription are very likely my own as it is difficult to
capture everything with high accuracy in real-time. Another thing to keep
in mind is that there are many different parallel conversations and I only
do linear serialization at best... and finally, I also want to mention that
this is the result of collaboration with many colleagues and this should
not be considered merely the work of just myself.

- Bryan
http://heybryan.org/
1 512 203 0507

--001a113d50689720790533d988b7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>It has occurred to me that some folks may not have se=
en the link floating around the other day on IRC.<br></div><div><br></div><=
div>Transcript:<br></div><div><a href=3D"https://bitcoincore.org/logs/2016-=
05-zurich-meeting-notes.html">https://bitcoincore.org/logs/2016-05-zurich-m=
eeting-notes.html</a><br></div><div><a href=3D"https://bitcoincore.org/logs=
/2016-05-zurich-meeting-notes.txt">https://bitcoincore.org/logs/2016-05-zur=
ich-meeting-notes.txt</a><br></div><div><br></div><div><div>Meeting notes s=
ummary:</div><div><a href=3D"https://bitcoincore.org/en/meetings/2016/05/20=
/">https://bitcoincore.org/en/meetings/2016/05/20/</a></div></div><div><br>=
</div><div>Topics discussed and documented include mostly obscure details a=
bout segwit, segwit code review, error correcting codes for future address =
types, encryption for the p2p network protocol, compact block relay, Schnor=
r signatures and signature aggregation, networking library, encrypted trans=
actions, UTXO commitments, MAST stuff, and many other topics. I think this =
is highly useful reading material.</div><div><br></div><div>Any errors in t=
ranscription are very likely my own as it is difficult to capture everythin=
g with high accuracy in real-time. Another thing to keep in mind is that th=
ere are many different parallel conversations and I only do linear serializ=
ation at best... and finally, I also want to mention that this is the resul=
t of collaboration with many colleagues and this should not be considered m=
erely the work of just myself.</div><div><br></div><div class=3D"gmail_sign=
ature">- Bryan<br><a href=3D"http://heybryan.org/" target=3D"_blank">http:/=
/heybryan.org/</a><br>1 512 203 0507</div>
</div>

--001a113d50689720790533d988b7--