search

0xB10C / miningpool-observer

Transparency for Mining Pool Transaction Selection
https://miningpool.observer
MIT License
55 stars 13 forks source link

add: detection of conflicting BIP-125 replaced and replacement transactions #2

Open 0xB10C opened 3 years ago

0xB10C commented 3 years ago

Note: Usually, many of the conflicting transactions listed below are not properly propagated BIP-125 (Opt-in Full Replace-by-Fee Signaling) replacement transactions.

This can be detected and the information about the RBF event can be displayed. Additionally, users should be able to filter the conflicting transaction page to hide these RBF conflicts. The non-RBF conflicts are of higher interest.

Example

image https://miningpool.observer/conflicting/0000000000000000000d1f2794b964c83b86586e83898aa0a9a7e5e66daa186a

The template transaction 49090b.. and the block transaction 12e154.. conflict. Both signal for RBF replaceability. 49090b.. pays a higher fee and thus a higher feerate than 12e154... The template transaction 49090b.. is very likely an RBF replacement for the replaced block transaction 12e154...

The template transaction 49090b... might not have propagated to the mining pool in time. The pool did issue work to mine on 12e154...

0xB10C commented 3 years ago

An RSS feed for non-RBF conflicts could also make sense.