You just Stated a couple days ago this Announcement, why you keep changing things. you announ PoS in place of Tor. And Now you saying couple months. you need to get ur crap together and quit misleading people so you can play the market. Why are you misleading this Community for ur profit, you are scamming all of us, Community dont be played by a fool. We are not all this dumb. We see what u are doing....
I believe you may have misunderstood as well, friend. Let's see if I can clarify while I have test builds running. PoS and Tor have switched priorities in order of release on the roadmap. Maybe that is a bit more clear in terminology. Instead of jumping to conclusions, waiting patiently like the rest of the community might be beneficial. Thanks for your input. |
|
|
|
Haven't read through the last few pages, just wanted to post a quick note to let you all know that the update is coming, just taking me a bit longer to get the compiles finished than I had expected.
so will this be a mandatory update for the wallet on Wednesday  a lot of people confused I think or maybe not lol Short answer no. Preparatory code will be in place for the next mandatory update, but this one is not said update. I've been trying to do some major refactoring while debugging the fork issue. I've come up with a solution, passed it by the team, and details will be made public soon, but this update is not a hard fork or absolutely mandatory, it's just a stepping stone to something better. I believe Xircom and I had a slight miscommunication on skype as to whether not this was intended to be a mandatory update. He is aware of everything going on, and the rest of his announcement was correct. (Also for anyone concerned, I know I haven't been as vocal here as I have in the past, but now that we have a more complete team I've been able to focus more on the code than on the discussion. That said, just because I'm not speaking doesn't mean I'm not listening.) |
|
|
|
|
Haven't read through the last few pages, just wanted to post a quick note to let you all know that the update is coming, just taking me a bit longer to get the compiles finished than I had expected.
|
|
|
|
|
Seems there may be a bit of confusion. Wednesday's update will not affect any older wallets' abilities to sync, nor will it involve any kind of network fork. The changes are stability related, code cleanup, refactoring, and preparatory.
|
|
|
|
Reverting back to the old wallet... current block and hash:
litecoindark getblockhash 37223
e754611fab573201d575833943fe9b6d6fdeb8cc55306567d82681ebf119ccc0
If we can get consensus on this (a block explorer would sure be helpful), we can re-enable our wallets.
Thanks
Richie
I'm currently in the process of downgrading the seed node and resyncing. Once I'm done, I'll post the hash. In the meantime -- Secondary block explorer: http://ltcd.blokki.info/ |
|
|
|
|
Sigh... If the disagreements have concluded, may we continue solving the blockchain issue now?
|
|
|
|
This node is directly under my administrative control and is in fact a valid seed node.
According to the series of messages back and forth between best-pool and myself, they are running on the correct wallet.
I'm hashing hard there myself. Doing everything I can.
TBF, if BEST-POOL doesn't lock their wallet peers to the "/Satoshi:1.2.0.1/" peers only, they will be on the wrong fork due to >50% of the miners/pools using the wrong wallet. Can you make sure they lock their wallet peers so that we know for sure they are on the right fork? If anyone else knows for sure any known good peer addresses, please feel free to share. I hate to put all the burden on 24.199.222.230. Thanks in advance! I'm already compiling a list. Please bear with me. |
|
|
|
Just to clarify, the known good peer is below, correct?
[
{
"addr" : "24.199.222.230:11040",
"services" : "00000003",
"lastsend" : 1412186747,
"lastrecv" : 1412186747,
"bytessent" : 1209,
"bytesrecv" : 8607,
"blocksrequested" : 0,
"conntime" : 1412186747,
"version" : 70002,
"subver" : "/Satoshi:1.2.0.1/",
"inbound" : false,
"startingheight" : 36999,
"banscore" : 0,
"syncnode" : true
}
]
If so, I have changed my litecoindark.info file to remove the
"addnode" addresses to something like:
listen=1
server=1
daemon=1
rpcuser=[yourusername]
rpcpassword=[yourpassword]
rpcport=21040
connect=24.199.222.230:11040
This connects my wallet to only the 24.199.222.230 node.
Please confirm two things:
1. Is this node the valid seed node?
2. Are you absolutely sure that BEST-POOL.COM's wallet is on this fork at block 36999? I am throwing some serious mining power
at BEST-POOL.COM and I want to make sure I am not wasting my hash power.
This node is directly under my administrative control and is in fact a valid seed node. According to the series of messages back and forth between best-pool and myself, they are running on the correct wallet. I'm hashing hard there myself. Doing everything I can.  |
|
|
|
Assuming the exchanges are just waiting to serve your needs is bullshite. You can say they are not doing their job, and they can say you are not doing yours. The coin price will lose it's momentum by being disabled from trading  Did I miss something? To my knowledge, no-one said anything about anyone not doing their jobs. |
|
|
|
Too many pool owners did not upgrade in time... We are on it with Bittrex
at the moment
ok so this ltcd.hashlink.eu is a dum ass he is updating now, and i was F.. already mining on block 36999 for F.. 5 a 6 hours i can say goodbye to that coins or what , i hope this all will be solved and my 20.000 transfer will arrived ad cryptsy soon. Thanks why this happens with this coin, and other coins go smoot? No, hashlink updated yesterday. Assuming you have updated and cryptsy have updated, your transaction wlll arrive when it is included in a block. Other coins don't typically need to hard fork twice in one month. Most of the community-requested updates to LTCD require hard forks. If you want to avoid hard forks, vote against changes that require them when polling is done. |
|
|
|
cant get any pool stats on best pool page cant be displayed This problem must be solved after block 37000. Now the wallet show: "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade." He guys i was mining and the block is on 582.43 % it takes hours , but i think this pool is stuck right now . i think the problem is on that mining pool ltcd,haslink.eu and there are somewhere 20.000 coins flying between my wallet and cryptsy Help me out please Hashlink was updated in time. Feeling your pain Bassie.. I have 400 plus coins hanging out on the chain somewhere between my wallet/s not updating and Best-Pool...
Best-Pool is current now. Transactions won't go anywhere until this block is found. |
|
|
|
cant get any pool stats on best pool page cant be displayed This problem must be solved after block 37000. Now the wallet show: "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade." Yes, this is warning is displayed because several nodes have not yet updated. I'm gearing up to throw every bit of hash rate at it I can find to get us past the marker... |
|
|
|
Hashlink Updated ... but our wallet stuck at 36999 "version" : 1020001,
"protocolversion" : 70002,
"walletversion" : 60000,
"blocks" : 36999,
"timeoffset" : 0,
"connections" : 1,
"proxy" : "",
"difficulty" : 696.11786850,
"testnet" : false,
"keypoololdest" : 1411937157,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
I've locket peers only to "addr" : "24.199.222.230", because Dev said it's updated seed node. What is wrong ? You're on the right fork, we just need blocks. My guess (and yes, it is only a guess) is that the majority of the network's hash rate is still on the old wallet (multipools.) |
|
|
|
Bestpool still finding blocks at the 800 rate
yea i just saw it to i am all in again !!!!!! They are on the wrong fork and updating. If you point hash power there it will be wasted I just received word that they've completed the update. Not sure if they've synced fully yet. |
|
|
|
anyone else noticed that the client version isnīt 1.2.0?   Someone asked the same question yesterday. I addressed it. Basically it would have taken me an additional 2 hours to recompile and run my entire test suite, verify, sign, and upload the new wallet just to change the version number in the about page. At which point, I would have needed to reevaluate a target block for the fork, and you have an endless cycle. It's purely cosmetic as getinfo reports the correct version, and this can easily be fixed in a quick update later. This was the least important issue that needed to be fixed, and was more urgent to get the update rolled out so that everyone would have time to update their wallets. Basically: It wasn't overlooked, but there were more important things to address. Let us deal with the issue at hand first. |
|
|
|
ETA till the coin halving?
We're above the block listed so it should have happened already The explorer is still showing a reward of 800, is anyone seeing anything different on the actual mining end? Explorer hasn't been updated yet Neither has best-pool. Working with them to get it taken care of. |
|
|
|
There is a hard fork and the DEV is not online for it?
I'm right here. Trying to figure out who still has not updated and why. |
|
|
|
wallet came on 36999 and blocked
This is the "fork" part of a hard fork. We have more miners on the old fork than the new one... Until someone on the new fork finds block 37000, we're not going anywhere. Anyone showing a height of more than 37000 in their wallet (including the block explorers *ahem*) are late to the update party... |
|
|
|
★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★ ★
Announcement:
Dear Community, it has been a journey at lightning speed. We have all build without doubt the most promising coin since LTC and yes, I know some would say its a bald statement.
Just to remind you: you spelt "bold" wrong! Is this a project without any hair? lol  Yes, I've seen this several times, I just keep forgetting to mention it to Robbert. |
|
|
|
|
Show Posts
