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

[David Latapie]

We'll have a post-mortem later today

I first thought this was a joke, but it is not, the term exists.

[1714468354]

1714468354

[1714468354]

1714468354

[1714468354]

1714468354

[1714468354]

1714468354

[Jojatekok]

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.

I'm not a pool operator, but if I know right, you should just:

• Shut down the daemon and wallet applications
• Remove '%AppData%\bitmonero\poolstate.bin' in order to clear your TX mempool
• Compile Monero's code from GitHub
• Replace the old 'bitmonerod.exe' and 'simplewallet.exe' with the produced ones
• Set your minimum TX fees to 0.1 XMR in your node-cryptonote-pool configuration file, by replacing
  "transferFee": 5000000000
  with
  "transferFee": 100000000000
• Start the daemon and wallet applications again

[perl]

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

[Quanttek]

I'm not a pool operator, but if I know right, you should just:

• Shut down the daemon and wallet applications
• Remove '%AppData%\bitmonero\poolstate.bin' in order to clear your TX mempool
• Compile Monero's code from GitHub
• Replace the old 'bitmonerod.exe' and 'simplewallet.exe' with the produced ones
• Set your minimum TX fees to 0.1 XMR in your node-cryptonote-pool configuration file, by replacing
  "transferFee": 5000000000
  with
  "transferFee": 100000000000
• Start the daemon and wallet applications again

Yes, that's how you update the pool. It should not take longer than 5 minutes

[fluffypony]

We'll have a post-mortem later today

I first thought this was a joke, but it is not, the term exists.

Yep, it's not my first time on the merry-go-round;)

[fluffypony]

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

There were some concerns in another thread that it could give Bytecoin the ability to use debug commands to get an overview of the network. Whilst we have already audited this part of the code and determined this is not the case, we felt it prudent to zero the key out for the moment so as to allay concerns.

[BitcoinForumator]

And how does a regular person (user) update? Just overwrite the old bitmonerod.exe and simplewallet.exe with new ones? And keep the old stuff like .keys, .txts and wallets in the same directory?

[netmonk]

exact !

[akula999]

Think something is wrong with Moneropool.com
My pending balance has been the same for 3 hours. However, there were a number of blocks found.

[smooth]

And how does a regular person (user) update? Just overwrite the old bitmonerod.exe and simplewallet.exe with new ones? And keep the old stuff like .keys, .txts and wallets in the same directory?

Yes the new node and wallet are all you need. No changes needed to anything else.

[owlcatz]

And how does a regular person (user) update? Just overwrite the old bitmonerod.exe and simplewallet.exe with new ones? And keep the old stuff like .keys, .txts and wallets in the same directory?

Thats' what i did. Seems to work ok , but I see a ton of this in bitmonerod -


2014-Aug-24 11:23:53.166318 [P2P1][122.245.180.120:18080 OUT]Tx verification fai
led, dropping connection
2014-Aug-24 11:23:53.166318 [P2P6]ERROR ..\..\src\cryptonote_core\tx_pool.cpp:91
 transaction fee is not enough: 0.010000000000, minumim fee: 0.100000000000

Wait - what's the current fee, is it really .10 as it states in the errors? Thanks!

[cxboyminer]

I haven't touched monero for ages... but have you updated your monerod to 0.8.8.2?

Please upgrade to 0.8.8.2, else your transactions will not be mined due to a temporary fee increase to prevent spam attacks

[tacotime]

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

allows remote command execution of some debugging commands

[owlcatz]

Think something is wrong with Moneropool.com
My pending balance has been the same for 3 hours. However, there were a number of blocks found.

i think i'm seeing the same thing ... anyone know the pool op?

[tacotime]

Think something is wrong with Moneropool.com
My pending balance has been the same for 3 hours. However, there were a number of blocks found.

i think i'm seeing the same thing ... anyone know the pool op?

minimum non-dust output on the network is now 0.10 XMR on the latest daemon, so your payouts may take longer. i can tell from the pool's blocks that he's running the latest daemon, so just be patient.

[aminorex]

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

I thought it would be funny!

Rolling on the floor laughing certainly means I found it funny 

The ne plus ultra is LOLSMOOMN

[akula999]

Think something is wrong with Moneropool.com
My pending balance has been the same for 3 hours. However, there were a number of blocks found.

i think i'm seeing the same thing ... anyone know the pool op?

minimum non-dust output on the network is now 0.10 XMR on the latest daemon, so your payouts may take longer. i can tell from the pool's blocks that he's running the latest daemon, so just be patient.

Thanks Taco and you gave me an idea - TACO Time!

[sammy007]

And how does a regular person (user) update? Just overwrite the old bitmonerod.exe and simplewallet.exe with new ones? And keep the old stuff like .keys, .txts and wallets in the same directory?

Update executables, remove poolstate.bin and p2pstate.bin then start.

[fluffypony]

Thanks Taco and you gave me an idea - TACO Time!

You need to watch this: http://vimeo.com/90127834

[akula999]

OMG - TACO Town!!