Skip to content
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

Node address api proxy banning burn address #127

Open
r4mmer opened this issue Feb 11, 2022 · 0 comments
Open

Node address api proxy banning burn address #127

r4mmer opened this issue Feb 11, 2022 · 0 comments

Comments

@r4mmer
Copy link
Member

r4mmer commented Feb 11, 2022

Summary

Currently, if an address takes too long to load on the proxy api for addresses it is banned as to not create an unnecessary load on the explorer full-node.

This ban should not be applied to the burn address.

Possible solutions

  1. Do not make calls with timeout if it's the burn address (would need to increase the lambda timeout as well).
  2. On the explorer, search directly on the full-node if it's the burn address.
  3. Have a service listening to the full-node and updating the burn address result so that the explorer-service can serve the cached result.
@r4mmer r4mmer changed the title Always wait for burn address on the address api proxy Node address api proxy banning burn address Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant