diamond2020

I’m curious why you picked (2**32) for noncework. In my tests, it takes around 2.5 hours, by then a block might be found already. Shouldn’t you be getting info sooner? Also, what’s the benefit of noncework(k) over…

Ran this on one core of an i5 and cranked out 10 million hashes in about 56 seconds. That’s 178k hashes/s, which equals 65 billion years to find a block. That’s like 14 times the Earth’s age!

Thanks for clarifying! I appreciate the breakdown (and ignoring my mistakes with terms). Don't think I need to run a Grubb's test since we get why this happens. Seems like there's a clear distinction in the character…

I was messing around with a python script and bitcoinlib to create a vanity address. Trying to get one like 1(name) where (name) is just 4 characters. Thought it'd be quick but it's taking longer than expected. Anyone…