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

Breakout-room discussion #5 (EIP-2930, EIP-2972, EIP-2718) Agenda #223

Closed
poojaranjan opened this issue Nov 13, 2020 · 3 comments
Closed

Comments

@poojaranjan
Copy link
Contributor

Date and Time

  • Meeting Date/Time: Nov 16, 2020 1500 UTC
  • Meeting Duration: 60 mins

Location

Zoom: Will be shared in the breakout-room in EthR&D discord channel

Agenda

Transaction format specifics

@RatanRSur
Copy link

This is my first breakout room, do we not create google calendar invites for this in addition to this?

@poojaranjan
Copy link
Contributor Author

We do, please DM me your email on discord.

@poojaranjan
Copy link
Contributor Author

poojaranjan commented Nov 17, 2020

Recording: Breakout room #5

Summary

Questions :

Should the legacy transactions be wrapped? 

How do we format the new tx type? Is now the right time to introduce the SSZ?

  • Enough support / not strong opposition to using SSZ from the people who attended the breakout room meeting.
  • People are open to hearing concerns with using SSZ.

Next steps

Piper Merriam will ping each client on Discord (async) to check if they are willing to use SSZ implementation from Eth2 clients or are feel a need for a massive amount of testing on their own.

  • Geth - agrees
  • Besu team seems to be fine with using SSZ
  • OpenEthereum thinks it should be okay but will confirm async
  • Trinity - supporting the proposal

To be discussed

  • Potential delays if SSZ is chosen to move ahead with figuring out whether or not Ethereum client teams are okay with it and some other details.

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

3 participants