public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Newton <djpnewton@gmail.com>
To: s7r@sky-ip.org
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Lightning Network's effect on miner fees
Date: Thu, 15 Oct 2015 12:42:31 +1300	[thread overview]
Message-ID: <CAOUBo+-7hbaJ9YMG6-WfB-=+6+9mn8U_vjQYqfNf6NwTA0p2yw@mail.gmail.com> (raw)
In-Reply-To: <561ED92C.2090203@sky-ip.org>

[-- Attachment #1: Type: text/plain, Size: 2916 bytes --]

You could make the same argument about changetip, coinbase, bitstamp or any
other entity that operates off chain transactions.

1) There is probably no way of blocking them or enforcing fee collection
from entities that operate off chain transactions
2) They all have to settle on chain eventually

On Thu, Oct 15, 2015 at 11:37 AM, s7r via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> -----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-----
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 3673 bytes --]

  reply	other threads:[~2015-10-14 23:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 10:14 [bitcoin-dev] Lightning Network's effect on miner fees s7r
2015-10-14 15:19 ` Paul Sztorc
2015-10-14 15:37   ` Bryan Bishop
2015-10-15  3:35     ` Daniel Stadulis
2015-10-14 22:37   ` s7r
2015-10-14 23:42     ` Daniel Newton [this message]
2015-10-14 23:55     ` Paul Sztorc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOUBo+-7hbaJ9YMG6-WfB-=+6+9mn8U_vjQYqfNf6NwTA0p2yw@mail.gmail.com' \
    --to=djpnewton@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=s7r@sky-ip.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox