search

spadebuilders / community

Repo for community activities across @SPADEBuilders projects
https://waffle.io/spadebuilders/community
Apache License 2.0
5 stars 0 forks source link

Community Call - Nov 27th 8am PST - JSON-RPC Spec and Testing for Ethereum Clients #15

Closed bmann closed 5 years ago

bmann commented 5 years ago

An initial call to gather interest and assign next steps in improving / solidifying the JSON-RPC specification for Ethereum clients, and how to run community resources for testing and validation.

@Arachnid made a call for documenting JSON-RPC in an EIP https://github.com/ethereum/EIPs/issues/1442

@bitpshr has added a PR starting this work https://github.com/ethereum/EIPs/pull/1474

This will be an organizing and initial "bootup" call to see who will be participating, how we will communicate, and so on. Feel free to use this community space for now, with notes preferred in HackMD format.

Please add topics and questions for discussion below, and use reactions to indicate which ones you like.

bmann commented 5 years ago

@egalano has some internal Infura JSON integration tests -- describe and discuss if this can be contributed.

bmann commented 5 years ago

@benjamincburns has been working on EEA spec.

@alexvotofuture also connected to EEA work.

How to align / re-use / connect / improve JSON-RPC spec out in the open for all Ethereum community, and how EEA can align & support that.

bmann commented 5 years ago

@atoulme & @cleishm have interest & time available to do spec editing and improvements.

bmann commented 5 years ago

@bmann will give overview of discussions leading up to EthMagicians and DevCon with @chaals (EEA) and others about how to use collaboration on JSON-RPC as a first test case to get useful work done.

bmann commented 5 years ago

@hermanjunge wants to extend the JSON-RPC spec to support slices https://github.com/paritytech/parity-ethereum/issues/9857 -- this is in support of the Mustekala Ethereum light node project.

I suggest this actually be done by a second EIP, applied as an extension or amendment to the first one, but that's just a guess on my part. I don't know that this has been formalized.

pipermerriam commented 5 years ago

I'd like to be included in this call. My team at the EF is absorbing ethereum/tests into our "umbrella" of responsibility and I see this as falling under that. Our primary contribution is likely not to be to spec itself (as that seems to be solidly underway) but rather creation and maintenance of a test suite for this spec under ethereum/tests and potentially tooling to assist in running the tests.

Arachnid commented 5 years ago

This might also be a good time to discuss replacing JSON-RPC. I'm personally working on defining a spec for a graphql API; I'd be keen to get feedback from others on it and whether we can standardise it across clients.

-Nick

On Fri, Nov 9, 2018 at 6:58 AM Boris Mann notifications@github.com wrote:

An initial call to gather interest and assign next steps in improving / solidifying the JSON-RPC specification for Ethereum clients, and how to run community resources for testing and validation.

@Arachnid https://github.com/Arachnid made a call for documenting JSON-RPC in an EIP ethereum/EIPs#1442 https://github.com/ethereum/EIPs/issues/1442

@bitpshr https://github.com/bitpshr has added a PR starting this work ethereum/EIPs#1474 https://github.com/ethereum/EIPs/pull/1474

  • Community Calendar
  • Zoom Video Link

Please add topics and questions for discussion below, and use reactions to indicate which ones you like.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spadebuilders/community/issues/15, or mute the thread https://github.com/notifications/unsubscribe-auth/AABFyUS_gKQlAMuCIz2pvy24gEFuRQ_dks5utHDVgaJpZM4YVIWb .

bmann commented 5 years ago

Great to see the INFURA team open sourced some of their tests https://github.com/INFURA/rpc_sanity_test

It looks like it’s specifically designed to compare results returned from multiple clients.

bobsummerwill commented 5 years ago

Count me in!

egalano commented 5 years ago

Happy to do it @bmann. It fit our straightforward use case but looking forward to seeing how extending it makes it more useful to others. In addition, I've started building an OpenAPI v3 spec for the current JSON-RPC API. Happy to collaborate on that as well.

bobsummerwill commented 5 years ago

Brilliant :-)

On Fri, Nov 16, 2018 at 2:05 PM Eleazar (E.G.) Galano < notifications@github.com> wrote:

Happy to do it @bmann https://github.com/bmann. It fit our straightforward use case but looking forward to seeing how extending it makes it more useful to others. In addition, I've started building an OpenAPI v3 spec for the current JSON-RPC API. Happy to collaborate on that as well.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/spadebuilders/community/issues/15#issuecomment-439543356, or mute the thread https://github.com/notifications/unsubscribe-auth/ADnNfAPZvhxlYMBewmsKlLmAE5djB3amks5uvzZtgaJpZM4YVIWb .

-- bob@summerwill.net

bmann commented 5 years ago

Confirming this call for tomorrow morning 8am PST, here's the Zoom link https://zoom.us/j/946476323

I have added a number of you to the calendar invite that I have email addresses for. I realize that the calendar invite is a little last minute if you haven't been tracking this. No worries if you can't make it, consider this a kick off call to get things moving, notes will be taken and posted.

EthMagicians thread here https://ethereum-magicians.org/t/json-rpc-specifications-and-testing-community-call-nov-27th-2018/2031

Live notes for the call in HackMD https://hackmd.io/FUE13Uh_Rj2qLoJOnHILqw

bmann commented 5 years ago

I have done follow up notes on the EthMagicians post https://ethereum-magicians.org/t/json-rpc-specifications-and-testing-community-call-nov-27th-2018/2031/2?u=boris

We'll use EthMagicians and the new repo I created https://github.com/spadebuilders/ethereum-json-rpc-spec for further coordination.

Everybody's core action item is to review the spec. I'd suggest filing issues in the repo and/or PRs for changes, TODOs, future calls, and so on.