Damus
𝕞ptf · 68w
Fuck Bitcoin Core Wizards. https://ibb.co/gLP20Yks
Bounty · 68w
What fucking universe is this
DagzTagz · 68w
Standardness will die
jgbtc · 68w
Miners decide what's in blocks, node runners decide what goes in their own mempools. I won't run software that takes away my autonomy. If there's a reason to remove the limit then convince me to change the setting. Forcing this is a big red flag.
btcttombola · 68w
Yes, as here too. nevent1qvzqqqqqqypzqycfjjnu6447dhwyf0t9lkmyucev3grk6tcvxa6w5ptf63kxl6lmqyghwumn8ghj7vf5xqhxvdm69e5k7tcprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0qy88wumn8ghj7mn0wvhxcmmv9uqzpyav36qmjpa2fmrt774vth7scmnwcwwfv6jv8j7puqztrdurrkhwsagxdh
negr0 · 68w
De que lado estas Odell, me gustaría saber
Jamin ☦️🏴󠁧󠁢󠁥󠁮󠁧󠁿 BIP110 · 68w
Your mempool should be as configurable as possible. OP_RETURN should be 42 bytes by default as it was originally.
Judge Hardcase · 68w
It doesn't seem to me that perverse incentives are fixed by adding a voluntary "polite" option. As long as it's cheaper for degens to take the impolite avenue, then it's pure hopium to think that's not exactly what they should be expected to continue to do. That being said, I don't believe I have ...
nostrich · 68w
"i am a large miner providing an out-of-band transaction processing service. by preventing consensus valid transactions from propagating in the mempool it creates a class of transaction that my competition is unable or unwilling to benefit from. this increases my return on the same amount of hashrat...
⚡₿it₿y₿it⚡ · 68w
Why impose it instead of giving users the option to enable it?
Jo ₿ · 68w
https://gist.github.com/instagibbs/c436110890ab25aa9997b13c2270d5ce https://blossom.primal.net/10b41b0adf892abb9e0400f011d2a29bfcad7a41e05d0a1db8001d39fbcfff49.png
Jo ₿ · 68w
https://gist.github.com/instagibbs/c436110890ab25aa9997b13c2270d5ce https://blossom.primal.net/a6677582e8b5d29d69a730929727cb8da6348614c1966c30b648531ff0c4a42e.jpg
Jo ₿ · 68w
nevent1qqsx94fmhplf30cvw4048tvpzlsknm69lp9g9na5wphg84xaj8mpcsqpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5u6vud2
sudocarlos · 68w
Couldn't spammers still use the witness field for putting arbitrary data on chain? And isn't it cheaper to use the witness field to do that? I don't think either points made under "The 80-byte ceiling is now counter-productive" address these questions and I'm not sure if I'm right so I'll post here.
₿oniz23⚡️🏴‍☠️🇮🇹 · 68w
I'm very doubtful which side to be on. It's a very complex discussion
btcttombola · 68w
A little reminder : nevent1qvzqqqqqqypzq40rg0n93yrn6vf0e2esqa0yk35px6dk23v7lum20ch7f7yq4ngmqqswr7sla434duatjp4m89grvs3zanxug05pzj04asxmv4rngvyv04sws3ew4
spyhunter · 68w
Hopefully more people start not using Core...
Dustin Dannenhauer · 68w
Just curious, the more data in the op_return, the higher the transaction fee because vbytes are higher? And doesn’t more users of the Bitcoin network lead to higher fees, higher demand for Bitcoin, and more money for miners, and higher Bitcoin prices when denominated in USD? Does this all boil do...
Pepe López · 68w
Do you know who owns GitHub? Yes, GitHub is owned by Microsoft. I never liked that for the Bitcoin reference software. Since it seems inevitable that arbitrary data could be stored on the Bitcoin blockchain, what better way to do it being the repository for the software itself? And of course, it wou...