-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
Offers with invalid maker tx in the orderbook #6815
Comments
Thanks for opening your first issue here! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant. |
Hi @alexblom102 AFAIK the trade fee filter has been turned back on so offers with an invalid maker fee should no longer appear in the offer book. |
Indeed it has, however, it only prevents peers from taking invalid offers. The problem is that invalid offers can still be broadcast and put in the order book. The mechanism used for deactivating these invalid orders can be bypassed. |
Looks like there was a PR to fix this here: #6615 @jmacxx is it possible for someone to broadcast offers with a failed maker fee? |
Description
There exist an issue where offers can be published with invalid maker fees.
Version
1.9.12
Steps to reproduce
Details
Thanks to the enabling of "disableMempoolValidation"(?) filter, anyone who tries to take an invalid offer are presented with:
"This offer is not valid. Please choose a different offer.
[Tx not found]"
The offer is deactivated after a couple minutes, however, a malicious client could reenable the offer programmatically.
There doesn't seem to be any onion-address banning for misbehaving clients.
Impact
Malicious actors can spam the orderbook with offers at almost zero cost, advertising/luring victims off-platform with the "Additional information" field, all without paying any maker fees or risking losing their deposit.
Remediation suggestions
The text was updated successfully, but these errors were encountered: