Topic: !<~~~~~[BAT] BatCoin - The Reincarnation [Stay tuned] ~~~~~>! - page 133. (Read 233949 times)
January 19, 2014, 03:30:25 PM
Can someone please explain files i need to delete in the folder....iv backed up wallet.dat but im seeing people loosing an lot of coins on re-syncing block chain...i dont feel like being one of those people tbh.
January 19, 2014, 01:33:24 PM
I'm now stuck on the same block!
January 19, 2014, 01:27:18 PM
My BAT From the Miners Best Pool still have not shown up in the wallet!!!
Now, NO Sync on Wallet... Stuck on Block, 3555
Now, NO Sync on Wallet... Stuck on Block, 3555
January 19, 2014, 05:06:46 AM
The windows client is long here,
But we can't seem to get it to sync all the way (sometimes does) -- there are to many people running the old client with the old chains!
DOWNALOAD THE NEW WINDOWS CLIENT
https://mega.co.nz/#!lRsBFCzS!du5DbjlNkx6Yq4PCngEhZB_VKOBOGWtslye8m9b4t7c
*DELETE YOUR OLD CHAIN (!!!!BACKUP WALLET.DAT!!!!)*
add to conf file:
But we can't seem to get it to sync all the way (sometimes does) -- there are to many people running the old client with the old chains!
DOWNALOAD THE NEW WINDOWS CLIENT
https://mega.co.nz/#!lRsBFCzS!du5DbjlNkx6Yq4PCngEhZB_VKOBOGWtslye8m9b4t7c
*DELETE YOUR OLD CHAIN (!!!!BACKUP WALLET.DAT!!!!)*
add to conf file:
Code:
rpcuser=x
rpcpassword=x
rpcallowip=127.0.0.1
daemon=1
server=1
addnode=84.109.103.114
addnode=88.198.40.3
rpcpassword=x
rpcallowip=127.0.0.1
daemon=1
server=1
addnode=84.109.103.114
addnode=88.198.40.3
please give us other nodes the node 88.198.40.3 is have the old wallet no sync and the 84.109.103.114 is offline long time
January 19, 2014, 01:45:16 AM
My Wallet is Connected. Have a lot of unconfirmed 
I am missing a Transfer from the Pool, the coins are going to show up in the wallet? The transfer is from Coins that ware Mined when the chain was restarted. The pool is showing confirmed.
I am missing a Transfer from the Pool, the coins are going to show up in the wallet? The transfer is from Coins that ware Mined when the chain was restarted. The pool is showing confirmed.
January 18, 2014, 11:18:16 PM
Only the dev can confirm that this is the source of the sync issues.
If it is, there is no fix, because there is no problem. We simply have to do what .Batman asked already : update to the last wallet version and delete the blockchain data.
Linux users also have to get the last commit from the 17th via a git pull.
It will then resolve itself automatically.
If it is, there is no fix, because there is no problem. We simply have to do what .Batman asked already : update to the last wallet version and delete the blockchain data.
Linux users also have to get the last commit from the 17th via a git pull.
It will then resolve itself automatically.
January 18, 2014, 10:49:36 PM
OK and the fix for this is?
January 18, 2014, 09:51:47 PM
Ok, there was a commit yesterday that changed back the rand function used in GetBlockValue to the "normal" one : generateMTRandom
This wasn't there when I last updated the linux daemon code, on the 17th, when this was supposed to be fixed.
I'm pretty sure that what's happening is that the majority of the users/pools still have the old code, but the wallet has the new one, and at block 3476, the check of the block value relying on the previous block's hash does not validate when compared to the real block 3477 value. All of this because the random function changed, and in very particular cases the result of the rand() default function is not the same as the boost mt rand one with the same seed.
So ConnectBlock fails, because block 3477 with hash 9bc3e6455ffe34d45d1d4fc43eb346dbd4675a33e7c70c7bd8080b6146e422b3 is considered bad, when everyone out there being at block 4000 or 5000 should have this specific hash for this block.
If it really comes from this block 3477's hash not validating, then every block beyond the 3476 one is not valid.
That also explains why nobody can sync past it.
This wasn't there when I last updated the linux daemon code, on the 17th, when this was supposed to be fixed.
I'm pretty sure that what's happening is that the majority of the users/pools still have the old code, but the wallet has the new one, and at block 3476, the check of the block value relying on the previous block's hash does not validate when compared to the real block 3477 value. All of this because the random function changed, and in very particular cases the result of the rand() default function is not the same as the boost mt rand one with the same seed.
So ConnectBlock fails, because block 3477 with hash 9bc3e6455ffe34d45d1d4fc43eb346dbd4675a33e7c70c7bd8080b6146e422b3 is considered bad, when everyone out there being at block 4000 or 5000 should have this specific hash for this block.
If it really comes from this block 3477's hash not validating, then every block beyond the 3476 one is not valid.
That also explains why nobody can sync past it.
January 18, 2014, 05:34:24 PM
4181
January 18, 2014, 04:47:13 PM
Looks like due to the block reset I'm out 300,000 BAT!
Damn Son! January 18, 2014, 04:43:17 PM
I'm stuck on 3476 out of 3657 blocks.
January 18, 2014, 04:40:52 PM
Ok I will give 1 Million coins to anyone who can fix this issue and keep it fixed for at least a couple weeks. I'll give you 500k up front and another 500k after one week of flawlessness
January 18, 2014, 04:40:35 PM
Looks like due to the block reset I'm out 300,000 BAT!
January 18, 2014, 04:38:20 PM
So is the chain still screwed up? Am I syncing for nothing?
This blows... Still Stuck, 4181
January 18, 2014, 04:35:37 PM
So is the chain still screwed up? Am I syncing for nothing?
January 18, 2014, 03:45:18 PM
Is it forked again? No pool works? Sitting at Block 5175
Is it ok now ? Trying to solo mine a little to see. I'm currently at block 5185.
But my new version's windows wallet can't sync past 3476 again. Even if the only node I put is my own private pool which was on the same chain as minersbest when there was still mining over there (yesterday).
Edit : stopped at block 5196. Don't see the point of being the only one to mine a coin that may pretty much be dead.
I was mining at the same pool, no workers, wtf is going on with this coin?
The new wallet don't work either... Stuck @ 4181...
January 18, 2014, 03:02:58 PM
Is it forked again? No pool works? Sitting at Block 5175
Is it ok now ? Trying to solo mine a little to see. I'm currently at block 5185.
But my new version's windows wallet can't sync past 3476 again. Even if the only node I put is my own private pool which was on the same chain as minersbest when there was still mining over there (yesterday).
Edit : stopped at block 5196. Don't see the point of being the only one to mine a coin that may pretty much be dead.
January 18, 2014, 01:46:37 PM
4338 here 
January 18, 2014, 01:23:55 PM
Is it forked again? No pool works? Sitting at Block 5175
January 18, 2014, 11:23:51 AM
Too long time to release the new wallet, dead coin now.
psssh, speak for yourself. Those of us holding millions of coins are looking forward to trading them.
I am still stuck at block 3476.
same
me too
Jump to: