This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 75
API Call #143
Comments
Tentative meeting time, Monday April 20th at 1:30pm UTC. Will confirm in ~2 days as these conversations progress (edit: oh shit, it's 420 🎄) |
Any specific topics you thought of? to maybe send some questions before hand? |
while not strictly API related, it would be useful to standardise the version string sent through the API. It would be most useful for 3rd party tools in the future |
This was referenced Apr 20, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As discussed on the previous eth2 call, we intended to do an API call this Wednesday to chat about API formats, beacon-node APIs, and cross-format tooling and CI.
@protolambda and I are also putting together a comprehensive look at existing APIs as well as some notes on both general and more specific requirements.
I propose we push this call to Monday to provide more time for input and discussion as well as digesting the additional resources we plan to publish tomorrow.
I also solicit more active engagement from at least one member of each client team.
Agenda
/beacon/{id}/resource
<- very nice construct, but would require some amount duck-typing/validator
,/state_roots
,/block_roots
,/balances
all fit in nicely here/forkchoice/ffg
,/network/host
(or sub-components))/beacon/forkchoice/individual_votes
)Call Monday @ 2pm UTC
The text was updated successfully, but these errors were encountered: