Ethereum Cat Herders Breakout Room, 7 Dec 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Breakout room meeting #6 (Pt.1)

Description

Agenda: https://github.com/ethereum/pm/issues/231
Video (Pt. 2): https://youtu.be/qjLJVmUXals

A

Why are we specifically doing 2718 with an rlp encoding? Instead of you know, pushing this out three or four months and doing ssd?

A

I realize that fatigue is a real thing and that this is something that we've been beating for quite a while at this point, but it just seems like we're at the point where we can do things right, the first time, rather than doing something, that's sub-optimal with the intention of fixing it in 6 to 18 months.

B

A

Reason is because.

B

2930 is a dos vector that we need to get fixed. Ascp. Sorry, 29.29 is a dos vector. 29.29 does not have consensus to go in unless 2930 goes in with it.

A

What yeah I mean, I realized that I'm just not sure if the need is that dire, like our do, we have oh.

C

A

29 in the next month, yes, you know.

B

A

B

Current popular belief, yes, that if we the longer this is out there, we'll eventually be attacked and we're basically just lucky right now,.

D

B

D

Every other kind of more uh uh bigger feature depends on 29.29, so, for example, account abstraction and 1559. Basically, both can't go in until 29.29 is live. um I think.

B

I think you mean 27 18, for this.

D

No 29.29 uh the biggest pushback against 1559 is if we, if we have this broken meter, attack on mainnet uh and and and we introduce blocks that are twice.