From: "David A. Harding" <dave@dtrt•org>
To: Eric Voskuil <eric@voskuil•org>
Cc: Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Billy Tetrud <billy.tetrud@gmail•com>
Subject: Re: [bitcoin-dev] Braidpool: Proposal for a decentralised mining pool
Date: Sun, 5 Sep 2021 21:54:30 -1000 [thread overview]
Message-ID: <20210906075430.hk44gaueu3njdkl3@ganymede> (raw)
In-Reply-To: <F8F16054-78DF-4D06-BD73-F8EBE7D902A5@voskuil.org>
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
On Mon, Sep 06, 2021 at 09:29:01AM +0200, Eric Voskuil wrote:
> It doesn’t centralize payment, which ultimately controls transaction selection (censorship).
Yeah, but if you get paid after each share via LN and you can switch
pools instantly, then the worst case with centralized pools is that
you don't get paid for one share. If the hasher sets their share
difficulty low enough, that shouldn't be a big deal.
I'm interested in whether braidpool offers any significant benefits over
an idealized version of centralized mining with independent transaction
selection.
-Dave
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-06 8:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 5:57 pool2win
2021-09-02 6:46 ` Billy Tetrud
2021-09-06 6:23 ` David A. Harding
2021-09-06 7:29 ` Eric Voskuil
2021-09-06 7:54 ` David A. Harding [this message]
2021-09-06 8:26 ` Eric Voskuil
2021-09-06 9:03 ` pool2win
2021-09-06 10:15 Prayank
2021-09-07 23:38 ` ZmnSCPxj
2021-09-08 10:03 ` pool2win
2021-09-10 9:30 ` Filippo Merli
2021-09-11 1:09 ` ZmnSCPxj
2021-09-11 7:54 ` Filippo Merli
2021-09-13 8:03 ` pool2win
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=20210906075430.hk44gaueu3njdkl3@ganymede \
--to=dave@dtrt$(echo .)org \
--cc=billy.tetrud@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=eric@voskuil$(echo .)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