Quote from: iCEBREAKER on July 08, 2015, 07:49:57 PM

Quote from: cypherdoc on July 08, 2015, 07:12:30 PM

the ongoing spam shows clearly that all full nodes are handling the traffic just fine. We were told that they would crash and burn from overloaded memory if we were foolhardy enough to implement Gavin's arbitrary, rushed, poorly-researched plan for 20MB blocks.

^Fixted for you.

Quote from: cypherdoc on July 08, 2015, 07:12:30 PM

The real shame is that they've been forced to do ask the validation and store it in mempool waiting for blocks that never come because of the 1MB cap. What a waste but it shows that the capacity of the network is far higher than we've been told.

If you look at the stream of full blocks going by, to me I see miners begging to be able to process bigger blocks to clear their mempools. That would force the spammers losses and eventually kill him.

Mempool is full of tx waiting to be (slowly, thanks to completely unoptimized Createnewblock) processed into new blocks.

The blocks are then propagated (slowly thanks to limited/expensive upstream bandwidth), and (eventually, thanks to slow ECDSA and quadratic scaling) validated by the receivers.

Validation is not done in mempool, as gmax and others have tried to explain to you, without success and at the cost of your remaining credibility.

Quote from: cypherdoc on July 08, 2015, 07:30:38 PM

The network will upgrade as a result of new user growth that the spammer can no longer disrupt. Meanwhile, the spammer gets taken out to the wood shed and gets raped. She won't be coming back.

The network does not distinguish between new users and old users. More users will include more spammers.

Wow, you've really gone off the deep end today. Consider a vacation, or therapy. It's not healthy for a man of your considerable age/education/income/stature to talk like a poorly disciplined young teen on their X-Box Halo chat.

All that slowness you're referring to results in the spam being deleted after 24 hours allowing recycling of the fees while still disrupting usage.