Open cbeams opened 6 years ago
There are discussions about improving CPFP in bitcoin core. Might be more useful as fees increase but unclear how bisq could use it.
Bitcoin Core 25.1 has been released. I don't see anything that require our attention there.
The new bitcoin core has some changes to how it handles rbf. This might affect Bisq users but I don't think it warrants an upgrade.
Cycle 52 report
Bitcoin Core 25.1 has been released. I don't see anything that require our attention there.
It would be not the first time that security fixes are disclosed later. I think we should upgrade to all new point releases.
@Emzy you have a point. Perhaps more urgency is needed to upgrade after point releases. Version 26.0 is out now and should be considered.
A responsible disclosure of a bug in pre Core 22 that affects LN users has been announced. Bisq doesn't use LN but I still think it makes sense to make sure to run version 22 or later.
There is work on a . release for bitcoin core. Could signify something. Otherwise nothing to report.
Bitcoin core version 26.1 has been released. Probably be worth upgrading to.
A free relay attack has been disclosed, https://gnusha.org/pi/bitcoindev/Zfg%2F6IZyA%2FiInyMx@petertodd.org/. I don't if this would be realistic issue to do anything about at the moment for bisq nodes.
I am unable to perform this role going forward. It might be best to just retire the role completely.
Best practice is to keep running the latest version of bitcoin core, which all node operators can do on their own. Main issue is to keep a look out for planned changes that would retire bitcoinj support.
@cbeams do you think this role should be retired at the same time as I'm retiring from it?
This @bisq-network/btcnode-maintainers role is responsible for maintaining the shared configuration for @bisq-network's federation of @bitcoin nodes, as hard-coded in https://github.com/bisq-network/exchange/blob/master/core/src/main/java/io/bisq/core/btc/BitcoinNodes.java.
This role should maintain a shared
bitcoin.conf
file in this repository, and work with @bisq-network/btcnode-operators to make sure they run the same configuration there.This role is responsible for responding in a timely fashion to GitHub issues added to this repository, questions asked in the
#bisq-btcnode
channel, and to ensure that monitoring notifications in#alerts
get handled in a timely fashion.Docs: none, other than the above Team: @bisq-network/btcnode-maintainers Primary owner: @sqrrm Secondary: @wiz