[ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer!

[slimcoin]

I am not the Dev of TGC coin, Slimcoin is not dead.

[1714521734]

1714521734

[1714521734]

1714521734

[TheCoinFinder]

Pool is under maintenance - duration 1-2 hours.

Pool is back up actually, but there will be intermittent downtime while I make changes.

Care to share your hash algo?

Last time I asked about this, OP poster deleted my post?!not exactly good for the coin imo

[reflector]

Pool is under maintenance - duration 1-2 hours.

Pool is back up actually, but there will be intermittent downtime while I make changes.

Care to share your hash algo?

Last time I asked about this, OP poster deleted my post?!not exactly good for the coin imo

This thread is not even self-moderated?

[TheCoinFinder]

Pool is under maintenance - duration 1-2 hours.

Pool is back up actually, but there will be intermittent downtime while I make changes.

Care to share your hash algo?

Last time I asked about this, OP poster deleted my post?!not exactly good for the coin imo

This thread is not even self-moderated?

Well if not this thread, there is another slimcoin thread that is? (I lose track to be honest):

A reply of yours, quoted below, was deleted by the starter of a self-moderated topic. There are no rules of self-moderation, so this deletion cannot be appealed. Do not continue posting in this topic if the topic-starter has requested that you leave.

You can create a new topic if you are unsatisfied with this one. If the topic-starter is scamming, post about it in Scam Accusations.

I am happy to set up an additional pool. But it seems that no one wants to share the hash code.

And unfortunately, I can't figure out how myself to make it from the cpumining or wallet code :/

Anyone care to github it?

[slimcoin]

In slimminer, it is dcrpyt.c and dcrpyt.h. Slimminer is available on Github.

[dstorm]

Pool is under maintenance - duration 1-2 hours.

Pool is back up actually, but there will be intermittent downtime while I make changes.

Care to share your hash algo?

Last time I asked about this, OP poster deleted my post?!not exactly good for the coin imo

https://bitbucket.org/dstorm/dcrypt-python-module

[primer-]

There's fire on bter!!! Traders burning dumped SLIMs!

[TheRealSteve]

allready moved to selfmoderated thread https://bitcointalk.org/index.php?topic=643300.new#new
they (or he) don't wanna hear criticism

Or they took one look at this thread, realized that some people's definition of 'criticism' is whining, moaning and bitching left right and center in juvenile language - and decided that they'd rather be accused of not wanting to hear criticism than have that in their thread.  There's always bitcointa.lk

A blockchain parser ...

That's great - looking forward to it

[ekoja]

Pool is down agian

[ekoja]

Pool is down agian

It seems pool is back again. Looks not steady.

[sandor111]

Pool is down agian

It seems pool is back again. Looks not steady.

Yep I had to restart the daemons... sorry for that.

[bitspender]

How can i setup a private pool to point all my seperate miners to one solo mining wallet?

[sandor111]

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.

[TheRealSteve]

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

[primer-]

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

[sandor111]

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?

[primer-]

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

[reflector]

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.

[skottiejay]

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? 

[primer-]

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