Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 105. (Read 284956 times)
June 14, 2014, 03:51:46 PM
Wallet is beyond shit. It just does not work.
June 14, 2014, 03:49:14 PM
addnode=63.141.232.170 - fully synced pool node.
does pool work now?
June 14, 2014, 03:47:00 PM
ERROR: bool CTxDB::LoadBlockIndex() : deserialize error on PoB index 15043
my database has crashed on 10 out of 20 nodes......
my database has crashed on 10 out of 20 nodes......
June 14, 2014, 03:42:12 PM
sandor, remove connect= from your config file, let the network size determine now which block we are on
Already did, also added all your nodes.
June 14, 2014, 03:42:03 PM
my blkindex.dat is corrupt AGAIN
LoadBlockIndex(): synchronized checkpoint 000001a14894369ce0055816fdb04142f711d51558f4863a9fb371e7c350d4c2
ERROR: HashBurnData() : Burn transaction does not meet minimum number of confirmations 0 < 6
ERROR: CheckProofOfBurnHash() : hash doesn't match nBurnBits
ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff > 000000024d200000000000000000000000000000000000000000000000000000
ERROR: bool CTxDB::LoadBlockIndex() : deserialize error on PoB index 15043
LoadBlockIndex(): synchronized checkpoint 000001a14894369ce0055816fdb04142f711d51558f4863a9fb371e7c350d4c2
ERROR: HashBurnData() : Burn transaction does not meet minimum number of confirmations 0 < 6
ERROR: CheckProofOfBurnHash() : hash doesn't match nBurnBits
ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff > 000000024d200000000000000000000000000000000000000000000000000000
ERROR: bool CTxDB::LoadBlockIndex() : deserialize error on PoB index 15043
June 14, 2014, 03:41:33 PM
sandor, remove connect= from your config file, let the network size determine now which block we are on
June 14, 2014, 03:40:44 PM
Here's couple of my nodes:
addnode=63.141.232.170
addnode=162.220.242.52
addnode=92.222.27.45
addnode=77.237.251.163
addnode=63.141.232.170
addnode=162.220.242.52
addnode=92.222.27.45
addnode=77.237.251.163
Sandor111 something's wrong with your pool. It found block 15045 then now going back to find block 15014.
June 14, 2014, 03:38:12 PM
Here's couple of my nodes:
addnode=63.141.232.170
addnode=162.220.242.52
addnode=92.222.27.45
addnode=77.237.251.163
addnode=63.141.232.170
addnode=162.220.242.52
addnode=92.222.27.45
addnode=77.237.251.163
June 14, 2014, 03:32:23 PM
slimcoinpool is at block 15032 already. Anyone able to sync that far ?
My nodes seem to have synced.
June 14, 2014, 03:30:25 PM
slimcoinpool is at block 15032 already. Anyone able to sync that far ?
June 14, 2014, 03:26:17 PM
More nodes! Seems to work now, network is stable.
addnode=144.76.139.178:10000
addnode=144.76.139.103:10000
addnode=144.76.139.104:10000
addnode=144.76.139.105:10000
addnode=144.76.139.106:10000
addnode=144.76.139.107:10000
addnode=144.76.139.108:10000
addnode=144.76.139.109:10000
addnode=144.76.139.110:10000
addnode=144.76.139.111:10000
and 10 more
addnode=144.76.238.233:10000
addnode=144.76.238.235:10000
addnode=144.76.238.236:10000
addnode=144.76.238.237:10000
addnode=144.76.238.239:10000
addnode=144.76.238.242:10000
addnode=144.76.238.243:10000
addnode=144.76.238.244:10000
addnode=144.76.238.245:10000
addnode=144.76.238.195:10000
addnode=144.76.139.178:10000
addnode=144.76.139.103:10000
addnode=144.76.139.104:10000
addnode=144.76.139.105:10000
addnode=144.76.139.106:10000
addnode=144.76.139.107:10000
addnode=144.76.139.108:10000
addnode=144.76.139.109:10000
addnode=144.76.139.110:10000
addnode=144.76.139.111:10000
and 10 more
addnode=144.76.238.233:10000
addnode=144.76.238.235:10000
addnode=144.76.238.236:10000
addnode=144.76.238.237:10000
addnode=144.76.238.239:10000
addnode=144.76.238.242:10000
addnode=144.76.238.243:10000
addnode=144.76.238.244:10000
addnode=144.76.238.245:10000
addnode=144.76.238.195:10000
June 14, 2014, 03:20:24 PM
Ok, this is probably NOT going to work. The wallet is still broken and starts to de-sync after some time. I've already got many de-synced nodes...
June 14, 2014, 03:14:40 PM
wtf, all blocks regrouped at "blocks" : 15008 as if hardcoded checkpoint killed all other blocks ?
Same... WTF is happening?
Ok, there were more people at 15008 than at our fork so it regrouped. should be ok now
use addnode instead of connect if you are fully synced
June 14, 2014, 03:09:49 PM
wtf, all blocks regrouped at "blocks" : 15008 as if hardcoded checkpoint killed all other blocks ?
Same... WTF is happening?
June 14, 2014, 03:07:06 PM
wtf, all blocks regrouped at "blocks" : 15008 as if hardcoded checkpoint killed all other blocks ?
June 14, 2014, 03:05:46 PM
Ok, the wallet is so fucked we cant use more than one main node so use :
144.76.139.111:10001
144.76.139.111:10001
June 14, 2014, 03:03:53 PM
ok, once you are fully synced you can replace connect with addnode, you should then receive peer list from me and sandor111
We are moving fast now, "blocks" : 15035
Yes and the other node is not catching up.. Did you run the pool ?
June 14, 2014, 03:03:22 PM
ok, once you are fully synced you can replace connect with addnode, you should then receive peer list from me and sandor111
We are moving fast now, "blocks" : 15035
June 14, 2014, 02:52:31 PM
One more note, if you can not sync with any of my nodes you must delete the blk* files and try again.
Current block : "blocks" : 15028
If you are fully synced post your nodes here people so others can connect to you, i cant handle ALL connections!!
Current block : "blocks" : 15028
If you are fully synced post your nodes here people so others can connect to you, i cant handle ALL connections!!
June 14, 2014, 02:50:34 PM
ok, once you are fully synced you can replace connect with addnode, you should then receive peer list from me and sandor111
Jump to: