slimcoin dev, i see you are online, i hope you has experience enough to figure out what to do? People also offered help! I do not mind if anyone helps and actually would appreciate it very much! Also, posting how much this wallet "sucks" will not get it fixed faster. The reason for this inability to sync is because the block chain before was very forked and it will take time to consolidate into 1 chain. Not true. I've had the exact same blockchain db copied over to 20 servers, all connected to one master node with the same copy via connect= flag. Guess what, after 10-15 blocks they stopped syncing. |
|
|
|
slimcoin dev, i see you are online, i hope you has experience enough to figure out what to do? People also offered help!
He has been online all day today, messaging people with his nodes, which of course did not work just as mine did not. |
|
|
|
Whats the url of the slimcoin clone, are they experiencing the same issues ? EDIT: Oh, SLM has been officially removed from BTER. EDIT2: nope, still there !!  |
|
|
|
|
I think the wallet is broken in many ways - the biggest issue by far is the p2p functionality. The nodes with empty wallets would just stop syncing from time to time. Some also got kicked/banned for providing 'low proof of work'. Even when connected they would just hang there for hours, not exchanging any data with other nodes.
Whats interesting is that it worked more or less for the first 10 minutes after we rebuilt the database from block 15013 but as soon as miners joined in it stopped syncing. Retard dev did not stress test long enough..
Anyway, I really think its beyond repair. Even if a new wallet is released there is no way all bugs will be addressed.
|
|
|
|
Wallet is beyond shit. It just does not work.
Yep, mine crashed also. Had to delete the blk* files again. Me too. Its over. game over for this shit coin. |
|
|
|
|
Wallet is beyond shit. It just does not work.
|
|
|
|
|
ERROR: bool CTxDB::LoadBlockIndex() : deserialize error on PoB index 15043
my database has crashed on 10 out of 20 nodes......
|
|
|
|
|
sandor, remove connect= from your config file, let the network size determine now which block we are on
|
|
|
|
slimcoinpool is at block 15032 already. Anyone able to sync that far ?
My nodes seem to have synced. |
|
|
|
|
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
|
|
|
|
|
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...
|
|
|
|
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 |
|
|
|
|
wtf, all blocks regrouped at "blocks" : 15008 as if hardcoded checkpoint killed all other blocks ?
|
|
|
|
|
Ok, the wallet is so fucked we cant use more than one main node so use :
144.76.139.111:10001
|
|
|
|
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 ? |
|
|
|
|
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!!
|
|
|
|
|
ok, once you are fully synced you can replace connect with addnode, you should then receive peer list from me and sandor111
|
|
|
|
|
is there a command similar to getpeerinfo ? I need a list of fully synced nodes connected to me so i can paste them here
|
|
|
|
addnode=63.141.232.170 - fully synced pool node.
Just make sure you delete addr.dat so you dont sent the bad nodes to incoming connections I have only your nodes in addr.dat.  Welcome to Primer-'s centralized network haha. Ok let me think how to spread the connections between the good nodes. |
|
|
|
addnode=63.141.232.170 - fully synced pool node.
Just make sure you delete addr.dat so you dont sent the bad nodes to incoming connections |
|
|
|
|
Show Posts
