Validators can vote for higher gas limits by setting it in the C-Chain config of their node:.

Since the implementation of ACP-176, average gas of the blocks on the Avalanche C-Chain has consistently aligned with the set target. In recent weeks, this target has been step-wise raised to 2 million gas as a result of validators voting for the increase

RT @Cointelegraph: 🔥 BREAKING: Visa adds support for PYUSD, USDG, and EURC stablecoins. Stellar and Avalanche join Ethereum and Solana for….

Join our online hack event around encrypted value transfers on Avalanche. The 1-month program includes workshops and a competition. The best teams will be considered for our incubator Codebase.

Felt like our Network Architecture Diagram needed a do-over

Choose Your Learning Path on Avalanche Academy. We've designed learning paths to make it easier to navigate our learning content. Let us know what you think

The L1 Toolbox on the Avalanche Builder Hub got a fresh design. Huge shoutout to @owenwahlgren 🙌🏻 We're not done yet and will keep shipping until launching an L1 is as easy as a dex swap.

For real interoperability, Explorers must do more. Every TX should show which interchain messages were read and which were sent. For cross token transfers, users should see the ICM message and the chain it came from or is going to.

One piece of infra less to set up and maintain. Taking down barriers one by one.

What if every Avalanche L1 had a block explorer by default, straight from the network? Teams could still add redundancy through self-hosting or providers — but the goal is to let them focus on the app, not the infrastructure.

RT @therollupco: "I've been very very impressed by the caliber of other ecosystems that I perhaps was not paying enough attention to" - @sa….

RT @Michael_Kaplan1: Avalanche ICM removed the need for any trusted third parties in interchain messaging, and now is leveling up its secur….

Interoperability is at the heart of the Avalanche L1 network. Many valuable insights from @Michael_Kaplan1, @ChrisFusillo and Angus Hopkinson at the @avax summit.

RT @luigidemeo: damn this is clean.

RT @janockbro: Great panel yesterday representing @AvaCloud and discussing the @avax L1 stack with @hilmarxo @gelatonetwork and @rpchamri….

RT @0xZeeve: The fire panel of @rpchamria, @hilmarxo, @martin_eckardt and Anthony Janocko sharing the "Insights from Ecosystem Leaders" on….

RT @0xZeeve: We're on stage discussing L1 Supremacy 😎🔺 @rpchamria @martin_eckardt @AvaLabs.

Thanks to @AaronBuchwald @Michael_Kaplan1 @MeagFitzgerald for their input and the authors of ACP-77 for their work that this ACP is building on.

This ACP proposes a new transaction type called CreateL1Tx that will consolidate the above steps into a single step.

This process has several drawbacks:. - three separate transactions.- increased complexity and potential for errors. - unnecessary state transitions and storage overhead . With this ACP, we can simplify the process, reduce overhead, and improve the developer experience.