Pages:
Author

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

full member
Activity: 182
Merit: 100
i'm still stuck @ 15157. i deleted everything, and just took the notes from the OP, and the correction which has been made later. do I just need to wait longer? does this have to worry me:

Code:
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake ec226cdb4ad2e2e1f0a2b515e6d47ed1fcdcdba4ec44866adf34df0996ac4754

I had that problem when I was testing, just delete the addr.dat, blkindex.dat, blk0001.dat and take 1 of the nodes on the OP and make it connect=
legendary
Activity: 1092
Merit: 1000
I cant even get my nodes to accept connections.
legendary
Activity: 914
Merit: 1001
i'm still stuck @ 15157. i deleted everything, and just took the notes from the OP, and the correction which has been made later. do I just need to wait longer? does this have to worry me:

Code:
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake ec226cdb4ad2e2e1f0a2b515e6d47ed1fcdcdba4ec44866adf34df0996ac4754
member
Activity: 111
Merit: 10
anyway this is fucked up, all 3 wallets are on another block

15952
15953
15972 which jumped back to 15962 and slimcoinpool payments are gone...
Yeah, this happened to me also
hero member
Activity: 798
Merit: 500
anyway this is fucked up, all 3 wallets are on another block

15952
15953
15972 which jumped back to 15962 and slimcoinpool payments are gone...
hero member
Activity: 798
Merit: 500
freaking hell...

slimcoinpool is paying me
member
Activity: 111
Merit: 10
Quote
wait a minute wtf, i was on block 15960, then all of a sudden i'm on block 15953

You were probably on a wrong fork and the syncronized checkpoint reorganized your block chain.
OH ok, that make sense, thanks
legendary
Activity: 1092
Merit: 1000
For anyone unable to sync up to 159xx use :

addnode=144.76.139.103:50000
addnode=144.76.139.104:50000
addnode=144.76.139.105:50000
addnode=144.76.139.106:50000
addnode=144.76.139.107:50000
addnode=144.76.139.108:50000
addnode=144.76.139.109:50000
addnode=144.76.139.110:50000
addnode=144.76.139.111:50000


Connection refused

Yes because they are not fully synced hmmmmmmmm
full member
Activity: 182
Merit: 100
Quote
wait a minute wtf, i was on block 15960, then all of a sudden i'm on block 15953

You were probably on a wrong fork and the syncronized checkpoint reorganized your block chain.
hero member
Activity: 616
Merit: 500
For anyone unable to sync up to 159xx use :

addnode=144.76.139.103:50000
addnode=144.76.139.104:50000
addnode=144.76.139.105:50000
addnode=144.76.139.106:50000
addnode=144.76.139.107:50000
addnode=144.76.139.108:50000
addnode=144.76.139.109:50000
addnode=144.76.139.110:50000
addnode=144.76.139.111:50000


Connection refused
hero member
Activity: 798
Merit: 500
member
Activity: 111
Merit: 10
wait a minute wtf, i was on block 15960, then all of a sudden i'm on block 15953

22:20:53

{
"blocks" : 15960,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00024602,
"errors" : "",
"generate" : false,
"genproclimit" : 7,
"hashespersec" : 0,
"networkghps" : 0.00000010,
"pooledtx" : 0,
"testnet" : false
}


22:21:17

getmininginfo


22:21:17

{
"blocks" : 15953,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00024414,
"errors" : "",
"generate" : false,
"genproclimit" : 7,
"hashespersec" : 0,
"networkghps" : 0.00000009,
"pooledtx" : 1,
"testnet" : false
}
hero member
Activity: 756
Merit: 500
stuck on 15157 too

If you are stuck on that block, it means you are not syncing from the correct nodes.

Well, how about some nodes we can actually connect to?
full member
Activity: 182
Merit: 100
stuck on 15157 too

If you are stuck on that block, it means you are not syncing from the correct nodes.
hero member
Activity: 798
Merit: 500
what is the last block ?? is this correct??


04:14:36
getblockhash 15957


04:16:26
35f591edaf2e544f817fb3424b0f40e93bc5dd12d94dd9816d71f87b1aafabff


i guess not, i replaced it with my blockchain which i zipped and they are back at block 15953 which i just found

04:20:14
getblockhash 15953

04:20:14
000009e69334c9554d7a0097ac1e580790c61a9048002ddede5454e3990b411f
legendary
Activity: 1092
Merit: 1000
stuck on 15157 too

Well there is a fork again after the block we relaunched from... I can sync others up to 15921
full member
Activity: 126
Merit: 100
legendary
Activity: 1092
Merit: 1000
For anyone unable to sync up to 159xx use :

addnode=144.76.139.103:50000
addnode=144.76.139.104:50000
addnode=144.76.139.105:50000
addnode=144.76.139.106:50000
addnode=144.76.139.107:50000
addnode=144.76.139.108:50000
addnode=144.76.139.109:50000
addnode=144.76.139.110:50000
addnode=144.76.139.111:50000
hero member
Activity: 798
Merit: 500
what is the last block ?? is this correct??


04:14:36
getblockhash 15957


04:16:26
35f591edaf2e544f817fb3424b0f40e93bc5dd12d94dd9816d71f87b1aafabff
legendary
Activity: 1092
Merit: 1000
Is this the right fork ?

getblockhash 15951
000009037a7ab7f9c2986eb060da09bdbccb7965fb098d1eb87d4226c4563359

Yes, that is correct.

Ok, i need 3 more blocks and then i'm starting up nodes.
Pages:
Jump to: