Bitcoin Forum
May 12, 2024, 11:43:02 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Coordination of mining pools  (Read 1144 times)
Geir (OP)
Full Member
***
Offline Offline

Activity: 546
Merit: 100



View Profile
March 06, 2012, 02:47:12 PM
 #1

I know the answer is out there but I can’t find it.
As I understand it, when you do mining you send a getwork(), get data back and do a sha256(sha256()) of the first 80 bytes (of the data part). If it’s not below the target you increase the nonce and try again. Everyone is not working on the same thing since merkle root is different for everyone.

My question is for mining pools, I guess everyone gets the same data from GetWrok(). How is it then coordinated so that they all don’t just tests the same hashes??

TOP Network   Enable real-world business with Blockchain 4.0 technology  |
–––––––   Whitepaper   |   Twitter   |   Facebook   |   Linkedln   |   Telegram   |   Medium  –––––––
|   No Transaction Fee   |   300K TPS   |   50 Million Active Users   |
Each block is stacked on top of the previous one. Adding another block to the top makes all lower blocks more difficult to remove: there is more "weight" above each block. A transaction in a block 6 blocks deep (6 confirmations) will be very difficult to remove.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715514182
Hero Member
*
Offline Offline

Posts: 1715514182

View Profile Personal Message (Offline)

Ignore
1715514182
Reply with quote  #2

1715514182
Report to moderator
1715514182
Hero Member
*
Offline Offline

Posts: 1715514182

View Profile Personal Message (Offline)

Ignore
1715514182
Reply with quote  #2

1715514182
Report to moderator
Geir (OP)
Full Member
***
Offline Offline

Activity: 546
Merit: 100



View Profile
March 06, 2012, 06:04:52 PM
 #2

Ok i found the answer, for you who are interested:
The pool sends a different header to every miner, then the miner goes trough the nonce.

OK so next question:
I've looked at the data returned from the miner to the pool. Looks like its the header again with the nonce that worked (the golden one), but also the merkle root changes. What is this all about???

TOP Network   Enable real-world business with Blockchain 4.0 technology  |
–––––––   Whitepaper   |   Twitter   |   Facebook   |   Linkedln   |   Telegram   |   Medium  –––––––
|   No Transaction Fee   |   300K TPS   |   50 Million Active Users   |
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!