-
-
Notifications
You must be signed in to change notification settings - Fork 306
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 finalized
property to HTTP API responses
#5693
Comments
|
Any updates on this? |
I think @ensi321 wanted to look into this, right now Lodestar is pretty limited in serving finalized data derived from the state as we only keep the unfinalized state in-memory and only persist very few states to load from disk (will be addressed by #6033). We could just hard code those to On the note of cross-client compatibliy, we currently also only support json bodies for all requests but as per spec there are a few APIs that should also support ssz bodies. How does Teku handle this case, do you send the ssz body and if you receive a 415 (unsupported media type) do you resend the request with a json body? I am working on a overhaul of the API to add first class support for ssz res/resp to (almost) all APIs so this will be addressed soon as well. |
@nflaig |
ah perfekt, this is the ideal behavior I also had in mind because we want to send ssz bodies for almost all APIs even those that don't have it (yet) defined in the spec |
We can implement this already without the historical state regen, we already can serve some finalized data without it, e.g. finalized blocks or finalized checkpoints. |
Problem description
Latest beacon API spec requires
finalized
property in some HTTP API responesfinalized
flag to chain data requests ethereum/beacon-APIs#254Solution description
Add
finalized
property to the following HTTP API responses:Additional context
No response
The text was updated successfully, but these errors were encountered: