Jorge Timón [ARCHIVE] on Nostr: 📅 Original date posted:2015-08-12 📝 Original message:I believe all concerns ...
📅 Original date posted:2015-08-12
📝 Original message:I believe all concerns I've read can be classified in the following groups:
> 1) Potential indirect consequence of rising fees.
- Lowest fee transactions (currently free transactions) will become
more unreliable.
- People will migrate to competing systems (PoW altcoins) with lower fees.
> 2) Software problem independent of a concrete block size that needs to
> be solved anyway, often specific to Bitcoin Core (ie other
> implementations, say libbitcoin may not necessarily share these
> problems).
- Bitcoin Core's mempool is unbounded in size and can make the program
crash by using too much memory.
- There's no good way to increase the fee of a transaction that is
taking too long to be mined without the "double spending" transaction
with the higher fee being blocked by most nodes which follow Bitcoin
Core's default policy for conflicting spends replacements (aka "first
seen" replacement policy).
I have started with the 3 concerns that I read more often, but please
suggest more concerns for these categories and suggest other
categories if you think there's more.
Published at
2023-06-07 15:46:38Event JSON
{
"id": "72fa0ebf98b1638245bcdda873d7c1efa62472e1b77c85c5a48bbe9603b83673",
"pubkey": "498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84",
"created_at": 1686152798,
"kind": 1,
"tags": [
[
"e",
"ed48e8b49c34ef64a5a6814f13a41de999188447a7a574d6553030c329674671",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2015-08-12\n📝 Original message:I believe all concerns I've read can be classified in the following groups:\n\n\u003e 1) Potential indirect consequence of rising fees.\n\n- Lowest fee transactions (currently free transactions) will become\nmore unreliable.\n- People will migrate to competing systems (PoW altcoins) with lower fees.\n\n\u003e 2) Software problem independent of a concrete block size that needs to\n\u003e be solved anyway, often specific to Bitcoin Core (ie other\n\u003e implementations, say libbitcoin may not necessarily share these\n\u003e problems).\n\n- Bitcoin Core's mempool is unbounded in size and can make the program\ncrash by using too much memory.\n- 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\nI have started with the 3 concerns that I read more often, but please\nsuggest more concerns for these categories and suggest other\ncategories if you think there's more.",
"sig": "8abf4bf7716ab9200141218fa882648aa9e0eda3251af85ea342ca6beca8ca3242e1a7eff5a6aa8e29bbc1f89d2d7a649ebc2ce2e17c29097be7af809ca1d7b1"
}