amovfx_ has quit [Remote host closed the connection]
amovfx_ has joined #bitcoin-core-dev
amovfx_ has quit [Ping timeout: 268 seconds]
amovfx_ has joined #bitcoin-core-dev
SpellChecker has quit [Remote host closed the connection]
SpellChecker has joined #bitcoin-core-dev
amovfx_ has quit [Ping timeout: 250 seconds]
yanmaani2 has quit [Remote host closed the connection]
yanmaani2 has joined #bitcoin-core-dev
amovfx_ has joined #bitcoin-core-dev
amovfx_ has quit [Ping timeout: 260 seconds]
amovfx_ has joined #bitcoin-core-dev
halosghost has quit [Quit: WeeChat 3.6]
amovfx_ has quit [Ping timeout: 246 seconds]
<ariard>
so i've been reached out offline by a zero-conf application operator finally waking up about the new `mempoolfullrbf` setting in upcoming release, raising awareness about the number and ranges of zero-conf services affected, i invited to share their argumentation publicly on the ML asap and recalled that release candidates were already tagged
<ariard>
good news, we have people actually caring about release candidates
amovfx_ has joined #bitcoin-core-dev
sudoforge has quit [Ping timeout: 265 seconds]
bitdex has quit [Remote host closed the connection]
bitdex has joined #bitcoin-core-dev
amovfx_ has quit [Ping timeout: 260 seconds]
_apex_ has quit [Ping timeout: 265 seconds]
<luke-jr>
ariard: you mean unconfirmed?
<luke-jr>
zero-conf = Lightning
_apex_ has joined #bitcoin-core-dev
<luke-jr>
ariard: in any case, there's no significant change in 24.x
<luke-jr>
it's just an option that's been available in Knots (and even by default) for years
<luke-jr>
not even default in Core
_apex_ has quit [Ping timeout: 268 seconds]
amovfx_ has joined #bitcoin-core-dev
SpellChecker has quit [Remote host closed the connection]
SpellChecker has joined #bitcoin-core-dev
_apex_ has joined #bitcoin-core-dev
hsmiths has quit [Quit: Connection closed for inactivity]
<bitcoin-git>
[bitcoin] hebasto closed pull request #18980: build: Decouple clientversion.cpp from the git repo (master...0515-decouple) https://github.com/bitcoin/bitcoin/pull/18980
Guyver2 has left #bitcoin-core-dev [Closing Window]
AaronvanW has joined #bitcoin-core-dev
amovfx_ has quit [Ping timeout: 265 seconds]
Guest8786 has joined #bitcoin-core-dev
amovfx_ has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] jonatack opened pull request #26257: script, test: python linter fixups and updates (master...2022-10-python-linter-fixups-and-updates) https://github.com/bitcoin/bitcoin/pull/26257
amovfx_ has quit [Ping timeout: 268 seconds]
ghost43 has quit [Ping timeout: 258 seconds]
realies has quit [Quit: Ping timeout (120 seconds)]
ghost43 has joined #bitcoin-core-dev
bitdex has quit [Quit: = ""]
Guest5034 has joined #bitcoin-core-dev
Guest5034 has quit [Client Quit]
AaronvanW has quit [Remote host closed the connection]
amovfx_ has joined #bitcoin-core-dev
amovfx_ has quit [Ping timeout: 250 seconds]
realies has joined #bitcoin-core-dev
_apex_ has joined #bitcoin-core-dev
SpellChecker has quit [Quit: bye]
brunoerg has joined #bitcoin-core-dev
AaronvanW has joined #bitcoin-core-dev
SpellChecker has joined #bitcoin-core-dev
_apex_ has quit [Quit: WeeChat 2.6]
realies has quit [Quit: Ping timeout (120 seconds)]
realies has joined #bitcoin-core-dev
sudoforge has joined #bitcoin-core-dev
Guest75 has joined #bitcoin-core-dev
Guest75 has quit [Client Quit]
Guest8786 has quit [Quit: Client closed]
amovfx_ has joined #bitcoin-core-dev
amovfx_ has quit [Ping timeout: 260 seconds]
amovfx_ has joined #bitcoin-core-dev
amovfx_ has quit [Ping timeout: 268 seconds]
Guest59 has joined #bitcoin-core-dev
Guest59 has quit [Client Quit]
gleb0 has quit [Ping timeout: 248 seconds]
jonatack has quit [Quit: WeeChat 3.6]
<bitcoin-git>
[gui] jonatack opened pull request #673: Use fallback value for Version and User Agent during peer connection (master...2022-09-display-fallback-for-gui-peers-version-and-user-agent) https://github.com/bitcoin-core/gui/pull/673
amovfx_ has quit [Remote host closed the connection]
amovfx_ has joined #bitcoin-core-dev
johnny96 has quit [Quit: Client closed]
amovfx_ has quit [Remote host closed the connection]
amovfx_ has joined #bitcoin-core-dev
amovfx__ has joined #bitcoin-core-dev
amovfx_ has quit [Ping timeout: 268 seconds]
amovfx_ has joined #bitcoin-core-dev
amovfx__ has quit [Ping timeout: 260 seconds]
amovfx__ has joined #bitcoin-core-dev
amovfx___ has joined #bitcoin-core-dev
amovfx_ has quit [Ping timeout: 260 seconds]
amovfx_ has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
halosghost is now known as hg
MatrixBot123 has quit [Ping timeout: 244 seconds]
amovfx__ has quit [Ping timeout: 268 seconds]
amovfx___ has quit [Ping timeout: 268 seconds]
amovfx__ has joined #bitcoin-core-dev
amovfx_ has quit [Ping timeout: 268 seconds]
sudoforge has joined #bitcoin-core-dev
amovfx_ has joined #bitcoin-core-dev
amovfx__ has quit [Ping timeout: 268 seconds]
<bitcoin-git>
[bitcoin] aureleoules opened pull request #26260: rpc: Set best header after reconsiderblock (master...2022-10-26245-fix-reconsiderblock) https://github.com/bitcoin/bitcoin/pull/26260
MatrixBot123 has joined #bitcoin-core-dev
sipsorcery has joined #bitcoin-core-dev
ghost43 has joined #bitcoin-core-dev
turdcoin has joined #bitcoin-core-dev
amovfx_ has quit [Remote host closed the connection]
vasild has joined #bitcoin-core-dev
Guyver2 has joined #bitcoin-core-dev
kexkey has joined #bitcoin-core-dev
amovfx_ has joined #bitcoin-core-dev
andrewtoth_ has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] brunoerg opened pull request #26261: p2p: return `std::vectorCNetAddr` in `LookupIntern` (master...2022-10-cleanup-netbase) https://github.com/bitcoin/bitcoin/pull/26261
yashraj has joined #bitcoin-core-dev
SpellChecker has quit [Remote host closed the connection]
SpellChecker has joined #bitcoin-core-dev
Talkless has joined #bitcoin-core-dev
amovfx has quit [Ping timeout: 268 seconds]
sipsorcery has quit [Ping timeout: 260 seconds]
amovfx has joined #bitcoin-core-dev
sipsorcery has joined #bitcoin-core-dev
<ariard>
luke-jr: yep, applications processing zero-conf transactions as valid payments. well apparently you have folks with a different qualification than what is a significant change for them and with another appreciation of the option being already available in Knots
AaronvanW has quit [Remote host closed the connection]
yashraj has quit []
amovfx__ has joined #bitcoin-core-dev
amovfx___ has joined #bitcoin-core-dev
amovfx_ has quit [Ping timeout: 250 seconds]
amovfx__ has quit [Ping timeout: 250 seconds]
vasild has quit [Remote host closed the connection]
<luke-jr>
ariard: zero-conf/Lightning is unaffected
<luke-jr>
ariard: an _option_ has been added to ignore the RBF opt-out bit; that option has always been available to users in the form of switching to Knots.
<sipa>
luke-jr: That's all true, but irrelevant I think without significant uptake. Rightfully or not, people may be concerned about the fact that it's an option in Bitcoin Core, as it can be interpreted as a move towards getting that as a common policy on the network/
<sipa>
I think it was inevitable that such a response comes, and I don't think it should affect much of what we're doing.
<luke-jr>
if they don't like it, they can turn it off or fork Core to remove it
<luke-jr>
it's not like non-RBF was ever an effective method of security
<bitcoin-git>
[bitcoin] instagibbs opened pull request #26265: POLICY: Relax MIN_STANDARD_TX_NONWITNESS_SIZE to 65 non-witness bytes (master...relax_too_small_tx) https://github.com/bitcoin/bitcoin/pull/26265
<sipa>
Again, I agree, but that's relevant relevant to people complaining about the risk of it being widely adopted on the network.
<sipa>
To be clear, I think this concern is misguided - all I'm saying is that saying "you and/or everyone always have had and have the ability to run other policy" isn't a counterargument to it.