[XMR] Monero - A secure, private, untraceable cryptocurrency

[aeoncurrency]

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

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.

[1714831855]

1714831855

[1714831855]

1714831855

[1714831855]

1714831855

[fluffypony]

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.

[aeoncurrency]

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.

Thank you for the update. I will help spread the word on Twitter:

https://twitter.com/aeoncurrency/status/687971825779884032

[dEBRUYNE]

- 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.

[iCEBREAKER]

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.

Nice fast response!

Mustangs 2
Trollblocks 0

[primer-]

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.

[netmonk]

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...

[binaryFate]

Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
No harm done I believe.

[primer-]

Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
No harm done I believe.

No harm done ? Look at the net hash rate, it has halved...

[GingerAle]

Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
No harm done I believe.

No harm done ? Look at the net hash rate, it has halved...

Oh primer. I don't get you.

[nioc]

Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
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...

[papa_lazzarou]

Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
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...

[Hueristic]

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.

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?

[Hueristic]

Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
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!

[primer-]

There was no fucking attack, it was just a bug!

[smooth]

There was no fucking attack, it was just a bug!

Oh really? Where did the version 2 block come from?

[primer-]

There was no fucking attack, it was just a bug!

Oh really? Where did the version 2 block come from?

Buggy code!

[dnaleor]

There was no fucking attack, it was just a bug!

It was an attack.

Someone created a block that can't be created by just using the 0.9 client.
So the attacker changed the code of 0.9 a bit so he/she/they was/were able to mine a block that was a v2block in stead of the default v1block.

[boolberry]

Kudos to the Monero development team for being alert and acting quickly to remedy the attack. Just like the fast response to the last major attack in 2014 the development team has proven itself. Thank you for being great stewards for Monero and continuing to improve upon the CryptoNote technology you inherited.

The Monero codebase looks nothing like it did in summer 2014 and that is a good thing. The Monero development team and Monero Research Lab deserve a tremendous amount of recognition for all of their work.

[dEBRUYNE]

Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
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!

Yes, Poloniex' wallet is disabled as well.