feat: Implement Optimal Jito Tip Retrieval and add Salt Lake City (Utah) Endpoint for US-West region #4
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.
Added Feature: Implement Optimal Jito Tip Retrieval and add Salt Lake City (Utah) Endpoint for US-West region
GM @MatrixYe,
Great work on the repo!
Additions
This PR includes functionality to fetch optimal Jito fee amounts (tip floors) in lamports for recently landed transactions based on the percentile of landed transactions (25/50/75/95/99 percentiles) fetched from Jito Bundles Tip Floors.
For lower latency in the US-West region, I also added the Salt Lake City, Utah Block Engine Endpoint from Jito Docs to the configuration.
Updated
README.mdto include a small example.Examples
Below is an example demonstrating how to use the new SLC endpoint and retrieve the Jito fee data in a single script:
Conclusion
Hope this is fine—let me know if you need any help or have feedback. I'd love to contribute further to this repo!