Fear & Greed57.2GreedTop MindshareBitcoin16.5%▼12.4Ethereum6.0%▼15.0Solana4.4%▼45.7Hot Narratives#PerpDEX#DePINRising ProjectsAEON+223%HEAT+300%DRV+96%
LIVE
Back to Projects

헤고타

Synced 2 min agoTrending
헤고타Discovered
HEGOTA
Mindshare
<0.1%0.0% 7D
Rank
#534of 561
1Mentions
1KViews
3Forwards
0Replies
1KReach

Mention Trend

Sep 15 to Sep 15

Mention Trend
09-15

Channel Breakdown

Last 30 days

Sentiment
(주)청년열정민트초코100.0%11K33dBearish

Recent Messages

(주)청년열정민트초코09/15[L1 and L2 starting to diverge: Native account abstraction negotiation breakdown] Today, negotiations between EIP-8141 and EIP-8130 surrounding the native account abstraction standard broke down. This could be seen as the first moment Ethereum L1 and L2 are seriously diverging. Native account abstraction is one of the proposals representing Ethereum's next-next upgrade, Hegota. As previously introduced, EIP-8141 proposed by Ethereum researchers and core developers and EIP-8130 proposed by Base have been competing. Weekly breakout meetings were held to narrow the gap between the two standards, but since their goals were different from the start, consensus does not appear to have been reached. As a result, L1 is expected to adopt EIP-8141 next year, while major L2s like Base/Arbitrum/Optimism will adopt EIP-8130. Why it's symbolic So far, major L2s have never significantly modified the EVM. Many alt-L1s have modified the EVM to fit business needs, but L2s evaluated as 'pan-Ethereum ecosystem' like Base or Arbitrum have fully maintained EVM compatibility. However, after Vitalik declared earlier this year that "the L2 roadmap has failed," a trend is visible where L2 identity is shifting from 'L1 scaling' to 'providing specialized features.' Base's EIP-8130 proposal seems to be under this trend. Of course, there have been L2s that slightly modified the EVM before. However, this time is different for two reasons. 1. The point that Base/Arbitrum/Optimism, which have the largest user bases, are trying to adopt EIP-8130. 2. The point that native account abstraction occupies a very large area in the protocol. With these two overlapping, this native account abstraction is likely to be the first point where L1 and L2 diverge significantly. Points for builders and users to consider • Tooling, infrastructure, dApp difficulties: L1 must support EIP-8141, L2 must support EIP-8130 respectively, so a layer that abstracts this at the tooling and infrastructure level is needed. This is a big opportunity for teams that solve it well, but the complexity builders must handle in the process is also expected to be considerable. • Where is EVM going: Starting from this incident, a situation may come where L1 and L2 each push different EVM implementations. Synergies that absorb advantages from each other's implementations can also be expected1K30