From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WdLfh-0006CN-Sd for bitcoin-development@lists.sourceforge.net; Thu, 24 Apr 2014 15:34:45 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.180 as permitted sender) client-ip=209.85.214.180; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f180.google.com; Received: from mail-ob0-f180.google.com ([209.85.214.180]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WdLfg-0004qq-TJ for bitcoin-development@lists.sourceforge.net; Thu, 24 Apr 2014 15:34:45 +0000 Received: by mail-ob0-f180.google.com with SMTP id wm4so2781922obc.25 for ; Thu, 24 Apr 2014 08:34:39 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.219.167 with SMTP id pp7mr1117283obc.85.1398353679531; Thu, 24 Apr 2014 08:34:39 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.96.180 with HTTP; Thu, 24 Apr 2014 08:34:39 -0700 (PDT) In-Reply-To: <53592A24.5000007@certimix.com> References: <53592A24.5000007@certimix.com> Date: Thu, 24 Apr 2014 17:34:39 +0200 X-Google-Sender-Auth: kFxzSWsLpwnbJz7vVmqjFj-5WH8 Message-ID: From: Mike Hearn To: Sergio Lerner Content-Type: multipart/alternative; boundary=089e0141ab8256c71204f7cb96ce X-Spam-Score: -0.5 (/) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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 X-Headers-End: 1WdLfg-0004qq-TJ Cc: bitcoin-development Subject: Re: [Bitcoin-development] Coinbase reallocation to discourage Finney attacks 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, 24 Apr 2014 15:34:46 -0000 --089e0141ab8256c71204f7cb96ce Content-Type: text/plain; charset=UTF-8 Thanks Sergio! On Thu, Apr 24, 2014 at 5:13 PM, Sergio Lerner wrote: > For more information you can check my post: > http://bitslog.wordpress.com/2014/02/17/5-sec-block-interval/ > Also NimbleCoin is a new alt-coin that uses 5-sec block intervals, allows > 100 tps and .... it's based on BitcoinJ (NimbleCoinJ now). So not only it > is possible, but it was coded by Mike itself. > Fascinating! I think that's the first time I heard of an alt coin entirely based on bitcoinj as its core implementation. Looking forward to your release. My understanding is that dogecoin suffers somewhat from having so many headers. SPV clients have to download them all in sequence so the more blocks you have, the more data they must download and thus the slower they sync. Sync times for SPV wallets today are fast enough that unless you spend six months in the jungle with your phone switched off, you probably won't notice. With 5 second block times unless there's some other solution you'd have much worse UX. BTW, Pieter experimented with relaying blocks as hash lists (actually merkleblocks) and I believe he found that it could often fail and be slower if the mempools were not quite synced. At any rate, it was apparently more complicated than it looked. That may be a side effect of trying to reuse the Bloom filtering code however. > Another solution to achieve <5 secs block intervals is this: > http://bitslog.wordpress.com/2014/03/20/mincen-a-new-protocol-to-achieve-instant-payments/ > MinCen looks like a rather interesting idea. I will read the paper. --089e0141ab8256c71204f7cb96ce Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Than= ks Sergio!

On Thu, Apr 24, 2014 at 5:13 PM, Sergio Lerner <<= a href=3D"mailto:sergiolerner@certimix.com" target=3D"_blank">sergiolerner@= certimix.com> wrote:
=20 =20 =20
For more inform= ation you can check my post: http://bitslog.wordpress.com/2014/02/17/5-sec-block-in= terval/
Also NimbleCoin is a new alt-coin that uses 5-sec block intervals, allows 100 tps and .... it's based on BitcoinJ (NimbleCoinJ now). S= o not only it is possible, but it was coded by Mike itself.

Fascinating! I think that's the first time= I heard of an alt coin entirely based on bitcoinj as its core implementati= on. Looking forward to your release.

My understanding is that dogecoin suffers somewhat from= having so many headers. SPV clients have to download them all in sequence = so the more blocks you have, the more data they must download and thus the = slower they sync. Sync times for SPV wallets today are fast enough that unl= ess you spend six months in the jungle with your phone switched off, you pr= obably won't notice. With 5 second block times unless there's some = other solution you'd have much worse UX.

BTW, Pieter experimented with relaying blocks as hash l= ists (actually merkleblocks) and I believe he found that it could often fai= l and be slower if the mempools were not quite synced. At any rate, it was = apparently more complicated than it looked. That may be a side effect of tr= ying to reuse the Bloom filtering code however.
=C2=A0
Another solution to achieve <5 secs block intervals i= s this: http://bitslog.wordpress.com/= 2014/03/20/mincen-a-new-protocol-to-achieve-instant-payments/

MinCen looks like a rather interesting idea. I will rea= d the paper.
--089e0141ab8256c71204f7cb96ce--