Closed quetzalcoatl closed 5 years ago
Actually, I started thinking about the headers due to their new x-proxy, but actually, we could use the header injection even now, regardless of whever the new rules are introduced or not. Header injection would probably allow us to use any miner, not just their special one.
Huh what, I did not want to close! oops
Those headers are already sent by the proxy by default.
I took a quick look at the x-proxy and the only improvement i can see is some status upload to http://bhd.hpool.com/proxy/uploadminerstatus
. I might play around with x-proxy the next days and see what it does exactly but i think we are good regarding their change.
You mentioned you got 0TB capacity displayed on hpool right now with blago either directly connected or via x-proxy? I'm mining on hpool right now with my proxy and i did not observe any degradations of capacity, everything looks good from my end.
I took a look at their uploadminerstatus
: You basically send a list of miners with their software, name, capacity etc. Hopefully hpool will give a more in-depth explanation of their upgrade and what exacly they are going to change (besides the upload miner stats endpoint). Maybe it is only that.
That being said ill probably implement it in the next days.
Is your feature request related to a problem? Please describe. bhd.hpool.com recently has posted an announcement: https://bhd.hpool.com/news/5cc1a87c5333e70348d65d74 where they warn about a required change in supported mining software. It's a bit hard to understand what they say exactly, but it looks like they will be rejecting incompatible clients and proxies and will require using their own specific proxy. Since the english version of the text is a bit hard to grasp, I tried the chinese version and google-translate, here's the result:
They plan to activate new rules on May 8th (the end of 'experience period'). They already require use of their own miner, so it seems possible that this will be extended to proxies as well. On https://bhd.hpool.com/download they have posted a modified blago miner and a new piece called "x-proxy".
I have played a bit with that and it seems that when I connect the newest blago miner (190301) either directly, or via their x-proxy, it is always seen by the pool as 0.0TB capacity. That's because their modified blago sends some extra headers along with normal requests. From what I've seen, these are, at least:
X-Miner is hardcoded to the .exe name, X-Capacity is just the total plot files in GB, X-ClientIP is obvious I suppose we could just hardwire it to 127.0.0.1, X-Minername and X-Account are read from configuration file and passed through. I don't know if they verify X-Miner name, so it probably would need to be configurable.
Plain blago miner doesn't send them and has no options for configuring this data. Without those headers, hpool doesn't seem to fully respect the miner. Since those headers are quite simple, the proxy seems a nice place to inject them on the fly.
Describe the solution you'd like I'd like to be able to configure the content of those headers via config yaml file and I'd like bhd-burst-proxy to send those header for me, as they are given in the config file, regardless of what miners connected to the proxy are sending.
Describe alternatives you've considered Once the rules are changed, I don't see any alternatives other than giving up on bhd-burst-proxy and switching to their modified blago and their x-proxy. I really don't want to do that, but right now I don't see any other way, since no other mining software has any options to send those headers.