Compatibility Matrix: revise RBF columns

[OttoAllmendinger]

The current compatibility matrix table for RBF has the following columns:

• "Notification" https://github.com/bitcoinops/bitcoinops.github.io/blob/a79c00308959cd39d9076a46e460a350a8aa67c0/_includes/templates/compatibility/rbf.md?plain=1#L22-L36 (Notification of incoming transaction notes that the transaction signals RBF.)
• "List" https://github.com/bitcoinops/bitcoinops.github.io/blob/a79c00308959cd39d9076a46e460a350a8aa67c0/_includes/templates/compatibility/rbf.md?plain=1#L38-L53 (Received transaction labeled replaceable in list)

In light of growing full-rbf adoption, these columns and the visual indicators might not be appropriate anymore. The difference between signalling and non-signalling transactions is diminishing.

Explicitly highlighting the "RBF" field suggests a significant difference between transactions that have opted in and those that have not. The wording in the "List" column does not even use "signals RBF" and just uses "replaceable". To some readers it could suggest that only RBF transactions are replaceable, when this is not true.

The easiest solution to this might be to remove these two columns.

[murchandamus]

I think you are bringing up some great points. With some adoption of mempoolfullrbf, it is a lot less important for wallets and services to notify that a transaction is marked as non-final. Essentially all transactions should be treated as non-final and replaceable.

We currently have someone looking into reworking the "Compatibility Matrix" into a "Best Practice Adoption Tracker". I will bring up the point there. Thank you for raising the issue.