From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RELP8-0001JL-D3 for bitcoin-development@lists.sourceforge.net; Thu, 13 Oct 2011 13:32:58 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.47 as permitted sender) client-ip=209.85.214.47; envelope-from=gavinandresen@gmail.com; helo=mail-bw0-f47.google.com; Received: from mail-bw0-f47.google.com ([209.85.214.47]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1RELP4-0001A8-Ja for bitcoin-development@lists.sourceforge.net; Thu, 13 Oct 2011 13:32:58 +0000 Received: by bkat8 with SMTP id t8so748593bka.34 for ; Thu, 13 Oct 2011 06:32:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.17.11 with SMTP id q11mr6239252faa.13.1318512768155; Thu, 13 Oct 2011 06:32:48 -0700 (PDT) Received: by 10.152.24.229 with HTTP; Thu, 13 Oct 2011 06:32:48 -0700 (PDT) Date: Thu, 13 Oct 2011 09:32:48 -0400 Message-ID: From: Gavin Andresen To: Bitcoin Dev Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RELP4-0001A8-Ja Subject: [Bitcoin-development] State of Bitcoin Development: October Brain Dump X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2011 13:32:58 -0000 In the spirit of open communication, I thought I'd try doing a monthly "what's up" with bitcoin development. Here's what's on my radar: =95 Wladimir agreed to help pull patches, especially Qt-GUI-related patches, and is now part of the core dev team (Wladimir did the bulk of the work on the new Qt-based GUI). =95 Matt and Wladimir will be working on 0.5 release candidate 1 binaries and an updated release process to either ship the Qt libraries or statically link against Qt; the goal is to have them ready this weekend. =95 Network stability and wallet security are still my top concerns; start-up experience for new users (the long wait to download the block chain) is next on my list. =95 Amir's Bitcoin Improvement Process proposal hasn't been getting the attention it deserves; I'm just as guilty as anybody, I suppose we're all very busy. Helping improve it and writing some BIPs is high on my priority list. =95 I've setup a public-write-only bitcoin-security@lists.sourceforge.net mailing list to be used as an official way to report and then discuss potential security or denial-of-service vulnerabilities in the bitcoin protocol, and invited the following people to participate: Amir Taaki, Mike Hearn, Stefan Thomas, Nils Schneider, Pieter Wuille, Jeff Garzi and myself. Stuff I've been working on or plan to be working on soon; let me know if you are able to take on any of these, there are too many things on my TODO list: =95 Implementing/experimenting: multi-signature transactions and using OP_EVAL and a new type of bitcoin address to create 'always secure' or 'always backed up' wallets. =95 Write BIPs proposing: OP_EVAL. 'standard' multi-signature transactions. Maybe an informational BIP proposing how to roll out upgrades in general. =95 Denial-of-service detection/prevention (see the DoSorphans pull request). It would be really nice if somebody with experience simulating network behavior would take this over... =95 Cross-platform testing infrastructure. I've made good progress on a Twisted-based tool, but still have a lot to do. =95 Tighten up block-time rules to fix the potential "timejacking" attack. =95 Work on 'discouraging' blocks/transactions to punish bad-for-the-common-good-but-good-for-me behaviors from miners or nodes. =95 Get back to work on headers-only-for-initial-download, so initial startup experience is better for people. Ongoing longer-term: =95=A0Rethink/rework transaction fees; give both miners and clients more flexibility to create a market instead of magic hard-coded constants. =95 Organization; many things would be much easier if there was a non-profit organization like the Tor Project to pay core developers, testers, a PR person, pay for the Jenkins nightly build server, etc etc etc. --=20 -- Gavin Andresen