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
feat: expose to the api whether peer uses estimates or not #3592
Comments
Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on. If no reviewer appears after a week, a reminder will be sent out. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed. If you wish to re-open it please provide additional information. |
This issue has now been re-opened. If applicable please provide additional information as requested by one of the reviewers. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Currently the only way to find out if a peer uses estimates under the hood is by sending a request to it and check the responses meta object for the
totalCountIsEstimate
property.This information should also be included in the
peers
api response, so that peers can be easily filtered by that property instead of having to query each peer individually if one with need to assemble a list of such peers.This could then also be implemented into into the peer discovery package,
@arkecosytem/typescript-peers
.The text was updated successfully, but these errors were encountered: