Usually the first pool always gets the cookies - and miners never ever move away from there as long it is not DDoS'ed, Forked or the Payout crons are hanging ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Except for the nicehash issues, nothing to report ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Payouts had obviously to be disabled at first while wallet gets updated, but nothing was confirmed yet so that shouldn't matter in this case. hmm.. strange... well.. i have that too sometimes.. its weird Back then we had no issues spreading miners around, they would comply. Minerpools attempted a few times to do so, but nobody moves their asses. I'm starting to understand why so many coins are trying to get rid of the miners by going 100% PoS or SPoW like URO. Not caring by the miners probably has a role to play in that.
|
|
|
Usually the first pool always gets the cookies - and miners never ever move away from there as long it is not DDoS'ed, Forked or the Payout crons are hanging ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Except for the nicehash issues, nothing to report ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Payouts had obviously to be disabled at first while wallet gets updated, but nothing was confirmed yet so that shouldn't matter in this case.
|
|
|
Where the hell is all the hash coming from? such and super don't have jack for hash.
Minerpools was the First here Heh, I was a few minutes ahead of him.. yet .. 16mh. >> I am shutting down www.suchpool.pw/xqn for lack of hashrate. - Please withdraw your coins!
|
|
|
Disabling sendmany seems to have done it.
|
|
|
Wallet still crash on payout attemps for me..
uh really ? Not the best wallet for a pool, huh ? hehe no not the best case scenario! the first one did it, but now the updated one seems to still do it.
|
|
|
Wallet still crash on payout attemps for me..
will try to disable sendmany
|
|
|
Pool Hash: 289.04 MH/s Net Hash: 17.96 GH/s
Spread them hashes around, Minerpools has 19gh out of 21..
|
|
|
I overlooked the confirmations, so users were assigned coins that were not available yet. I moved those back to where they should be, the coins will unconfirm when they are mature enough!
I also am updating the source right now to re-enable payouts!
|
|
|
Buddy just threw his hash back onto the network and found the last ten blocks. Herp a derp.
And yet we have difficulty finding blocks because of that wave :/
|
|
|
tested out sending from wallet. it crashes if you try and send coin anywhere.
Yeah, I found that too and I'm already on it... Just need a few minutes to debug here, must have introduced a bug at the last minute, will turn around a fix. Waiting on the update, I disabled the payouts for now to avoid creating invalid tx's on the pool.
|
|
|
Guys spread some of the hash to such pool as well
![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif)
|
|
|
Well the guy with the huge farm seems to have found us..
![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) We just went from 35ghs to 65ghs.. Guy loves to match networks hashrate and instamine till difficulty gets high, then let's us battle it out to drop the diff. IMO, that's one of the downturn of the ASICs.. all that hash could be sitting in one single office now, no need for large gpu farms to match networks!
|
|
|
... Strange your nicehash ports didn't work for me, yet miner pools worked immediately. Should re initiate your proxy faster next time, since now my rentals pointed in your direction fired up.
Both pools working for me now. Thanks guys.
We try to do that in the last resort. When we do this, it does drop TCP connections to most of the miners, sometimes triggering their failovers.
|
|
|
finally connected
Could be frontend lag. Check pool stats to see if you were mining before. I tried it myself, for no reason Nicehash wouldn't connect at all. Seems to be working now, Betarigs aswell.
|
|
|
rented 5 miners but they are not connecting to your pool
What error message do you get? How much hash also? im not getting any error.betarigs say they are all online and mining and on pool it says they are not Did you try on port 23346? Betarigs may be looking for a specific diff. tried all ports.I am fuking over betarigs.they have screwed me so many times ![Angry](https://bitcointalk.org/Smileys/default/angry.gif) We don't usually have issues with them, except at some times. Not sure why. Some users report issues with nicehash also either on SuchPool or MinerPools. Edit: Re-initiated our proxys, it might work better for you now
|
|
|
rented 5 miners but they are not connecting to your pool
What error message do you get? How much hash also? im not getting any error.betarigs say they are all online and mining and on pool it says they are not Did you try on port 23346? Betarigs may be looking for a specific diff.
|
|
|
rented 5 miners but they are not connecting to your pool
What error message do you get? How much hash also?
|
|
|
We're up! www.suchpool.pw/xqnEdit: I will be adding a port for rentals/nicehash in a few minutes. Waiting.. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Check a bit up, I added them in my previous post! For rentals I suggest 13346
|
|
|
We're up! www.suchpool.pw/xqnEdit: I will be adding a port for rentals/nicehash in a few minutes. Edit2: Regular hashrate VARDIFF ranging from 32 to 2048 (Good below 5-8MH/s): stratum+tcp://stratum1.suchpool.pw:3346 stratum+tcp://stratum2.suchpool.pw:3346 High hashrate VARDIFF port ranging from 512 to 20048 (For a wider range of devices): stratum+tcp://stratum1.suchpool.pw:13346 stratum+tcp://stratum2.suchpool.pw:13346 VARDIFF ranging from 3500 to 4000: stratum+tcp://stratum1.suchpool.pw:23346 stratum+tcp://stratum2.suchpool.pw:23346 Happy mining everybody!
|
|
|
|