From: "info@bitmarkets•net" <info@bitmarkets•net>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Off-chain transactions and miner fees
Date: Mon, 10 Aug 2015 00:20:36 +0200 [thread overview]
Message-ID: <55C7D234.1040306@bitmarkets.net> (raw)
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.
next reply other threads:[~2015-08-09 22:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 22:20 info [this message]
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
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=55C7D234.1040306@bitmarkets.net \
--to=info@bitmarkets$(echo .)net \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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