> It is not possible to guarantee that a transaction will be mined within N
blocks irrespective of fees. It is vulnerable if a project's security
relies on it, and should fix it by changing the security assumptions.
It's not possible to guarantee that any funds can be moved ever. But we
still
Hi cndm1,
> If you see a "lack of basic options" and no one has opened a pull request for
> it, it may be for two reasons.
The basic option to disable all RBF policies in a node's mempool if required
was removed in [PR #16171][1]. No one has opened a pull request to revert this
because most
alicexbt wrote:
> I do not have issues with multiple RBF policies being tried out and full-rbf
> being one of them. My disagreements are with rationale, lack of basic options
> in Bitcoin Core to employ/disable different RBF policies and a few arguments
> made in support for full-rbf. Whether
