Create ergoplatform-ergo-1884.json (reservation, 500 SigUSD) - #47
Open
Ergologica wants to merge 2 commits into
Open
Create ergoplatform-ergo-1884.json (reservation, 500 SigUSD)#47Ergologica wants to merge 2 commits into
Ergologica wants to merge 2 commits into
Conversation
Contributor
Submission triage
Reviewer hint: @MrStahlfelge |
This was referenced Aug 2, 2026
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
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.
Type
Submission Checklist
submissions/*.jsonfile changedcontributormatches PR authorwallet_addressis real, not placeholderstatusis one ofin-progress,awaiting-review,reviewed,paidwork_linkpayment_tx_idandpayment_dateNotes
Reservation for ergoplatform/ergo#1884 — Fee estimation APIs getExpectedWaitTime/getRecommendedFee return invalid values (500 SigUSD).
Work submitted upstream as ergo#2450 (open, awaiting review):
getExpectedWaitTimenow derives its estimate from the same mempool fee histogram used bygetRecommendedFee, making the two endpoints mutually consistent, and the position-based fallback is bounded by the statistics measurement window so stuck transactions can no longer produce the ~20-year estimates reported in the issue. Four new tests inErgoMemPoolSpeccover the fee-estimation API, which previously had none.Will switch this submission to
awaiting-reviewonce the upstream PR is merged.