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

♻️ Remove SSTORE compat for TSTORE libs #1159

Open
Vectorized opened this issue Nov 7, 2024 · 0 comments
Open

♻️ Remove SSTORE compat for TSTORE libs #1159

Vectorized opened this issue Nov 7, 2024 · 0 comments

Comments

@Vectorized
Copy link
Owner

Vectorized commented Nov 7, 2024

Shanghai: April 12, 2023
Cancun: March 13, 2024

This is what ChatGPT says:

Qn: What EVM chains have adopted Shanghai, but have not adopted Cancun yet?

As of November 8, 2024, several Ethereum Virtual Machine (EVM) compatible chains have adopted the Shanghai upgrade but have not yet implemented the Cancun upgrade. The Shanghai upgrade, activated on April 12, 2023, introduced features such as enabling withdrawals of staked ETH and various improvements to the Ethereum Virtual Machine (EVM). The subsequent Cancun upgrade, activated on March 13, 2024, focused on scalability enhancements, including Proto-Danksharding (EIP-4844).

While Ethereum's mainnet has implemented both upgrades, other EVM-compatible chains may have different upgrade schedules. For instance, Polygon, an EVM-compatible sidechain, adopted the Shanghai upgrade to maintain compatibility with Ethereum's mainnet. However, as of the current date, Polygon has not announced the implementation of the Cancun upgrade. Similarly, other EVM-compatible chains like Binance Smart Chain (BSC) and Avalanche's C-Chain have incorporated the Shanghai upgrade but have not yet adopted the Cancun upgrade.

It's important to note that each EVM-compatible chain operates independently and may choose to implement upgrades on different timelines based on their specific governance processes and technical considerations. For the most accurate and up-to-date information, it's advisable to consult the official communication channels of each respective chain.

Hmm... might keep it for now. At the time of writing, Tron hasn't implemented transient opcodes yet.

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

1 participant