Thanks.
Yes I wanted only the basic workflow, later on I'll try to understand this:
"Pools assign work units, similar to the current block being worked on, however at difficulty 1" but I'll get into this later. Right now cpuminer can't even connect to what will be a pool. There are authorization problems.
So thanks again!
Topic: Bitcoind daemon - what is it for? (Read 2939 times)
Quote
There are many ways to get work for the miners. Bitcoind uses Getblocktemplate which replaces the old getwork command.
However most pools will use stratum or another pool server to getblocktemplate.
However most pools will use stratum or another pool server to getblocktemplate.
OK, thanks, but is this workflow I presented correct?
In my post above I stated the workflow. I cant describe it much better than I already have. Your basic workflow is almost correct except replace step 3 with the end of the quotation in my above post.
Quote
There are many ways to get work for the miners. Bitcoind uses Getblocktemplate which replaces the old getwork command.
However most pools will use stratum or another pool server to getblocktemplate.
However most pools will use stratum or another pool server to getblocktemplate.
OK, thanks, but is this workflow I presented correct?
There are many ways to get work for the miners. Bitcoind uses Getblocktemplate which replaces the old getwork command.
However most pools will use stratum or another pool server to getblocktemplate.
"Pools assign work units, similar to the current block being worked on, however at difficulty 1 (or higher depending on your hashing power), which are called shares. The idea is that you solve your mini-block, and submit it back to the pool, to show your proof of work, out of every X shares submitted, one will also solve the "real" block being worked on (by chance).
So you are in essence solving an easier problem, that can potentially solve a more difficult one, and everyone doing this over and over and over eventually do find a block."
Read
https://en.bitcoin.it/wiki/Pooled_mining
and
https://mining.bitcoin.cz/
However most pools will use stratum or another pool server to getblocktemplate.
"Pools assign work units, similar to the current block being worked on, however at difficulty 1 (or higher depending on your hashing power), which are called shares. The idea is that you solve your mini-block, and submit it back to the pool, to show your proof of work, out of every X shares submitted, one will also solve the "real" block being worked on (by chance).
So you are in essence solving an easier problem, that can potentially solve a more difficult one, and everyone doing this over and over and over eventually do find a block."
Read
https://en.bitcoin.it/wiki/Pooled_mining
and
https://mining.bitcoin.cz/
Yes I was on this page some time ago, but apparently back then, I had no idea how bitcoin in general works so I had troubles understanding this very specific page.
Still have troubles,after reading it, is it true that a pool:
1. communicates with bitcoind to get new work for miner (and so, bitcoind is being used for both, communicating with the network and a wallet)
2. then communicates with a miner to give it the work
3. if miner finds a hash < pool difficulty,sends it to the pool, then if hash
Is that true?
Still have troubles,after reading it, is it true that a pool:
1. communicates with bitcoind to get new work for miner (and so, bitcoind is being used for both, communicating with the network and a wallet)
2. then communicates with a miner to give it the work
3. if miner finds a hash < pool difficulty,sends it to the pool, then if hash
Is that true?
Have you read the bitcoind wiki ?
https://en.bitcoin.it/wiki/Bitcoind
Perhaps if you read through it properly and then return with more specific questions you will be more succesful in receiving help.
But the command line argument for notified of blocks is -blocknotify=. You can also change this setting in bitcoin.conf.
https://en.bitcoin.it/wiki/Bitcoind
Perhaps if you read through it properly and then return with more specific questions you will be more succesful in receiving help.
But the command line argument for notified of blocks is -blocknotify=
Hi,
I'm back to trying to understand all this bitcoin staff.
Is it true that I can use Bitcoind daemon to do all the staff related to communicating with bitcoin network, e.g confirming blocks are valid? If not, then what should I search for in google to get information about it?
I found this:
https://en.bitcoin.it/wiki/API_reference_(JSON-RPC)
and it looks like we can get information about current wallet status of a user, yes? But what about e.g. confirming blocks?
I.e. I need to create a pool and still have no idea how to "communicate with the bitcoin network", I still see this phrase but no simple/or event not-so-simple explanation of how to do that.
I'm back to trying to understand all this bitcoin staff.
Is it true that I can use Bitcoind daemon to do all the staff related to communicating with bitcoin network, e.g confirming blocks are valid? If not, then what should I search for in google to get information about it?
I found this:
https://en.bitcoin.it/wiki/API_reference_(JSON-RPC)
and it looks like we can get information about current wallet status of a user, yes? But what about e.g. confirming blocks?
I.e. I need to create a pool and still have no idea how to "communicate with the bitcoin network", I still see this phrase but no simple/or event not-so-simple explanation of how to do that.
Jump to: