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.

Sign up for GitHub

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

Jump to bottom

Utilize Public Validator API Instead of Internal Endpoints #4105

Closed
rauljordan opened this issue Nov 25, 2019 · 1 comment
Closed

Utilize Public Validator API Instead of Internal Endpoints #4105

rauljordan opened this issue Nov 25, 2019 · 1 comment
Assignees
@rauljordan
Labels
API Api related tasks Enhancement New feature or request Priority: High High priority item
Milestone
Testnet restart f...

Comments

@rauljordan
Copy link
Contributor

This is a tracking issue for us to use the Public Validator API instead of internal methods such as RequestBlock or RequestAttestation to maintain a nice standard for other clients to eventually interop with our API as well. Opening this after seeing issues such as #4097 raised by users, which show we aren't using all of our public API endpoints to their full extent.
@rauljordan rauljordan added Enhancement New feature or request Priority: High High priority item labels Nov 25, 2019
@rauljordan rauljordan self-assigned this Nov 25, 2019
@rauljordan
Copy link
Contributor Author

I'll be taking on this task

@rauljordan rauljordan mentioned this issue Nov 25, 2019
Closed
@rauljordan rauljordan added the API Api related tasks label Nov 27, 2019
This was referenced Dec 7, 2019
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rauljordan rauljordan

Labels
API Api related tasks Enhancement New feature or request Priority: High High priority item
Projects
None yet
Milestone
Testnet restart for v0.9.1, v0.9.2, v...
Development

No branches or pull requests
2 participants
@rauljordan @prestonvanloon