From: Mike Hearn <mike@plan99•net>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] DevCore London
Date: Thu, 9 Apr 2015 22:23:52 +0200 [thread overview]
Message-ID: <CANEZrP1MqzgfVrRHDjwizWCjnJqmMyRXJWDPAhv-rYU06sYw0g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
Next week on April 15th Gavin, Wladimir, Corey and myself will be at
DevCore London:
https://everyeventgives.com/event/devcore-london
If you're in town why not come along?
It's often the case that conferences can be just talking shops, without
much meat for real developers. So in the afternoon I'll be doing two things:
1. Running a hackathon/workshop type event. The theme is contracts, but
we can hack on whatever you all feel like.
2. My "talk" will actually be a live coding event. Writing contracts
apps has become a lot easier in the past few years, and to prove it to you
I will write a decentralised cross-platform Tor supporting document
timestamping app that uses OP_RETURN outputs and has a nice GUI ..... in 30
minutes, on stage.
Don't think it can be done? Turn up and see for yourself.
See you there!
[-- Attachment #2: Type: text/html, Size: 1068 bytes --]
next reply other threads:[~2015-04-09 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 20:23 Mike Hearn [this message]
2015-06-02 14:20 ` Mike Hearn
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=CANEZrP1MqzgfVrRHDjwizWCjnJqmMyRXJWDPAhv-rYU06sYw0g@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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