There was no fucking attack, it was just a bug!
Oh really? Where did the version 2 block come from?
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 705. (Read 4670673 times)
January 15, 2016, 12:38:58 PM
Oh really? Where did the version 2 block come from?
January 15, 2016, 12:32:44 PM
There was no fucking attack, it was just a bug!
January 15, 2016, 12:31:47 PM
Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
No harm done I believe.
No harm done I believe.
No harm done ? Look at the net hash rate, it has halved...
So what, it had just doubled. Although that could have been the attacks. Any dev input on this?
What was the timeframe of the attack?
This must be why withdrawals are locked on bittrex, are they locked on all exchanges?
LOL I always buy at the "Interesting" times!
January 15, 2016, 12:27:30 PM
NB: https://forum.getmonero.org/1/news-announcements-and-editorials/2452/monero-network-malicious-fork-from-block-913193-updates-and-resolution
From that post (which will be kept updated) -
Hi all,
The Monero network was (once again) the subject of an attack. Due to an error during the development of 0.9, Hydrogen Helix, we omitted a check that allowed for v2 blocks to be added to the network prior to the hard fork block height. Thus instead of forking on March 20, at block height 1009827, a v2 block was added to the network at block height 913193.
This is obviously problematic as not all services have updated to 0.9, and the bulk of the network hash rate is still on 0.8.x. We are preparing a point release to 0.9 that resolves this, but in the meantime only if you are running 0.9 you can do the following as a quick patch:
Shut down your Monero daemon
Grab a checkpoints.json file from getmonero: https://downloads.getmonero.org/checkpoints.json
Put the file in your bitmonero working directory (eg. ~/.bitmonero or C:\ProgramData\bitmonero)
Restart the daemon
As soon as the patched point release is out you can remove the checkpoints.json file, if you wish, and run the updated version. The checkpoints.json patch is a quick fix and does not prevent the attacker from replaying their attack at a later block.
From that post (which will be kept updated) -
Hi all,
The Monero network was (once again) the subject of an attack. Due to an error during the development of 0.9, Hydrogen Helix, we omitted a check that allowed for v2 blocks to be added to the network prior to the hard fork block height. Thus instead of forking on March 20, at block height 1009827, a v2 block was added to the network at block height 913193.
This is obviously problematic as not all services have updated to 0.9, and the bulk of the network hash rate is still on 0.8.x. We are preparing a point release to 0.9 that resolves this, but in the meantime only if you are running 0.9 you can do the following as a quick patch:
Shut down your Monero daemon
Grab a checkpoints.json file from getmonero: https://downloads.getmonero.org/checkpoints.json
Put the file in your bitmonero working directory (eg. ~/.bitmonero or C:\ProgramData\bitmonero)
Restart the daemon
As soon as the patched point release is out you can remove the checkpoints.json file, if you wish, and run the updated version. The checkpoints.json patch is a quick fix and does not prevent the attacker from replaying their attack at a later block.
After all this time on testnet I'm surprised to hear this, isn't there anyone on the team adept at at debugging and exploit testing?
Does anyone actually have a position that actively attack testnet before release? If not there are those out there that relish in this and do it for the accolades.
Not trying to be insulting hear as I know how hard you guys work on this but alpha/beta stages are there for a reason and really this is a simple expliot that should have been on the first error checks before release. I wish I it was 16 years ago, as I would have jumped on this just for the lulz.
Also are all the devs listed active? Did they all check this prior to release? What is the list that signed off on this?
January 15, 2016, 11:34:34 AM
Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
No harm done I believe.
No harm done I believe.
No harm done ? Look at the net hash rate, it has halved...
It is down by 25%. I guess that is the same as halved...
It half-halved maybe...
January 15, 2016, 11:07:03 AM
Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
No harm done I believe.
No harm done I believe.
No harm done ? Look at the net hash rate, it has halved...
It is down by 25%. I guess that is the same as halved...
January 15, 2016, 10:55:03 AM
Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
No harm done I believe.
No harm done I believe.
No harm done ? Look at the net hash rate, it has halved...
Oh primer. I don't get you.
January 15, 2016, 10:36:36 AM
Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
No harm done I believe.
No harm done I believe.
No harm done ? Look at the net hash rate, it has halved...
January 15, 2016, 10:35:11 AM
Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
No harm done I believe.
No harm done I believe.
January 15, 2016, 10:32:52 AM
Another fuck-up by the devs. They had a whole year to work on this minor release and guess what, they fucked it up. Retards.
At least they really succeed to fuck the blockchain, not like you and your claim back in the day...
January 15, 2016, 10:27:14 AM
Another fuck-up by the devs. They had a whole year to work on this minor release and guess what, they fucked it up. Retards.
January 15, 2016, 10:20:59 AM
NB: https://forum.getmonero.org/1/news-announcements-and-editorials/2452/monero-network-malicious-fork-from-block-913193-updates-and-resolution
From that post (which will be kept updated) -
Hi all,
The Monero network was (once again) the subject of an attack. Due to an error during the development of 0.9, Hydrogen Helix, we omitted a check that allowed for v2 blocks to be added to the network prior to the hard fork block height. Thus instead of forking on March 20, at block height 1009827, a v2 block was added to the network at block height 913193.
This is obviously problematic as not all services have updated to 0.9, and the bulk of the network hash rate is still on 0.8.x. We are preparing a point release to 0.9 that resolves this, but in the meantime only if you are running 0.9 you can do the following as a quick patch:
Shut down your Monero daemon
Grab a checkpoints.json file from getmonero: https://downloads.getmonero.org/checkpoints.json
Put the file in your bitmonero working directory (eg. ~/.bitmonero or C:\ProgramData\bitmonero)
Restart the daemon
As soon as the patched point release is out you can remove the checkpoints.json file, if you wish, and run the updated version. The checkpoints.json patch is a quick fix and does not prevent the attacker from replaying their attack at a later block.
From that post (which will be kept updated) -
Hi all,
The Monero network was (once again) the subject of an attack. Due to an error during the development of 0.9, Hydrogen Helix, we omitted a check that allowed for v2 blocks to be added to the network prior to the hard fork block height. Thus instead of forking on March 20, at block height 1009827, a v2 block was added to the network at block height 913193.
This is obviously problematic as not all services have updated to 0.9, and the bulk of the network hash rate is still on 0.8.x. We are preparing a point release to 0.9 that resolves this, but in the meantime only if you are running 0.9 you can do the following as a quick patch:
Shut down your Monero daemon
Grab a checkpoints.json file from getmonero: https://downloads.getmonero.org/checkpoints.json
Put the file in your bitmonero working directory (eg. ~/.bitmonero or C:\ProgramData\bitmonero)
Restart the daemon
As soon as the patched point release is out you can remove the checkpoints.json file, if you wish, and run the updated version. The checkpoints.json patch is a quick fix and does not prevent the attacker from replaying their attack at a later block.
Nice fast response!
Mustangs 2
Trollblocks 0
January 15, 2016, 09:53:23 AM
- Poloniex was and is on the correct chain, coins are safe, wallet is currently disabled but trading is allowed.
- MyMonero is not affected, thus coins stored there are safe.
- The devs are preparing a point release to 0.9 that resolves the issue caused by the malicious fork.
- MyMonero is not affected, thus coins stored there are safe.
- The devs are preparing a point release to 0.9 that resolves the issue caused by the malicious fork.
January 15, 2016, 08:19:06 AM
NB: https://forum.getmonero.org/1/news-announcements-and-editorials/2452/monero-network-malicious-fork-from-block-913193-updates-and-resolution
From that post (which will be kept updated) -
Hi all,
The Monero network was (once again) the subject of an attack. Due to an error during the development of 0.9, Hydrogen Helix, we omitted a check that allowed for v2 blocks to be added to the network prior to the hard fork block height. Thus instead of forking on March 20, at block height 1009827, a v2 block was added to the network at block height 913193.
This is obviously problematic as not all services have updated to 0.9, and the bulk of the network hash rate is still on 0.8.x. We are preparing a point release to 0.9 that resolves this, but in the meantime only if you are running 0.9 you can do the following as a quick patch:
Shut down your Monero daemon
Grab a checkpoints.json file from getmonero: https://downloads.getmonero.org/checkpoints.json
Put the file in your bitmonero working directory (eg. ~/.bitmonero or C:\ProgramData\bitmonero)
Restart the daemon
As soon as the patched point release is out you can remove the checkpoints.json file, if you wish, and run the updated version. The checkpoints.json patch is a quick fix and does not prevent the attacker from replaying their attack at a later block.
From that post (which will be kept updated) -
Hi all,
The Monero network was (once again) the subject of an attack. Due to an error during the development of 0.9, Hydrogen Helix, we omitted a check that allowed for v2 blocks to be added to the network prior to the hard fork block height. Thus instead of forking on March 20, at block height 1009827, a v2 block was added to the network at block height 913193.
This is obviously problematic as not all services have updated to 0.9, and the bulk of the network hash rate is still on 0.8.x. We are preparing a point release to 0.9 that resolves this, but in the meantime only if you are running 0.9 you can do the following as a quick patch:
Shut down your Monero daemon
Grab a checkpoints.json file from getmonero: https://downloads.getmonero.org/checkpoints.json
Put the file in your bitmonero working directory (eg. ~/.bitmonero or C:\ProgramData\bitmonero)
Restart the daemon
As soon as the patched point release is out you can remove the checkpoints.json file, if you wish, and run the updated version. The checkpoints.json patch is a quick fix and does not prevent the attacker from replaying their attack at a later block.
Thank you for the update. I will help spread the word on Twitter:
https://twitter.com/aeoncurrency/status/687971825779884032
January 15, 2016, 08:04:23 AM
NB: https://forum.getmonero.org/1/news-announcements-and-editorials/2452/monero-network-malicious-fork-from-block-913193-updates-and-resolution
From that post (which will be kept updated) -
Hi all,
The Monero network was (once again) the subject of an attack. Due to an error during the development of 0.9, Hydrogen Helix, we omitted a check that allowed for v2 blocks to be added to the network prior to the hard fork block height. Thus instead of forking on March 20, at block height 1009827, a v2 block was added to the network at block height 913193.
This is obviously problematic as not all services have updated to 0.9, and the bulk of the network hash rate is still on 0.8.x. We are preparing a point release to 0.9 that resolves this, but in the meantime only if you are running 0.9 you can do the following as a quick patch:
Shut down your Monero daemon
Grab a checkpoints.json file from getmonero: https://downloads.getmonero.org/checkpoints.json
Put the file in your bitmonero working directory (eg. ~/.bitmonero or C:\ProgramData\bitmonero)
Restart the daemon
As soon as the patched point release is out you can remove the checkpoints.json file, if you wish, and run the updated version. The checkpoints.json patch is a quick fix and does not prevent the attacker from replaying their attack at a later block.
From that post (which will be kept updated) -
Hi all,
The Monero network was (once again) the subject of an attack. Due to an error during the development of 0.9, Hydrogen Helix, we omitted a check that allowed for v2 blocks to be added to the network prior to the hard fork block height. Thus instead of forking on March 20, at block height 1009827, a v2 block was added to the network at block height 913193.
This is obviously problematic as not all services have updated to 0.9, and the bulk of the network hash rate is still on 0.8.x. We are preparing a point release to 0.9 that resolves this, but in the meantime only if you are running 0.9 you can do the following as a quick patch:
Shut down your Monero daemon
Grab a checkpoints.json file from getmonero: https://downloads.getmonero.org/checkpoints.json
Put the file in your bitmonero working directory (eg. ~/.bitmonero or C:\ProgramData\bitmonero)
Restart the daemon
As soon as the patched point release is out you can remove the checkpoints.json file, if you wish, and run the updated version. The checkpoints.json patch is a quick fix and does not prevent the attacker from replaying their attack at a later block.
January 15, 2016, 07:52:55 AM
Hello Monero friends. Any feedback would be appreciated
https://twitter.com/aeoncurrency/status/687654160045617153
Its poll time. Cast your vote!
When should we ask @Poloniex to list #aeon alongside its other #CryptoNote coins like #monero and #boolberry?
1. Now
2. After LMDB
3. After GUI
https://twitter.com/aeoncurrency/status/687654160045617153
Its poll time. Cast your vote!
When should we ask @Poloniex to list #aeon alongside its other #CryptoNote coins like #monero and #boolberry?
1. Now
2. After LMDB
3. After GUI
I would say 3, Let XMR get traction then when people are used to it's gui launch. BTW what role is Aeon trying to fill?
Thank you for your feedback. The poll ends in a few more hours. I will let smooth address the technical differences, but Aeon plans aggressive experimentation with a focus on developing technologies that facilitate mobile use. Making technical choices deemed "too risky or premature" for Monero (such as pruning for example) and retaining a light footprint are part of that focus.
Aeon started as a Monero fork and clearly benefits from Monero development. Monero can also decide to implement (or not) some of the new ideas introduced by Aeon.
January 15, 2016, 05:56:42 AM
Quote
There is a -detach feature now. I don't use it (I prefer screen) but some people were just discussing it on the Monero Support thread.
It was so easy after all
January 15, 2016, 05:52:10 AM
Talking about nodes, there is a reason why GUI would help. Before the recent release my laptop would be laggy as hell but now everything seems okay. But i simply dont want to start the daemon every time i turn my PC on. And i dont like to have a command line tab open all the time.
Now of course, i will google how to autostart and hide the process on Ubuntu, i know it is not that difficult. But still...you get the point.
Maybe there is an option for that right now?
Now of course, i will google how to autostart and hide the process on Ubuntu, i know it is not that difficult. But still...you get the point.
Maybe there is an option for that right now?
There is a -detach feature now. I don't use it (I prefer screen) but some people were just discussing it on the Monero Support thread.
January 15, 2016, 05:50:25 AM
Talking about nodes, there is a reason why GUI would help. Before the recent release my laptop would be laggy as hell but now everything seems okay. But i simply dont want to start the daemon every time i turn my PC on. And i dont like to have a command line tab open all the time.
Now of course, i will google how to autostart and hide the process on Ubuntu, i know it is not that difficult. But still...you get the point.
Maybe there is an option for that right now?
Now of course, i will google how to autostart and hide the process on Ubuntu, i know it is not that difficult. But still...you get the point.
Maybe there is an option for that right now?
January 14, 2016, 04:26:15 PM
Be careful syncing from scratch! I just got shutdown temporarily due to high CPU load.
Wait for Fluffypony's script, it downloads a current blockchain database dump and doesn't hammer the CPU.
Wait for Fluffypony's script, it downloads a current blockchain database dump and doesn't hammer the CPU.
Hehe, yeah they shut me down for it. You must ask permission first apparently...
Sorry about that. I got a bit too excited about it.
If you have another 0.9 node running, you can try copying the lmdb blockchain over to the new VPS and running that way without the high CPU load of syncing from scratch. I'm in the process of doing that now, will report back.
Jump to: