Topic: [ANN][RIC] Riecoin: constellations POW *CPU* HARD FORK successful, world record - page 77. (Read 685207 times)

thats ok ...

the python hash ( a lot of pools no longer use the python stratum - but we have a unique custom built one now for cwi - so we need the python hash install file ) for granite is an x11 hash - and as such is available everywhere on git ... ill locate one to show you as the one we have installed is via pip ... if you have pip installed in your linux distro - you can find it in there - called x11_hash or dash_hash or something similar ...

we use centos 7 x64 - not ubuntu / debian ...

let me know how you go ...

#crysx

I've never dealt with pool code before - can you give me a pointer to the equivalent python hash code for some other coin so I can see what interface it needs?  Just doing the PoW verification in Python should be easy, as long as you don't care if it's super-optimized.

a riecoin pool ...

if someone can create a python hash to install - ill get it installed into the cwi-stratum and set up a pool to test / run the riecoin daemon ...

i can get started on this next week ... if we can get this working - this will make it for a higher distribution of miners ...

this is THE main reason when i first asked - about the 'algo' ... the name - the type - the hashfunctions that make up the algo that riecoin uses ... had i known this from the beginning - we could have setup something in the mean time ...

but - we are here now - and help would be appreciated to get the python hash organized and installed in the cwi-stratum - so that we can get a the riecoin pool into the cwi-poolsystem ...

let me know what you guys / gals think ...

#crysx

Hi dga, trying to compile, compiler say cant find primesieve.hpp. Is this a compiler file? or maybe forgot to include in the repo?

Thanks

ok.  I'm out of time for now, but as a start, I've:
(a)  Merged the pull request for stratum support from the riecoin github account into mine, in branch "stratum".
(b)  Started a little bit of code cleanup as I try to remember my way around the code.  As a starting point, I
ripped out a little code in favor of using the primesieve library, fixed a bug with the choice of the number of
workers doing the sieve, and started moving the code a bit more to more-standard c++11.

this is all in github/dave-andersen/fastrie on branch "stratum".

is there any reason to keep the old ypool/xpt protocol version around, or should we just go all-stratum?

I'd be curious if anyone sees a performance difference or regression from that bugfix, but it won't
be more than a percent or three.  Right now, my focus is on getting the code into a slightly
better place for further optimization.  (Please don't expect miracles or be annoyed if they don't
manifest.

+1 Here ... I might even start mining again. 

A performance boost for the open source miner would certainly help promote better hashrate distribution.

Interesting.  Would it be helpful if I updated the open-source miner?  I don't have very much time right now in the semester, but might be able to sneak in a weekend.  It's been two years - I bet I can find at least a 10% speed bump, though it's been a while since I've looked at my code.

And yet, this is what doesn't make sense.

Pools or not, miners get block rewards in proportion to their share of the total hash rate.

That's it.  Pools have benefits for smaller miners, and it's good to have pools around to make it easier for everyone to participate.  But pools are bad for larger miners, because they charge fees that would otherwise go in their own pockets.  And, as anyone who's played the game knows, mining is a very low-margin activity, particularly for CPU coins like this where botnets often get involved.

But as long as there are some ways for small miners to play, then it doesn't matter if pools get 5% of the hash or 100% of the hash.

Cryptocurrencies are generally viewed as secure as long as no entity or colluding group of entities has more than 50% (or 33%, if you favor the selfish mining interpretation) of the hash rate.  In that regard, any pool having more than 50% is a *potential* problem, because the operator of that pool could choose to discard the work done by others, or prevent certain transactions from going through.

What's the argument that all users need to use pools?

Having a strong *community* is important, and pools can be a part of that, or they can not -- but that very much depends on the pool operator.  Operators who just run a pool aren't very important.  Operators who contribute code back, help publicize the coin, and support users and miners, etc., are great.  People who DDoS nodes attempting to join the network, however, are actively harmful to the health of the coin, because they make it harder for people to use it and join the community.