Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1393. (Read 4670630 times)

I just re-downloaded the blockchain following the link on the OP. Now bitmonerod has synced. Latest diff:

diff
2014-Sep-25 01:28:18.357703 BH: 232726, DIFF: 1092360188, HR: 18206003 H/s

Mine is:
diff
2014-Sep-25 01:12:49.076636 BH: 232616, DIFF: 1074246915, HR: 17904115 H/s
2014-Sep-25 01:12:57.568924 [P2P9][143.239.71.93:18080 OUT]Sync data returned unknown top block: 232616 -> 232704 [88 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 01:12:58.730542 [P2P9][76.16.250.210:18080 OUT]Sync data returned unknown top block: 232616 -> 232704 [88 blocks (0 days) behind]
SYNCHRONIZATION started

I'm in the same boat (and the same block).  I'm wondering if it's due to everyone I'm connected to not being on the latest rev.  

Smooth, my diff says:
2014-Sep-25 01:04:34.991768 BH: 232616, DIFF: 1074246915, HR: 17904115 H/s

What does diff say?

So, I just recompiled bitmonerod, and now it seems to be stuck on block 232616. Here's some of the output:

2014-Sep-25 00:59:26.151813 [P2P5][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:32.237618 [P2P5][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:38.255829 [P2P8][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:44.404735 [P2P8][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started

Did I do something wrong?

Aaaannnd tewinget just updated the repo to remove that dependency.

https://github.com/monero-project/bitmonero/commit/145dc19eebd2c9f289381debfa1fb7a4b8c71ef7

Yes, if its on poloniex.
They're updated and open for withdrawals and deposits of all coins.
I've not checked all the others yet, but suspect they are also open or will be soon.

In OS X, this worked:

brew install unbound
brew install --HEAD bitmonero

Out of curiosity, what's been added that requires unbound?  I'm familiar with it being a DNS resolving library, but what's in store?


Edit:
Also, of note, installing just the unbound dev libraries was not enough, "ldns" is also a requirement.

On Debian, this should satisfy the new dependencies: apt-get install libunbound-dev libunbound2 libldns-dev

For people interested in a general discussion on checkpoints (as it applied to Bitcoin), see here: https://bitcointalksearch.org/topic/what-are-checkpoints-in-bitcoin-code-194078

It would do you fuck all good to have it stolen or destroyed.

I agree.

As with the previous attacks this will make us stronger.

Weird, I would have picked some other words to indicate success.
Such as:
"We will be distributing updated checkpoint files that will continue to protect the blockchain without the need for a full update of the daemon."

This has been done exactly never before on other coins.
It shows the innovation on demand this team can produce, with rapid on-point responsiveness to a real-time threat with no warning, whether it be real or not.

They could be writing anything, anywhere, and yet have chosen to work on this project.
I am humbled by their generosity to advancing the state of the art as we know it in this arena.

Thank you gentlemen, thank you kindly, you are a credit to your profession.

Dear Monero

Can I have have access to my fucking money yet??

phantom attack: success

Important update (source code only)

We have a new update with additional precautionary checkpoints added to protect more of the existing blockchain. In addition this update adds the ability to read checkpoints from an external file. We will be distributing updated checkpoint files that will continue to protect the blockchain without the need for a full update of the daemon.

Although there has been no actual attack we consider the threat credible and are acting accordingly. We urge you to do the same.

We are however, continuing development and this update also contains some new features that will be included in the next official numbered build. As such, dependencies have changed. For example Linux dependencies:


https://github.com/monero-project/bitmonero

Plain 'git pull' wont work. Unless you are doing your own modifications to the code it is probably easiest to make a new clone. If you are doing your own modifications you should know how to use git.

If you are operating a pool or other important service, or if you are solo mining, and you compile your own node, please pull master from github and upgrade ASAP. If you are not a git expert it is probably better to just create a new clone. Likewise if you have AWS images, please rebuild them with the new version.

Our recommendation for exchange is to remain frozen for external transactions. If you are still running a node, please update.

The only evidence of anomalous activity is what was reported by fluffypony. Nevertheless malicious activity may occur that is not visible until the moment of the attack.

The update is an important precaution.

Updated binaries will follow shortly.

Further measures will be taken as necessary.

I think sponsoring a good optimized CPU and GPU Miner would be a great initiative. It would promote mining and if you built in a 1 or 2% developer fee you would still be preferable to other 5% miners and generate operating capital to boot!

The need for checkpoints likely will remain for quite some time (bitcoin has them as mentioned earlier) but their frequency will depend on the nature of the environment in which they operate, which will certainly evolve.

Maybe, but only if your security model is that the file is in a different trust domain than the daemon itself. For example, that would make it possible to store the blockchain.bin file on a cloud drive without being vulnerable to tampering there. That's possible but not really in line with how anyone is using it to my knowledge.

Poloniex suspended XMR deposit/withdraw as a precautionary measure.
You just need to wait a bit longer, or submit a support ticket.