{"type":"rich","version":"1.0","author_name":"npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8","author_url":"https://nostr.ae/npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-08-14\n📝 Original message:On Sat, Aug 15, 2015 at 12:35 AM, Jorge Timón \u003cjtimon at jtimon.cc\u003e wrote:\n\u003e On Wed, Aug 12, 2015 at 1:21 PM, Venzen Khaosan \u003cvenzen at mail.bihthai.net\u003e wrote:\n\u003e\u003e 4) General, undefined fear that something bad is going to happen when\n\u003e\u003e nodes choke up on a backlog of transactions.\n\u003e\u003e - - no specific symptoms are pointed at but presumably there is\n\u003e\u003e \"pre-traumatic stress\" at play.\n\u003e\u003e - - Bitcoin-based businesses are going to lose money, customers and\n\u003e\u003e potentially fail\n\u003e\u003e - - people will flee Bitcoin for another cryptocoin and Bitcoin will be\n\u003e\u003e left in the corner, collecting dust and memories of it will fade as\n\u003e\u003e SuperCoin with its big blocks becomes all things to all people.\n\u003e\n\u003e I believe thisbelongs in 2, not really sure if 2.1 or 2.2 since it's\n\u003e related to both.\n\nI was tempted to add it as a sub-sub-risk in both, since both things\nneed to be solved before that stop being a concern. But they may be\nmore things to do to solve that so I'm listing it as a separate\nsub-risk in 2:\n\n2.3) Big list of valid unconfirmed transactions\n\nresulting list:\n\n1) Potential indirect consequence of rising fees.\n\n1.1) Lowest fee transactions (currently free transactions) will become\nmore unreliable.\n1.2) People will migrate to competing systems (PoW altcoins) with lower fees.\n1.3) Layer 2 settlements become more expensive\n1.4) Less usage than we could have had with a bigger size\n1.4.1) More regulation pressure\n1.4.2) Not enough fees when subsidy is lower\n\n2) Software problem independent of a concrete block size that needs to\nbe solved anyway, often specific to Bitcoin Core (ie other\nimplementations, say libbitcoin may not necessarily share these\nproblems).\n\n2.1) Bitcoin Core's mempool is unbounded in size and can make the program\ncrash by using too much memory.\n\n2.2) There's no good way to increase the fee of a transaction that is\ntaking too long to be mined without the \"double spending\" transaction\nwith the higher fee being blocked by most nodes which follow Bitcoin\nCore's default policy for conflicting spends replacements (aka \"first\nseen\" replacement policy).\n\n2.3) Big list of valid unconfirmed transactions"}