public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Bryan Bishop <kanzure@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>,
	Bryan Bishop <kanzure@gmail.com>
Subject: [bitcoin-dev] Zurich engineering meeting transcript and notes (2016-05-20)
Date: Fri, 27 May 2016 16:24:36 -0500	[thread overview]
Message-ID: <CABaSBaxyR=emQa0+ford3mxSz6hAQm9o_A3iTDspTzsNf8-MPw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1688 bytes --]

                 reply	other threads:[~2016-05-27 21:24 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='CABaSBaxyR=emQa0+ford3mxSz6hAQm9o_A3iTDspTzsNf8-MPw@mail.gmail.com' \
    --to=kanzure@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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