aatom
Newbie
Offline
Activity: 14
Merit: 0
|
|
June 14, 2014, 09:19:54 AM |
|
what's the right addnode???
I can't syncing again,it's stopping at 10583 now.
|
|
|
|
|
|
|
|
|
Even if you use Bitcoin through Tor, the way transactions are handled by the network makes anonymity difficult to achieve. Do not expect your transactions to be anonymous unless you really know what you're doing.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
sandor111
|
|
June 14, 2014, 09:27:52 AM |
|
We're stuck at 10574, no movement at all... Guys please add banscore=9999 to your slimcoin.conf, this will increase syncing speed.
|
|
|
|
sandor111
|
|
June 14, 2014, 09:34:45 AM |
|
The problem is that nodes are banning other nodes for unintentionally submitting invalid block data.
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
June 14, 2014, 10:21:20 AM |
|
We're stuck at 10574, no movement at all... Guys please add banscore=9999 to your slimcoin.conf, this will increase syncing speed.
I can confirm this, it was my suggestion earlier anyway
|
|
|
|
sandor111
|
|
June 14, 2014, 10:43:25 AM |
|
We're stuck at 10574, no movement at all... Guys please add banscore=9999 to your slimcoin.conf, this will increase syncing speed.
I can confirm this, it was my suggestion earlier anyway Still stuck... looks like the pool will be down until the dev fixes the wallet.
|
|
|
|
Stormbringer
|
|
June 14, 2014, 10:44:21 AM |
|
The following addnodes have been restarted with the latest release of Slimcoin and are currently syncing with the network: addnode=107.181.250.216 addnode=107.181.250.217 addnode=144.76.142.47 addnode=144.76.142.49
I'll update this post again when they are fully up and running. Should I delete old nodes before adding this nodes?
|
BTC:14aefvedNKjJJoHZ8Pv5LqXqjj5Nprd89d
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
June 14, 2014, 10:47:15 AM |
|
We're stuck at 10574, no movement at all... Guys please add banscore=9999 to your slimcoin.conf, this will increase syncing speed.
I can confirm this, it was my suggestion earlier anyway Still stuck... looks like the pool will be down until the dev fixes the wallet. Wait, i think i can help, one of my nodes on the old wallet is up to date. I'll provide an IP soon, just make sure you add maxconnections=1 and connect=MYIP to .conf when syncing. Once its fully synced you can remove the entries. I'll send you PM, dont want others to fu.. up my node, pool node is more important.
|
|
|
|
sandor111
|
|
June 14, 2014, 10:49:58 AM |
|
We're stuck at 10574, no movement at all... Guys please add banscore=9999 to your slimcoin.conf, this will increase syncing speed.
I can confirm this, it was my suggestion earlier anyway Still stuck... looks like the pool will be down until the dev fixes the wallet. Wait, i think i can help, one of my nodes on the old wallet is up to date. I'll provide an IP soon, just make sure you add maxconnections=1 and connect=MYIP to .conf when syncing. Once its fully synced you can remove the entries. I'll send you PM, dont want others to fu.. up my node, pool node is more important. Thanks, waiting for your PM.
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
June 14, 2014, 10:59:08 AM |
|
We're stuck at 10574, no movement at all... Guys please add banscore=9999 to your slimcoin.conf, this will increase syncing speed.
I can confirm this, it was my suggestion earlier anyway Still stuck... looks like the pool will be down until the dev fixes the wallet. Wait, i think i can help, one of my nodes on the old wallet is up to date. I'll provide an IP soon, just make sure you add maxconnections=1 and connect=MYIP to .conf when syncing. Once its fully synced you can remove the entries. I'll send you PM, dont want others to fu.. up my node, pool node is more important. Thanks, waiting for your PM. [root@CentOS-64-64-minimal .slimcoin]# slimcoind getmininginfo { "blocks" : 14976, Is this the current block ?
|
|
|
|
sandor111
|
|
June 14, 2014, 11:00:19 AM |
|
We're stuck at 10574, no movement at all... Guys please add banscore=9999 to your slimcoin.conf, this will increase syncing speed.
I can confirm this, it was my suggestion earlier anyway Still stuck... looks like the pool will be down until the dev fixes the wallet. Wait, i think i can help, one of my nodes on the old wallet is up to date. I'll provide an IP soon, just make sure you add maxconnections=1 and connect=MYIP to .conf when syncing. Once its fully synced you can remove the entries. I'll send you PM, dont want others to fu.. up my node, pool node is more important. Thanks, waiting for your PM. [root@CentOS-64-64-minimal .slimcoin]# slimcoind getmininginfo { "blocks" : 14976, Is this the current block ? It appears to be.
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
June 14, 2014, 11:08:28 AM Last edit: June 14, 2014, 11:22:30 AM by primer- |
|
We're stuck at 10574, no movement at all... Guys please add banscore=9999 to your slimcoin.conf, this will increase syncing speed.
I can confirm this, it was my suggestion earlier anyway Still stuck... looks like the pool will be down until the dev fixes the wallet. Wait, i think i can help, one of my nodes on the old wallet is up to date. I'll provide an IP soon, just make sure you add maxconnections=1 and connect=MYIP to .conf when syncing. Once its fully synced you can remove the entries. I'll send you PM, dont want others to fu.. up my node, pool node is more important. Thanks, waiting for your PM. [root@CentOS-64-64-minimal .slimcoin]# slimcoind getmininginfo { "blocks" : 14976, Is this the current block ? It appears to be. { "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...
|
|
|
|
sandor111
|
|
June 14, 2014, 11:24:55 AM Last edit: June 14, 2014, 11:46:49 AM by sandor111 |
|
We're stuck at 10574, no movement at all... Guys please add banscore=9999 to your slimcoin.conf, this will increase syncing speed.
I can confirm this, it was my suggestion earlier anyway Still stuck... looks like the pool will be down until the dev fixes the wallet. Wait, i think i can help, one of my nodes on the old wallet is up to date. I'll provide an IP soon, just make sure you add maxconnections=1 and connect=MYIP to .conf when syncing. Once its fully synced you can remove the entries. I'll send you PM, dont want others to fu.. up my node, pool node is more important. Thanks, waiting for your PM. [root@CentOS-64-64-minimal .slimcoin]# slimcoind getmininginfo { "blocks" : 14976, Is this the current block ? It appears to be. { "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... 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. Est. Avg. Time per Round (Network) 6 minutes 1 second Est. Avg. Time per Round (Pool) 1 minute 37 seconds Est. Shares this Round 32,552 (done: 6007.02%) Next Network Block 14,978 (Current: 14,977)
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
June 14, 2014, 11:51:01 AM |
|
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.
|
|
|
|
AizenSou
|
|
June 14, 2014, 11:52:43 AM |
|
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. Est. Avg. Time per Round (Network) 6 minutes 1 second Est. Avg. Time per Round (Pool) 1 minute 37 seconds Est. Shares this Round 32,552 (done: 6007.02%) Next Network Block 14,978 (Current: 14,977) 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
|
|
|
|
rfcdejong
|
|
June 14, 2014, 11:59:36 AM |
|
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)
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
June 14, 2014, 12:01:25 PM |
|
OMG, seems like the moron did not push the update to github! https://github.com/slimcoin/slimcoinlook 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.........
|
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
June 14, 2014, 12:13:52 PM |
|
|
|
|
|
rfcdejong
|
|
June 14, 2014, 12:14:21 PM |
|
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" ] }
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
June 14, 2014, 12:20:03 PM |
|
Same here, lets see if it gets to 14979...
|
|
|
|
|