Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id BE075323 for ; Wed, 14 Oct 2015 22:37:49 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outbound.mailhostbox.com (outbound.mailhostbox.com [162.222.225.9]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 7666D187 for ; Wed, 14 Oct 2015 22:37:48 +0000 (UTC) Received: from [0.0.0.0] (unknown [62.212.68.201]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: s7r@sky-ip.org) by outbound.mailhostbox.com (Postfix) with ESMTPSA id 307B01A1350; Wed, 14 Oct 2015 22:37:40 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sky-ip.org; s=20110108; t=1444862262; bh=bjAgBjDm7GGQDKdTZY2vMlCgdeO+B5cmJoNgsZrlaeQ=; h=Reply-To:Subject:References:To:From:Date:In-Reply-To; b=OU1m0NCsftPjT9Rc9P9EzOdCnTVfbslJaaysA/c+qHhXxVdQJmgZyZo0tjKSn6Aps OG9VDPbfWM1P9Y+RhLCiUKdGNrQ+8dzx81sa4ZjSmjf4Y+ERO5REhqd3M0FgUbgRv+ adgon6/HQ+64G1Qn3MhUKk01sTsrTFO4/+rkZoUw= Reply-To: s7r@sky-ip.org References: <561E2B09.3090509@sky-ip.org> <561E7283.2080507@gmail.com> To: Paul Sztorc , bitcoin-dev@lists.linuxfoundation.org From: s7r Message-ID: <561ED92C.2090203@sky-ip.org> Date: Thu, 15 Oct 2015 01:37:32 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <561E7283.2080507@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=IPz/cVbG c=1 sm=1 tr=0 a=5M4orznF5aKOCIxUleZT5A==:117 a=5M4orznF5aKOCIxUleZT5A==:17 a=N659UExz7-8A:10 a=133aka-2VnpJHL5j1oYA:9 a=TSYOrG0CUd8z129l:21 a=eJrE9ZIiWyQ9KwPL:21 a=pILNOxqGKmIA:10 X-Scanned-By: MIMEDefang 2.72 on 172.18.214.92 X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,URIBL_BLACK autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Lightning Network's effect on miner fees X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2015 22:37:49 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 10/14/2015 6:19 PM, Paul Sztorc wrote: > LN transactions are a substitute good for on-chain transactions. > > Therefore, demand for on-chain transactions will decrease as a > result of LN, meaning that fees will be lower than they would > otherwise be. > > However, the two are also perfect compliments, as LN transactions > cannot take place at all without periodic on-chain transactions. > > The demand for *all* Bitcoin transactions (LN and otherwise) is > itself a function of innumerable factors, one of which is the > question "Which form of money [Bitcoin or not-Bitcoin] do I think > my trading partners will be using?". By supporting a higher rate of > (higher-quality) Bitcoin transactions, the net result is highly > uncertain, but will probably be that LN actually increases trading > fees. Probably yes. But probably no. Having less hashing power is not good, and it's unrelated to scalability and decentralization, it's related to security. Of course we could argue that the hashing power is not super decentralized at this moment but it's unrelated to the topic. I'd rather have less decentralized big amount of hashing power as opposite to less hashing power. One theory, very close to yours, is that if Bitcoin transactions demand grows so high that we need the lightning network, there should be plenty of on chain transactions for miners to collect fees from. I haven't yet seen the incentives of everyone involved in lightning network (payment channel end points, hub operators, miners, etc.) but would it make sense to enforce a % of the fees collected by on payment hubs to be spent as miner fees, regardless if the transactions from that hub go on the main chain or not? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBCAAGBQJWHtksAAoJEIN/pSyBJlsR9Y0H+QE/XdW7yauhrNJtp2eIBPg9 zVUanzR2LT0zAkeF5/Xsx3PFoypALOV7R0YNL29jI3F2XkZA8v24wfNvPi0DETcC ZOxw4G1erIEjjj51Qz4M7okjQecJxPHOJ+Nz6iNZEDFcZG2b15phCRSQKZwSHP+b Erw6a4NPs1foieZyk260KSOB8lFs9e8bUJfXd4FfA7l60RA9582K6p05aqVtehFW ONTe8ULv8F0ba+EzVyTodzzY6ehjD+uc31zL6mDFIbiW+InivFbfi2uDVN1BP/US m99lLHvDEthnkTokFrbDu81kXdD0lHwIu4O0EMzCnw2E0vWi3sGKd+M0P0sv4WA= =1qxh -----END PGP SIGNATURE-----