New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make rieMiner competitive for breaking world records #19

Open
Pttn opened this Issue Jan 14, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@Pttn
Copy link
Owner

Pttn commented Jan 14, 2019

Right now, rieMiner is optimized for 6-tuples mining, but I am not sure if we can efficiently use the Benchmark Mode to break any current record, even the 6-tuple one. It also is fairly inefficient for other tuple sizes.

Rockhawk himself said

Nearly 20 years ago I wrote "APSieve" which is basically a generalised version of the sieving part of the riecoin miner. I was surprised to see that some relatively recent k-tuplet records still credit it, including the top 6-tuplet! I don't think I even have the source for that any more, and I'm certain that the code in rieMiner is faster. That said, being able to sieve more deeply before testing would be necessary to be competitive for a record. This can be done with less memory when you only have one "block" - rieMiner is structured a bit differently because it needs to start testing primes within seconds not days or weeks!

I am donating 5000 RIC for anyone that writes elegant code for a fourth mode (with Solo/Pool/Benchmark) that can be used to beat new records for different tuple lengths and makes rieMiner a reference software for prime constellation finding.

If that person also beats any current world record with such new implementation, I double the bounty.

I measured that we would currently need 2-2.5 years in average with a 2700X to find a block at Difficulty 3600 (which would beat the current 6-tuples world record), using the Benchmark Mode. If there is some way to reduce this value to 1 year or less, it will clearly be eligible for the bounty. This would become a reasonable ~3 months for a 32 Cores CPU.

Bounty valid until March 31. After this point, it will be halved to 2500 RIC and valid until end 2019.

@Pttn Pttn added this to the 0.99 milestone Jan 14, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment