Bitcoin Forum
June 21, 2024, 11:25:06 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [ANN][POOL] [Magi XMG] Pool42 | 300 KH/s Limit | Automated Limit Bot  (Read 536 times)
Pool42 (OP)
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile WWW
August 30, 2017, 12:50:51 PM
Last edit: September 20, 2017, 12:19:41 PM by Pool42
 #1

Pool42 Mining Pool
https://xmg.pool42.com



Relevant Informations:

  • Magi (XMG) crypto using M7M algorythm
  • Pool hosted in Europe
  • Automatic / Manual payout
  • 1% Fee
  • SSL secured website
  • 600 KH/s limit
  • DDoS protected servers
  • Automated limit bot disconnecting users with hashrate too high


Details:

  • Magi is a CPU only coin (using tools such as minerd, cpuminer, etc)
  • Europe is actually the location we're using and we're planning to expand to US once we'd have the resources to
  • The limit per user is set to 600 KH/s in order to make sure everyone can get a fair share of the loot, people going above are automatically disconnected from the pool

Support:

The support is currently available through mail at the follow address: contact[a.t]pool42.com .

We hope to see you soon  Wink
https://xmg.pool42.com.
Pool42 (OP)
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile WWW
September 02, 2017, 07:07:14 PM
 #2

We are currently working on a way to automatically enforce the 300 KH/s limit, stay tuned for more informations !  Wink
Pool42 (OP)
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile WWW
September 04, 2017, 11:08:10 AM
 #3

We have updated Pool42 to include a new script that will automatically and regularly check the hashrate of every clients and remove the workers exceeding the hashrate limit.
As we can't overlook at the pool hashrates, 24/7, this bot shall deal with clients exceeding the limit, and that, more efficiently than we could ever do.

If your workers were removed for exceeding the limit, you just have to recreate your worker(s) and restart your miner.
Happy mining Cheesy.
Pool42 (OP)
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile WWW
September 11, 2017, 12:16:14 PM
 #4

Hello,

Pool42 has now updated its wallet to 1.4.3.1, our apologies for the downtime of a few instants you may have experienced, should be all fine now.
Thank you @joe for the update,

Regards.
Pool42 (OP)
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile WWW
September 17, 2017, 12:13:28 PM
 #5

Hello,

Pool42 is running on wallet version 1.4.4.1 for two days, and everything seems to work.
The past issues related with the blockchains seem to be all gone !

We are now mining at full blast extracting blocks of ~40 XMG !
Thanks to @joelabo & @ex33s for their work and support !

Happy mining  Wink,
Regards.
Pool42 (OP)
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile WWW
September 20, 2017, 12:20:24 PM
 #6

Hello people,

We've made a bit of changes at Pool42 !

Quote
Hello fellow miners !

These last days we've been asking you your opinion regarding the hashrate limit in place, if we should remove it or not.
After having discussed with you all who decided to take the poll with us, exchanging your ideas and eventually the pros and cons,
it appeared that most of you were not really in favor of a hashrate limit removal, but more about a hashrate limit increase.

This is the reason why the pool hashrate limit will now be increased from 300 KH/s to 600 KH/s this way allowing medium-end
miners to come in while keeping large botnets out of the pool. This way, we hope to be able to counterbalance large pools such
as Minerclaim & Zpool in an effort to extract a decent amount of blocks per day as we used to.

We thank you all for taking part in this poll, and thank you for the constructive exchanges we have been able to have with you.
The new limit is effective from now on. Please note the tolerance of 15% is still effective.

Happy mining,
Regards.

After having made a poll among our miners, it has been decided by the vast majority that the hashrate limit should be
increased from 300 KH/s to 600 KH/s in order to be able to have a larger share of the network hashrate.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!