Quote from: IMJim on August 21, 2014, 09:51:10 PM

Quote from: IMJim on August 21, 2014, 09:08:32 PM

What addnodes or config file are we supposed to use with the latest wallet?

Anybody know the answer to this?

The wallet should load without this but here is a peers.dat file I keep handy since it almost always works: https://dl.dropboxusercontent.com/u/25508862/peers.dat

Quote from: iDUMP on August 21, 2014, 10:01:28 PM

I've just pulled the latest SRC from github and built. but I still get errors.

{
"version" : 80602,
"protocolversion" : 70004,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 5169,
"timeoffset" : 0,
"connections" : 28,
"proxy" : "",
"difficulty" : 0.00024414,
"testnet" : false,
"cakenet" : false,
"keypoololdest" : 1408244855,
"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."
}

Any guesses ?

Try my peers file. Clean your chain data completely and then drop in my peers and fire it back up, should be good.

We have a new windows wallet build to address the "hang" issue. Please backup your wallet before testing this out. This is still 0.1.3, we have disabled loading of offers and aliases in the QT UI for now as it was the cause of the hang (only in windows). We will reinstate these sections as soon as we can, we are still waiting for fund release.

Windows 0.1.3 Wallet EXE [fixes hang issue]: https://mega.co.nz/#!zFxHiLwR!OP6xg_5zZyh1mq5KdOwXw5LDbcLp-3b23WQIrA4ra2Q

Will move this new wallet to OP after some more windows ppl verify. We are moving away from using "installers" as they are too invasive.