Just want to mention that my (non static) wallet that I've compiled myself on ubuntu 12.04 never crashed and I'm constantly pointing at least 5 miners to it. Maybe your static build is broken or the libraries that was linked to it and not the coin itself. I used to have similar problems with other coins on windows when I used specific versions of DB and/or boost libraries.
This is not a static build, i've ran multiple wallets wihout issues on these boxes. Its slimcoin specific. EDIT: How are you pointing 5 miners to the wallet when it does not support rpcthreads ? It supports only one connection. Looks like the connection is dropped after getwork obtains the data so another connection can be made by another miner. Good luck with that  |
|
|
|
Just want to mention that my (non static) wallet that I've compiled myself on ubuntu 12.04 never crashed and I'm constantly pointing at least 5 miners to it. Maybe your static build is broken or the libraries that was linked to it and not the coin itself. I used to have similar problems with other coins on windows when I used specific versions of DB and/or boost libraries.
This is not a static build, i've ran multiple wallets wihout issues on these boxes. Its slimcoin specific. EDIT: How are you pointing 5 miners to the wallet when it does not support rpcthreads ? It supports only one connection. |
|
|
|
Originating from China.
Random or not ? If random, its a botnet and you know it. My 20 high-end i7 4770k processors do around 100KH/s so 1MH/s spread accross 150 IPs sounds impossible unless they are all 32 cores My i7 4770 does about 5.3Kh/s  Very doubtfull your telling the truth here... Haha you don't know some big farmer out there. ypool or gpool alone they have ten times of this power. primer- said that he got around 1k SLM daily. At current diff that means he has around 400khs. It is pretty big already. I've got 180KH/s + 9% of all burned coins .. |
|
|
|
|
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.
|
|
|
|
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.
The pool will always pay you the same amount. Realy? My transaction are going from 0.12 to 0.43 SLM... That depends on the total pool hash rate. What might be fishy is this guy with 1MH/s. I am watching pool stats closely. I do not see many blocks found. What *MIGHT* be happening is pool owner running a fake pool worker with 1MH/s in order to collect most of the pool income I've seen it many times before... EDIT : No new blocks in 15 minutes with 1.87MH/s at "difficulty" : 0.10595522 ... hmm very unlikely ..  EDIT2 : Block found after about 20 min. Keep watching guys, does not look good. http://63.141.232.170/tbs |
|
|
|
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. I confirm the math, i've mined 27 blocks with 150-180KH/s in the last 24h compared to 50-60SLMs earned by the pool in 24h. I dont remember the diff/total pool hash rate but still the diff. is huge. |
|
|
|
Originating from China.
Random or not ? If random, its a botnet and you know it. My 20 high-end i7 4770k processors do around 100KH/s so 1MH/s spread accross 150 IPs sounds impossible unless they are all 32 cores My i7 4770 does about 5.3Kh/s Very doubtfull your telling the truth here... 5.3 x 20 = 106KH/s Idiot. |
|
|
|
Originating from China.
Random or not ? If random, its a botnet and you know it. My 20 high-end i7 4770k processors do around 100KH/s so 1MH/s spread accross 150 IPs sounds impossible unless they are all 32 cores |
|
|
|
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.*) ? |
|
|
|
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. |
|
|
|
I've read about that one, looks like I'll have to go investigate in the meantime I might as well do something with this little bit of coin I have right now.
3 coins ? At the current exchange rate, they are worth 40 cents |
|
|
|
So now everyone is dumping this coin? I have an instance on my cpu and one up on digital ocean, it seems like I'd be better off mining some other coin or something at this rate, since I only have 3 coins I doubt there's any way I'd get a legit amount for it. What's the next best coin?  Curecoin sounds interesting and is CPU-able... https://bitcointalk.org/index.php?topic=197773.0 |
|
|
|
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? Each node has its own wallet. Each wallet is allowed only one connection to a remote wallet via connect=IP arg in the .conf file (to keep the cpu usage low). XX instances running, 1-5 crash every hour and require a full db rebuild. I should just give up, coin is far from salvageable. Current exchange price , 1000 coins for 0.2btc. I'd be better off mining scrypt with my cpus I'll give you 1 BTC if you follow through this time, leave, and don't come back. Send the BTC to 13MF2Yuhvq9Lmq5ZE1CLeputsXwnfcxf1X and you will never hear from me again in this thread.. |
|
|
|
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? Each node has its own wallet. Each wallet is allowed only one connection to a remote wallet via connect=IP arg in the .conf file (to keep the cpu usage low). XX instances running, 1-5 crash every hour and require a full db rebuild. I should just give up, coin is far from salvageable. Current exchange price , 1000 coins for 0.2btc. I'd be better off mining scrypt with my cpus |
|
|
|
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 |
|
|
|
There's fire on bter!!! Traders burning dumped SLIMs! |
|
|
|
The burn block I found is confirmed with 8 confirmations, but it doesnt show the 11 coins in any of my balances...why is that because the wallet is broken, you did not find a pob block. click on it for more info. or use listtransactions for real info every time you don't like this coin and you always at here I see you are active in the new moderated slim-coin fork thread. Let me tell you something, chance you get your fork on an exchange after slimcoin fiasco is zero to none. ZERO. 不可能 !! |
|
|
|
The burn block I found is confirmed with 8 confirmations, but it doesnt show the 11 coins in any of my balances...why is that because the wallet is broken, you did not find a pob block. click on it for more info. or use listtransactions for real info |
|
|
|
Pool is under maintenance - duration 1-2 hours.
Thank you. Let the instamine for us soloing begin |
|
|
|
|
Show Posts
