mempool question... what are the pinning vectors to be aware of for a SIGHASH_SINGLE | ANYONECANPAY input that's signed as RBFable? is being griefed by the RBF "must beat absolute fee" attacker-escalation the only thing you have to worry about?
jonatack1 has quit [Ping timeout: 246 seconds]
sipsorcery has quit [Ping timeout: 256 seconds]
brunoerg has quit 
Guest99 has joined #bitcoin-core-dev
Guest9942 has joined #bitcoin-core-dev
Talkless has quit [Quit: Konversation terminated!]
bitcoin/master 89c1491 furszy: wallet: if only have one output type, don't perform "mixed" coin selection
bitcoin/master ba47a4b Andrew Chow: Merge bitcoin/bitcoin#26668: wallet: if only have one output type, don't p...
[bitcoin] achow101 merged pull request #26668: wallet: if only have one output type, don't perform "mixed" coin selection (master...2022_wallet_double_coin_selection) https://github.com/bitcoin/bitcoin/pull/26668
hg has joined #bitcoin-core-dev
jonatack1 has joined #bitcoin-core-dev
jamesob: iirc, descendant junk where the adversary attaches a chain of transactions with low-feerate, high-fee from a new bip143 input/ouptut pair. Under BIP125 rule 3, your replacement candidate will be rejected
I advised him it's "constrained" to rule#3 pinning pretty much