[XMR] Monero - A secure, private, untraceable cryptocurrency - page 1536.

tacotime

legendary

Activity: 1484

Merit: 1005

Quote from: owlcatz on August 24, 2014, 11:42:04 AM

Quote from: akula999 on August 24, 2014, 11:16:13 AM

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.

owlcatz

legendary

Activity: 3570

Merit: 1959

Quote from: akula999 on August 24, 2014, 11:16:13 AM

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

legendary

Activity: 1484

Merit: 1005

Quote from: perl on August 24, 2014, 08:00:38 AM

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

cxboyminer

hero member

Activity: 896

Merit: 500

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

Quote

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

owlcatz

legendary

Activity: 3570

Merit: 1959

Quote from: BitcoinForumator on August 24, 2014, 11:07:42 AM

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!

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: BitcoinForumator on August 24, 2014, 11:07:42 AM

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.

akula999

hero member

Activity: 509

Merit: 500

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.

netmonk

full member

Activity: 219

Merit: 100

exact !

BitcoinForumator

legendary

Activity: 1120

Merit: 1000

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?

fluffypony

donator

Activity: 1274

Merit: 1060

GetMonero.org / MyMonero.com

Quote from: perl on August 24, 2014, 08:00:38 AM

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.

fluffypony

donator

Activity: 1274

Merit: 1060

GetMonero.org / MyMonero.com

Quote from: David Latapie on August 24, 2014, 07:39:11 AM

Quote from: fluffypony on August 24, 2014, 07:05:09 AM

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;)

Quanttek

member

Activity: 93

Merit: 10

Quote from: Jojatekok on August 24, 2014, 07:56:17 AM

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

perl

legendary

Activity: 1918

Merit: 1190

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

Jojatekok

sr. member

Activity: 264

Merit: 250

Quote from: fluffypony on August 24, 2014, 07:26:23 AM

Quote from: perl on August 24, 2014, 07:18:29 AM

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

David Latapie

hero member

Activity: 658

Merit: 503

Monero Core Team

Quote from: fluffypony on August 24, 2014, 07:05:09 AM

We'll have a post-mortem later today

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

fluffypony

donator

Activity: 1274

Merit: 1060

GetMonero.org / MyMonero.com

Quote from: perl on August 24, 2014, 07:18:29 AM

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.

perl

legendary

Activity: 1918

Merit: 1190

Quote from: fluffypony on August 24, 2014, 07:04:32 AM

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

donator

Activity: 1274

Merit: 1060

GetMonero.org / MyMonero.com

Quote from: AlexGR on August 24, 2014, 06:26:06 AM

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

fluffypony

donator

Activity: 1274

Merit: 1060

GetMonero.org / MyMonero.com

Quote from: perl on August 24, 2014, 05:41:07 AM

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.

David Latapie

hero member

Activity: 658

Merit: 503

Monero Core Team

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.

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