- This topic has 1 reply, 1 voice, and was last updated 2 months, 1 week ago by
KAX1107.
- Posts
Retro_pexI saw a lot of turmoil about this new feature on the GitHub of bitcoin.
Could you give me your opinion on this function, what it implies and the problem it solves.
Other things I would like to know what you think about the fact that the developers released an update even if it was rather controversial by the community.
Thank you in advance.
KAX1107>give me your opinion on this function
It’s off by default. If and only if nodes were to manually set mempoolfullrbf=1 in their bitcoin.conf (I have) does this change take effect.
>it was rather controversial by the community
It was not. It was by one company in particular misleading users about zero confs and also misleading them about this update. Mempool and mempool policies are individually managed by each node, there’s no common mempool. Accepting a transaction sitting in mempool was always dangerous, can and has been double spent. Not actually double spent because it was never confirmed but has been double spent because of people accepting unconfirmed transactions. This change IF it’s adopted by nodes makes it too risky to accept zero conf transactions and removes the assumption that miners act rationally which is just a situation where you’re trusting people. The whole point of Bitcoin is to remove trust.
- You must be logged in to reply to this topic.