Topic: Problem submitting Monero stratum results (Read 97 times)
One line in my stratum code treats the nonce, as an int, instead of unsigned..... argh!! Still it works now.. New miner features now finally under development!!
Quick bump! I'm currently building my own stratum test socket, with blackjack, and hookers so I can get direct wireshark captures of a working miner vs mine! Someone must know why a pool would disconnect though!
Don't suppose there's a dev group, for this sort of stuff, most of the discussion here is on the actual mining itself!
Hi again,, still a bit stuck at this point. Have tried with another pool and got the same result ... is there any way to check a result? I think it is more likely my stratum code is wrong, rather than the hashing, because I have done a test hashing a known blob and get the expected result..
But as an example I've got this here job:
"blob":"060692baefd2057a0fe6dd28e539071344e333eea1515f5be7e881d70a01f6db8e6ee2051b08fd0 00000007178596eb1deae148f4a8b6b8b33eff4d5d05079c4ffab302aae88ba941addfb08"
"target":"711b0d00"
Which is mined to this result:
"nonce":"53aeaaaa"
"result":"834433beab3e3ade4bf575dcecfbb0fc6f757fadc88fa486a0c4c5827ea60200"
Which looks right to me. Am now trying to pull apart another miner, to check it, but wondering if there's any ready made tools I could use here...
Thx Monerofox
But as an example I've got this here job:
"blob":"060692baefd2057a0fe6dd28e539071344e333eea1515f5be7e881d70a01f6db8e6ee2051b08fd0 00000007178596eb1deae148f4a8b6b8b33eff4d5d05079c4ffab302aae88ba941addfb08"
"target":"711b0d00"
Which is mined to this result:
"nonce":"53aeaaaa"
"result":"834433beab3e3ade4bf575dcecfbb0fc6f757fadc88fa486a0c4c5827ea60200"
Which looks right to me. Am now trying to pull apart another miner, to check it, but wondering if there's any ready made tools I could use here...
Thx Monerofox
Hi!
I'm trying to build my own Monero pool mining software,,, and struggling with submitting results ...
So I thought I'd got the build to a stage where it should work and connected up to one of the pools... Things start off well, connected and logged in fine, processed the job correctly I think and started mining. But when it gets a result, and sends the submit back to the pool, it immediately gets a disconnect on the socket...
FYI was running Wireshark to see independently of my own code what goes over the wire... my submit call goes out in a packet, and 284ms later, I am getting a FIN, ACK in reply.. I've tried to test some of my results as well with an open source cryptonight implementation, to validate that my result is valid, and it seems OK there also.
Anyone seen that sort of thing before? What does it mean if the pool disconnects me on submit?
Thx Monerofox
I'm trying to build my own Monero pool mining software,,, and struggling with submitting results ...
So I thought I'd got the build to a stage where it should work and connected up to one of the pools... Things start off well, connected and logged in fine, processed the job correctly I think and started mining. But when it gets a result, and sends the submit back to the pool, it immediately gets a disconnect on the socket...
FYI was running Wireshark to see independently of my own code what goes over the wire... my submit call goes out in a packet, and 284ms later, I am getting a FIN, ACK in reply.. I've tried to test some of my results as well with an open source cryptonight implementation, to validate that my result is valid, and it seems OK there also.
Anyone seen that sort of thing before? What does it mean if the pool disconnects me on submit?
Thx Monerofox
Jump to: