Topic: [LTCD] LitecoinDark.com ★ Scrypt ★ Difficulty Shield ★ Multipool ★ Fast - page 155. (Read 368565 times)
October 01, 2014, 12:55:36 PM
Feeling your pain Bassie.. I have 400 plus coins hanging out on the chain somewhere between my wallet/s not updating and Best-Pool...
October 01, 2014, 12:50:47 PM
"Disabled" at Bittrex 
because I just spoke to them and they are on Wrong wallet. They did not see the e-mails ......Stupid! 
October 01, 2014, 12:49:48 PM
"Disabled" at Bittrex
October 01, 2014, 12:49:16 PM
cant get any pool stats on best pool page cant be displayed 
This problem must be solved after block 37000.Now the wallet show:
Code:
"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...
October 01, 2014, 12:44:32 PM
cant get any pool stats on best pool page cant be displayed
This problem must be solved after block 37000.Now the wallet show:
Code:
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
October 01, 2014, 12:44:16 PM
well pool stats backup at best pool 
October 01, 2014, 12:33:56 PM
cant get any pool stats on best pool page cant be displayed
October 01, 2014, 12:30:05 PM
best-pool showing block reward 800
Is block reward now 800 or 25 ?
We just updated our wallet and now the pool is on block 36999 (current block).Is block reward now 800 or 25 ?
Block with 800 reward is block 37009, but this block is still not found on network.
So this block will be orphan.
October 01, 2014, 12:26:10 PM
best-pool showing block reward 800
Is block reward now 800 or 25 ?
Is block reward now 800 or 25 ?
October 01, 2014, 12:18:13 PM
October 01, 2014, 12:13:09 PM
Bittrex still have to update their wallet LTCD 37091. They are past 37000
October 01, 2014, 12:12:27 PM
The Addict at the top of the list has just stopped accumulating hahaha
http://www.richlist.eu/litecoindark/stats/LVS7x6bBWFqFbBd8F8d14aPkp6cH3k1HgE
http://www.richlist.eu/litecoindark/stats/LVS7x6bBWFqFbBd8F8d14aPkp6cH3k1HgE
Where does the richlist get it's info from?. I have 93563.70517530 1.31737697 and my address is not listed on there
If you had nothing in your wallet and have just bought LTCD for the first time you may need to wait until it gets updated.
My address is on the list. It seems fine
October 01, 2014, 12:08:03 PM
Give it <1hr -- the Blocks will move along as planned. Great work dev team.
Edit: Just checked the Bittrex order books. o.o
Edit: Just checked the Bittrex order books. o.o
October 01, 2014, 12:03:19 PM
Hashlink Updated ... but our wallet stuck at 36999
I've locket peers only to "addr" : "24.199.222.230", because Dev said it's updated seed node.
What is wrong ?
Code:
"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."
"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.)
October 01, 2014, 12:02:05 PM
Hashlink Updated ... but our wallet stuck at 36999
I've locket peers only to "addr" : "24.199.222.230", because Dev said it's updated seed node.
What is wrong ?
Code:
"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."
"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 ?
It seems like the person on top of the list has not updated the wallet neither. Otherwise it would have been already found.
October 01, 2014, 12:01:23 PM
Just read 2 post back and you have your answer !
I know about the cosmetic version in the wallet. I was talking abotu being stuck at block 36999 :-)
So we are waiting for someone to find 37000
Lol ... okay
So we're just waiting
October 01, 2014, 11:58:43 AM
Just read 2 post back and you have your answer !
I know about the cosmetic version in the wallet. I was talking abotu being stuck at block 36999 :-)
So we are waiting for someone to find 37000
October 01, 2014, 11:56:54 AM
Hashlink Updated ... but our wallet stuck at 36999
I've locket peers only to "addr" : "24.199.222.230", because Dev said it's updated seed node.
What is wrong ?
Code:
"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."
"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 ?
October 01, 2014, 11:56:25 AM
Shame...
Price was going really well last night until someone(s) laid down six stacks of 5 BTC walls around 15. From that moment the price
stopped rising. Im certain the price would have hit 20. Interesting there hasnt been a price crash due to those walls so if the whale(s)
were looking for cheaper coins their walls arnt working. Maybe they should consider removing those walls.....let the price go up
and they can join in the fun to. Alternatively its the person who owns 40% of this coin playing games..but its really in thei interest
to push the price upward, not downward...
Price was going really well last night until someone(s) laid down six stacks of 5 BTC walls around 15. From that moment the price
stopped rising. Im certain the price would have hit 20. Interesting there hasnt been a price crash due to those walls so if the whale(s)
were looking for cheaper coins their walls arnt working. Maybe they should consider removing those walls.....let the price go up
and they can join in the fun to. Alternatively its the person who owns 40% of this coin playing games..but its really in thei interest
to push the price upward, not downward...
I saw these walls too.
Bittex detrimental bot system-pattern has just repeated itself again with LTCD. It gained popularity and people started buying it but Bittrex bot system didn't allow to pass the barrier of 0.000015 BTC.
Check this up.
https://bitcointalk.org/index.php?topic=802335.new#new
Anyway, the price will certainly come back, at some point, to what it was 2 weeks ago (0.0015 USD/LTCD)
If it is Bittrex they have serious problems if it turns out to be them and we have to investigate.
I do still think its another coin trying to keep the price down. Why on earth should bittrex keep the price down besides if they have interest in another coin.
It is a very strange behaviour thats for sure, when price goes a little further up than ,15 then it kicks in and start to sell lower and not just a little lower its MUCH lower..
Is this possible to track down in anyway ?
You may be right. It's just my guess. We will see.
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.
okay, thanks.
but what about the block explorer? it shows 37008.
my wallet (1.1.0 pre = 1.2.0) stuck on 36999
I updated my wallet yesterday and it also now stuck at block 36999 :-)
Just read 2 post back and you have your answer !
October 01, 2014, 11:53:45 AM
Shame...
Price was going really well last night until someone(s) laid down six stacks of 5 BTC walls around 15. From that moment the price
stopped rising. Im certain the price would have hit 20. Interesting there hasnt been a price crash due to those walls so if the whale(s)
were looking for cheaper coins their walls arnt working. Maybe they should consider removing those walls.....let the price go up
and they can join in the fun to. Alternatively its the person who owns 40% of this coin playing games..but its really in thei interest
to push the price upward, not downward...
Price was going really well last night until someone(s) laid down six stacks of 5 BTC walls around 15. From that moment the price
stopped rising. Im certain the price would have hit 20. Interesting there hasnt been a price crash due to those walls so if the whale(s)
were looking for cheaper coins their walls arnt working. Maybe they should consider removing those walls.....let the price go up
and they can join in the fun to. Alternatively its the person who owns 40% of this coin playing games..but its really in thei interest
to push the price upward, not downward...
I saw these walls too.
Bittex detrimental bot system-pattern has just repeated itself again with LTCD. It gained popularity and people started buying it but Bittrex bot system didn't allow to pass the barrier of 0.000015 BTC.
Check this up.
https://bitcointalk.org/index.php?topic=802335.new#new
Anyway, the price will certainly come back, at some point, to what it was 2 weeks ago (0.0015 USD/LTCD)
If it is Bittrex they have serious problems if it turns out to be them and we have to investigate.
I do still think its another coin trying to keep the price down. Why on earth should bittrex keep the price down besides if they have interest in another coin.
It is a very strange behaviour thats for sure, when price goes a little further up than ,15 then it kicks in and start to sell lower and not just a little lower its MUCH lower..
Is this possible to track down in anyway ?
You may be right. It's just my guess. We will see.
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.
okay, thanks.
but what about the block explorer? it shows 37008.
my wallet (1.1.0 pre = 1.2.0) stuck on 36999
I updated my wallet yesterday and it also now stuck at block 36999 :-)
Jump to: