From: GC <slashdevnull@hotmail•com>
To: "Rune K. Svendsen" <runesvend@gmail•com>,
"info@bitmarkets•net" <info@bitmarkets•net>
Cc: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Off-chain transactions and miner fees
Date: Mon, 10 Aug 2015 13:31:40 +0430 [thread overview]
Message-ID: <BLU436-SMTP89C5F8F9A87EC52C8BD1E5C6700@phx.gbl> (raw)
In-Reply-To: <567909F0-F686-4B38-A745-637423E12311@gmail.com>
Following this, Bitcoin and proposed payment networks like LN will be
competing for fees based on duration and cost to process transactions.
If fees on Bitcoin network stay low and zero-conf txns are possible,
competing payment networks will need some very special features to survive
and make money for their investors.
On 10/8/15 10:27 am, "Rune K. Svendsen via bitcoin-dev"
<bitcoin-dev@lists•linuxfoundation.org> wrote:
>Nodes in the Lightning network earn fees that wouldn't be there if it
>weren't for the Lightning network. The base Bitcoin layer can't handle
>the transaction throughout that Lightning can, so the Lightning fees were
>never available to Bitcoin miners in the first place.
>
>What Lightning does is raise the value of a transaction on the block
>chain. Imagine you're a Lightning node, and in order to collect your
>fees, that you've earned over the past month, you have to settle on the
>blockchain. If you've earned, say, 0.5 BTC in fees, you can attach a huge
>0.005 BTC fee to the Bitcoin settlement transaction. The miners earn a
>larger fee, and you make sure your transaction gets into the blockchain
>quickly, and you can afford to pay this fee because you've made much more
>on the Lightning transactions you've routed.
>
>/Rune
>
>
>
>> Den 10/08/2015 kl. 00.20 skrev info--- via bitcoin-dev
>><bitcoin-dev@lists•linuxfoundation.org>:
>>
>> Hello all,
>>
>> one argument I often read on this mailing list is that it's essential to
>> reward miners with transaction fees at some point to secure the network.
>>
>> Off-chain transactions, whether it's Lightning or something else,
>> potentially extract fees, which may otherwise be paid to miners, if the
>> transactions were actually on-chain.
>>
>> In this context, wouldn't it be contradictory, maybe even harmful, to
>> aim for an environment, where some/many/most transactions are off-chain?
>>
>> I have not yet seen this conflict addressed in the recent discussions.
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists•linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>_______________________________________________
>bitcoin-dev mailing list
>bitcoin-dev@lists•linuxfoundation.org
>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2015-08-10 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 22:20 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
2015-08-10 9:01 ` GC [this message]
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=BLU436-SMTP89C5F8F9A87EC52C8BD1E5C6700@phx.gbl \
--to=slashdevnull@hotmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=info@bitmarkets$(echo .)net \
--cc=runesvend@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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