public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Thomas Zander <thomas@thomaszander.se>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Off-chain transactions and miner fees
Date: Mon, 10 Aug 2015 23:16:11 +0200	[thread overview]
Message-ID: <1531960.ajae0oEZC4@coldstorage> (raw)
In-Reply-To: <55C8C8FD.9040600@LeoWandersleb.de>

On Monday 10. August 2015 12.53.33 Leo Wandersleb via bitcoin-dev wrote:
> > The reason of it being faster makes no sense, as your example the channel
> > has  been open for a month then he really doesn't care it takes 1, 10 or
> > 50 blocks before his transaction is included.  What is 5 hours wait on a
> > month of profit?
>
> I guess the assumption here is a full-block scenario where users of LN would
> be willing to pay 100 times the fees users of crude transactions would be
> willing to pay for the same limited space in the blockchain, simply because
> LN would group 100 real world payments into 1 crude transaction.

Thats exactly what I argued makes no sense to me.

Why pay for something you don't need? Paying something Just because you have 
money is really not a good business strategy. I doubt that will happen.

-- 
Thomas Zander


  reply	other threads:[~2015-08-10 21:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09 22:20 [bitcoin-dev] Off-chain transactions and miner fees info
2015-08-10  5:01 ` Joseph Poon
2015-08-10  5:57 ` Rune K. Svendsen
2015-08-10  8:39   ` Thomas Zander
2015-08-10 15:53     ` Leo Wandersleb
2015-08-10 21:16       ` Thomas Zander [this message]
2015-08-10  9:01   ` GC
2015-08-10 15:35   ` info
2015-08-10 18:50 ` Anthony Towns
2015-08-10 19:14   ` Hector Chu
2015-08-10 19:26     ` Anthony Towns
2015-08-10 19:54       ` Hector Chu
2015-08-10 21:12   ` Eric Voskuil

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=1531960.ajae0oEZC4@coldstorage \
    --to=thomas@thomaszander.se \
    --cc=bitcoin-dev@lists.linuxfoundation.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