Categories
- 17.3K All Categories
- 9.5K Mining
- 574 Pool Discussion
- 378 Promotional
- 1.4K General Project Discussion (non-technical)
- 485 Education
- 811 Protocol and Client discussion
- 170 web3-js
- 29 Whisper
- 16 Swarm
- 3 RLP
- 303 IoT & Hardware
- 1.2K Smart Contracts and Dapps
- 28 Serpent
- 359 Solidity
- 664 Projects
- 1.2K Reference clients code and builds
- 249 Eth & AlethZero- Cpp Implementation
- 471 Geth - Go Implementation
- 242 Mist
- 15 Node.js Implementation
- 36 Python Implementation
- 49 Mix
- 36 Other Implementations
- 170 Meetups
- 40 Other Events
- 226 Jobs & Skills
- 281 Press and Articles
- 75 Audio/Video
- 296 Ether Sale
- 1.2K Other Languages
- 96 Chinese
- 255 German
- 33 Italian
- 111 French
- 3 Hebrew
- 42 Japanese
- 75 Portugese
- 46 Romanian
- 185 Russian
- 231 Spanish
- 47 Turkish
- 125 Watercooler
Mining Clarification
work2heat
Member Posts: 8 ✭
I have an idea for un-ASIC-able mining but I need to clarify something first.
My understanding is that a miner will receive txs, run all the code, package the txs and the outputs of the code into a block, and start hashing the block. The key is the separability between running the code and hashing the block. So if I were part of a mining pool, we would only need one node to actually execute all the code, and pass the results along to the miners, who can then spend their time on the proof of work hashing.
Is this correct, or does each individual miner (in a pool) actually have to execute code?
My understanding is that a miner will receive txs, run all the code, package the txs and the outputs of the code into a block, and start hashing the block. The key is the separability between running the code and hashing the block. So if I were part of a mining pool, we would only need one node to actually execute all the code, and pass the results along to the miners, who can then spend their time on the proof of work hashing.
Is this correct, or does each individual miner (in a pool) actually have to execute code?
Comments
However, he does need to run all the code when a block is accepted and he now has to work on the next block, because otherwise you dont know if an adress has enough ether to buy gas/create a transaction. (Creating an invalid block is of no use for a miner)
The thing about mining pools is exactly something ethereum would like to prevent. The problem is that mining pools are essentially a single big miner in many ways, and can compromise decentralization, and create problems regarding single entities doing a lot of mining.
Btw: There is an idea to make the process of mining execute randomly modified bits of code/input of code, it is about trying to force the requirement of general computing; to help prevent ASICs.(CPUs are sort of ASICs for general computation.) It is only for trying to keep mining decentralized, not for helping computation along.
Looks like they're on it