<bitcoin-git>
[bitcoin] yancyribbens opened pull request #33701: test: add case where `TOTAL_TRIES` is exceeded yet solution remains (master...coin-grinder-iter-limit) https://github.com/bitcoin/bitcoin/pull/33701
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 246 seconds]
kevkevin has joined #bitcoin-core-dev
jonatack has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 256 seconds]
jonatack has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 252 seconds]
jonatack has quit [Ping timeout: 264 seconds]
kevkevin has joined #bitcoin-core-dev
Ademan has quit [Ping timeout: 265 seconds]
kevkevin has quit [Ping timeout: 264 seconds]
kevkevin has joined #bitcoin-core-dev
hacker4web3bitco has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 252 seconds]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 255 seconds]
cmirror has quit [Remote host closed the connection]
cmirror has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 256 seconds]
kevkevin has joined #bitcoin-core-dev
saturday- has joined #bitcoin-core-dev
Saturday7 has quit [Ping timeout: 265 seconds]
AaronvanW has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 255 seconds]
AaronvanW has quit [Ping timeout: 256 seconds]
AaronvanW has joined #bitcoin-core-dev
LainIwakura has quit [Quit: Client closed]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 256 seconds]
AaronvanW has quit [Remote host closed the connection]
<bitcoin-git>
bitcoincore.org/master c0922b2 azuchi: Add japanese translation for security advisories in 30.0
<bitcoin-git>
bitcoincore.org/master 74b528c merge-script: Merge bitcoin-core/bitcoincore.org#1194: Add japanese translation for secu...
<bitcoin-git>
[bitcoincore.org] fanquake merged pull request #1194: Add japanese translation for security advisories in 30.0 (master...ja-translate-security-advisories-30) https://github.com/bitcoin-core/bitcoincore.org/pull/1194
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 240 seconds]
l0rinc has joined #bitcoin-core-dev
l0rinc has quit [Ping timeout: 240 seconds]
kevkevin has joined #bitcoin-core-dev
AaronvanW has joined #bitcoin-core-dev
l0rinc has joined #bitcoin-core-dev
LainIwakura has joined #bitcoin-core-dev
AaronvanW has quit [Ping timeout: 246 seconds]
l0rinc has quit [Ping timeout: 240 seconds]
l0rinc has joined #bitcoin-core-dev
l0rinc has quit [Ping timeout: 256 seconds]
kevkevin has quit [Ping timeout: 246 seconds]
cstrm has quit [Quit: cstrm]
cstrm has joined #bitcoin-core-dev
AaronvanW has joined #bitcoin-core-dev
AaronvanW has quit [Ping timeout: 240 seconds]
enochazariah has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] maflcko opened pull request #33702: contrib: Remove brittle, confusing and redundant UTF8 encoding from Python IO (master...2510-everything-is-utf8) https://github.com/bitcoin/bitcoin/pull/33702
kevkevin has joined #bitcoin-core-dev
enochazariah has quit [Ping timeout: 250 seconds]
MapleStory has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 240 seconds]
<MapleStory>
Hey guys, so I was reading a bit about the debate for op_return on bitcointalk and I would like to just get a yes/no if what I concluded is correct: Basically the limit removal for op_return is more of an escape valve with less damage than anything, since people are already creating arbitrary data using the taproot method (that creates non
<MapleStory>
pruneable data, where op_return can prune data)
<MapleStory>
My only question is: is there ongoing active effort to combat the taproot "exploit", what can actually be done at the consensus level to make it that only scripts are actually allowed, not arbitrary data?
enochazariah has joined #bitcoin-core-dev
enochazariah has quit [Quit: Client closed]
AaronvanW has joined #bitcoin-core-dev
enochazariah has joined #bitcoin-core-dev
AaronvanW has quit [Ping timeout: 265 seconds]
Guest30 has joined #bitcoin-core-dev
Guest30 has quit [Client Quit]
enochazariah has quit [Quit: Client closed]
djschnei21 has joined #bitcoin-core-dev
enochazariah has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
djschnei21 has quit [Remote host closed the connection]
djschnei21 has joined #bitcoin-core-dev
djschnei21 has quit [Remote host closed the connection]
djschnei21 has joined #bitcoin-core-dev
<pinheadmz>
MapleStory you should ask this on bitcoin.stackexchange.com or look for similar questions
<pinheadmz>
but your context is basically correct about damage control
<pinheadmz>
its clearly up for debate but personlly I think 100% of bitcoin is "arbitrary data" that people use as money. so filtering anything is a sort of censorship that works against bitcoin
<MapleStory>
Wouldn't you agree that as a network, it *should not be the focus* to *make easily* posting arbitrary data though. I think I agree with you except for the fact that if you want to do non financial transactions it should be at the expense of big cost, then I'm fine with it
<MapleStory>
But yeah, I'm more interested for the fact of bloating the blockchain size if the taproot exploit way of posting cheap arbitrary data should be removed, if thats even possible
djschnei21 has quit [Ping timeout: 256 seconds]
<pinheadmz>
ideally, censorship of any kind is not possible on bitcoin
<pinheadmz>
and to be slightly more accurate, the real disaster is using unspendable outputs not taproot witness or taproot control block. blockchain size is already restricted by consensus but UTXO bloat is not restricted
<MapleStory>
I dont agree that censorship is not possible, its just at the expense at cost, if exploitative code paths are blocked so that you cant cheaply post arbitrary data then thats a fix to me, because it'd just cost you $ to do something the network *isnt focused around*. Yeah the unspendable outputs are an issue, but isn't it an issue that posting
<MapleStory>
arbitrary data as witness data an exploit since it has discounted fees?
<MapleStory>
Thanks I will read that
<pinheadmz>
exactly, witness data is discounted and always has been. that's why the v30 policy change is... not a big change.