Author

Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 135. (Read 284956 times)

hero member
Activity: 616
Merit: 500
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-?  Grin

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 Smiley

EDIT2 : Its back Smiley 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.
full member
Activity: 140
Merit: 110
bitcoinnaire
I'll take the 1 BTC and leave for 3 months lol, I could certainly use that money right now. Maybe I'll just buy up some low coin and dump it for btc I don't know. This is ridiculous, I should shut off my digitalocean miner since it's really not getting me anywhere.
sr. member
Activity: 826
Merit: 263
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 Smiley

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..

You first.  Leave for a period of 3 months, and I'll send the bitcoin.

You can go into business.  Lots of money in being a professional asshole.
legendary
Activity: 1092
Merit: 1000
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-?  Grin

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 Smiley

EDIT2 : Its back Smiley 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.
full member
Activity: 140
Merit: 110
bitcoinnaire
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

In my current situation 40 cents is better than nothing I guess. Haha
hero member
Activity: 938
Merit: 1000
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-?  Grin
legendary
Activity: 1092
Merit: 1000
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
full member
Activity: 140
Merit: 110
bitcoinnaire
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.
legendary
Activity: 1092
Merit: 1000
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?  Roll Eyes
Curecoin sounds interesting and is CPU-able...
https://bitcointalksearch.org/topic/ann-curecoin-to-be-released-soon-197773
legendary
Activity: 1092
Merit: 1000
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 Smiley

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..
full member
Activity: 140
Merit: 110
bitcoinnaire
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?  Roll Eyes
sr. member
Activity: 826
Merit: 263
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 Smiley

I'll give you 1 BTC if you follow through this time, leave, and don't come back.
legendary
Activity: 1092
Merit: 1000
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 Smiley
hero member
Activity: 616
Merit: 500
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?
legendary
Activity: 1092
Merit: 1000
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
hero member
Activity: 686
Merit: 500
FUN > ROI
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. )
hero member
Activity: 616
Merit: 500
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.
hero member
Activity: 658
Merit: 500
How can i setup a private pool to point all my seperate miners to one solo mining wallet?
hero member
Activity: 616
Merit: 500
Pool is down agian Huh Huh Huh

It seems pool is back again. Looks not steady.

Yep I had to restart the daemons... sorry for that.
hero member
Activity: 700
Merit: 500
Pool is down agian Huh Huh Huh

It seems pool is back again. Looks not steady.
Jump to: