Skip to content

Fix fee estimation bounds - #2410

Merged
kushti merged 1 commit into
ergoplatform:v6.0.5from
a-shannon:fix/fee-estimation-stability
Jul 13, 2026
Merged

kushti merged 1 commit into
ergoplatform:v6.0.5from
a-shannon:fix/fee-estimation-stability

Conversation

@a-shannon

Copy link
Copy Markdown
Contributor

Closes #1884.

Summary

  • Floor recommended fees at the configured node minimal fee so /transactions/getFee cannot recommend a fee below the accepted minimum.
  • Cap expected wait-time calculations to the mempool statistics window so long node idle uptime does not dominate the estimate.
  • Keep HTTP parameter validation separate from Harden REST API input validation #2374; this PR fixes the core mempool estimation behavior.

Tests

  • sbt "testOnly org.ergoplatform.nodeView.mempool.ErgoMemPoolSpec"
  • sbt "testOnly org.ergoplatform.http.routes.TransactionApiRouteSpec"
  • publication guard

@kushti
kushti changed the base branch from master to v6.0.5 July 13, 2026 11:47
@kushti
kushti merged commit ce1dfac into ergoplatform:v6.0.5 Jul 13, 2026
7 of 8 checks passed
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.

Fee estimation APIs getExpectedWaitTime/getRecommendedFee return invalid values

2 participants