XMR Monero Pool xmr.suprnova.cc MPOS Based PPLNS

[m1n1ngP4d4w4n]

Payment id and integrated addresses are currently implemented and being tested. I'll activate the use of them shortly

Any new about this ?  

Integrated addresses are now integrated. Can someone check if the payment works / arrives at Kraken ?

EDIT: Confirmed working !

Synced now: xmr-us.suprnova.cc

Same port as on the regular server

Is it SSL enabled? Can't connect with :5221

Port 5221 now active on xmr-us as well !



Separate Payment ID's are next, but it's not THAT easy.. I need a few more hours including testing etc.

Nice  Keep up the good work

[joaogti36]

Disconnected. Pool difficulty too low. when trying to send some rented power thrugh nicehash port ((((

getting disconnect like crazy...
fix?!

[zoggie]

having same issue with low difficulty on a few workers that are hashing over 4k. Worst part is that worker gets banned even though the server is still accepting work for suprnova.

On top of that, when the worker gets banned, it doesn't send an email of an idle worker. Tested by taking a worker not banned offline and still no email 1 hour later. Block emails come in just fine.

Edit. Low difficulty issue solved for me by using xmr and not xmr-us where issue existed. I'll test xmr-us. again tomorrow if xmr. remains stable.

Email notifications for idle workers seem still to not be working.

Edit2. Low difficulty share is only occuring during a DevFee (claymore) event and very rarely. But enough for occasional banning.

[ocminer]

having same issue with low difficulty on a few workers that are hashing over 4k. Worst part is that worker gets banned even though the server is still accepting work for suprnova.

On top of that, when the worker gets banned, it doesn't send an email of an idle worker. Tested by taking a worker not banned offline and still no email 1 hour later. Block emails come in just fine.

Low difficulty means invalid work,  that can happen with some overclocking settings.

Banning should not happen at all unless you send ONLY invalid shares for a certain amount of time.

I'll check banning again though.

[Prelude]

I've also been IP banned. For no apparent reason, rejects shot up to about 33% on all rigs which is (I assume) why I was banned. Rigs are 100% stable on any algo for weeks on end, and before this happened I was sitting at 0.01% rejected according to ethman across all rigs.

Unfortunately, I've had to switch back to dwarf for the time being. Let me know when you've solved the issue and I'll be back.

[ocminer]

I indeed found a bug where some unintended ip banning on stratum happened in case you've used claymore over ssl.

Fixed now!

[Prelude]

I indeed found a bug where some unintended ip banning on stratum happened in case you've used claymore over ssl.

Fixed now!

17 seconds later and the problem is solved.  I'm back.

How is the payment address + ID coming along?

[ocminer]

I indeed found a bug where some unintended ip banning on stratum happened in case you've used claymore over ssl.

Fixed now!

17 seconds later and the problem is solved.  I'm back.

How is the payment address + ID coming along?

I'd say I'm at 80%... Some checks need to be implemented that users don't enter false payments ids or no id at all. Also the id has to be removed when the user changes to a kraken address with integrated ID etc..  It's not as easy as thought first, but I'm pretty far already

[Prelude]

I indeed found a bug where some unintended ip banning on stratum happened in case you've used claymore over ssl.

Fixed now!

17 seconds later and the problem is solved.   I'm back.

How is the payment address + ID coming along?

I'd say I'm at 80%... Some checks need to be implemented that users don't enter false payments ids or no id at all. Also the id has to be removed when the user changes to a kraken address with integrated ID etc..  It's not as easy as thought first, but I'm pretty far already

Glad to hear. Keep up the good work!

[ocminer]

Disconnected. Pool difficulty too low. when trying to send some rented power thrugh nicehash port ((((

getting disconnect like crazy...
fix?!

Thanks for your Info, found the error and fixed it.

[zoggie]

Disconnect still occurring according to your dashboard page but worker page shows workers still connected. Monitoring emails of idle workers being sent out. Hashrate on dashboard almost zero. Issues today?

[ocminer]

Disconnect still occurring according to your dashboard page but worker page shows workers still connected. Monitoring emails of idle workers being sent out. Hashrate on dashboard almost zero. Issues today?

I've just restarted the stratum because of the nicehash fix so that should have caused a small disconnect but that was all, nothing else should have happened and your workers should be working again.

[m1n1ngP4d4w4n]

I indeed found a bug where some unintended ip banning on stratum happened in case you've used claymore over ssl.

Fixed now!

17 seconds later and the problem is solved.  I'm back.

How is the payment address + ID coming along?

I'd say I'm at 80%... Some checks need to be implemented that users don't enter false payments ids or no id at all. Also the id has to be removed when the user changes to a kraken address with integrated ID etc..  It's not as easy as thought first, but I'm pretty far already

Awesome, keep up the good work 

[zoggie]

payout fees went up to 0.07 XMR from 0.01?

[sminside]

payout fees went up to 0.07 XMR from 0.01?

whats wrong with this pool @ocminer ? from hard to find block now payout fee is 0.07 xmr ? that higher than any other xmr pool 

[Ned Kelly]

payout fees went up to 0.07 XMR from 0.01?

whats wrong with this pool @ocminer ? from hard to find block now payout fee is 0.07 xmr ? that higher than any other xmr pool  

It's because the HF. Tx sizes went up, so someone has to pay for increased size. Other pools has 2% fee they can afford to pay it.

[sminside]

payout fees went up to 0.07 XMR from 0.01?

whats wrong with this pool @ocminer ? from hard to find block now payout fee is 0.07 xmr ? that higher than any other xmr pool  

It's because the HF. Tx sizes went up, so someone has to pay for increased size. Other pools has 2% fee they can afford to pay it.

then why not using 2% fee instead this fix 0.07 xmr
stay back micro miner, you will not have change profit on this pool anymore
this pool only for miner farm 

[Ned Kelly]

payout fees went up to 0.07 XMR from 0.01?

whats wrong with this pool @ocminer ? from hard to find block now payout fee is 0.07 xmr ? that higher than any other xmr pool  

It's because the HF. Tx sizes went up, so someone has to pay for increased size. Other pools has 2% fee they can afford to pay it.

then why not using 2% fee instead this fix 0.07 xmr
stay back micro miner, you will not have change profit on this pool anymore
this pool only for miner farm 

2% from anything more than 3.5 xmr is less profitable than 0.07 xmr.
Also, fees will come down with the time, because block size will be larger and will be no penalty for pool operator to put txs for miners into the block. However it will take some time.

[ocminer]

I'll reduce the withdrawal fees once the network reduces them, I just had to set them accordingly to the network as already several withdrawals were made with 0.01 fee but i've paid way more since the hardfork.

Best would probably be to discuss this issue direct with the Monero devs in their topic:

https://bitcointalk.org/index.php?topic=583449.msg17469638#new

As the fee doesn't come from the pool, it comes from the coin.

[sminside]

Good to see ocminer has fast respon, maybe the best thing is hold my xmr on your pool until the fee reduced right
i will start mining again on your pool tomorrow