Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
0xB10C opened this issue May 7, 2021 · 1 comment
Open

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

0xB10C opened this issue May 7, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@0xB10C
Copy link
Owner

0xB10C commented May 7, 2021

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 0xB10C added the enhancement New feature or request label May 7, 2021
@0xB10C
Copy link
Owner Author

0xB10C commented May 7, 2021

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

@0xB10C 0xB10C mentioned this issue Nov 10, 2022
Closed
0xB10C added a commit that referenced this issue Apr 10, 2023
@0xB10C
# This is a combination of 2 commits.
e9bec8c 
# This is the 1st commit message:

add: store block and transaction sigops in db

# The commit message #2 will be skipped:

# fixup! add: store block and transaction sigops in db
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@0xB10C