feat: add Stellar fee estimation with Horizon caching - #167
Open
praizeD10 wants to merge 2 commits into
Open
Conversation
- New estimateFee(opKind, urgency) function for stroops calculation - Pulls fee stats from Horizon /fee_stats endpoint - Caches results for 30 seconds with per-URL keying - Supports urgency levels: low (p10), normal (p50), high (p90) - Enforces minimum base fee of 100 stroops - Comprehensive unit tests with mocked Horizon responses - Optional integration test for futurenet - Exported from Stellar chains module
|
@praizeD10 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #138