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 1X8EGR-00013a-SS for bitcoin-development@lists.sourceforge.net; Fri, 18 Jul 2014 19:56:19 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com designates 74.125.82.174 as permitted sender) client-ip=74.125.82.174; envelope-from=jgarzik@bitpay.com; helo=mail-we0-f174.google.com; Received: from mail-we0-f174.google.com ([74.125.82.174]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1X8EGQ-0006fW-QE for bitcoin-development@lists.sourceforge.net; Fri, 18 Jul 2014 19:56:19 +0000 Received: by mail-we0-f174.google.com with SMTP id x48so5038801wes.19 for ; Fri, 18 Jul 2014 12:56:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=yjEEx6EKjoN7WkGKHPxOlEm98p9uls4QdxMsiPhHsx0=; b=TZIlYISHYeKdAqlqKjz9TMfCYHJopA3ycIi2NeNoucMnRAtS9d1xGzILSd8tAwBK23 RzknpeIzfqrCudfJ1PptJSU9dGaAs9AgT5CxLQiw6hP5bSRRUR+D4alqfP/Ug23VEu5W Fmo5NSwvNRCqyrLu+n6Rx6ep0bwmZZ3J1fgYW8dRIOdyPuhTipNOglFotKHh0JHsMDNb yoYazzot8UdbBndeLG7LGsfFCz+BrirBRMe9T4vUHZu937b/GUhBwsy98rUGcNV9HEP+ LULV9YR57quYAr3ScOHEK8DsSAjLaDNg6bZwZxMeaxokq6MfEuHRqzQVSRGLZN8uJGME 1n+w== X-Gm-Message-State: ALoCoQnQeCjVscIURjXUWxottO+wHpo42q63/efD1hCm81LERvQGTBogKfQn6WC3ydAbVQRywUxg X-Received: by 10.194.205.65 with SMTP id le1mr10246672wjc.67.1405713372568; Fri, 18 Jul 2014 12:56:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.5.67 with HTTP; Fri, 18 Jul 2014 12:55:52 -0700 (PDT) In-Reply-To: References: From: Jeff Garzik Date: Fri, 18 Jul 2014 15:55:52 -0400 Message-ID: To: Kaz Wesley Content-Type: text/plain; charset=UTF-8 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 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 X-Headers-End: 1X8EGQ-0006fW-QE Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Squashing redundant tx data in blocks on the wire 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: Fri, 18 Jul 2014 19:56:20 -0000 Related: We must handle some legitimate miner-privately-mined cases, such as miner payout TXs (outside coinbase) or side chain conditional TXs[1]. [1] https://bitcointalk.org/index.php?topic=676703.msg7682680#msg7682680 On Fri, Jul 18, 2014 at 3:51 PM, Kaz Wesley wrote: > I've updated the gist, and added an additional proposal that I think > meshes well: > https://gist.github.com/kazcw/43c97d3924326beca87d#ultra-fast-block-validation > > sparseblocks + UFBV would tighten the new-block process to this (when > txes have been received in advance): > - receive block (~2kB for 1000 tx) > - check whether block contains txes known to belong to conflict-sets, > and if so whether more than one tx from a single conflict-set has been > included (a few operations on very small sets) > - relay block (~2kB) > > The benefits of these changes only occur when the transactions have > been seen in advance, but incentivizing ahead-of-block transaction > propogation is a plus, as Jeff mentioned; working on a block without > first ensuring peers have its transactions would be very expensive > from a miner's point of view. > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/