cypherdoc (OP)
Legendary

Activity: 1764
Merit: 1009
|
 |
July 29, 2015, 06:59:39 PM |
|
i think this proves that miners are perfectly capable of handling bigger blocks as evidenced by the "no delays" in confirmation intervals. if anything i find it interesting that they get sped up to <10 min during these attacks. with bigger blocks, we'd clear out that mempool in an instant: 
|
|
|
|
|
cypherdoc (OP)
Legendary

Activity: 1764
Merit: 1009
|
 |
July 29, 2015, 07:00:39 PM |
|
|
|
|
|
|
cypherdoc (OP)
Legendary

Activity: 1764
Merit: 1009
|
 |
July 29, 2015, 07:02:02 PM |
|
clearing out the mempool quickly would solidify the attackers losses and gratify the previous tx validation work already done by all full nodes in the network.
|
|
|
|
|
cypherdoc (OP)
Legendary

Activity: 1764
Merit: 1009
|
 |
July 29, 2015, 07:05:32 PM |
|
notice how the extra fees paid by full blocks actually strengthened the mining hashrate during the last attacks. probably the extra revenue from tx fees encouraged miners to bring on more hashrate. that's a good thing and could actually be even better if they were allowed to harvest/clear all the additional fees in the bloated mempools: 
|
|
|
|
|
NewLiberty
Legendary

Activity: 1204
Merit: 1002
Gresham's Lawyer
|
 |
July 29, 2015, 07:09:03 PM |
|
i think this proves that miners are perfectly capable of handling bigger blocks as evidenced by the "no delays" in confirmation intervals. if anything i find it interesting that they get sped up to <10 min during these attacks. with bigger blocks, we'd clear out that mempool in an instant:  Well, no. Bigger blocks just make the "attacks" marginally more expensive. Individually, I could also swamp the mempool at any of the proposed sizes. The "attacks" are providing some funding, so I don't really mind them all that much. This tragedy of the commons is not quite so tragic as the UTXO set growth and chain size would be with a similar attack on larger blocks, especially if combined with a validation time attack (TX with many inputs and outputs in a tangled array). Very large blocks would be a much more vulnerable environment in which to conduct such an attack. We'll get to the point of ameliorating these vulnerabilities, and the right people are working on it. Patience... Bitcoin is still in beta, its so young. Lets give it the chance to grow up without breaking it along the way.
|
|
|
|
NewLiberty
Legendary

Activity: 1204
Merit: 1002
Gresham's Lawyer
|
 |
July 29, 2015, 07:12:00 PM |
|
notice how the extra fees paid by full blocks actually strengthened the mining hashrate during the last attacks. probably the extra revenue from tx fees encouraged miners to bring on more hashrate. that's a good thing and could actually be even better if they were allowed to harvest/clear all the additional fees in the bloated mempools:  Yes  More "attacks" please. Just not really big blocks yet. 1-3mb are ok. 8mb is too much right now (yes the miners are wrong, there's bad stuff they haven't seen yet). Getting blocks that take >10mins to validate is not a good thing. Fortunately with better code optimization, we may get that validation time down even more, as well as the other advances to make this safer. We'll get there.
|
|
|
|
cypherdoc (OP)
Legendary

Activity: 1764
Merit: 1009
|
 |
July 29, 2015, 07:32:48 PM |
|
i think this proves that miners are perfectly capable of handling bigger blocks as evidenced by the "no delays" in confirmation intervals. if anything i find it interesting that they get sped up to <10 min during these attacks. with bigger blocks, we'd clear out that mempool in an instant:  Well, no. Bigger blocks just make the "attacks" marginally more expensive. Individually, I could also swamp the mempool at any of the proposed sizes. The "attacks" are providing some funding, so I don't really mind them all that much. This tragedy of the commons is not quite so tragic as the UTXO set growth and chain size would be with a similar attack on larger blocks, especially if combined with a validation time attack (TX with many inputs and outputs in a tangled array). Very large blocks would be a much more vulnerable environment in which to conduct such an attack. We'll get to the point of ameliorating these vulnerabilities, and the right people are working on it. Patience... Bitcoin is still in beta, its so young. Lets give it the chance to grow up without breaking it along the way. so looking at the peak of the last attack ~40BTC per day worth of tx fees were harvested. let's say we go to 20MB blocks tomorrow. since real tx's only amount to ~500kB per block worth of data, you'd have to essentially fill the 20MB all by yourself and spend 20*40BTC=800BTC per day give or take. at $290/BTC that would equal $232000 per day. and then you'd have to sustain that to even dent the network; say for a month. that would cost you $7,000,000 for one month. you sure you can do that all by yourself? 
|
|
|
|
|
NewLiberty
Legendary

Activity: 1204
Merit: 1002
Gresham's Lawyer
|
 |
July 29, 2015, 07:36:30 PM |
|
i think this proves that miners are perfectly capable of handling bigger blocks as evidenced by the "no delays" in confirmation intervals. if anything i find it interesting that they get sped up to <10 min during these attacks. with bigger blocks, we'd clear out that mempool in an instant:  Well, no. Bigger blocks just make the "attacks" marginally more expensive. Individually, I could also swamp the mempool at any of the proposed sizes. The "attacks" are providing some funding, so I don't really mind them all that much. This tragedy of the commons is not quite so tragic as the UTXO set growth and chain size would be with a similar attack on larger blocks, especially if combined with a validation time attack (TX with many inputs and outputs in a tangled array). Very large blocks would be a much more vulnerable environment in which to conduct such an attack. We'll get to the point of ameliorating these vulnerabilities, and the right people are working on it. Patience... Bitcoin is still in beta, its so young. Lets give it the chance to grow up without breaking it along the way. so looking at the peak of the last attack ~40BTC per day worth of tx fees were harvested. let's say we go to 20MB blocks tomorrow. since real tx's only amount to ~500kB per block worth of data, you'd have to essentially fill the 20MB all by yourself and spend 20MB*40BTC=800BTC per day give or take. at $290/BTC that would equal $232000 per day. and then you'd have to sustain that to even dent the network; say for a month. that would cost you $7,000,000 for one month. you sure you can do that all by yourself?  Why would you doubt it? But in your example of 20MB, there are much easier and cheaper ways to DoS the network, as mentioned.
|
|
|
|
awemany
Newbie

Activity: 28
Merit: 0
|
 |
July 29, 2015, 07:36:56 PM |
|
1-3mb are ok. 8mb is too much right now (yes the miners are wrong, there's bad stuff they haven't seen yet). Getting blocks that take >10mins to validate is not a good thing.
I believe Gavin wants to limit TXN size to 100kiB at the same time the bigger block hard fork comes into effect. Shouldn't this very much remove your worries about an increase in blocksize? And, yes, I agree, faster validation is even better than putting another artificial limit into the code base.
|
|
|
|
|
iCEBREAKER
Legendary

Activity: 2156
Merit: 1073
Crypto is the separation of Power and State.
|
 |
July 29, 2015, 07:37:10 PM Last edit: July 29, 2015, 07:57:15 PM by iCEBREAKER |
|
The introduction of sidechains, LN and whatever other solutions is a complicated solution. It's also a solution motivated by a desire to fix a perceived economic issue, rather than sticking to the very simple issue at hand. It is the very opposite of what you are claiming to be important, that software should be kept simple.
That is a contradiction.
The simple solution is to remove the artificial cap. A cap that was put in place to prevent DDOS.
Your reference of CVE-2013-2292 is just distraction. It is a separate issue, one that exists now and would continue to exists with a larger block size.
Bloating Layer 1 is a complicated solution; scaling at Level 2+ is an elegant one. You still don't understand Tannenbaum's maxim. Its point isn't 'keep software simple FOREVER NO MATTER WHAT.' That is your flawed simpleton's interpretation. "Fighting features" means ensuring a positive trade-off in terms of security and reliability, instead of carelessly and recklessly heaping on additional functionality without the benefit of an adversarial process which tests their quality and overall impact. One does not simply "remove the artificial cap." You may have noticed some degree of controversy in regard to that proposal. Bitcoin is designed to strenuously resist (IE fight) hard forks. Perhaps you were thinking of WishGrantingUnicornCoin, which leaps into action the moment anyone has an idea and complies with their ingenious plan for whatever feature or change they desire. Like DoS, CVE-2013-2292, as an issue that exists now, is fairly successfully mitigated by the 1MB cap. It is not a separate concern because larger blocks exacerbate the problem in a superlinear manner. You don't get to advocate 8MB blocks, but then wave your hands around eschewing responsibility when confronted with the immediate entailment of purposefully constructed 8MB tx taking 64 times longer to process than a 1MB one. The issue is intrinsic to larger blocks, which is why Gavin proposed a 100k max tx size be married to any block size increase. Fully parsed, what you are claiming is The simple solution is to remove the artificial cap hard fork Bitcoin. Do you realize how naive that makes you look?
|
██████████ ██████████████████ ██████████████████████ ██████████████████████████ ████████████████████████████ ██████████████████████████████ ████████████████████████████████ ████████████████████████████████ ██████████████████████████████████ ██████████████████████████████████ ██████████████████████████████████ ██████████████████████████████████ ██████████████████████████████████ ████████████████████████████████ ██████████████ ██████████████ ████████████████████████████ ██████████████████████████ ██████████████████████ ██████████████████ ██████████ Monero
|
| "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
|
| | |
|
|
|
cypherdoc (OP)
Legendary

Activity: 1764
Merit: 1009
|
 |
July 29, 2015, 07:50:22 PM |
|
i think this proves that miners are perfectly capable of handling bigger blocks as evidenced by the "no delays" in confirmation intervals. if anything i find it interesting that they get sped up to <10 min during these attacks. with bigger blocks, we'd clear out that mempool in an instant:  Well, no. Bigger blocks just make the "attacks" marginally more expensive. Individually, I could also swamp the mempool at any of the proposed sizes. The "attacks" are providing some funding, so I don't really mind them all that much. This tragedy of the commons is not quite so tragic as the UTXO set growth and chain size would be with a similar attack on larger blocks, especially if combined with a validation time attack (TX with many inputs and outputs in a tangled array). Very large blocks would be a much more vulnerable environment in which to conduct such an attack. We'll get to the point of ameliorating these vulnerabilities, and the right people are working on it. Patience... Bitcoin is still in beta, its so young. Lets give it the chance to grow up without breaking it along the way. so looking at the peak of the last attack ~40BTC per day worth of tx fees were harvested. let's say we go to 20MB blocks tomorrow. since real tx's only amount to ~500kB per block worth of data, you'd have to essentially fill the 20MB all by yourself and spend 20MB*40BTC=800BTC per day give or take. at $290/BTC that would equal $232000 per day. and then you'd have to sustain that to even dent the network; say for a month. that would cost you $7,000,000 for one month. you sure you can do that all by yourself?  Why would you doubt it? b/c i'm assuming it would be cost prohibitive for you? and pretty much anyone else i might add altho i'm sure you'd argue not for a gvt; which actually might be true which is why i advocate NO LIMIT as that would throw a huge amount of uncertainty as to just how successfully one could jack the mempool in that scenario as it removes user disruption and thus greatly increases the financial risk ANY attacker would be subject o. But in your example of 20MB, there are much easier and cheaper ways to DoS the network, as mentioned.
i know; your normal sized convoluted multi-input block that would have to, btw, be constructed as a non-standard tx block that is self mined by a miner which makes it unlikely b/c you'd have to believe a miner would be willing to risk his reputation and financial viability by attacking the network in such a way which has repercussions. that's also good news in that it removes a regular spammer or gvt attacker (non-miner) from doing this. and finally, that type of normal sized but convoluted validation block will propagate VERY slowly which risks orphaning which makes that attack also unlikely.
|
|
|
|
|
cypherdoc (OP)
Legendary

Activity: 1764
Merit: 1009
|
 |
July 29, 2015, 07:52:01 PM |
|
1-3mb are ok. 8mb is too much right now (yes the miners are wrong, there's bad stuff they haven't seen yet). Getting blocks that take >10mins to validate is not a good thing.
I believe Gavin wants to limit TXN size to 100kiB at the same time the bigger block hard fork comes into effect. Shouldn't this very much remove your worries about an increase in blocksize? And, yes, I agree, faster validation is even better than putting another artificial limit into the code base. he's backed off the 100kB tx limit in deference to limiting the #sigops and simplifying the hashing process. for details, someone provide the link to his ML post.
|
|
|
|
|
awemany
Newbie

Activity: 28
Merit: 0
|
 |
July 29, 2015, 07:58:50 PM |
|
he's backed off the 100kB tx limit in deference to limiting the #sigops and simplifying the hashing process. for details, someone provide the link to his ML post.
Thanks for the update! The effect on transaction validation time should be essentially the same, though... it should be enough to make 'overly complicated' blocks impossible for the time being.
|
|
|
|
|
|
brg444
|
 |
July 29, 2015, 08:03:16 PM |
|
|
"I believe this will be the ultimate fate of Bitcoin, to be the "high-powered money" that serves as a reserve currency for banks that issue their own digital cash." Hal Finney, Dec. 2010
|
|
|
iCEBREAKER
Legendary

Activity: 2156
Merit: 1073
Crypto is the separation of Power and State.
|
 |
July 29, 2015, 08:08:23 PM |
|
- #rekt
>It was _well_ .... understood that the users of Bitcoin would wish to protect its decenteralization by limiting the size of the chain to keep it verifyable on small devices.No it wasn't. That is something you invented yourself much later. "Small devices" isn't even defined anywhere, so there can't have been any such understanding. Hearn #rekt confirmed: In the above statement you're outright backwards-- there was a clear expectation that all who ran nodes would mine. Gmax nailed this, Hearn's understanding (only miners run nodes) of Satoshi's original design (all nodes are miners) is completely bungled. Now its Frap.doc's turn to get rekt: Piling every proof-of-work quorum system in the world into one dataset doesn't scale.
Bitcoin users might get increasingly tyrannical about limiting the size of the chain so it's easy for lots of users and small devices.

|
██████████ ██████████████████ ██████████████████████ ██████████████████████████ ████████████████████████████ ██████████████████████████████ ████████████████████████████████ ████████████████████████████████ ██████████████████████████████████ ██████████████████████████████████ ██████████████████████████████████ ██████████████████████████████████ ██████████████████████████████████ ████████████████████████████████ ██████████████ ██████████████ ████████████████████████████ ██████████████████████████ ██████████████████████ ██████████████████ ██████████ Monero
|
| "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
|
| | |
|
|
|
thezerg
Legendary

Activity: 1246
Merit: 1018
|
 |
July 29, 2015, 08:21:55 PM |
|
anyone concerned about the BTC lower high?
|
|
|
|
|
cypherdoc (OP)
Legendary

Activity: 1764
Merit: 1009
|
 |
July 29, 2015, 08:22:56 PM |
|
Now its Frap.doc's turn to get rekt: Piling every proof-of-work quorum system in the world into one dataset doesn't scale.
Bitcoin users might get increasingly tyrannical about limiting the size of the chain so it's easy for lots of users and small devices.
 i find it amusing that you bash Satoshi on the one hand but when you find a morsel quote of his (which you've misread) you latch onto it as gospel. if you read the actual link you posted, Satoshi was talking about how Bitcoin should not be combined with BitDNS. he's not even talking about tx's. he wanted them to be separate with their own fates. he also drew an extreme example of how BitDNS might want to include other huge datasets while Bitcoin might want to keep it small as an example of how the decision making might diverge btwn the two. not that Bitcoin users wanted to keep a small blockchain.
|
|
|
|
|
|
brg444
|
 |
July 29, 2015, 08:28:21 PM |
|
Now its Frap.doc's turn to get rekt: Piling every proof-of-work quorum system in the world into one dataset doesn't scale.
Bitcoin users might get increasingly tyrannical about limiting the size of the chain so it's easy for lots of users and small devices.
 i find it amusing that you bash Satoshi on the one hand but when you find a morsel quote of his (which you've misread) you latch onto it as gospel. if you read the actual link you posted, Satoshi was talking about how Bitcoin should not be combined with BitDNS. he's not even talking about tx's. he wanted them to be separate with their own fates. he also drew an extreme example of how BitDNS might want to include other huge datasets while Bitcoin might want to keep it small as an example of how the decision making might diverge btwn the two. not that Bitcoin users wanted to keep a small blockchain. Bitcoin users might get increasingly tyrannical about limiting the size of the chain so it's easy for lots of users and small devices.
 Are you really trying to spin this one again?
|
"I believe this will be the ultimate fate of Bitcoin, to be the "high-powered money" that serves as a reserve currency for banks that issue their own digital cash." Hal Finney, Dec. 2010
|
|
|
cypherdoc (OP)
Legendary

Activity: 1764
Merit: 1009
|
 |
July 29, 2015, 08:31:43 PM |
|
Greg has made it abundantly clear that he is a Bear on Bitcoin. he should step down as a core dev. and what's this about him not thinking Bitcoin can be used on small devices? smartphones are KEY to Bitcoin's long term success.
|
|
|
|
|
|
brg444
|
 |
July 29, 2015, 08:34:45 PM |
|
Greg has made it abundantly clear that he is a Bear on Bitcoin. he should step down as a core dev. and what's this about him not thinking Bitcoin can be used on small devices? smartphones are KEY to Bitcoin's long term success.
Yeah... maybe you need to read this again. What did I tell you about putting words in people's mouth. "A bear on Bitcoin"  So much non sense!
|
"I believe this will be the ultimate fate of Bitcoin, to be the "high-powered money" that serves as a reserve currency for banks that issue their own digital cash." Hal Finney, Dec. 2010
|
|
|
|