Search content
Sort by

Showing 3 of 3 results by Sonoftexas
Post
Topic
Re: Halving double-hash instruction count
by
Sonoftexas
on 04/11/2018, 22:56:04 UTC
but after that short delay the circuit spits out 1 solution every clock cycle.

Ah, so you're saying that as soon as the signal for one hash leaves a transistor to go the next, the next hash is already incoming to that first transistor? Then the limit on clock speed is only the switching speed of one transistor, and so there's no way to really improve it? Would reducing the number of transistors just reduce the power consumption then?
Post
Topic
Re: Halving double-hash instruction count
by
Sonoftexas
on 31/10/2018, 14:32:27 UTC
You need to set the power at the correct pins (which basically is the input) and after the electricity has gone trough the hardware you are measuring which bits are set (output; effectively the hash).
The time it needs to calculate a hash is the time the electricity needs to run through the hardware (not exactly, but basically).

Yeah, so currently a double hash is like 2000+ sequential operations, so there's a maximum frequency you can operate while you wait for the output. If you somehow could use just 1000 gates, you could run it ~twice as fast, right? Or is there some other limitation?
Post
Topic
Halving double-hash instruction count
by
Sonoftexas
on 30/10/2018, 21:55:22 UTC
I haven't followed bitcoin since before ASICs, and I remember when people were trying to squeeze every optimization they could out of the hashing algorithm in the gpu codes.

I didn't know where to put this thread, but my question is about how ASICs are optimized. If I managed to find an extremely good optimization that somehow halved the instruction count needed for a double hash, is that interesting to the ASIC designers? I would think it would save power consumption at least. If not halving, what ratio is interesting? A tenth?