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

[aminorex]

Agree we need pics

too much identifying  info already.

[1715277918]

1715277918

[1715277918]

1715277918

[1715277918]

1715277918

[Anon136]

Agree we need pics

too much identifying  info already.

ZzZzZz. Not such a good story without a picture of the painting. Still grats on your wall not being boring anymore.

[nioc]

Agree we need pics

too much identifying  info already.

Yes, your name spells either XMR or Monero (if you use the o twice).


Back on topic, a question from the cadmium induced drooling masses.  For the update, all I need to do is download it and it will replace the files that need to be replaced automatically with nothing else needed to be done on our part?

[xulescu]

Back on topic, a question from the cadmium induced drooling masses.  For the update, all I need to do is download it and it will replace the files that need to be replaced automatically with nothing else needed to be done on our part?

Would be better if you deleted poolstate.bin after you shutdown the daemon and before you start it up again. If my understanding is correct, you will have hundreds of spam transactions in your mempool and you would have to wait 24h for them to drop out. In the meanwhile, I'm not sure how you would be affected.

If the blockchain is the persistent storage of the network then the mempool is its RAM. Better make sure you don't cache stale data.

In other news I had also purchased a painting with Monero but more to the tune of about 80. It is also rather significantly smaller than my whole wall. De gustibus and all that.

[smooth]

Back on topic, a question from the cadmium induced drooling masses.  For the update, all I need to do is download it and it will replace the files that need to be replaced automatically with nothing else needed to be done on our part?

Would be better if you deleted poolstate.bin after you shutdown the daemon and before you start it up again. If my understanding is correct, you will have hundreds of spam transactions in your mempool and you would have to wait 24h for them to drop out. In the meanwhile, I'm not sure how you would be affected.

This is most important for (solo) miners and pool nodes. For ordinary users having the spam in your mempool for 24 hours doesn't really matter.

[ArticMine]

Linux binaries have been updated to 0.8.8.2 with the temporary fee hike fix: http://monero.cc/downloads/monero.linux.x64.latest.tar.bz2

Please switch to this version - we will have a permanent fix in the next few weeks that will bring the fees back down.

After replacing the linux binaries and running

Code:

./bitmonerod

I get

Code:

Illegal instruction (core dumped)

Operating System, Ubuntu 12.04 64bit

Monero was originally installed using the compilation script http://www.monero.cc/blog/new-version-installation-script-now-cpuminer-installation-support-ubuntu-12-04/index.html on 2014-07-13

Edit1: Should I rerun the script and recompile?

Edit2: I renamed bitmonero to bitmoneroback, ran (to recompile from source)

Code:

git clone git://github.com/monero-project/bitmonero && cd bitmonero && make

and then copied wallet.bin, and wallet.bin.keys, to ~/bitmonero/build/release/src and now everything works fine.

[rpietila]

Current tx fees are very low to keep XMR accessible to all users (about 1 cent per 24.4 KB)

when someone comes to me giving a factual example how his monero use actually suffers due to the fees, I will support him from my own pocket, considering this as a donation to monero ecosystem.

Ok, dude, we are pool ops and we are paying tx fees from our profits. Now, when fee raised 20 times, it's significant impact.

The fees go to the miners in the first place, so asking me to support your getting 20 times richer already, is understandably ROTFLMAO.

[sammy007]

Current tx fees are very low to keep XMR accessible to all users (about 1 cent per 24.4 KB)

when someone comes to me giving a factual example how his monero use actually suffers due to the fees, I will support him from my own pocket, considering this as a donation to monero ecosystem.

Ok, dude, we are pool ops and we are paying tx fees from our profits. Now, when fee raised 20 times, it's significant impact.

The fees go to the miners in the first place, so asking me to support your getting 20 times richer already, is understandably ROTFLMAO.

Why so serious, man? I thought it would be funny!

BTW, it seems exchanges in no hurry, I see last 15 blocks without transactions at all

[rpietila]

Current tx fees are very low to keep XMR accessible to all users (about 1 cent per 24.4 KB)

when someone comes to me giving a factual example how his monero use actually suffers due to the fees, I will support him from my own pocket, considering this as a donation to monero ecosystem.

Ok, dude, we are pool ops and we are paying tx fees from our profits. Now, when fee raised 20 times, it's significant impact.

The fees go to the miners in the first place, so asking me to support your getting 20 times richer already, is understandably ROTFLMAO.

Why so serious, man? I thought it would be funny!

BTW, it seems exchanges in no hurry, I see last 15 blocks without transactions at all

Rolling on the floor laughing certainly means I found it funny 

[perl]

monero.crypto-pool.fr as playing the games, the first 3 biggest pool has make mandatory update.

Resulrs broken my pool and dev (fluffony) not interest me for help résolve the problem ( is problem off pool ).

I resolve on solo with bad patch. ( DEV Bitmonero have been able to limit patch on transaction with bad fee and no other problem badhash per exemple )

Code:

--- a/src/cryptonote_protocol/cryptonote_protocol_handler.inl
+++ b/src/cryptonote_protocol/cryptonote_protocol_handler.inl
@@ -273,7 +273,7 @@ namespace cryptonote
       if(tvc.m_verifivation_failed)
       {
         LOG_PRINT_CCONTEXT_L0("Tx verification failed, dropping connection");
-        m_p2p->drop_connection(context);
+        //m_p2p->drop_connection(context);
         return 1;
       }
       if(tvc.m_should_be_relayed)

For information pool for admin:
If you update with new patch bitmonerod Before other.

When other node relay to you transaction fee 0.005.
You reject TX + Disconnecter node on P2P + add in greylisting.
After you reconnect at node when greylisting is not switch to blacklisting.

Your pool is connected only 3 node  and you make orphan and get last block with many time.

I have fixed code with comment line disconnect node send bad transaction.

Actualy my patch is bad (You can flood bitmonerod off my pool with bad transaction).

I have not choice. I use the patch or my pool not work.

I do not thank the DEV (fluffony) telling me to wait
DEV: Remember that a crypto is also the Pool and not only your code

[David Latapie]

Could some esperanto speaker propose motto in esperanto? Let's first consider it in English then after in Esperanto. The actual motto could be slightly changed after the move to esperanto, for euphonic reasons (traduttore, traditore).

Below a compilation of previous proposals I am aware of. I also opened a reddit for this, it will probably be easier to handle there. Also note that this is an exercice in style and it doesn't constitute an official sanction of the motto idea, even though I am in the core team.

I also opened a reddit, which will probably be easier to handle than Bitcointalk: Monero motto in Esperanto.

Also, I propose an official motto for monero, suitable for business cards, physical coins & c.:

Monero est priquiditas pro populo.

Because: Quidquid latine dictum sit, altum videtur.

"Securing Freedom through Privacy" - Google Latin "Praesent libero per Securitate"
"Securing Financial Liberty through Privacy" - Google Latin "Aliquam erat volutpat Securitate libertas"

[David Latapie]

Missive timeline overview

I added this link to the OP (Longer summary of each missive by Globb0).
Remember to update on the same post. Thanks for your efforts.

[Globb0]

OK will do.

Thankyou

[David Latapie]

only a few spots left in our Monero XMR giveaway!

Find out how to claim your FREE 0.4 XMR here:
https://bitcointalk.org/index.php?topic=731365.0

I updated the OP accordingly

Giveaways
Petitioning Cryptsy, Btc-e and others for Monero(XMR)

[AlexGR]

Can we have some data on the aftermath of the attack? I'm primarily interested in

- number of transactions done in a given timeframe,
- megabytes added as bloat,
- effect in transaction speed
- total cost for the attacker

If there is anything else you find important, please share.

[David Latapie]

The Monero Status Android Widget had been added to the OP
Note to Bitcoin moderator: next time you delete a post, please notify of the reason.

[fluffypony]

monero.crypto-pool.fr as playing the games, the first 3 biggest pool has make mandatory update.

This is an incredibly bad patch. It completely breaks the consensus network and relays broke transactions (not just those with the incorrect fee). Pools and nodes deploying this patch will allow an attacker to DDoS the entire network with bad transactions. I cannot emphasise strongly enough how bad this patch is, applying sets us on a path to destroying Monero completely.

The network will be a little bit rocky for the next 48 hours as bad (older) nodes are isolated and segregated off, and good nodes are deployed. I'm seeing around 40% of the nodes the DNS seeders connect to having already upgraded. Pools will still operate just fine, transactions will still go through just fine, the nodes that will suffer from flailing connectivity are the ones that have NOT upgraded, not those that have.

[fluffypony]

Can we have some data on the aftermath of the attack? I'm primarily interested in

- number of transactions done in a given timeframe,
- megabytes added as bloat,
- effect in transaction speed
- total cost for the attacker

If there is anything else you find important, please share.

We'll have a post-mortem later today

[perl]

The network will be a little bit rocky for the next 48 hours as bad (older) nodes are isolated and segregated off, and good nodes are deployed. I'm seeing around 40% of the nodes the DNS seeders connect to having already upgraded. Pools will still operate just fine, transactions will still go through just fine, the nodes that will suffer from flailing connectivity are the ones that have NOT upgraded, not those that have.

Yes i agree is verry bad patch. Without my patch my pool is broken not broken now ( lower efficiency ).

You make error. I not relay bad transaction and other node not greylisting my pool ( I not relay bad transaction )
I wait all other pool make update for remove patch .

My pool not break consensus off TX Fee.

I have to give miners the best performance possible, actualy is possible only with my patch.
You still want to include a pool perspective

You can explain , you have delete key P2P_STAT_TRUSTED_PUB_KEY ?
And what it does exactly?

[fluffypony]

Yes i agree is verry bad patch. Without my patch my pool is broken.

You make error. I not relay bad transaction and other node not greylisting my pool ( I not relay bad transaction )
I wait all other pool make update for remove patch .

My pool not break consensus off TX Fee.

None of the other pools are using your patch, nor are any of them reporting being "broken".

Your patch breaks the consensus network because it does not prevent malicious nodes from constantly pushing bad transactions by cutting them off. An attacker can spin up 50 ec2 instances and broadcast nonsense transactions (20kb transactions filled with random data) at you at a rate of tens of thousands a second. Because you're not disconnecting their connections, you will burn CPU time verifying the transactions. Even though you aren't relaying the malicious transactions, you are creating a trivial attack vector for someone to take your pool and any nodes that use this patch out of commission.

This patch is bad for you, bad for the network, and fixes an imaginary problem that does not exist.