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

[TheRealSteve]

make sure that your wallet is properly synced, currently @ block 12225

I think that might currently be a problem for many

Mine repeatedly gets stuck at 10202, with the debug.log citing "ERROR: ConnectInputs() : tried to spend coinbase/coinstake at depth 408".  I've got it wiping everything restarting periodically, but might as well wait for an updated wallet with a proper fix

[ltcnim]

my clients, no matter if windows or linux do not sync more than 10559 blocks (which is the checkpoint i guess):

Code:

2014-06-11 17:39:27 UTC 10559 ------------------------------- 1 0 0 0 -1 -1 -1
2014-06-11 17:40:34 UTC LoadBlockIndex(): hashBestChain=000000025510171c1e94  height=10559  trust=10560
2014-06-11 17:40:51 UTC Block 10559 has this many transactions in it: 2, Block Pos 7259458
2014-06-11 17:41:14 UTC nBestHeight = 10559

[sp00lin9]

make sure that your wallet is properly synced, currently @ block 12225

I think that might currently be a problem for many

Mine repeatedly gets stuck at 10202, with the debug.log citing "ERROR: ConnectInputs() : tried to spend coinbase/coinstake at depth 408".  I've got it wiping everything restarting periodically, but might as well wait for an updated wallet with a proper fix

I had the same issue, & this is how i fixed my wallet.

1. Close Wallet
2. Delete everything in %appdata%/slimcoin EXCEPT WALLET.DAT & SLIMCOIN.CONF
3. Edit Slimcoin.conf, delete EVERYTHING and paste this :

server=1
daemon=1
rpcuser=USER
rpcpassword=PASSWD
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
rpcallowip=localhost
connect=144.76.139.111:10000

4. Be patient & let it sync COMPLETELY
5. After its done, go back to %appdata%/Slimcoin
6. Edit slimcoin.conf, delete EVERYTHING & add this :

server=1
daemon=1
rpcuser=USER
rpcpassword=PASSWD
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
rpcallowip=localhost
addnode=114.34.15.168
addnode=63.141.232.170
addnode=50.116.56.210
addnode=108.7.224.149
addnode=85.25.195.74
addnode=72.252.176.12
addnode=213.82.213.152
addnode=144.76.142.47
addnode=77.237.251.163
addnode=84.198.182.60
addnode=76.127.202.17
addnode=96.237.174.192
addnode=107.181.250.216
addnode=107.181.250.217
addnode=144.76.142.47
addnode=144.76.142.49

7. Reopen Slimcoin-QT

[reflector]

No new patches, dev has no idea whats going on, difficulty lower than 24h after launch, bter trading suspended.

I am out. Good luck guys, hope the traders earn back what they lost.

Agree.
Shame on dev. This coin was perspective, but dev is slow.

Shame on you! You want stuff faster? Do it yourself!
You want a fulltime dev? Donate him! Or gtfo here and grab youself some scamcoin at ipo

Dev's doing a great job, all bugs so far have been fixed in time (<48 hours). He asks for debugs to fix the sync issue.. SEND THEM instead of complaining!

++1

1++

[primer-]

make sure that your wallet is properly synced, currently @ block 12225

I think that might currently be a problem for many

Mine repeatedly gets stuck at 10202, with the debug.log citing "ERROR: ConnectInputs() : tried to spend coinbase/coinstake at depth 408".  I've got it wiping everything restarting periodically, but might as well wait for an updated wallet with a proper fix

I had the same issue, & this is how i fixed my wallet.

1. Close Wallet
2. Delete everything in %appdata%/slimcoin EXCEPT WALLET.DAT & SLIMCOIN.CONF
3. Edit Slimcoin.conf, delete EVERYTHING and paste this :

server=1
daemon=1
rpcuser=USER
rpcpassword=PASSWD
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
rpcallowip=localhost
connect=144.76.139.111:10000

4. Be patient & let it sync COMPLETELY
5. After its done, go back to %appdata%/Slimcoin
6. Edit slimcoin.conf, delete EVERYTHING & add this :

I will be taking down node 144.76.139.111 in 10 minutes. Use a different node for syncing.

[TheRealSteve]

connect=144.76.139.111:10000

Yeah, unfortunately that one's going down (or IS down, by now).  Of the other ones in the first post, only 3 ever connected when I tried them, and all 3 ended up getting stuck.  Like I said, probably better to wait and see what happens with the wallet

[sp00lin9]

connect=144.76.139.111:10000

Yeah, unfortunately that one's going down (or IS down, by now).  Of the other ones in the first post, only 3 ever connected when I tried them, and all 3 ended up getting stuck.  Like I said, probably better to wait and see what happens with the wallet

Sorry, i didnt know. My wallet successfully syncs with the following slimcoin.conf file

server=1
daemon=1
rpcuser=USER
rpcpassword=PASSWD
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
rpcallowip=localhost
addnode=114.34.15.168
addnode=63.141.232.170
addnode=50.116.56.210
addnode=108.7.224.149
addnode=85.25.195.74
addnode=72.252.176.12
addnode=213.82.213.152
addnode=144.76.142.47
addnode=77.237.251.163
addnode=84.198.182.60
addnode=76.127.202.17
addnode=96.237.174.192
addnode=107.181.250.216
addnode=107.181.250.217
addnode=144.76.142.47
addnode=144.76.142.49

[primer-]

I;ve got over 70 connections at the node so i will keep it up for an hour or so.

[TheRealSteve]

My wallet successfully syncs with the following slimcoin.conf file

I think those are the ones from the first post - but I'll give it another shot

[sp00lin9]

My wallet successfully syncs with the following slimcoin.conf file

I think those are the ones from the first post - but I'll give it another shot

It couldn't hurt right! Lol. I've got a fully synced green check mark with incoming / outgoing transactions working as intended! Hopefully it does the same for you!

[ltcnim]

well, slimcoind is using all CPU power since hours. It's currently synced to block 12591 (which is the latest block I guess), but the log is flooded with:

Code:

2014-06-11 19:53:58 UTC getblocks 5863 to 0000000449b33a0ecc01 limit 1021
2014-06-11 19:54:00 UTC   getblocks stopping at 6746 0000000449b33a0ecc01 (470070 bytes)
2014-06-11 19:54:01 UTC getblocks 5863 to 00000006643fbac4e750 limit 1021
2014-06-11 19:54:05 UTC   getblocks stopping at 6748 00000006643fbac4e750 (471401 bytes)
2014-06-11 19:54:05 UTC getblocks 5863 to 000000022bb352e1160a limit 1021
2014-06-11 19:54:08 UTC   getblocks stopping at 6752 000000022bb352e1160a (472880 bytes)
2014-06-11 19:54:08 UTC getblocks 5863 to 00000007edff4df1b449 limit 1021
2014-06-11 19:54:11 UTC   getblocks stopping at 6754 00000007edff4df1b449 (473591 bytes)
2014-06-11 19:54:11 UTC getblocks 5863 to 0000000354118d287a3d limit 1021
2014-06-11 19:54:13 UTC   getblocks stopping at 6764 0000000354118d287a3d (477462 bytes)
2014-06-11 19:54:13 UTC getblocks 5863 to 00000008797034a709b7 limit 1021
2014-06-11 19:54:16 UTC   getblocks stopping at 6770 00000008797034a709b7 (481037 bytes)
2014-06-11 19:54:16 UTC getblocks 5863 to 0000000056ee7692aa30 limit 1021
2014-06-11 19:54:19 UTC   getblocks stopping at 6774 0000000056ee7692aa30 (482650 bytes)

and as I said, it get out of sync after a few minutes. Result was 6 orphans in a row...

[TheRealSteve]

It couldn't hurt right! Lol. I've got a fully synced green check mark with incoming / outgoing transactions working as intended! Hopefully it does the same for you!

True - can't get worse than not syncing   It got stuck on 9,000-something, but eventually made it to 12,146.  Unfortunately, it should be at 12,604 - so, we'll see if it catches up

[sp00lin9]

It couldn't hurt right! Lol. I've got a fully synced green check mark with incoming / outgoing transactions working as intended! Hopefully it does the same for you!

True - can't get worse than not syncing   It got stuck on 9,000-something, but eventually made it to 12,146.  Unfortunately, it should be at 12,604 - so, we'll see if it catches up

Currently, my wallet shows fully synced at block 12614, last block generated 38 sec ago, your almost there! lol

[TheRealSteve]

Currently, my wallet shows fully synced at block 12614, last block generated 38 sec ago, your almost there! lol

The Little Wallet That Could?

[rfcdejong]

How much are you people burning?
This is mine currently..

"Net Burnt Coins" : 314.77400400,
"Effective Burnt Coins" : 312.86937900,
"Immature Burnt Coins" : 0.00000000,
"Decayed Burnt Coins" : 1.90462500

burnt only 12 coins more now..

"Net Burnt Coins" : 326.04721200,
"Effective Burnt Coins" : 323.92589700,
"Immature Burnt Coins" : 0.00000000,
"Decayed Burnt Coins" : 2.12131500

and burnt another 17... still not finding PoB blocks

"Net Burnt Coins" : 342.94665600,
"Effective Burnt Coins" : 340.44341300,
"Immature Burnt Coins" : 0.00000000,
"Decayed Burnt Coins" : 2.50324300

Receiving lots of coins today from slimcoinpool

Burned like 80 more coins, this speed i will get my target in a few days!

"Net Burnt Coins" : 418.47106900,
"Effective Burnt Coins" : 415.41875400,
"Immature Burnt Coins" : 0.00000000,
"Decayed Burnt Coins" : 3.05231500

total 100 / 85094.996982 * 418.47106900 = 0.49% of the network speed, i'm halfway!

[sp00lin9]

Currently, my wallet shows fully synced at block 12614, last block generated 38 sec ago, your almost there! lol

The Little Wallet That Could?

LOL CHOOOO CHOOOOO!

[jadefalke]

no sign of life from DEV? i pm'ed him 2 Debug.log to fix that wallet Problem i still cannot sync. that sucks.

[sp00lin9]

no sign of life from DEV? i pm'ed him 2 Debug.log to fix that wallet Problem i still cannot sync. that sucks.

Hes here! I sent a few debugs also, i think we buried him in debugs so hes working hard to fix the wallet! [:

[TheRealSteve]

LOL CHOOOO CHOOOOO!

Choo choo is almost there... 12,600 now - a pool is reporting 12,640, so only 40 short.  Pool's also reporting 10 minutes since last block, though.  Oh well, I got the part I need..

[sp00lin9]

LOL CHOOOO CHOOOOO!

Choo choo is almost there... 12,600 now - a pool is reporting 12,640, so only 40 short.  Pool's also reporting 10 minutes since last block, though.  Oh well, I got the part I need..

Nice!