-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add endpoint to enable estimation of inclusion fee #105
Comments
Notes:
|
References that may help in determining computing logic: |
We already proposed doing this from the RPC spec and I'd like to include what we actually want to build in the ticket description. Mind let me create the ticket? |
Feel free |
Another idea that came up while discussing with Jane. We can simplify the MVP even more: use the same logic as fee_stats but filter out soroban tx for the new endpoint |
Closed in favor of #114 |
What problem does your feature solve?
As a transaction-submitting developer, I need a way to estimate inclusion fee so that I can be sure my transaction will make it into the next ledger.
What would you like to see?
An endpoint that returns an inclusion fee, where the value of the fee is such that it maximizes the probability of the transaction making it into the current ledger while minimizing wasted XLM.
What alternatives are there?
N/A
The text was updated successfully, but these errors were encountered: