2022-07-05 Contributor Call
(Meeting Link: https://zoom.us/j/97540031823?pwd=dEJrRW1LakFlWnZPelI3VGxoVjg2dz09)
EMEA Friendly Time (https://www.timeanddate.com/worldclock/converter.html?iso=20220607T150000&p1=224&p2=179&p3=1440&p4=195&p5=47)
8 am Tuesday Los Angeles time
11 am Tuesday New York time
17h Tuesday Paris time
Agenda
Housekeeping
Antitrust notice - https://www.linuxfoundation.org/antitrust-policy/
This meeting is being recorded
Please Mute unless speaking
If you have a question use the raise hand feature
General Announcements
mentioning this from Hart
Tim Beiko (in charge of the Besu CIP program from the EF side) likes our format. Please go ahead and document your mainnet contributions this year (starting from Jan. 1). Thanks!
@Justin Florentineadding some points in the doc
There will (finally) be a meeting to put together a sub-HLF organization to handle the grant money on Wednesday.
(Hart: I am double-booked and probably can't make the meeting. Sorry!).
Release updates
Tracking who is doing each release Release Rotations 2022
22.4.3 - June 14th - Justin
Sepolia merge is tomorrow 6 July
22.7.0-RC1 was delayed to develop the fix in PR#4041
Danno is disconnected from the internet until Jul 8 and cannot run the release
Also, Java 17 support has been bumped to 22.10.0 because CI build tools don't support Java 17 to the level we need yet
discussion on merge and version sync
RPC - Extra fields in transaction serialization (from @Daniel Lehrner )
When returning a transaction we return two fields that are not part of the spec: public key and raw. Should we keep them or not?
Discussion on Eth R&D Discord: https://discord.com/channels/595666850260713488/910910348922589184/991299338133327894
Danno's thoughts in the Eth R&D Discord - https://discord.com/channels/595666850260713488/910910348922589184/993556490487087155
Danno's thoughts in the HLF discord - https://discord.com/channels/905194001349627914/992724025870651392/993557409542979695
@Justin Florentine agree with what Karim suggested to get rid of those fields: you can still treat the client as a black-box. Need more discussion on spec architecture
Own of this investigation RPC compatibility: @Justin Florentinebut no commitment on time/ pre-merge, not urgent
Liveness Check (issue #4007 form @Daniel Lehrner )
Our liveness check currently is just a stub. There was a user request to implement a proper check. Should we do that? If yes, what would we check?
Definition of liveness (and readiness) by RedHat: https://cloud.redhat.com/blog/liveness-and-readiness-probes
question: should we move the endpoints?
@Daniel Lehrner will update the doc and close with a documentation
Work Updates