About Starknet Alpha 0.9.0 — Why it’s cool?

Starknet Alpha 0.9.0 brings mandatory fees on Testnet, soon on Mainnet. Contract factory pattern introduced, along with Contract Classes, replacing delegate_call with library_call. Major steps towards protocol maturity.

🌐 Contract Classes

Inspired by OOP, Starknet separates contract code and implementation, enabling a more straightforward use of delegate_call and introducing the factory pattern.

Exciting move with Contract Classes! The class/instance separation brings clarity and efficiency to Starknet’s contract architecture.

📜 ‘Declare’ Transaction

A new transaction type declares a contract class without deploying an instance, providing flexibility in contract deployments.

‘Declare’ transaction is a game-changer, offering flexibility in contract deployment strategies. Starknet making strides towards user-friendly development!

🚀 ‘Deploy’ System Call

Allows deployment of new class instances with specified parameters, introducing contract factories into Starknet.

🔄 Moving to ‘Library Call’

Deprecated delegate_call is replaced by a new library_call system call, enhancing efficiency in contract interactions.

Smart transition from ‘Delegate Call’ to ‘Library Call’ for improved contract interactions. Clearing up ambiguity enhances overall security and stability.

🛠️ New API Endpoints

Two new API endpoints facilitate retrieval of class-related data, contributing to a more streamlined developer experience.

💸 Mandatory Fees

Fees become mandatory for invoke transactions, a vital step towards a self-sustainable L2 ecosystem.

Mandatory fees are a bold move, ensuring sustainability and independence for Starknet. Excited to see the impact on the Mainnet!

🚀 Future Plans

Starknet continues its roadmap with plans for sequencer parallelization and a focus on the structure of Starknet’s accounts, paving the way for mass adoption.

My Twitter

See you again👋