@TheBlueMatt's brilliant proposal that separates 1/ block construction process from 2/ payout process. You'll still get the benefit of connecting to a pool (stable payouts) while not conceding the right to propose a block. Best of both worlds solution that will help d14n. 
https://twitter.com/TheBlueMatt/status/1004106026721972224 …
-
-
Assuming BetterHash makes improvements on lowering the cost to run a pool (BetterHash ‘Pool Protocol’ operator vs Stratum pool operator), then does that not incentivize more competition between pool operators, thus improving security?
-
No, the incentive for competition remains unchanged. If there is a financial benefit to the protocol, they simply all upgrade.
-
1) No, this is unchanged vs. current pools. They of course have the "right" to change pools, but the larger pool wins. No improvement. 2) This is not a system security improvement, and is not necessarily an improvement. 3) No, in this case latency increases.
-
1/ That’s assuming pooling will be winner-take-all, which is possible but not guaranteed - why hasn’t one single pool dominated the market *already*?
-
2/ That logic also doesn’t factor in the possibility of solving mining variance *without using pools*, e.g., thru external means such as financial hedges. See my thread on the topic of variance - finding blocks is not the only type of variance.https://twitter.com/hugohanoi/status/1004875566477004800 …
-
3/ Pool architecture dominates mining today, which means the majority of mining traffic is unauthenticated. How is adding authentication not a security improvement?
-
4/ Can you elaborate RE: latency? Traditional pools rely on one single getblocktemplate() service to divide the work between all miners. Eliminating this bottleneck at least gets rid of one type of latency.
-
5/ Bottom line is even if it’s possible to solve mining variance thru something like
#braidpool, it doesn’t mean we can’t pursue both approaches. Especially given that#braidpool is still highly experimental. - 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
