public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pindar Wong <pindar.wong@gmail.com>
To: Jeremy <jlrubin@mit.edu>
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Call for Proposals for Scaling Bitcoin Hong Kong
Date: Tue, 10 Nov 2015 08:52:44 +0800	[thread overview]
Message-ID: <CAM7BtUrNc-CQ+TpKC+PHNv6qr2tEXWXUM_cKQb9tjKE0oTSbdA@mail.gmail.com> (raw)
In-Reply-To: <CAD5xwhhO8DBm4MayDWw_fO+4SYrhfFmAkjpeddOiTF=icdc3Bw@mail.gmail.com>

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

Dear All,

Just a note that we've extended the last day for submissions by two days.

i.e. Proposals should be submitted to proposals@scalingbitcoin.org by November
11th 23:59 UTC

Cheers,

p.


On Thu, Nov 5, 2015 at 11:32 PM, Jeremy via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> The second Scaling Bitcoin Workshop will take place December 6th-7th at
> the Cyberport in Hong Kong. We are accepting technical proposals for
> improving Bitcoin performance including designs, experimental results, and
> comparisons against other proposals. The goals are twofold: 1) to present
> potential solutions to scalability challenges while identifying key areas
> for further research and 2) provide a venue where researchers, developers,
> and miners can communicate about Bitcoin development.
>
> We are accepting two types of proposals: one in which accepted authors
> will have an opportunity to give a 20-30 minute presentation at the
> workshop, and another where accepted authors can run an hour-long
> interactive workshop.
>
> Topics of interest include:
>
> Improving Bitcoin throughput
> Layer 2 ideas (i.e. payment channels, etc.)
> Security and privacy
> Incentives and fee structures
> Testing, simulation, and modeling
> Network resilience
> Anti-spam measures
> Block size proposals
> Mining concerns
> Community coordination
>
>
> All as related to the scalability of Bitcoin.
>
> Important Dates
>
> November 9th - Last day for submission
> November 16th - Last day for notification of acceptance and feedback
>
> Formatting
>
> We are doing rolling acceptance, so submit your proposal as soon as you
> can. Proposals may be submitted as a BIP or as a 1-2 page extended abstract
> describing ideas, designs, and expected experimental results. Indicate in
> the proposal whether you are interested in speaking, running an interactive
> workshop, or both. If you are interested in running an interactive
> workshop, please include an agenda.
>
> Proposals should be submitted to proposals@scalingbitcoin.org by November
> 9th.
>
> All talks will be livestreamed and published online, including slide decks.
>
> --
> @JeremyRubin <https://twitter.com/JeremyRubin>
> <https://twitter.com/JeremyRubin>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

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

      reply	other threads:[~2015-11-10  0:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05 15:32 [bitcoin-dev] Call for Proposals for Scaling Bitcoin Hong Kong Jeremy
2015-11-10  0:52 ` Pindar Wong [this message]

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=CAM7BtUrNc-CQ+TpKC+PHNv6qr2tEXWXUM_cKQb9tjKE0oTSbdA@mail.gmail.com \
    --to=pindar.wong@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=jlrubin@mit.edu \
    /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