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

It is possible we are all on a fork and only a couple of devs nodes are on the right chain... Do not enable pool just yet, wait for the blocks to start coming in at a 90 sec interval

All who is synced on block 14978, please post your node IPs so we know which ones to add.

I'm also on 14978
My node is : 84.228.247.33

same, the wallets which don't open show this error in the end loading blkindex.dat error

EnvShutdown exception: DbEnv::close: Invalid argument (22)

Pool syncing in progress :
accepted connection 63.141.232.170:27438
Added time data, samples 21, offset +0 (+0 minutes)
nTimeOffset = +0  (+0 minutes)
version message: version 60003, blocks=0
getblocks 1 to 00000000000000000000 limit 500
  getblocks stopping at limit 500 0000002a085c6068b74c (177839 bytes)
received getdata for: block 000006e022fc5e432e55        nHeight: 1
received getdata for: block 000004e9a182e21d4524        nHeight: 2
received getdata for: block 000000a481e0ae6ae1bf        nHeight: 3
received getdata for: block 00000099c838cf2ca9d1        nHeight: 4
received getdata for: block 000002dabf45967e733f        nHeight: 5

Mine is still stuck at nHeight: 14978

diff will go down because of an invalid hash in the blockchain, something or someone did but that invalid hash in there. The wallet needs to be modified to skip that hash and continue..

The fundamental problem is the node disorder
Why developers do not provide a valid node?

Sure it is fuckin scammer
Dont run - most likely a virus

Same here, lets see if it gets to 14979...

my working wallet just noticed a new block found 14978


14:14:06

{
"blocks" : 14978,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.01457942,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 3344,
"networkghps" : 0.00013823,
"pooledtx" : 6,
"testnet" : false
}



14:15:00

getblock 0000000b79a33940505115d65e00b6833b25e26ee5f279f5d6d236ccf71cf522


14:15:00

{
"hash" : "0000000b79a33940505115d65e00b6833b25e26ee5f279f5d6d236ccf71cf522",
"size" : 6743,
"height" : 14978,
"version" : 1,
"merkleroot" : "aa0734a0a03f187b1bdf9cddbf685494f736a2d78268c6eacd7b03cb3a9efbd4",
"time" : "2014-06-14 12:08:39 UTC",
"nonce" : 198857,
"bits" : "1d4496bb",
"difficulty" : 0.01457942,
"mint" : 17.98000000,
"previousblockhash" : "000000071e08b8cf2bc49cf07119dce119761565f0a6f5ec74e01680ae8ab228",
"flags" : "proof-of-work",
"proofhash" : "0000000b79a33940505115d65e00b6833b25e26ee5f279f5d6d236ccf71cf522",
"entropybit" : 1,
"modifier" : "bb99d634c3c170c4",
"modifierchecksum" : "537d3420",
"tx" : [
"96281053fc46757dfc1ff67e7497e4bf6f7d5d3d4b98489fe15bc94f89dce27d",
"47caa420d6182c7f84b71e642979279ef4346ea115560c84b3e1cd6a9105be65",
"fb706121049f9e8b7df4c63cb99abf936b28880f0b2518ad81df46e55b0a4a2e",
"1c493354bad080b3597ae09f2d5d96f29412386705e8fd67a8a7501367b2f438",
"cf96b3d61af5a5f5146c7e3cc98e146360c24ac2b80ca75104fe23cb2509866e"
]
}

http://imgur.com/0RiiRAE

6 days ago changed, 10 hours ago pull request merged..

https://github.com/slimcoin/slimcoin/commit/145ccd9b49c8c6cb0f1ff95fb7813dcbdd261f78

OMG, seems like the moron did not push the update to github!

https://github.com/slimcoin/slimcoin

look at the date of the last commit
John Smith authored 6 days ago

EDIT: he did update the executables, but not the source code.
EDIT2: Good luck running his linux static build.........

Yes stuck on block 14977

And do NOT close your wallet: blkindex.dat cannot be loaded!
I have it on two wallet now, other wallet is stuck on block 14977


LoadBlockIndex(): hashBestChain=000000071e08b8cf2bc4  height=14977  trust=14978
LoadBlockIndex(): synchronized checkpoint 000000045d8fdec420c1ed9a212ac7aa94e400cc5e91d0b68f6efe6cd9e44716
ERROR: HashBurnData() : Burn transaction does not meet minimum number of confirmations 0 < 6
ERROR: CheckProofOfBurnHash() : hash doesn't match nBurnBits
   ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff > 000000024eca0000000000000000000000000000000000000000000000000000
ERROR: bool CTxDB::LoadBlockIndex() : deserialize error on PoB index 14987
 block index           42886ms
Loading wallet...
nFileVersion = 60300
Error loading blkindex.dat
 wallet                  296ms
Done loading
mapBlockIndex.size() = 15326
nBestHeight = 14977
setKeyPool.size() = 103
mapWallet.size() = 15
mapAddressBook.size() = 2
EnvShutdown exception: DbEnv::close: Invalid argument (22)

From the OP:

 We are investingating issues in the backend. Your shares and hashrate are safe and we will fix things ASAP.

Findblocks disabled, new blocks will currently not show up in the frontend

Nope, it is broken. Still stuck at 14977.

I dont get it, the guy releases a new wallet but does not try to sync with the nodes list on first page ? What a fu..... moron. I would not let him sweep the floor at my company let alone develop a digital currency.
Guy is a total moron guys, there is no way this coin takes off with the developer this stupid. If not stupid - he just does not give a fuck.

The other pool (slm.blockquarry.com) has also been stuck at block 14977 for a while.
Is taking them 60x longer than usual to find a block, something is definitely broken.

   {  
        "account" : "",
        "category" : "immature",
        "amount" : 17.71000000,
        "confirmations" : 1,
        "blockhash" : "000000071e08b8cf2bc49cf07119dce119761565f0a6f5ec74e01680ae8ab228",
        "blockindex" : 0,
        "txid" : "876ac791174a2d9fc50ef10acae939ba73c24eacff2ba70ea8e400f53670a3fe",
        "time" : 1402744022
    }


OK, give me 30 minutes of instamine time and i'll be sending instructions how to sync up
EDIT : hopefully this message pisses of dev and he releases a proper fucking wallet fix

EDIT2: Its stuck at blocks=14977............ Not sure if due to a suddent drop in difficulty or if its just broken... Lets give it 10 more min...

It appears to be.