[ANN][LIM]LimeCoin X11 Algo | OBSOLETE move to LimecoinX please - page 14.

stevegreer

legendary

Activity: 1148

Merit: 1001

Official Zeitcoin community ambassador

Quote from: A-tM on May 10, 2014, 04:52:16 PM

No, you don't get it yet.
The principal fact is, that the minging algorithm was designed for to mine WHOLE HALF of the coins in half an hour.
It is unfair - early privileged miner or miners (the only informed), were getting coins with uncomparable easyness in comparison to hard working miners later.
This is scam.

Look at bitcoin halving algorithm - it is completely different and it is unbiased. Everybody gets coins proportional to his work.
Halving periods are much longer, and are designed to counteract increasing hashing power, for nothing else, to retain fairness even more.

And regarding "huge chunks". Do you think that just few people do own HALF of the all bitcoins, that will ever be mined?

No, I understand the point you are making. I think it sucks that so many were mined so quickly too. And believe me, I don't own enough of them to really have made a dent in the total supply anyway. But it's too late to worry about that now. And I am a glass half full kind of guy, so I'm not too quick to say that the dev purposely designed the coin to be instamined. Maybe he did, maybe he didn't, but I have no concrete evidence of it. If I end up getting burned if the coin gets dumped and the value comes crashing down, then too bad for me. It won't be the first time I lost money on a coin. It's a gamble with any coin.

Good point about Bitcoin too. I was only using that scenario as an example. My point was that Bitcoin is not immune from manipulation by the large holders either. All coins can be manipulated. But you are right, Bitcoin is a much more fair and balanced coin. That's why it's the king!

Eastwind

hero member

Activity: 896

Merit: 1000

Quote from: stevegreer on May 10, 2014, 04:34:20 PM

And there are a few people who hold a huge chunk of the Bitcoins. Does that make it a scam too? So a few people with big hash power were quick to mine a chunk of them. So what? More power to them. And if it is a bubble waiting to pop then what is wrong with other people taking advantage of it while they can? The same could be said for Blackcoin, Darkcoin, Bitcoin Plus, etc., etc., etc. Those are all coins with a few people holding huge amounts and doing everything they can to manipulate the prices in order to make big profits. That is the name of the game, isn't it? No different than the stock market.

And thanks for the reply A-tM. I wasn't getting any real response from gmcm.

In present times, if the developer wants the coin to be successful and distributed fairly among miners, then he should make sure the distribution is according to the plan. If the block time is 1 min, then it should take 10000 min to issue 10000 blocks. He can adjust the difficulty level to achieve that.

If the coin is not issued according to the specification, ie, instamine, then it is a scam. I will avoid those coins. It is as simple as that.

A-tM

member

Activity: 90

Merit: 10

Quote from: stevegreer on May 10, 2014, 04:34:20 PM

And there are a few people who hold a huge chunk of the Bitcoins. Does that make it a scam too? So a few people with big hash power were quick to mine a chunk of them. So what? More power to them.

No, you don't get it yet.
The principal fact is, that the minging algorithm was designed for to mine WHOLE HALF of the coins in half an hour.
It is unfair - early privileged miner or miners (the only informed), were getting coins with uncomparable easyness in comparison to hard working miners later.
This is scam.

Look at bitcoin halving algorithm - it is completely different and it is unbiased. Everybody gets coins proportional to his work.
Halving periods are much longer, and are designed to counteract increasing hashing power, for nothing else, to retain fairness even more.

And regarding "huge chunks". Do you think that just few people do own HALF of the all bitcoins, that will ever be mined?

stevegreer

legendary

Activity: 1148

Merit: 1001

Official Zeitcoin community ambassador

And there are a few people who hold a huge chunk of the Bitcoins. Does that make it a scam too? So a few people with big hash power were quick to mine a chunk of them. So what? More power to them. And if it is a bubble waiting to pop then what is wrong with other people taking advantage of it while they can? The same could be said for Blackcoin, Darkcoin, Bitcoin Plus, etc., etc., etc. Those are all coins with a few people holding huge amounts and doing everything they can to manipulate the prices in order to make big profits. That is the name of the game, isn't it? No different than the stock market.

And thanks for the reply A-tM. I wasn't getting any real response from gmcm.

A-tM

member

Activity: 90

Merit: 10

Quote from: stevegreer on May 10, 2014, 03:03:46 PM

Why don't you tell me why you think it's a scam coin? Is it because someone else told you it is? Or do you have evidence?

It is simple. Investigate the blockchain. (link to investigation)

Quote

The first 1000 blocks, at 500 coins a pop, yields 500,000 LC. All in under 27 minutes. This is over half the total planned coins in under half an hour.

This means, these coins are in possession of just a few people, who can dump it whenever they want, they were gained too easily, and it is only a matter of time these holders want to take huge profit of it.
It is one big bubble, ready to blow.

Regards,
Andy

gmcm

member

Activity: 118

Merit: 10

Quote from: stevegreer on May 10, 2014, 03:03:46 PM

Why don't you tell me why you think it's a scam coin? Is it because someone else told you it is? Or do you have evidence?

Apparently, u like scam LC coin and u know where is evidence. You just don't want to admit it.

stevegreer

legendary

Activity: 1148

Merit: 1001

Official Zeitcoin community ambassador

Why don't you tell me why you think it's a scam coin? Is it because someone else told you it is? Or do you have evidence?

gmcm

member

Activity: 118

Merit: 10

Quote from: stevegreer on May 10, 2014, 02:52:07 PM

Enlighten me as to how exactly LC is a scam?

Why do you protect scam LC coin ?

stevegreer

legendary

Activity: 1148

Merit: 1001

Official Zeitcoin community ambassador

Enlighten me as to how exactly LC is a scam?

gmcm

member

Activity: 118

Merit: 10

Quote from: stevegreer on May 10, 2014, 02:25:41 PM

Quote from: gmcm on May 10, 2014, 02:37:52 AM

LIM was a first to come on market. LC is a scam copy.

Nah, the real difference is LIM = 385 sat and LC = 3010 satoshi (presently according to crypto-prices.com)

Prices are subject to change especially considering LC is scam.

stevegreer

legendary

Activity: 1148

Merit: 1001

Official Zeitcoin community ambassador

Quote from: gmcm on May 10, 2014, 02:37:52 AM

LIM was a first to come on market. LC is a scam copy.

Nah, the real difference is LIM = 385 sat and LC = 3010 satoshi (presently according to crypto-prices.com)

A-tM

member

Activity: 90

Merit: 10

Quote from: IParn on May 10, 2014, 08:39:07 AM

news:

the updates are focused not in new code features (like difficulty, security or anonimity) but in what can you do with the coin (services). i shouldnt be telling you this but believe me, some users have seen what we are doing, and we are doing good things on limecoin.

atm : glad to hear your wallet synced.

regards!

Ok, thank you. I am looking forward to these new things.
Have a nice day.

Andy

IParn

full member

Activity: 406

Merit: 101

news:

the updates are focused not in new code features (like difficulty, security or anonimity) but in what can you do with the coin (services). i shouldnt be telling you this but believe me, some users have seen what we are doing, and we are doing good things on limecoin.

atm : glad to hear your wallet synced.

regards!

A-tM

member

Activity: 90

Merit: 10

If I close the wallet and start it again, it again shows "up to date, processed 5093 blocks of transaction history".
Funny. Now, after about half an hour of this behaviour, and a few restarts, the wallet finally synced.

IParn

full member

Activity: 406

Merit: 101

A-tM

member

Activity: 90

Merit: 10

Anyway, I am experiencing weird wallet behaviour.

Right after start of the program, the syncing will proceed completely, at least according to the wallet.
After few minutes, the wallet show out of sync.

Right now it shows:
"Processed 5093 of 470000 (estimated)... etc"

here is the tail of log:

Code:

2014-05-10 12:07:21 received block 0000000010c7e476903a8cbef118f196590696fb47dc0135eda3056744d28c34
2014-05-10 12:07:21 AddToWallet 7c6476cb55e7bd3732ac9c91a80f9583647165fb27514755ef6ad0466ab01d34  update
2014-05-10 12:07:21 NotifyTransactionChanged 7c6476cb55e7bd3732ac9c91a80f9583647165fb27514755ef6ad0466ab01d34 status=1
2014-05-10 12:07:21 updateWallet 7c6476cb55e7bd3732ac9c91a80f9583647165fb27514755ef6ad0466ab01d34 1
2014-05-10 12:07:21    inWallet=1 inModel=1 Index=11-12 showTransaction=1 derivedStatus=1
2014-05-10 12:07:21 Committing 1558 changed transactions to coin database...
2014-05-10 12:07:21 SetBestChain: new best=0000000010c7e476903a8cbef118f196590696fb47dc0135eda3056744d28c34  height=5093  log2_work=49.194336  tx=12717  date=2014-05-10 12:07:14 progress=0.039866
2014-05-10 12:07:21 ProcessBlock: ACCEPTED
2014-05-10 12:07:23 Flushing wallet.dat
2014-05-10 12:07:23 Flushed wallet.dat 3ms
2014-05-10 12:07:32 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:07:32 connected 69.28.94.67
2014-05-10 12:07:32 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:07:32 socket closed
2014-05-10 12:07:32 disconnecting node 69.28.94.67
2014-05-10 12:07:52 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:07:52 connected 69.28.94.67
2014-05-10 12:07:52 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:07:53 socket closed
2014-05-10 12:07:53 disconnecting node 69.28.94.67
2014-05-10 12:08:04 accepted connection 108.170.157.63:64879
2014-05-10 12:08:04 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=108.170.157.63:64879, peer=108.170.157.63:64879
2014-05-10 12:08:04 Added time data, samples 10, offset +31 (+0 minutes)
2014-05-10 12:08:04 receive version message: /Satoshi:0.9.1.2/: version 70002, blocks=4582, us=XXX.XXX.XXX.XXX:9030, them=108.170.157.63:9030, peer=108.170.157.63:64879
2014-05-10 12:08:13 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:08:13 connected 69.28.94.67
2014-05-10 12:08:13 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:08:13 socket closed
2014-05-10 12:08:13 disconnecting node 69.28.94.67
2014-05-10 12:08:34 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:08:34 connected 69.28.94.67
2014-05-10 12:08:34 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:08:34 socket closed
2014-05-10 12:08:34 disconnecting node 69.28.94.67
2014-05-10 12:08:54 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:08:54 connected 69.28.94.67
2014-05-10 12:08:54 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:08:55 socket closed
2014-05-10 12:08:55 disconnecting node 69.28.94.67
2014-05-10 12:08:55 accepted connection 162.243.24.177:46951
2014-05-10 12:08:55 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=162.243.24.177:46951, peer=162.243.24.177:46951
2014-05-10 12:08:55 Added time data, samples 11, offset +11 (+0 minutes)
2014-05-10 12:08:55 nTimeOffset = +11  (+0 minutes)
2014-05-10 12:08:55 receive version message: /litecoinseeder:0.01/: version 70002, blocks=470000, us=XXX.XXX.XXX.XXX:9030, them=0.0.0.0:0, peer=162.243.24.177:46951
2014-05-10 12:08:56 socket closed
2014-05-10 12:08:56 disconnecting node 162.243.24.177:46951
2014-05-10 12:09:15 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:09:15 connected 69.28.94.67
2014-05-10 12:09:15 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:09:15 socket closed
2014-05-10 12:09:15 disconnecting node 69.28.94.67
2014-05-10 12:09:36 getblocks 3550 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-05-10 12:09:36   getblocks stopping at limit 4049 00000000058eac53d04d71af7eb02cd3ef64d0fcc46291cff638cbe26010fd78
2014-05-10 12:09:36 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:09:36 connected 69.28.94.67
2014-05-10 12:09:36 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:09:36 socket closed
2014-05-10 12:09:36 disconnecting node 69.28.94.67
2014-05-10 12:09:36 received getdata (94 invsz)
2014-05-10 12:09:36 socket send error 10053
2014-05-10 12:09:36 disconnecting node 108.170.157.63:64879
2014-05-10 12:09:40 accepted connection 178.79.153.13:50294
2014-05-10 12:09:41 partner 178.79.153.13:50294 using obsolete version 60006; disconnecting
2014-05-10 12:09:41 ProcessMessage(version, 110 bytes) FAILED
2014-05-10 12:09:41 disconnecting node 178.79.153.13:50294
2014-05-10 12:09:52 accepted connection 176.31.186.58:46673
2014-05-10 12:09:52 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=176.31.186.58:46673, peer=176.31.186.58:46673
2014-05-10 12:09:52 Added time data, samples 12, offset +10 (+0 minutes)
2014-05-10 12:09:52 receive version message: /litecoinseeder:0.01/: version 70002, blocks=470000, us=XXX.XXX.XXX.XXX:9030, them=0.0.0.0:0, peer=176.31.186.58:46673
2014-05-10 12:09:53 socket closed
2014-05-10 12:09:53 disconnecting node 176.31.186.58:46673
2014-05-10 12:09:56 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:09:57 connected 69.28.94.67
2014-05-10 12:09:57 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:09:57 socket closed
2014-05-10 12:09:57 disconnecting node 69.28.94.67
2014-05-10 12:10:17 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:10:17 connected 69.28.94.67
2014-05-10 12:10:17 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:10:17 socket closed
2014-05-10 12:10:17 disconnecting node 69.28.94.67
2014-05-10 12:10:30 accepted connection 162.243.251.13:35481
2014-05-10 12:10:30 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=162.243.251.13:35481, peer=162.243.251.13:35481
2014-05-10 12:10:30 Added time data, samples 13, offset +11 (+0 minutes)
2014-05-10 12:10:30 nTimeOffset = +11  (+0 minutes)
2014-05-10 12:10:30 receive version message: /litecoinseeder:0.01/: version 70002, blocks=470000, us=XXX.XXX.XXX.XXX:9030, them=0.0.0.0:0, peer=162.243.251.13:35481
2014-05-10 12:10:31 socket closed
2014-05-10 12:10:31 disconnecting node 162.243.251.13:35481
2014-05-10 12:10:38 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:10:38 connected 69.28.94.67
2014-05-10 12:10:38 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:10:38 socket closed
2014-05-10 12:10:38 disconnecting node 69.28.94.67
2014-05-10 12:10:58 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:10:59 connected 69.28.94.67
2014-05-10 12:10:59 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:10:59 socket recv error 10054
2014-05-10 12:10:59 disconnecting node 69.28.94.67
2014-05-10 12:11:07 accepted connection 66.178.182.35:48086
2014-05-10 12:11:07 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=66.178.182.35:48086, peer=66.178.182.35:48086
2014-05-10 12:11:07 Added time data, samples 14, offset +10 (+0 minutes)
2014-05-10 12:11:07 receive version message: /litecoinseeder:0.01/: version 70002, blocks=470000, us=XXX.XXX.XXX.XXX:9030, them=0.0.0.0:0, peer=66.178.182.35:48086
2014-05-10 12:11:08 socket closed
2014-05-10 12:11:08 disconnecting node 66.178.182.35:48086
2014-05-10 12:11:16 Flushed 1 addresses to peers.dat  2ms
2014-05-10 12:11:19 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:11:19 connected 69.28.94.67
2014-05-10 12:11:19 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:11:19 socket closed
2014-05-10 12:11:19 disconnecting node 69.28.94.67
2014-05-10 12:11:22 accepted connection 93.142.128.113:57810
2014-05-10 12:11:23 partner 93.142.128.113:57810 using obsolete version 60011; disconnecting
2014-05-10 12:11:23 ProcessMessage(version, 102 bytes) FAILED
2014-05-10 12:11:23 disconnecting node 93.142.128.113:57810
2014-05-10 12:11:40 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:11:40 connected 69.28.94.67
2014-05-10 12:11:40 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:11:40 socket closed
2014-05-10 12:11:40 disconnecting node 69.28.94.67
2014-05-10 12:12:01 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:12:01 connected 69.28.94.67
2014-05-10 12:12:01 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:12:01 socket closed
2014-05-10 12:12:01 disconnecting node 69.28.94.67
2014-05-10 12:12:19 ResendWalletTransactions()
2014-05-10 12:12:21 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:12:22 connected 69.28.94.67
2014-05-10 12:12:22 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:12:22 socket closed
2014-05-10 12:12:22 disconnecting node 69.28.94.67
2014-05-10 12:12:42 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:12:42 connected 69.28.94.67
2014-05-10 12:12:42 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:12:42 socket closed
2014-05-10 12:12:42 disconnecting node 69.28.94.67
2014-05-10 12:13:03 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:13:03 connected 69.28.94.67
2014-05-10 12:13:03 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:13:03 socket closed
2014-05-10 12:13:03 disconnecting node 69.28.94.67
2014-05-10 12:13:24 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:13:24 connected 69.28.94.67
2014-05-10 12:13:24 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:13:24 socket recv error 10054
2014-05-10 12:13:24 disconnecting node 69.28.94.67
2014-05-10 12:13:44 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:13:45 connected 69.28.94.67
2014-05-10 12:13:45 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:13:45 socket closed
2014-05-10 12:13:45 disconnecting node 69.28.94.67
2014-05-10 12:14:05 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:14:05 connected 69.28.94.67
2014-05-10 12:14:05 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:14:06 socket closed
2014-05-10 12:14:06 disconnecting node 69.28.94.67
2014-05-10 12:14:26 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:14:26 connected 69.28.94.67
2014-05-10 12:14:26 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:14:27 socket closed
2014-05-10 12:14:27 disconnecting node 69.28.94.67
2014-05-10 12:14:47 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:14:47 connected 69.28.94.67
2014-05-10 12:14:47 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:14:47 socket closed
2014-05-10 12:14:47 disconnecting node 69.28.94.67
2014-05-10 12:15:08 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:15:08 connected 69.28.94.67
2014-05-10 12:15:08 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:15:08 socket recv error 10054
2014-05-10 12:15:08 disconnecting node 69.28.94.67
2014-05-10 12:15:29 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:15:29 connected 69.28.94.67
2014-05-10 12:15:29 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:15:29 socket closed
2014-05-10 12:15:29 disconnecting node 69.28.94.67
2014-05-10 12:15:50 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:15:50 connected 69.28.94.67
2014-05-10 12:15:50 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:15:50 socket closed
2014-05-10 12:15:50 disconnecting node 69.28.94.67
2014-05-10 12:16:10 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:16:11 connected 69.28.94.67
2014-05-10 12:16:11 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:16:11 socket recv error 10054
2014-05-10 12:16:11 disconnecting node 69.28.94.67
2014-05-10 12:16:19 UPnP Port Mapping successful.
2014-05-10 12:16:21 accepted connection 162.243.12.248:40261
2014-05-10 12:16:21 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=162.243.12.248:40261, peer=162.243.12.248:40261
2014-05-10 12:16:21 Added time data, samples 15, offset +11 (+0 minutes)
2014-05-10 12:16:21 nTimeOffset = +11  (+0 minutes)
2014-05-10 12:16:21 receive version message: /worldcoinseeder:0.01/: version 75000, blocks=0, us=XXX.XXX.XXX.XXX:9030, them=0.0.0.0:0, peer=162.243.12.248:40261
2014-05-10 12:16:23 socket closed
2014-05-10 12:16:23 disconnecting node 162.243.12.248:40261
2014-05-10 12:16:31 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:16:31 connected 69.28.94.67
2014-05-10 12:16:31 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:16:31 socket recv error 10054
2014-05-10 12:16:31 disconnecting node 69.28.94.67
2014-05-10 12:16:52 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:16:52 connected 69.28.94.67
2014-05-10 12:16:52 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:16:52 socket recv error 10054
2014-05-10 12:16:52 disconnecting node 69.28.94.67
2014-05-10 12:17:13 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:17:13 connected 69.28.94.67
2014-05-10 12:17:13 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:17:13 socket closed
2014-05-10 12:17:13 disconnecting node 69.28.94.67
2014-05-10 12:17:34 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:17:34 connected 69.28.94.67
2014-05-10 12:17:34 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:17:34 socket closed
2014-05-10 12:17:34 disconnecting node 69.28.94.67
2014-05-10 12:17:54 trying connection 69.28.94.67 lastseen=0.0hrs
2014-05-10 12:17:56 connected 69.28.94.67
2014-05-10 12:17:56 send version message: version 70002, blocks=5093, us=0.0.0.0:0, them=69.28.94.67:9030, peer=69.28.94.67:9030
2014-05-10 12:17:56 socket closed
2014-05-10 12:17:56 disconnecting node 69.28.94.67

gmcm

member

Activity: 118

Merit: 10

Quote from: A-tM on May 10, 2014, 07:26:01 AM

Quote from: A-tM on May 10, 2014, 07:15:37 AM

Quote from: gmcm on May 10, 2014, 06:08:19 AM

No problems with windows wallet. Just download it from http://limecoin.org and delete all previous info in AppData\Roaming\limecoin before install new one. Dont forget to back up ur wallet.

I have done it already, exactly according to instructions on the forum.
Wallet version is "Windows Wallet V3.13", not 3.12.
It is the most current, isn't it?

Ok, so I will try oncemore whole sequence.

Ok, my fault.
Recently I have deleted the content of Appdata\Roaming\Limecoin folder AFTER the install, then copied backed-up wallet.dat into it.
I did not realize that I have deleted also the fixed config files, and consequently, the config files recreated with wallet.exe were the broken ones.

Now I have deleted Appdata\Roaming\Limecoin folder BEFORE the install, and only replaced wallet.dat.

It seems it works.
Sorry for confusion, folks.
Thank you.

Regards,
Andy

You are welcome! Glad it works for you too.

A-tM

member

Activity: 90

Merit: 10

Quote from: A-tM on May 10, 2014, 07:15:37 AM

Quote from: gmcm on May 10, 2014, 06:08:19 AM

No problems with windows wallet. Just download it from http://limecoin.org and delete all previous info in AppData\Roaming\limecoin before install new one. Dont forget to back up ur wallet.

I have done it already, exactly according to instructions on the forum.
Wallet version is "Windows Wallet V3.13", not 3.12.
It is the most current, isn't it?

Ok, so I will try oncemore whole sequence.

Ok, my fault.
Recently I have deleted the content of Appdata\Roaming\Limecoin folder AFTER the install, then copied backed-up wallet.dat into it.
I did not realize that I have deleted also the fixed config files, and consequently, the config files recreated with wallet.exe were the broken ones.

Now I have deleted Appdata\Roaming\Limecoin folder BEFORE the install, and only replaced wallet.dat.

It seems it works.
Sorry for confusion, folks.
Thank you.

Regards,
Andy

A-tM

member

Activity: 90

Merit: 10

Quote from: gmcm on May 10, 2014, 06:08:19 AM

No problems with windows wallet. Just download it from http://limecoin.org and delete all previous info in AppData\Roaming\limecoin before install new one. Dont forget to back up ur wallet.

I have done it already, exactly according to instructions on the forum.
Wallet version is "Windows Wallet V3.13", not 3.12.
It is the most current, isn't it?

Ok, so I will try oncemore whole sequence.

gmcm

member

Activity: 118

Merit: 10

Topic: [ANN][LIM]LimeCoin X11 Algo | OBSOLETE move to LimecoinX please - page 14. (Read 61937 times)