sipa commented 9 hours ago
•It's perfectly possible to keep accepting 0-conf transactions, if you believe they are safe for your use case. Opt-in RBF sets a non-maximum nSequence value, which causes many providers to already consider the transaction non-standard for the purpose of accepting 0-conf.
•As a customer, you can choose to set opt-in RBF, and thus lose the ability to get your payment accepted before confirmation, but with the ability to easily change the fee afterwards or combine the transaction with others.
•As a miner, the rational behaviour is to take the transaction with the highest fee (even for non opt-in cases). If you don't, another miner can.
And, no, opt-in RBF is not theft. It's indicating that you're not sure whether what you're submitting is the final form of the transaction. This is the exact semantics that nSequence had since the earliest version of Bitcoin.
Yeah, cause you can surely tell that this satisfied his objection lol. It gets better... (He knows his $$ comes from the users, not the devs...)
wangchun commented 8 hours ago: "@jonasschnelli Could you please tell me which wallet has been ready to warn users for potential RBF transactions? What the average user without much Bitcoin knowledge can do when he/she see this warning?"
wangchun commented 8 hours ago: "So you admit nobody has yet been ready for opt-in RBF but deploy it in the next release IMHO this is no better than force a hard fork without consensus" (Bolded by my decision)
Wang Chun has gone up in my estimation. He is playing the Coretards for the chumps that they are. Unbelievable. There isn't a single principle among the lot of them.
where's inca's giraffe eating popcorn gif?