@theZerg: so cool! Looking forward to a report on how the bigger blocks go!!
You only think it's crazy because you're not in the business of selling solutions that to a problem that only exists if Bitcoin is broken.But intentionally making 0-conf less secure seems pure crazy to me!
Yes. CPFP is simply smarter miner logic in choosing transactions while still staying within the parameters satoshi laid out. RBF is a fundamental change in P2P behavior, yes miners could do it today, but they don't because they understand doing so weakens bitcoin and the value of their investments.CPFP definitely seems like something a profit maximizing miner is going to implement themselves anyway as a policy, simply to make rational decisions about tx inclusion vis-a-vis fee density.
RBF rubs me the wrong way at this point, because while it's simply a policy rule that any miner could implement, barring grotesque UX schemes based on functioning persistently at Qmax, it seems unsettling to make something akin to an attack such a priority to actually be a feature of the reference client.
First the Peter_R effect, now the Gavin_A effect:That's the biggest BUY signal I've seen in years.
That the market sees it exactly the same way that we do here tells me that not all is lost with regards to humanity, its average intelligence and sheeple following idiotsFirst the Peter_R effect, now the Gavin_A effect:
I have changed my mind about zeroconf, and I am now for protecting it. With sufficiently large blocks, no change is necessary. We will have to remember that it will always have some risk, and that it will always be up to the discretion of the miners to choose a newer transaction in case of double spend.I've never understood the benefit of replace-by-fees (RBF) if child-pays-for-parent (CPFP) is available. People argue that CPFP only allows the receiver to speed up the TX but this is not true: in (nearly) all cases, the TX would have a change-to-self output. The user would just re-spend this change output back to himself with a high fee.
The only thing I can see that RBF does that CPFP doesn't is RBF makes double-spending 0-conf TXs easier. But intentionally making 0-conf less secure seems pure crazy to me!
To me that post is Todd intuitively sensing danger and wanting to get over to the right side before TSHTF for miniblockists.I wholeheartedly agree with Peter Todd (it's been a while since last time it happened, fwiw).
Furthermore this comment fits perfectly with BU base principles.
The thing about 0-conf txn is that they are ugly design- and security-wise but they actually work.I have changed my mind about zeroconf, and I am now for protecting it. With sufficiently large blocks, no change is necessary. We will have to remember that it will always have some risk, and that it will always be up to the discretion of the miners to choose a newer transaction in case of double spend.
Right, I think what we are seeing happen in the debate is the unstoppable force of the mindset you explain here meeting the immovable object of "market takes care of things in ways no one can preordain or conceive of"/"perfect is enemy of good"/"common sense beats ivory tower narrow thinking". Two contradictory things that are Always True™ exist at once, with different people reaching different conclusions as to which really allows for exceptions and which does not.Because, well, we all learned in IT security that only the paranoid enemies-everywhere mindset works and is the 'right' approach. Because miners will screw other people over because you cannot rely on their goodwill. Ever.
They work not because of design but because of economics.The thing about 0-conf txn is that they are ugly design- and security-wise but they actually work.