|
Guys, please move to the fork with the longest chain, or you will cry!
|
|
|
|
|
We are on the right fork! Come join our pool...
|
|
|
|
More than 3k SLM has been paid out! Join our pool.  |
|
|
|
OK, what just happened 1 min ago, pending went from 110 to 109, confirmed stayed the same at 178 and orphaned is still 1.
Pool owner, please check if that one block got kicked. Not trolling , seriously, counter went back and orhpan or confirmed did not move.
Yes, 12 kicked blocks 000000066c4683fc73a17b2154f04a5e259ab6ab021c3cdffa63b224bee83fe7:7122eb189e7dc2b641d72a6e77bb585fbf53b980afbb9432e17a97ee935035d2:8546:31 000000027596ea379c5b0f21c9b9ceb8e6666392ed5153af35bcf3143a029187:5120f63f0fac644963413d0c0228f82dd6045965694008e43a5558af68f16e5f:8698:31 0000000785b4acfe604d3824eaa1064ec58065f5789827485eb643b2058389c6:6807fcabe1b907997e7cc1d6e2b1b5fca676f2c7ac60c5d7f70966298593dc41:8668:31 0000000063a614e8df21043c38a05e6fac9b374773442d748d7aa7551dc5e734:b5e17ef51777d413bf7a3b48649b610beb680df94912db7adfc7fd79fba67dbb:8497:31 0000000737a95389d9e09852ea6375ae80778ac4399ae4e9846e56fc170c3ca6:0de31c460e3908cd28ee95f0ee46373e3f2e11b316e358aa5a9b23320c45c9cf:8697:31 00000009c966bbbc2ce15461873ac87d309f14c3ec11b597a7352278c067ee2b:9636355d2ba13ab5cf00bb2a1d54dffa50f266dddc080ea177d6edddd5a82174:8647:31 0000000d76936258fc7bfeed209156581be8004a9eccd4b955a6eed210e4c513:5d1217674b6e1d27a782ccfacb73f4ba4d670fb1af94a67010847b50d8cddc04:8786:31 0000000a468389d5f99e0ac419a83098bb2e5577260f604918b8a1e057543dbc:c9bd19f5b1d1b284a78a48c57b15b2bc5739b4f47997a65140c498eea10732bf:8719:31 000000078ae0479aa488fe5381a2dc68d8724288c38c6d1f73132618d1c7c336:312dc8a44b7bb82726f7e847c3198578f28abd7dc8b0f2c4d28a0d87d3aad68e:8793:31 0000000457d1e8b73399bce608195f58900e6c3bd88993a37deab56dd44aa1ec:aa981e733d292ab99440936d6626543c9be739941d54147acb20c68f25098f7a:8809:31 0000000205681ab595c48657e8ea5d589b24b5971b0b75ae398ab0ffacfe0348:066134d23e5df6143ba0918330867ac8d6e29f3da32d3477798da134a55a4fe2:8810:31 00000002e20ee5684655b28264abd2eccf2b1abf4aa990bf2da036fde01c255c:460d10683e0e0e919119732634f82b620473dee4e8b72c2653744b40f5336029:8670:31 |
|
|
|
How can i setup a private pool to point all my seperate miners to one solo mining wallet?
That's not going to be efficient, why not use my pool? Only 1% fee. Solo mining gave me already about 180 SLM PoS. When i spread all my individual miners to your pool using slimcoinminer, i get a payout between 0.17 - 0.25 SLM (18 - 24 Kh). You can check my address SPDwAHXGn7ZdtH7nmchaK4QuSXTwr724Re. I'm in the pool for over 36 hours now, it generated a mere 39 SLM. So solo mining is the way to go for this coin. I prefer to wait 48 hours to find a single block PER instance i'm running, and get 11 SLM per instance, than to keep waisting time and money in your pool, because some big hashrate's steal all earnings from the small ones. To bad, not your fault of course. But i just love to combine my instances to a single wallet. Not really, there is a big luck factor involved when solo mining, the earnings from solo mining will fluctuate more wildy the lower your hashrate. The pool will always pay you the same amount, given that the block generation is constant. I have already paid out everything that the pool earns, and more, the pool wallet is sitting at ~60 SLM. |
|
|
|
Originating from China.
Random or not ? If random, its a botnet and you know it. Not random. The network bits are the same. |
|
|
|
It seems pool is back again. Looks not steady.
Set up both a pool and a solo miner, give the pool one a higher priority - if the pool works, that should use all the processing power, if the pool is down that miner uses almost no processing power and it goes to the solo miner instead. ( Or you could just solo mine, if you've got a fair amount of processing power to begin with. ) You must have come from some other coin-land, let me remind you, solo is almost impossible with slimcoin wallet, rpcthreads is not supported so you are left with 1. running a full wallet on every node you mine off or 2. err i'm not going to bother describing my set up, it works but i have to keep an eye on all wallets 24/7. Simple restart script wont work as i have to rebuild blockchain databases every couple of hours. Totally agreed. This coin is very buggy. If you just mine and dump, this coin is no longer profitable. btw I just see some whale with 1Mhs at the poola. Is that you primer-? I wish , thats some serious CPU power. Probably a botnet, doubt someone is paying Amazon AWS as its not profitable at all. Perhaps pool owner can take a look if all workers produce the same amount of hash power or not. If not, than its a botnet. EDIT : HAHAHA it fucking dissapeared, right after my post. Botnet or pool owner fake worker  EDIT2 : Its back I would not trust the pool at all. EDIT 3 : Its back with only half the hash power. Something fishy going on at the pool. There is about 150 unique IPs mining to that address... I don't know about the individual hashrate. Are IP addresses random or do they belong to amazon (54.*) ? Originating from China. |
|
|
|
It seems pool is back again. Looks not steady.
Set up both a pool and a solo miner, give the pool one a higher priority - if the pool works, that should use all the processing power, if the pool is down that miner uses almost no processing power and it goes to the solo miner instead. ( Or you could just solo mine, if you've got a fair amount of processing power to begin with. ) You must have come from some other coin-land, let me remind you, solo is almost impossible with slimcoin wallet, rpcthreads is not supported so you are left with 1. running a full wallet on every node you mine off or 2. err i'm not going to bother describing my set up, it works but i have to keep an eye on all wallets 24/7. Simple restart script wont work as i have to rebuild blockchain databases every couple of hours. Totally agreed. This coin is very buggy. If you just mine and dump, this coin is no longer profitable. btw I just see some whale with 1Mhs at the poola. Is that you primer-? I wish , thats some serious CPU power. Probably a botnet, doubt someone is paying Amazon AWS as its not profitable at all. Perhaps pool owner can take a look if all workers produce the same amount of hash power or not. If not, than its a botnet. EDIT : HAHAHA it fucking dissapeared, right after my post. Botnet or pool owner fake worker EDIT2 : Its back I would not trust the pool at all. EDIT 3 : Its back with only half the hash power. Something fishy going on at the pool. There is about 150 unique IPs mining to that address... I don't know about the individual hashrate. |
|
|
|
It seems pool is back again. Looks not steady.
Set up both a pool and a solo miner, give the pool one a higher priority - if the pool works, that should use all the processing power, if the pool is down that miner uses almost no processing power and it goes to the solo miner instead. ( Or you could just solo mine, if you've got a fair amount of processing power to begin with. ) You must have come from some other coin-land, let me remind you, solo is almost impossible with slimcoin wallet, rpcthreads is not supported so you are left with 1. running a full wallet on every node you mine off or 2. err i'm not going to bother describing my set up, it works but i have to keep an eye on all wallets 24/7. Simple restart script wont work as i have to rebuild blockchain databases every couple of hours. EDIT : This is what i have to deal with every hour : *** glibc detected *** slimcoind: double free or corruption (fasttop): 0x00007f26cc000ac0 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x76166)[0x7f2705e84166] /usr/lib64/libstdc++.so.6(_ZNSs6assignERKSs+0x85)[0x7f27066d9565] slimcoind(_Z8ReadHTTPRSiRSt3mapISsSsSt4lessISsESaISt4pairIKSsSsEEERSs+0xe5)[0x50ac45] /usr/local/lib/libboost_thread.so.1.55.0(+0xcaa3)[0x7f2707b64aa3] /lib64/libpthread.so.0(+0x79d1)[0x7f27069499d1] /lib64/libc.so.6(clone+0x6d)[0x7f2705ef6b6d] ======= Memory map: ======== 00400000-00636000 r-xp 00000000 08:03 2623376 /usr/local/bin/slimcoind 00835000-00837000 r--p 00235000 08:03 2623376 /usr/local/bin/slimcoind 00837000-00838000 rw-p 00237000 08:03 2623376 /usr/local/bin/slimcoind 00838000-0083b000 rw-p 00000000 00:00 0 00a98000-00ad1000 rw-p 00000000 00:00 0 00ad1000-00ad2000 rw-p 00000000 00:00 0 00ad2000-00ada000 rw-p 00000000 00:00 0 00ada000-00c36000 rw-p 00000000 00:00 0 00c36000-00c37000 rw-p 00000000 00:00 0 00c37000-00ca1000 rw-p 00000000 00:00 0 Is that crash when you point all slimminer instances to a single wallet? Or each node has it's own wallet? |
|
|
|
How can i setup a private pool to point all my seperate miners to one solo mining wallet?
That's not going to be efficient, why not use my pool? Only 1% fee. |
|
|
|
It seems pool is back again. Looks not steady. Yep I had to restart the daemons... sorry for that. |
|
|
|
OK, maintenance is over. Everything should be smooth now. |
|
|
|
Pool is under maintenance - duration 1-2 hours.
Pool is back up actually, but there will be intermittent downtime while I make changes. |
|
|
|
|
Pool is under maintenance - duration 1-2 hours.
|
|
|
|
No more orphans since the fix, everyone is getting what they mined for + 10%. |
|
|
|
The fix seems to be working nicely. |
|
|
|
anybody have a list of active nodes, I used the ones in the op but unable to synch for over an hour, I have a wallet working but there's not "getpeerinfo" command implemented in the wallet so can use those... any help appreciated..
addnode=63.141.232.170 addnode=144.76.142.47 addnode=144.76.142.49 addnode=94.229.76.122 addnode=185.21.191.189 addnode=85.110.8.131 addnode=96.237.174.192 addnode=60.250.174.75 addnode=198.199.101.230 addnode=192.82.119.85 addnode=107.170.123.185 addnode=95.85.25.57 addnode=222.134.95.70 addnode=54.187.155.212 addnode=54.201.166.212 addnode=192.241.173.228 addnode=119.63.94.173 addnode=181.193.75.66 addnode=144.76.142.47 addnode=144.76.142.49 addnode=76.127.202.17 addnode=96.237.174.192 addnode=125.115.54.166 addnode=76.127.202.17 addnode=96.237.174.192 addnode=107.181.250.216 addnode=107.181.250.217 |
|
|
|
I have just increased the pool payout by 10% per worker temporarily!
I urge everyone to wait until wallet problems are fixed by the dev. I am missing at least 3-5 payouts from the pool. Blocks were confirmed but no payouts have been sent. Anyway, diff is low, solo mining is now possible. If the blocks were confirmed it would obviously have paid out, what is your address? I'll send you some compensation so you can shut up. |
|
|
|
|
I have just increased the pool payout by 10% per worker temporarily!
|
|
|
|
I have just killed 180KH/s to the pool and i suggest others do the same, pool is not paying out and there are problems with the wallet.
Several payouts appear to have come in just now. Now the question is.. will you re-connect?  There are obviously problems with the wallet, so naturally the pool is having issues as well, nothing I can do about it except modify the pool so it can deal with the buggy failure that the wallet is. I have just added a block check counter, it will only discard the block after the block have been verified to be an orphan at least 10 times, hopefully this will lead to much less "fake" orphan blocks. |
|
|
|
|
Show Posts
