think im seeing progress but need to know what dev thinks. 
Topic: i quit - page 51. (Read 142570 times)
looking at code again all day to complete and total fix think im seeing progress but need to know what dev thinks.
think im seeing progress but need to know what dev thinks.
I have staking issues as well, a lot of generated but not accepted. Is there multiple forks going on? I have started from scratch having deleted the .litedoge directory, restore old wallet and then execute repairwallet from the debug console last night will do this again now... 
Block explorer does not work : http://cryptoplorer.com:3011/
Use this temporary explorer
http://www.sooncoin.com/litedogeex/block_crawler.php
Block explorer does not work : http://cryptoplorer.com:3011/
no its prob because some can fork still and checkpoint server reject older nodes not synced.
thats why it can freeze. (my best guess)
thats why it can freeze. (my best guess)
So what's the plan?
We are waiting for..?
Me is confused.
i for 1 am waiting on dev to change code i told him. not staking myself till its fully fixed. but will try to keep community positive
no its prob because some can fork still and checkpoint server reject older nodes not synced.
thats why it can freeze. (my best guess)
thats why it can freeze. (my best guess)
So what's the plan?
We are waiting for..?
Me is confused.
no its prob because some can fork still and checkpoint server reject older nodes not synced.
thats why it can freeze. (my best guess)
thats why it can freeze. (my best guess)
Sounds like bittrex was suffering from the frozen block height issue. I saw that once before yesterday or the day before but things were so messed up generally I just deleted everything and resynced and didn't think about it. I will try that repairwallet thing next time if it happens again. That seems a different issue than the forking though. Maybe another problem with the wallet code.
seems that withdraws from bittrex are stuck again :\
status looks like they are. but best to contact support i guess.
ps. i tried and mine didn't arrive either. (so you see im with community and not only trying to yell something here )
ps. i tried and mine didn't arrive either. (so you see im with community and not only trying to yell something here )
Oh no, nobody said that
we are together in this mess, obviously
I went to eat and now that I'm back, something is weird
I am stuck on #44640
killed wallet and restarted and it is still on that block.... says it is synced and staking
run "repairwallet" in console twice in a row ... it fixes mine ...
... we have to look at more permanent fix ...
yep... I agree with Lorren, it is progress but we all know we need something solid
if you get that do a full resync again it looks like you was forked off chain and send to wrong 1.
if you don't have coins anymore i will pay those back to you as long i can support community with it that way.
coin still needs work i totally agree but we can withstand this mess and make it great.
Also please before you send coins or receive please look up or check crawler for now first so you know if you send wrong or not. best way to do is type in last block in crawler to see if your wallet see that hashed or tx
resyncing again
no, coins were in the wallet and now I see the transactions confirming again
not sure why I had 1 "mismatched spent coin"
I find it weird that it stopped on block 44640, yet I received the coins from Bittrex!
status looks like they are. but best to contact support i guess.
ps. i tried and mine didn't arrive either. (so you see im with community and not only trying to yell something here )
ps. i tried and mine didn't arrive either. (so you see im with community and not only trying to yell something here )
Oh no, nobody said that
we are together in this mess, obviously
I went to eat and now that I'm back, something is weird
I am stuck on #44640
killed wallet and restarted and it is still on that block.... says it is synced and staking
run "repairwallet" in console twice in a row ... it fixes mine ...
... we have to look at more permanent fix ...
23:20:20

checkwallet
23:20:20

{
"mismatched spent coins" : 1,
"amount in question" : 52483.92380000
}
23:20:35

repairwallet
23:20:35

{
"mismatched spent coins" : 1,
"amount affected by repair" : 52483.92380000
}
yep... I agree with Lorren, it is progress but we all know we need something solid
if you get that do a full resync again it looks like you was forked off chain and send to wrong 1.
if you don't have coins anymore i will pay those back to you as long i can support community with it that way.
coin still needs work i totally agree but we can withstand this mess and make it great.
Also please before you send coins or receive please look up or check crawler for now first so you know if you send wrong or not. best way to do is type in last block in crawler to see if your wallet see that hashed or tx
yeah i preposed a fix to dev.
until then i can't do much more then keep checkpoint server online like i do now.
also making new extra nodes for bittrex to add.
if ppl setting up nodes not staking also please post ip's so we get a more stable network.
how i see it now is that older not synced nodes receive hash from stakes and push you of the right chain etc.
until then i can't do much more then keep checkpoint server online like i do now.
also making new extra nodes for bittrex to add.
if ppl setting up nodes not staking also please post ip's so we get a more stable network.
how i see it now is that older not synced nodes receive hash from stakes and push you of the right chain etc.
status looks like they are. but best to contact support i guess.
ps. i tried and mine didn't arrive either. (so you see im with community and not only trying to yell something here )
ps. i tried and mine didn't arrive either. (so you see im with community and not only trying to yell something here )
Oh no, nobody said that
we are together in this mess, obviously
I went to eat and now that I'm back, something is weird
I am stuck on #44640
killed wallet and restarted and it is still on that block.... says it is synced and staking
run "repairwallet" in console twice in a row ... it fixes mine ...
... we have to look at more permanent fix ...
23:20:20

checkwallet
23:20:20

{
"mismatched spent coins" : 1,
"amount in question" : 52483.92380000
}
23:20:35

repairwallet
23:20:35

{
"mismatched spent coins" : 1,
"amount affected by repair" : 52483.92380000
}
yep... I agree with Lorren, it is progress but we all know we need something solid
All transactions were stuck in the wallet with 0 confirms... not sure why... We manually rebroadcasted and that seemed to have worked... hopefully that will be the end of that.
thanks,
Richie
thanks,
Richie
tnxs for the fast work richie. Again !
So if all the nodes will depend on these two nodes and will use at the same time option listen = 0, then noone will be able to verify whether the owner of these two nodes are not manipulating the chain, because the option listen = 0 makes that the chain can not be verified with other nodes.
I'm sure that this is not the permanent solution. It's better than what we've had the previous couple of days though.
This temporary fix has been working for me. I've staked a few times and haven't forked... it's progress.
coins from bittrex received now
same here, they just arrived
and I still see the damn #44640 block as the latest one!
All transactions were stuck in the wallet with 0 confirms... not sure why... We manually rebroadcasted and that seemed to have worked... hopefully that will be the end of that.
thanks,
Richie
thanks,
Richie
coins from bittrex received now
status looks like they are. but best to contact support i guess.
ps. i tried and mine didn't arrive either. (so you see im with community and not only trying to yell something here )
ps. i tried and mine didn't arrive either. (so you see im with community and not only trying to yell something here )
Oh no, nobody said that
we are together in this mess, obviously
I went to eat and now that I'm back, something is weird
I am stuck on #44640
killed wallet and restarted and it is still on that block.... says it is synced and staking
run "repairwallet" in console twice in a row ... it fixes mine ...
... we have to look at more permanent fix ...
So if all the nodes will depend on these two nodes and will use at the same time option listen = 0, then noone will be able to verify whether the owner of these two nodes are not manipulating the chain, because the option listen = 0 makes that the chain can not be verified with other nodes.
Jump to: