Sync of several pools.

[vazha]

Hello dear sammy007,

The question is - if it possible to organize for example three ETH pools in different locations, for exapmle in America, Europe and Asia, and syncronize them. So if miners will connect to any of this pools , they will see its actual (same) mining data. How to sync redis databases, or may be should use redis only on one pool (as master) and remotly connect to this redis from other pools (but in this case will be big delaying).

[jrischma]

+1

[9600-]

Almost all of the work to implement this kind of stratum topology has already been done for you by the ETH core team and Sammy007.

What you're looking for is less of a configuration or setting for Open-Ethereum-Pool and more of a federation of GETH or Parity nodes across geographic availability zones.

This kind of thing is fairly common and straight forward to implement.

Run different pool stratum servers in your availability regions but make sure the pools are making RPC calls to your nodes (loaded with the correct 'coinbase" account) in that respective region.

Super simple.

[jrischma]

@9600-
Thank you! That's what I think we should do, but I'm a bit silly and despite knowing what to do, I do not really know how to do it, can you help us with a step by step?

[9600-]

Would be happy to help, but not as a free service through GitHub. Happy to help people with config issues and simple fixes, but you're getting deep into application architecture for a distributed, highly-available, financial service.

Everything is roses until you lose your redis DB and have a community of angry miners awaiting payouts.

If you'd like, I can set you up with our account manager to either contract the labor or grab an engineer for consulting. But there is a cost associated there.

There are a LOT of variables depending on the regions you'd like to setup In, and the availability of infrastructure services in those areas. For instance, syncing a GETH node in AWS can pose unique challenges vs passing that traffic over another ISP or cloud provider.

[jrischma]

@9600-

thank you again, it really seems fair to pay for the knowledge, especially for saving time, I would be willing to accept your proposal as long as it is not for you to do it, but for me to give you a step by step how to do it, because my pool is 0% fee, and I'm not looking for economic reward for it, what interests me is to learn, tell me your mail to contact you

[jrischma]

hi, redis slave not write on master... why ? please help.... thanks

[jrischma]

hi, i have problem with node

show high latency with claymore

[mikeyb]

then connect to a closer pool or move your mining proxy. Why would you expect anyone here to make the internet faster for your server?

[jrischma]

redis-master - server USA - ping from chile 170ms
redis-slave - server CHILE - ping from chile 40ms

when i set my rig to USA i get 170ms
when i set my rig to CHL i get 900ms

what is the problem ??

[svenrenhoek]

Claymore / Phoenix is not reporting the latency properly - mostly happens when shares are found within 1,000 ms of one another. See this happen a lot. This is a mining application problem, not an OEP issue.

[jrischma]

@svenrenhoek , how solved this on maxhash.org ?

[svenrenhoek]

There is no solution - it is a mining software issue

[duyk16]

@jrischma
I have same issue with you, miner wait when it submit a share to your 2nd pool, the 2nd pool sent share to main redis and wait for response, after that miner will receipt share accecpt. Maybe this is prob, but I have no idea to fix it

[jrischma]

@duyk16 u found solution ?