it falls under the "not-so-nice" moniker that kano gave it
+1 to that  |
|
|
|
I'm a bit confused by your reply... sorry for my misunderstanding here. The issue is duplicate share submissions. There are a few ways that have been posted on how to mitigate this behavior (for example, force the nonce to lower case): _this.emit('submit',
{
name : message.params[0],
jobId : message.params[1],
extraNonce2 : message.params[2],
nTime : message.params[3].toLowerCase(),
nonce : message.params[4].toLowerCase()
},
Are there any other known fixes to address duplicate shares in NOMP? Once the appropriate code changes have been made, is there anything other than restarting the stratum server that needs to be done? If so, what other steps need to be taken (not sure what crontab scripts you're referring to, please explain)? Erroneous shares... if indeed it is the case that duplicate shares have been submitted, then writing SQL to clean them out of the shares tables isn't too hard to do. In fact, if it were indeed discovered that a user had been successfully submitting duplicate shares, I'd simply wipe all of that user's shares from the database and ban the user from the pool. Thanks again for the replies. |
|
|
|
|
That's completely dependent on how the rental site manages it. Sometimes you'll get one bridge, other times you'll get more.
|
|
|
|
|
It's very likely that your rental was either stopped on NH end and then restarted there... or different bridges were established from NH, which the pool would consider a new connection and would start at 1042.
This is supported in the logs...
At 14:45:59 you had a share accepted with diff 9985
At 14:47:50 your worker was authorized (i.e. a new connection)
At 14:47:50 your worker was authorized on another thread (another new connection)
At 14:48:03 your worker was authorized on a third thread (new connection)
At 14:49:13 the first share was accepted at diff 1042.
For some reason, the rental service established new connections for your worker, which caused the pool to default back to the starting diff of 1042, until it was adjusted.
|
|
|
|
|
We are only at 53% of expected shares...
|
|
|
|
Hey everyone, In the interest of supporting large hash rate renters, I've opened up port 3334. Diff starts at 65535. The lowest it'll go is 8129. The highest it will go is 1048576. So, if you want to use that please feel free. ./cgminer -o stratum+tcp://stratum.bravo-mining.com:3334 -u username.workerName -p workerPassword
Enjoy. |
|
|
|
|
That's truly odd because there's nothing in the logs, and I didn't restart the stratum servers. Unless connectivity to the servers was lost at the data center and all miners were disconnected... but that's on my provider. I'll have to see if there was a service disruption that they didn't notify me about.
|
|
|
|
Its even a little bit more than 1MB  Ok so we just multiply standard fee times number of TX, but the question is can all the TX be included in 1 block because of the 1MB cap correct? Well, I do know how much is in each work sent out Right now it's 0.33222592 BTC Alright, call me John Snow because I know nothing  If someone could be so kind to direct me to the best learning center. I'll be back next year if I'm lucky  When a pool tries to create a block, it knows exactly what transactions are in that block, and therefore the value (25 BTC + fees). So, it's very easy for a pool operator to tell you the transaction fees included in their blocks. To determine the outstanding transaction fees for all unconfirmed transactions in the network, you'd just need to add them all up |
|
|
|
Well, thanks to the renter who put up an infinite order earlier, I've still got about 3.5 hours left of my rental. I continue to perform the requisite rituals and sacrifices to the block gods in hopes of gaining their favor |
|
|
|
|
I'll take a look at the logs to see if something happened on the server side. I certainly didn't bounce anything... Been stuck in client meetings for the past 3 hours.
|
|
|
|
|
The diff starts at 1042 and adjusts. NH shouldn't be complaining that the difficulty is too low since they supposedly allow down to 127 as a start from a pool. If you guys want, I can open a new port with a higher starting difficulty specifically geared for large hash rentals. If so, it'll take me a little bit and require me to bounce the stratum servers.
|
|
|
|
|
nicehash.com or miningrigrentals.com are the two I use...
|
|
|
|
Certainly hoping so... I've got about another 10 hours (was wrong when I stated 9 earlier) on my 200TH rental from NH. Would love to see another block cracked |
|
|
|
It's just a complete lack of understanding on his part... his whole theory is, "they solve more blocks, therefore they're better". If he bothered to take a look at all, he'd see that kano.is would have netted him more coin than the "communist mining companies" as he calls them... You posting facts and showing data just scares him |
|
|
|
|
Typically yes. For example with my own gear, I'm usually about 99.97%. With the rentals I've had the past few days, my efficiency percentage has dropped to 99.89%.
It's the price you pay with rentals... no telling what they're doing between the miners, their service and the pool.
|
|
|
|
...democracy...china
Best Regards
d57heinz
Pretty sure that's called an oxymoron... |
|
|
|
|
Half of my rental is about to expire... so I'll be down to 200TH for the remainder (about 9 more hours).
|
|
|
|
Cool... glad to have the additional horsepower . Good luck guys! |
|
|
|
There are places right here on these forums where you can sell items . |
|
|
|
|
Show Posts
