New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove internal miner #7507
Remove internal miner #7507
Conversation
This code removes the internal miner which is only useful on Testnet. This leaves the internal miner that is useful on RegTest intact.
ACK 8d1de43 |
Why? Having a builtin miner was tremendously useful when experimenting with segnet. |
ACK. But this was useful when testing Segnet. I guess this marks the official end of an era? Haha. |
@sipa Meh. Its really trivial to go git clone some CPU miner and point it to bitcoind...we dont need an entirely-unmaintained CPU miner in the codebase when we have a separate (?!) codepath for mining on regtest. If someone feels like merging this codepath and regtest, I'd be more happy, but having two separate built-in miners seems like overkill. |
Feel free to go merge the codepaths then, or add a simple python based RPC miner instead. But I disagree with not being able to actually create valid blocks at all. |
https://github.com/pooler/cpuminer |
BFGMiner also has CPU mining support FWIW. |
Well at the very least, remove the restriction that |
I agree with removing the duplicated code path, by the way. We wanted to do that when the regtest-specific behaviour of |
Tested ACK |
ACK Leviathn@8d1de43 |
NITS: please remove some
Few more lines to be deleted... |
I tend to agree with this on the longer term. However, before this can be merged, there needs to be an easy to compile and set up CPU miner (let's say a "reference miner"). As well as instructions in Last time this was proposed, that was far from the case. I tried various project that were proposed to be as alternative but they were professional miner tools with lots of setup options, or a tangled web of dependencies. So that's the condition. |
I argued pretty vigorously against this before in that I feel that Bitcoin Core should be "complete"-- that sending people off to weave together many programs to build a functioning system was not in the sincere spirit of decentralization. Today testnet is not really cpu minable and we have the regtest miner. So I'm increasingly feeling this is a principled distinction with no practical impact. I think Wladimir's call for an easy to setup cpu miner and clear docs is good; and perhaps the best remediation possible given the facts we can't control. |
|
@luke-jr As a reference miner, that's like swatting a fly with a thermonuclear missile. Checking it out is like downloading an operating system. I'd prefer something minimal and self-contained that people can more easily study. |
So if you would:
That means that instead of |
@sipa that seems reasonable, but changing the behavior of the generate rpc probably belongs in a new pr |
Edit: I've talked with @sipa on IRC and he convinced me that this is the way to go. Our 'reference miner' (for testnet) will just be a python script that calls |
@Leviathn are you going to move this forward according to sipa's comment? |
See #7663. |
8d1de43 Remove internal miner (Leviathn)
8d1de43 Remove internal miner (Leviathn)
Undo "Remove internal miner", see dash#8d1de43 and bitcoin#7507. Version set to 0.12.11.0
This reverts commit fa03411. And wrap all of it in #if ENABLE_MINER Signed-off-by: Pasta <pasta@dashboost.org> # Conflicts: # src/rpc/client.cpp # src/rpc/mining.cpp # src/rpc/server.cpp # src/rpc/server.h
Undo "Remove internal miner", see bitcoin#7507. New icon shows mining status on main form. Hash rate info. Dialog guided activation. Mining thread priority. Normal and weak mining.
This code removes the internal miner which is only useful on Testnet.
This leaves the internal miner that is useful on RegTest intact.