Skip to content

Policy: warn if -minrelaytxfee is too high #99

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

Open
wants to merge 1 commit into
base: 28.x-knots
Choose a base branch
from

Conversation

Retropex
Copy link

@Retropex Retropex commented Mar 28, 2025

Stop bitcoind if the value of -minrelaytxfee is superior or equal to 1. Can be forced with a prefix (i.e f1)

@luke-jr
Copy link
Collaborator

luke-jr commented Mar 28, 2025

I don't believe this even compiles...

@Retropex
Copy link
Author

It compiles and work.

@Retropex
Copy link
Author

I hope it won't hurt your eyes to much :)

@Retropex Retropex marked this pull request as ready for review March 29, 2025 10:55
@Retropex
Copy link
Author

I think I should even lower the value, I don't see anyone putting 100000 sats/vbytes min fee relay.

@michaelfolkson
Copy link

michaelfolkson commented May 12, 2025

Might be missing context here but why is it a concern if the minrelaytxfee is too high?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants