From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1TmTzi-0003Pv-P0 for bitcoin-development@lists.sourceforge.net; Sat, 22 Dec 2012 18:40:22 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of m.gmane.org designates 80.91.229.3 as permitted sender) client-ip=80.91.229.3; envelope-from=gcbd-bitcoin-development@m.gmane.org; helo=plane.gmane.org; Received: from plane.gmane.org ([80.91.229.3]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1TmTzd-0006Gw-Eh for bitcoin-development@lists.sourceforge.net; Sat, 22 Dec 2012 18:40:22 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TmTzi-000744-IS for bitcoin-development@lists.sourceforge.net; Sat, 22 Dec 2012 19:40:22 +0100 Received: from e179076186.adsl.alicedsl.de ([85.179.76.186]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 22 Dec 2012 19:40:22 +0100 Received: from andreas by e179076186.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 22 Dec 2012 19:40:22 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-development@lists.sourceforge.net From: Andreas Schildbach Date: Sat, 22 Dec 2012 19:39:59 +0100 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: e179076186.adsl.alicedsl.de User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 X-Spam-Score: -0.4 (/) 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 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [80.91.229.3 listed in list.dnswl.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 1.1 DKIM_ADSP_ALL No valid author signature, domain signs all mail -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1TmTzd-0006Gw-Eh Subject: [Bitcoin-development] Testnet3 difficulty transition problem? 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: Sat, 22 Dec 2012 18:40:23 -0000 Both blocks 38304 00000000015bb4069249fa1f41ae61d8a7447aaacc33c50dacd3c3654377fa43 and 40320 000000008011f56b8c92ff27fb502df5723171c5374673670ef0eee3696aee6d are difficulty transition blocks. However, block 40320 has a difficulty of 1. I know there is this special testnet rule that allows mining a block at difficulty 1, but I always thought you can't use this exception on difficulty transition blocks. As a result, bitcoinj based clients do not advance their blockchain past block 40319.