|
MinerFTW
|
 |
April 17, 2015, 07:58:12 PM |
|
Block Count:
44689
|
|
|
|
|
|
|
The block chain is the main innovation of Bitcoin. It is the
first distributed timestamping system.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
xPooky
|
|
April 17, 2015, 07:59:43 PM |
|
same block here, so maybe bittrex is not on the right chain
|
|
|
|
|
|
MinerFTW
|
|
April 17, 2015, 08:02:40 PM |
|
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 )
|
|
|
|
|
heavensopen
|
|
April 17, 2015, 08:11:32 PM |
|
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 )
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 |
|
|
|
|
not.you
Legendary
 Offline
Activity: 1726
Merit: 1018
|
|
April 17, 2015, 08:14:33 PM |
|
Bittrex has disabled market again
|
|
|
|
|
olszeww0
Newbie
Offline
Activity: 4
Merit: 0
|
|
April 17, 2015, 08:14:47 PM |
|
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.
|
|
|
|
|
litedoge
Sr. Member
Offline
Activity: 280
Merit: 250
wow much coin such love
|
|
April 17, 2015, 08:16:39 PM |
|
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 )
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 ... |
|
|
|
|
|
xPooky
|
|
April 17, 2015, 08:17:48 PM |
|
coins from bittrex received now
|
|
|
|
|
|
richiela
|
|
April 17, 2015, 08:18:52 PM |
|
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
|
|
|
|
|
heavensopen
|
|
April 17, 2015, 08:20:00 PM |
|
coins from bittrex received now
same here, they just arrived and I still see the damn #44640 block as the latest one! |
|
|
|
|
|
Lorren
|
|
April 17, 2015, 08:20:06 PM |
|
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. |
BitcoinLove Bitcoin products on Zazzle. BTC: 1BaRWVFD927cfDcCfxn9vhJn2L6ZKKNSP1
|
|
|
|
MinerFTW
|
|
April 17, 2015, 08:23:12 PM |
|
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
tnxs for the fast work richie. Again ! |
|
|
|
|
heavensopen
|
|
April 17, 2015, 08:23:41 PM |
|
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 )
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 |
|
|
|
|
|
MinerFTW
|
|
April 17, 2015, 08:25:53 PM |
|
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.
|
|
|
|
|
MinerFTW
|
|
April 17, 2015, 08:27:43 PM |
|
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 )
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 |
|
|
|
|
heavensopen
|
|
April 17, 2015, 08:36:48 PM |
|
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 )
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! |
|
|
|
|
|
xPooky
|
|
April 17, 2015, 08:38:12 PM |
|
seems that withdraws from bittrex are stuck again :\
|
|
|
|
|
not.you
Legendary
Offline
Activity: 1726
Merit: 1018
|
|
April 17, 2015, 08:38:20 PM |
|
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.
|
|
|
|
|
|
MinerFTW
|
|
April 17, 2015, 08:49:49 PM |
|
no its prob because some can fork still and checkpoint server reject older nodes not synced.
thats why it can freeze. (my best guess)
|
|
|
|
|
bitrev
|
|
April 17, 2015, 11:25:10 PM |
|
no its prob because some can fork still and checkpoint server reject older nodes not synced.
thats why it can freeze. (my best guess)
So what's the plan? We are waiting for..? Me is confused. |
|
|
|
|
|
