Vardiff currently unsupported

[rrybarczyk]

Supporting variable difficulty in the mining proxy and pool is a needed feature for potential users. Previously, #251 was opened but was subsequently closed without addressing it. I do not remember why.

[pavlenex]

According to @GitGab19 variable difficulty is included with tProxy. Since this feedback comes from early adopter, we should prfioritize this feature when tackling the pool role.

[plebhash]

I remember that @rrybarczyk had previously mentioned the idea of modularizing the vardiff logic, so that it is not statically baked into tProxy

this makes a lot of sense, as ideally we need to be able to easily integrate vardiff as a feature to applications as needed

---

as we tackle this, we should be very strategic about test-driven development

the main challenge around this kind of feature is its statistical nature, which makes it very prone to non-deterministic behavior, especially as different platforms (with different computational capacity) are used to emulate the incoming hashrate

we have some valuable lessons learned from MG CI of tProxy, and more insight can be found on https://github.com/stratum-mining/stratum/issues/1208

[plebhash]

not directly but somewhat correlated to this topic is the need for modularizing translation logic, which could fit into a potential approach for cgminer integration, as it was laid out here: https://github.com/plebhash/cgminer-sv2/issues/1#issuecomment-2185278906

depending on which direction this effort goes, we should also consider creating a separate issue for isolating translation logic