From: "pool2win" <kohli@ctemplar.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Braidpool: Proposal for a decentralised mining pool
Date: Sun, 29 Aug 2021 05:57:43 -0000 [thread overview]
Message-ID: <0aff157f62ea4abba71df4f87eb54880-kohli@ctemplar.com> (raw)
We have been working on a peer to peer mining pool that overcomes the
problems faced by P2Pool and enables building a futures market for
hashrate.
The proposal can be found here:
https://github.com/pool2win/braidpool/raw/main/proposal/proposal.pdf
The key features of the pool are:
1. Lower variance for smaller miners, even when large miners join
the pool.
2. Miners build their own blocks, just like in P2Pool.
3. Payouts require a constant size blockspace, independent of the
number of miners in the pool.
4. Provide building blocks for enabling a futures market of hash
rates.
Braidpool: Decentralised Mining Pool for Bitcoin
Abstract. Bitcoin P2Pool's usage has steadily declined over the years,
negatively impacting bitcoin's decentralisation. The variance in
earnings for miners increases with total hashrate participating in
P2Pool, and payouts require a linearly increasing block space with the
number of miners participating in the pool. We present a solution that
uses a DAG of shares replicated at all miners. The DAG is then used to
compute rewards for miners. Rewards are paid out using one-way payment
channels by an anonymous hub communicating with the miners using Tor's
hidden services. Using the payment channels construction, neither the
hub nor the miners can cheat.
Full proposal at
https://github.com/pool2win/braidpool/raw/main/proposal/proposal.pdf
Details on trading hashrate are here:
https://pool2win.github.io/braidpool/2021/08/18/deliver-hashrate-to-market-makers.html
@pool2win
next reply other threads:[~2021-08-29 6:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 5:57 pool2win [this message]
2021-09-02 6:46 ` [bitcoin-dev] Braidpool: Proposal for a decentralised mining pool 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
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=0aff157f62ea4abba71df4f87eb54880-kohli@ctemplar.com \
--to=kohli@ctemplar.com \
--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