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.

ACP-77 introduced Avalanche L1s, providing greater sovereignty and flexibility compared to Subnets. However, creating an L1 currently requires a three-step process:. 1.) CreateSubnetTx.2.) CreateChainTx.3.) ConvertSubnetToL1Tx.

Thrilled to propose a streamlined approach to launching an L1 blockchain. This ACP introduces a new CreateL1Tx transaction type on the P-Chain, enabling the entire L1 creation process to be executed as a single atomic operation.

RT @Nutymoon: 💥 ACP-99 is officially a thing!. No announcement from @AvaLabs yet, but Validator Manager V2 was released yesterday on GitHub….

Launch a production-grade L1 in under a minute.

RT @AvaCloud: 🧵 AvaCloud Unveils Wallet as a Service:.Bringing seamless onboarding and secure embedded wallets to Avalanche L1s 🔺. Let’s br….

RT @0x_Ali3N: 🔺There’s been some chatter around "outflows" from Avalanche DeFi, but context matters. Let’s look at what’s actually happenin….