Pop Chunhapanya
Pop Chunhapanya
Why should we have all the clients follow this art spec? This seems to me that it's an implementation thing rather than a spec thing. The protocol will work fine...
This seems related to https://github.com/ethereum/consensus-specs/pull/2875
> There are a lot of old nodes with network bugs such as this one. so this is a bit hard to pinpoint Are you sure that it happens only...
@fradamt I thin I understand what you are trying to say. > To simplify, let's even forget the rotation for the moment and just consider a single instance of a...
This makes sense to me. I think there is no reason to use suffixes for anything, so using the prefixes probably always make more sense.
Note from the consensus call as well: we have to think about the upgrade process and the fork boundary as well.
Should this be closed? since it's already superseded.
Is this issue resolved? The test passes in my machine.
``` pop@thinkpad-t14:~/repos/shadow(go-netlink)$ uname -a Linux thinkpad-t14 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux pop@thinkpad-t14:~/repos/shadow(go-netlink)$ lsb_release -a No LSB modules are available. Distributor ID:...
This doesn't make sense at all. As @abcoathup said, rollups are already incentivized. There is no need for this EIP. I think this PR can be safely closed.