I don't know where it was a week ago, but it was talked about in this very thread ~19 days ago. Including bonus comments from the original author of that article, when someone first tried to use it to say the Monero dev's were scammers (hint - they're not):

This is a very true point. I'm not really expecting to make any headway with people who have their opinions set in stone (due to allegiances with competing cryptocurrencies, due to paid shilling, or just misplaced hate & vitriol). It's more to provide some counterbalance for the sake of other, rational people who may be reading this thread.

The only advice I have to offer is that people shouldn't blindly trust unsubstantiated and unproven internet rumours, and should do their own due diligence and make their own assessment of risk. Whereas your advice seems to be 'OMG SOME BAD STUFF GOING DOWN, DUMP MONERO AND BUY STEALTHCOIN'.

I wonder which of those two pieces of advice an impartial external party would consider to be the most sensible?

Did you miss the part where one of the developers said it's entirely possible for Monero to integrate Chandran signatures at some point in the future, if they deem it to be worthwhile? And also the part where Chandran signatures only offer space savings vs the ring-sig implementation in XMR for TX's with extreme high mixin values.

Like a lingering bad smell. The putrid stench of rotten advice coming from the fetid mind of a spiteful man.

... Did you not just say you'd be back in two days?

Oh wait, that's right, I almost forgot you're completely full of shit.

Sounds good, see you in two days!  

How about you follow your own advice and fuck off out of this thread? I'm sure they could use your 'expertise' back in the stealthcoin thread. You've clearly made your point here and as far as I can tell you're only still in this thread trying to scare Monero supporters into your waiting stealthcoin arms.

At the moment, there has been no confirmed exploit in Monero. And there won't be a confirmed exploit until someone either provides specific technical details or actually carries it out either on the main Monero blockchain or the testnet blockchain. Even then, the lasting impact of such an attack is uncertain. Given the XMR dev team's track record of dealing with blockchain attacks, it's entirely possible they'll quickly catch it, perform remedial action, and then put in place measures to prevent it from happening in the future.

It's not smart money to be shaken out of the tree by unsubstantiated and unproven rumours. Specially not if you end up wrong after following the rumour and end up having to buy back in for higher than you cashed out at.

Just spotted this book titled "Anonymous Cryptocurrencies: The rise of bitcoin alternatives that offer true anonymity" at http://www.amazon.com/dp/B00KZ6WANE

Apparently it gives a favourable writeup of XMR. Seems the author know what he's talking about, I think I'll check it out. The author also has it for sale for bitcoin on his site http://willmartin.com/, as well as some interesting posts regarding anonymity and privacy.

Typically when your pc freezes up like that (can't end the task using task manager and have to restart) it is indicative of a file system or hardware problem. Certainly isn't likely to be a problem that would be caused by the monero software. Do you have another machine you could try the wallet on?

#rekt

Well, you said the previous version worked fine for you. The new version makes sure that your blockchain is synced up to the right fork. As your blockchain is already past the fork, you can go back to the old version (that you said worked fine).

If you still have problems then it is an issue with your machine/Windows install. Have you got another machine you can try it on?

Looks like you forgot a few points in your post there so I went and fixed it up for you.

Nope, they released a patched version. It's up to all the people running these nodes (like you and me) to update to the correct version, or they won't be able to use their wallets.

No problem, just your node receiving blocks from others that are on the wrong chain. You can safely ignore these errors.

Works for me. Copy/paste what happens when you try to type 'exit'.

Could be a problem with your setup rather than the wallet.

I think devs have had problems getting their Windows x64 blockchain to sync to the correct fork themselves.

(bold emphasis mine)

Not surprised, it took a few attempts for me to get it synced right. Didn't expect to see that there's still so many daemons on the wrong fork though. Noticing a lot of this in my bitmonerod output:


I posted some tips in my last post on how to get synced up using the blockchain in the OP. It just takes a little while is all.

Ah ok, with that being the case I can see why a downloaded blockchain could be problematic if crafted maliciously. As people have no reason to trust me I will share the tricks I used to get my win x64 blockchain synced and updated. As I said in my edited post above:

If anyone wants to sync themselves due to the chance of a dodgy blockchain (mine isn't but I can understand the concerns - see smooth's post below), download the blockchain from the OP and then start bitmonerod with the flag "--add-priority-node 88.151.101.22:18080". That will preferentially try to sync to a known good node (thanks to hegemoOn and his pool [monero.coolmining.club] for that). It's how I got my chain synced to the right fork. You can still end up on the wrong fork but this gives you a better chance.

Also, you can 'save' your blockchain in bitmonerod at around block 202000, so that way if you end up on the wrong fork just close bitmonerod without saving and try again.

Understandable. You can only approve what you guys know to be 100% legitimate and have put out yourself. Out of curiosity - would it even be possible to craft a malicious blockchain file? I always figured it would just fail to load and error out. Worst case scenario would be having to resync from the genesis block, or download from the OP and then sync up from a month ago, hoping you get the right fork.

Windows x64 blockchain (on the right fork) here:

https://mega.co.nz/#!1pM3zDRR!mByS0T0eZU4pGfbQ2N6B1yyooneJ9-cSSWi1DN0uBQs

Redownloaded to test and it loads succesfully:



Edit: If anyone wants to sync themselves due to the chance of a dodgy blockchain (mine isn't but I can understand the concerns - see smooth's post below), download the blockchain from the OP and then start bitmonerod with the flag "--add-priority-node 88.151.101.22:18080". That will preferentially try to sync to a known good node (thanks to hegemoOn and his pool [monero.coolmining.club] for that). It's how I got my chain synced to the right fork. You can still end up on the wrong fork but this gives you a better chance.

Also, you can 'save' your blockchain in bitmonerod at around block 202000, so that way if you end up on the wrong fork just close bitmonerod without saving and try again.