Bitcoin Forum
December 11, 2016, 10:23:01 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Poll
Question: Will you support Gavin's new block size limit hard fork of 8MB by January 1, 2016 then doubling every 2 years?
1.  yes
2.  no

Pages: « 1 ... 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 [1427] 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 ... 1560 »
  Print  
Author Topic: Gold collapsing. Bitcoin UP.  (Read 1808623 times)
cypherdoc
Legendary
*
Offline Offline

Activity: 1764



View Profile
July 08, 2015, 08:08:33 PM
 #28521

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.

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.


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.
1481451781
Hero Member
*
Offline Offline

Posts: 1481451781

View Profile Personal Message (Offline)

Ignore
1481451781
Reply with quote  #2

1481451781
Report to moderator
1481451781
Hero Member
*
Offline Offline

Posts: 1481451781

View Profile Personal Message (Offline)

Ignore
1481451781
Reply with quote  #2

1481451781
Report to moderator
1481451781
Hero Member
*
Offline Offline

Posts: 1481451781

View Profile Personal Message (Offline)

Ignore
1481451781
Reply with quote  #2

1481451781
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481451781
Hero Member
*
Offline Offline

Posts: 1481451781

View Profile Personal Message (Offline)

Ignore
1481451781
Reply with quote  #2

1481451781
Report to moderator
1481451781
Hero Member
*
Offline Offline

Posts: 1481451781

View Profile Personal Message (Offline)

Ignore
1481451781
Reply with quote  #2

1481451781
Report to moderator
1481451781
Hero Member
*
Offline Offline

Posts: 1481451781

View Profile Personal Message (Offline)

Ignore
1481451781
Reply with quote  #2

1481451781
Report to moderator
iCEBREAKER
Legendary
*
Offline Offline

Activity: 1512


Crypto is the separation of Power and State.


View Profile WWW
July 08, 2015, 08:17:33 PM
 #28522

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.

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.

What network disruption are we talking about here?

What usage "disruption" are we talking about here?  I fear you may be exaggerating again, as is your wont.

Fees rising from ~2 to ~5 cents is mere adjustment, not disruption.  If you're using a fixed-fee wallet/service, that's not BTC's fault.

The spam being deleted is a good thing.  It doesn't need to (and shouldn't) be included on the One True Eternal Blockchain, to be slowly propagated and validated and stored by every node until the end of Bitcoin Time.

The 24-hour deletion/resubmission cycle gives mine/pool ops/devs time to adjust their spam filters accordingly.

The difference between bad and well-developed digital cash will determine whether we have a dictatorship or a real democracy.  David Chaum 1996
Fungibility provides privacy as a side effect.  Adam Back 2014
"Monero" : { Private - Auditable - 100% Fungible - Flexible Blocksize - Wild & Free® - Intro - Wallets - Podcats - Roadmap - Dice - Blackjack - Github - Android }


Bitcoin is intentionally designed to be ungovernable and governance-free.  luke-jr 2016
Blocks must necessarily be full for the Bitcoin network to be able to pay for its own security.  davout 2015
Blocksize is an intentionally limited resource, like the 21e6 BTC limit.  Changing it degrades the surrounding economics, creating negative incentives.  Jeff Garzik 2013


"I believed @Dashpay instamine was a bug & not a feature but then read: https://bitcointalk.org/index.php?topic=421615.msg13017231#msg13017231
I'm not against people making money, but can't support questionable origins."
https://twitter.com/Tone_LLT/status/717822927908024320


The raison d'être of bitcoin is trustlessness. - Eric Lombrozo 2015
It is an Engineering Requirement that Bitcoin be “Above the Law”  Paul Sztorc 2015
Resiliency, not efficiency, is the paramount goal of decentralized, non-state sanctioned currency -Jon Matonis 2015

Bitcoin is intentionally designed to be ungovernable and governance-free.  luke-jr 2016

Technology tends to move in the direction of making surveillance easier, and the ability of computers to track us doubles every eighteen months. - Phil Zimmerman 2013

The only way to make software secure, reliable, and fast is to make it small. Fight Features. - Andy Tanenbaum 2004

"Hard forks cannot be co
Peter R
Legendary
*
Offline Offline

Activity: 938



View Profile
July 08, 2015, 08:50:15 PM
 #28523

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

Does CreateNewBlock currently take longer to execute if there are more TXs in a miner's mempool to pick from?  If so, this would add credence to Cypherdoc's hunch that miner's are producing more empty blocks when mempool swells.  


Run Bitcoin Unlimited (www.bitcoinunlimited.info)
iCEBREAKER
Legendary
*
Offline Offline

Activity: 1512


Crypto is the separation of Power and State.


View Profile WWW
July 08, 2015, 10:00:20 PM
 #28524

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

Does CreateNewBlock currently take longer to execute if there are more TXs in a miner's mempool to pick from?  If so, this would add credence to Cypherdoc's hunch that miner's are producing more empty blocks when mempool swells.

 Undecided  I think gmax already (indirectly?) answered your question here:

I expect correlation between empty blocks and mempool size-- though not for the reason you were expecting here: Createnewblock takes a long time, easily as much as 100ms,  as it sorts the mempool multiple times-- and no one has bothered optimizing this at all becuase the standard mining software will mine empty blocks while it waits for the new transaction list. So work generated in the first hundred milliseconds or so after a new block will usually be empty. (Of course miners stay on the initial work they got for a much loonger time than 100ms).

This is, however, unrelated to SPV mining-- in that case everything is still verified. As many people have pointed out (even in this thread) the interesting thing here isn't empty blocks, its the mining on an invalid chain.

but I'll attempt to unpack and contextualize his response...  Tongue


CNB execution time depends on CPU/RAM/SSD speed and mempool size, both of which are adjustable user defined values.

The theoretical "more empty blocks when mempool swells" effect only dominates when the previous block validates faster than the "100ms" maximum CNB takes to make the next one; according to gmax avg. validation times are "16-37sec" (for f2p/ant).

IOW, CNB while 'slow' in the relative sense it is unoptimized, is much (>1600-3700 times) faster than avg. blocks' verification times.

So, (if I've not failed spectacularly in my amateur hour gmax impersonation) Frap.doc's hunch only applies after empty or nearly empty, very small, tiny little blocks.

As block become larger (non-tiny/empty), verification time increases quadratically.  Absent any threshold effects, I'd expect CNB performance to be ~linear with mempool size (which, again, is adjustable, unlike previous blocksize).

Larger blocks are thus self-defeating (IE encounter negative marginal return) because their quadratically-scaling verification time greatly exceeds CNB's (perhaps linearly-scaling but in any case much faster) execution time, ensuring more empty blocks are produced exactly when network throughput/load needs non-empty blocks the most.

The difference between bad and well-developed digital cash will determine whether we have a dictatorship or a real democracy.  David Chaum 1996
Fungibility provides privacy as a side effect.  Adam Back 2014
"Monero" : { Private - Auditable - 100% Fungible - Flexible Blocksize - Wild & Free® - Intro - Wallets - Podcats - Roadmap - Dice - Blackjack - Github - Android }


Bitcoin is intentionally designed to be ungovernable and governance-free.  luke-jr 2016
Blocks must necessarily be full for the Bitcoin network to be able to pay for its own security.  davout 2015
Blocksize is an intentionally limited resource, like the 21e6 BTC limit.  Changing it degrades the surrounding economics, creating negative incentives.  Jeff Garzik 2013


"I believed @Dashpay instamine was a bug & not a feature but then read: https://bitcointalk.org/index.php?topic=421615.msg13017231#msg13017231
I'm not against people making money, but can't support questionable origins."
https://twitter.com/Tone_LLT/status/717822927908024320


The raison d'être of bitcoin is trustlessness. - Eric Lombrozo 2015
It is an Engineering Requirement that Bitcoin be “Above the Law”  Paul Sztorc 2015
Resiliency, not efficiency, is the paramount goal of decentralized, non-state sanctioned currency -Jon Matonis 2015

Bitcoin is intentionally designed to be ungovernable and governance-free.  luke-jr 2016

Technology tends to move in the direction of making surveillance easier, and the ability of computers to track us doubles every eighteen months. - Phil Zimmerman 2013

The only way to make software secure, reliable, and fast is to make it small. Fight Features. - Andy Tanenbaum 2004

"Hard forks cannot be co
Odalv
Legendary
*
Offline Offline

Activity: 1064



View Profile
July 08, 2015, 10:10:31 PM
 #28525

Spammer only spends money 1x during lifetime, but miner has to keep bigger disk-space forever (2 hard disc consume more electricity than single one)

OK.  Provide me with your estimates for the following (and explain how you arrived at your numbers) and I'll update my table using your numbers:

1.  The cost per node to store 1 GB of additional blockchain data for 5 years, assume the outputs are spent.
2.  The cost per node to store 1 GB of additional blockchain data for 5 years, assuming the outputs are unspent.


I want to say. (English is not my mother tongue)

The more adoption the more spammers.  ( if only 0.1% is malicious then it is 1,000,000 spammers for every 1,000,000,000 adopters )
The more full nodes the more upgrade of whole network will cost.

=> result: increasing block size can kill bitcoin
 b/c
 a) spamming is cheaper (goes to zero)
 b) and mining costs more (goes to infinity)
iCEBREAKER
Legendary
*
Offline Offline

Activity: 1512


Crypto is the separation of Power and State.


View Profile WWW
July 08, 2015, 10:27:05 PM
 #28526

I want to say. (English is not my mother tongue)

The more adoption the more spammers.  ( if only 0.1% is malicious then it is 1,000,000 spammers for every 1,000,000,000 adopters )
The more full nodes the more upgrade of whole network will cost.

=> result: increasing block size can kill bitcoin

That makes sense.  English is my mother tongue, but I can't explain it any more clearly than this:

Quote

The difference between bad and well-developed digital cash will determine whether we have a dictatorship or a real democracy.  David Chaum 1996
Fungibility provides privacy as a side effect.  Adam Back 2014
"Monero" : { Private - Auditable - 100% Fungible - Flexible Blocksize - Wild & Free® - Intro - Wallets - Podcats - Roadmap - Dice - Blackjack - Github - Android }


Bitcoin is intentionally designed to be ungovernable and governance-free.  luke-jr 2016
Blocks must necessarily be full for the Bitcoin network to be able to pay for its own security.  davout 2015
Blocksize is an intentionally limited resource, like the 21e6 BTC limit.  Changing it degrades the surrounding economics, creating negative incentives.  Jeff Garzik 2013


"I believed @Dashpay instamine was a bug & not a feature but then read: https://bitcointalk.org/index.php?topic=421615.msg13017231#msg13017231
I'm not against people making money, but can't support questionable origins."
https://twitter.com/Tone_LLT/status/717822927908024320


The raison d'être of bitcoin is trustlessness. - Eric Lombrozo 2015
It is an Engineering Requirement that Bitcoin be “Above the Law”  Paul Sztorc 2015
Resiliency, not efficiency, is the paramount goal of decentralized, non-state sanctioned currency -Jon Matonis 2015

Bitcoin is intentionally designed to be ungovernable and governance-free.  luke-jr 2016

Technology tends to move in the direction of making surveillance easier, and the ability of computers to track us doubles every eighteen months. - Phil Zimmerman 2013

The only way to make software secure, reliable, and fast is to make it small. Fight Features. - Andy Tanenbaum 2004

"Hard forks cannot be co
gmaxwell
Staff
Legendary
*
Offline Offline

Activity: 2030



View Profile
July 08, 2015, 11:26:59 PM
 #28527

OK.  Provide me with your estimates for the following (and explain how you arrived at your numbers) and I'll update my table using your numbers:
1.  The cost per node to store 1 GB of additional blockchain data for 5 years, assume the outputs are spent.
2.  The cost per node to store 1 GB of additional blockchain data for 5 years, assuming the outputs are unspent.
I may be missing the context as this thread is high volume and I've not read any of the backlog...

But for a full verifying node, the on-going cost cost of 1GB of additional transactions with all outputs spent is 0; all the cost related to that 1GB of data is related to the bandwidth to get it to you and the verification cost, and for short term storage until its burried, after that it need not be stored.
The cost for unspent is some non-zero number which depends on your estimation of storage costs.


Does CreateNewBlock currently take longer to execute if there are more TXs in a miner's mempool to pick from?  If so, this would add credence to Cypherdoc's hunch that miner's are producing more empty blocks when mempool swells.  
Yep, I already pointed that out to you specifically! It's superlinear in the mempool size (well, ignoring caching)  But thats unrelated to f2pool/antpool and the other SPV miners, as they're not ever calling createnewblock in that case, as they're mining without even validating.   One can mine on a validated chain with no transactions while waiting for createnewblock (which is what eligius does, for example).  I also pointed out that this is trivially optimizable, but no one has bothered previously.

tvbcof
Legendary
*
Offline Offline

Activity: 1988


View Profile
July 08, 2015, 11:38:03 PM
 #28528

...
I may be missing the context as this thread is high volume and I've not read any of the backlog...

I wonder if I can get you to touch on my question here if you could:

  https://bitcointalk.org/index.php?topic=68655.msg11817437#msg11817437


iCEBREAKER
Legendary
*
Offline Offline

Activity: 1512


Crypto is the separation of Power and State.


View Profile WWW
July 09, 2015, 12:04:40 AM
 #28529

Does CreateNewBlock currently take longer to execute if there are more TXs in a miner's mempool to pick from?  If so, this would add credence to Cypherdoc's hunch that miner's are producing more empty blocks when mempool swells.  
Yep, I already pointed that out to you specifically! It's superlinear in the mempool size (well, ignoring caching)  But thats unrelated to f2pool/antpool and the other SPV miners, as they're not ever calling createnewblock in that case, as they're mining without even validating.   One can mine on a validated chain with no transactions while waiting for createnewblock (which is what eligius does, for example).  I also pointed out that this is trivially optimizable, but no one has bothered previously.

Wait, how is an empty block created without calling createnewblock?  Is there a createemptyblock thingy or what?

The difference between bad and well-developed digital cash will determine whether we have a dictatorship or a real democracy.  David Chaum 1996
Fungibility provides privacy as a side effect.  Adam Back 2014
"Monero" : { Private - Auditable - 100% Fungible - Flexible Blocksize - Wild & Free® - Intro - Wallets - Podcats - Roadmap - Dice - Blackjack - Github - Android }


Bitcoin is intentionally designed to be ungovernable and governance-free.  luke-jr 2016
Blocks must necessarily be full for the Bitcoin network to be able to pay for its own security.  davout 2015
Blocksize is an intentionally limited resource, like the 21e6 BTC limit.  Changing it degrades the surrounding economics, creating negative incentives.  Jeff Garzik 2013


"I believed @Dashpay instamine was a bug & not a feature but then read: https://bitcointalk.org/index.php?topic=421615.msg13017231#msg13017231
I'm not against people making money, but can't support questionable origins."
https://twitter.com/Tone_LLT/status/717822927908024320


The raison d'être of bitcoin is trustlessness. - Eric Lombrozo 2015
It is an Engineering Requirement that Bitcoin be “Above the Law”  Paul Sztorc 2015
Resiliency, not efficiency, is the paramount goal of decentralized, non-state sanctioned currency -Jon Matonis 2015

Bitcoin is intentionally designed to be ungovernable and governance-free.  luke-jr 2016

Technology tends to move in the direction of making surveillance easier, and the ability of computers to track us doubles every eighteen months. - Phil Zimmerman 2013

The only way to make software secure, reliable, and fast is to make it small. Fight Features. - Andy Tanenbaum 2004

"Hard forks cannot be co
Peter R
Legendary
*
Offline Offline

Activity: 938



View Profile
July 09, 2015, 12:19:04 AM
 #28530

OK.  Provide me with your estimates for the following (and explain how you arrived at your numbers) and I'll update my table using your numbers:
1.  The cost per node to store 1 GB of additional blockchain data for 5 years, assume the outputs are spent.
2.  The cost per node to store 1 GB of additional blockchain data for 5 years, assuming the outputs are unspent.
I may be missing the context as this thread is high volume and I've not read any of the backlog...

But for a full verifying node, the on-going cost cost of 1GB of additional transactions with all outputs spent is 0; all the cost related to that 1GB of data is related to the bandwidth to get it to you and the verification cost, and for short term storage until its burried, after that it need not be stored.
The cost for unspent is some non-zero number which depends on your estimation of storage costs.

This thread can be hard to follow if you're not following it all the time!  

The question was in reference to a debate I was having with Odalv about these "order of magnitude" estimates shown in this table.  I was suggesting that, under the conditions considered in the table, it is cheaper for miners to write the spam to the Blockchain and more costly for the spammer, than continually rejecting it:



Does CreateNewBlock currently take longer to execute if there are more TXs in a miner's mempool to pick from?  If so, this would add credence to Cypherdoc's hunch that miner's are producing more empty blocks when mempool swells.  
Yep, I already pointed that out to you specifically! It's superlinear in the mempool size (well, ignoring caching)  But thats unrelated to f2pool/antpool and the other SPV miners, as they're not ever calling createnewblock in that case, as they're mining without even validating.   One can mine on a validated chain with no transactions while waiting for createnewblock (which is what eligius does, for example).  

Sorry, yes I know you explained that.  The point I'm trying to make is that if CreateNewBlock is super-linear in mempool size, then it would not be surprising to see more empty blocks (what Cypher was calling "defensive blocks") when mempool swells (the miners are mining on an empty block for longer while waiting for CreateNewBlock to finish).  This was Cypher's point from the very beginning that many people, including myself, were suggesting was probably not the case!  

Furthermore, how can f2pool/antpool mine a non-empty block without calling createnewblock?

Run Bitcoin Unlimited (www.bitcoinunlimited.info)
Adrian-x
Legendary
*
Offline Offline

Activity: 1330



View Profile
July 09, 2015, 12:24:26 AM
 #28531

Spammer only spends money 1x during lifetime, but miner has to keep bigger disk-space forever (2 hard disc consume more electricity than single one)

OK.  Provide me with your estimates for the following (and explain how you arrived at your numbers) and I'll update my table using your numbers:

1.  The cost per node to store 1 GB of additional blockchain data for 5 years, assume the outputs are spent.
2.  The cost per node to store 1 GB of additional blockchain data for 5 years, assuming the outputs are unspent.



I'm sorry, I have no estimates. I know that bloat-chain is not solution  There are better solutions how to organize blockchain.

My full node just crashed ... all data are lost ... downloading 6 years 25 weeks.  ... hmm I hope that it is only me and there will remain some copy of blockchain. :-)  (not joking)

your data management systems need updating if you lost the data. Bitcoin is a $3B network and if you dont have an invested interest in keeping the blockchain to prove you own X coin or care enough to manage the responsibility you shouldn't be dictating how we should use it. not everyone who can't backup data or doesn't want to should be running a node. I have friends who dont trust digital photos because they trust paper copies more. I'm surprised to find you fit the profile.

I also think you're not weighting the cost and benefits correctly, the cost of 2 hard disc consuming more electricity than single one, is an inconsequential cost at the scale of executing this same attack with an 8MB block. (hell its inconsequential at the cost of the attack on the 1MB block.)

limiting block space is not going to save anyone except you a little bandwidth because you dont back up.


Thank me in Bits 12MwnzxtprG2mHm3rKdgi7NmJKCypsMMQw
solex
Legendary
*
Offline Offline

Activity: 1078


100 satoshis -> ISO code


View Profile
July 09, 2015, 01:25:48 AM
 #28532

I just want to highlight the comments here from bitcoin-dev today, which seem to indicate that these spamming attacks would have been 5.5x more expensive if a dust threshold software change had not been made. Perhaps there are deeper insights someone else has on this...?

Quote
16:53   wangchun   why can those spam get confirmed. 0.00001 BTC vout below dust threshold right?
16:54   phantomcircuit   wangchun, iirc the dust threshold is 546 satoshis
16:54   wangchun   not 5460 satoshis? changed?
16:54   aschildbach   wangchun: Yes it was cut by 10 a few months ago.

cypherdoc
Legendary
*
Offline Offline

Activity: 1764



View Profile
July 09, 2015, 02:12:12 AM
 #28533

The point I'm trying to make is that if CreateNewBlock is super-linear in mempool size, then it would not be surprising to see more empty blocks (what Cypher was calling "defensive blocks") when mempool swells (the miners are mining on an empty block for longer while waiting for CreateNewBlock to finish).  This was Cypher's point from the very beginning that many people, including myself, were suggesting was probably not the case!  

that is exactly what i was saying w/o knowing anything about CNB.  it was just intuitive that constructing a new block would take longer for a large mempool so i deduced that a miner might decide "f*ck it" that he doesn't want to not only spend additional time validating a large incoming block but also not want to spend additional time creating a large new block so instead just automatically switch to 0 block mining upon arrival of a large block.  the thing none of us anticipated was that he would not validate that incoming large block at all and switch to SPV mining while >50% of the network would also be SPV mining (Discus, Antpool, BTCGuild) and trigger an invalid SPV longest chain.

that's some wild shit going on.

given this newly recognized scenario, i still conclude however that this is all a result of the block size limit being hit continuously by attacking spammers and secondarily intentionally causing a bloated mempool which then causes these unanticipated defensive strategies and more intentionally, user disruption.
cypherdoc
Legendary
*
Offline Offline

Activity: 1764



View Profile
July 09, 2015, 02:55:42 AM
 #28534

I just want to highlight the comments here from bitcoin-dev today, which seem to indicate that these spamming attacks would have been 5.5x more expensive if a dust threshold software change had not been made. Perhaps there are deeper insights someone else has on this...?

Quote
16:53   wangchun   why can those spam get confirmed. 0.00001 BTC vout below dust threshold right?
16:54   phantomcircuit   wangchun, iirc the dust threshold is 546 satoshis
16:54   wangchun   not 5460 satoshis? changed?
16:54   aschildbach   wangchun: Yes it was cut by 10 a few months ago.

i don't think it really matters, does it?

since most of the mined blocks are filled with real demand trying to get into blocks with or without spamming, the only difference being that with spamming the real demand has to pay significantly higher fees to get in, the cost to fill up the rest of the block with spam is minimal as is the minimal cost to bloat the mempool to extraordinary levels (94K 0confs as i write).  i say minimal cost for the mempool b/c most of it gets turned over after 24h deletion allowing that spam to be recycled w/o having to pay.
cypherdoc
Legendary
*
Offline Offline

Activity: 1764



View Profile
July 09, 2015, 03:59:27 AM
 #28535

all the yearly silver and mining stocks have that sick top left to bottom right chart configuration. this is a horrible leading indicator for both gold and stocks:

silver futures:



SLW:



PAAS:



silverbox's GPL:

TPTB_need_war
Sr. Member
****
Offline Offline

Activity: 420


View Profile
July 09, 2015, 04:08:36 AM
 #28536

When miner's mempool exceeds block size by some backlog factor, they need to send out a message to the peers they are connected to saying "don't propagate transactions to me with smaller than X fee per kilobyte until further notice". This will mitigate the impact that spam-that-can-never-be-added-to-a-block can have on the network, but it won't entirely eliminate it, because as the mempool backlog reduces, the miner will need to back off the notice to some unknown lower fee threshold. The miner could guess but it will never be 100% accurate. So spam will get verified and rejected. But perhaps those estimates can be close enough that the losses the spammers takes in fees for transactions it sends that do get into a block will be greater than the gains it values from effective spamming (what ever those gains are  Huh). Appears to me the issue can be fixed.

Afaik, the reason incoming transactions are verified before it is known whether they will be in a new block, is because it is considered spam to propagate (send out again to another peer) invalid transactions that would be rejected and never appear in a block.

cypherdoc
Legendary
*
Offline Offline

Activity: 1764



View Profile
July 09, 2015, 04:27:03 AM
 #28537

When miner's mempool exceeds block size by some backlog factor, they need to send out a message to the peers they are connected to saying "don't propagate transactions to me with smaller than X fee per kilobyte until further notice". This will mitigate the impact that spam-that-can-never-be-added-to-a-block can have on the network, but it won't entirely eliminate it, because as the mempool backlog reduces, the miner will need to back off the notice to some unknown lower fee threshold. The miner could guess but it will never be 100% accurate. So spam will get verified and rejected. But perhaps those estimates can be close enough that the losses the spammers takes in fees for transactions it sends that do get into a block will be greater than the gains it values from effective spamming (what ever those gains are  Huh). Appears to me the issue can be fixed.

Afaik, the reason incoming transactions are verified before it is known whether they will be in a new block, is because it is considered spam to propagate (send out again to another peer) invalid transactions that would be rejected and never appear in a block.

gmax already told us to use minrelaytxfee.
tvbcof
Legendary
*
Offline Offline

Activity: 1988


View Profile
July 09, 2015, 04:47:58 AM
 #28538

Spammer only spends money 1x during lifetime, but miner has to keep bigger disk-space forever (2 hard disc consume more electricity than single one)

OK.  Provide me with your estimates for the following (and explain how you arrived at your numbers) and I'll update my table using your numbers:

1.  The cost per node to store 1 GB of additional blockchain data for 5 years, assume the outputs are spent.
2.  The cost per node to store 1 GB of additional blockchain data for 5 years, assuming the outputs are unspent.


I'm sorry, I have no estimates. I know that bloat-chain is not solution  There are better solutions how to organize blockchain.

My full node just crashed ... all data are lost ... downloading 6 years 25 weeks.  ... hmm I hope that it is only me and there will remain some copy of blockchain. :-)  (not joking)

Don't worry.  According to Mike Hearn Bitcoin can survive just fine with 4 or 6 (forgot which) copies of the blockchain worldwide.


domob
Legendary
*
Offline Offline

Activity: 939


View Profile WWW
July 09, 2015, 05:28:52 AM
 #28539

Yes, but 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. Not true.

Wait, wasn't that exactly Hearn's main argument in his "the sky is falling if we don't increase the blocksize" blog post?  So why do you see the fact that it did not prove true so far as supporting your position of increasing the block size?

Use your Namecoin identity as OpenID: https://nameid.org/
Donations: 1domobKsPZ5cWk2kXssD8p8ES1qffGUCm | NMC: NCdomobcmcmVdxC5yxMitojQ4tvAtv99pY
BM-GtQnWM3vcdorfqpKXsmfHQ4rVYPG5pKS | GPG 0xA7330737
Peter R
Legendary
*
Offline Offline

Activity: 938



View Profile
July 09, 2015, 05:37:00 AM
 #28540

Yes, but 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. Not true.

Wait, wasn't that exactly Hearn's main argument in his "the sky is falling if we don't increase the blocksize" blog post?  So why do you see the fact that it did not prove true so far as supporting your position of increasing the block size?

It provided evidence that the network can handle the increased load, and it confirmed that people do get frustrated by the confirmation delays. 

Run Bitcoin Unlimited (www.bitcoinunlimited.info)
Pages: « 1 ... 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 [1427] 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 ... 1560 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!