Starknet roundup #69

Your weekly Starknet newsletter

Starknet roundup #69

This newsletter is made possible thanks to Braavos, the open-source wallet designed for Starknet, offering a state-of-the-art and constantly evolving UX.

With Braavos, you can easily access all the necessary wallet features with a brand new UX as well as new exclusive ones that keep your digital assets secure. Notably, the Braavos security pyramid, consisting of the Seed Signer, Hardware Signer, and Multi-Signer (decentralized 3FA), give you complete confidence as you navigate the exciting DeFi world of Starknet. By combining something you know (your seed phrase) with something you are (face ID/biometric fingerprints) and something you have (your smartphone), you can now maximize the security of your funds on Starknet.

To learn more about these exclusive features, head over to:

Welcome to the 69th edition of my weekly comprehensive Starknet summary. Would you like to sponsor this newsletter? Reach out to me.

If you enjoy this newsletter, don’t forget to subscribe. It’s free!

Let’s get into this week’s news! 💪

Protocol & dev tool updates

Media highlights

Ecosystem Highlights

Ecosystem stats

The APY mentioned here is calculated on a daily basis; rates vary widely from day to day

Starknet Community & Shamans Highlights


We’re introducing changes to the syntax of Cairo 1 to improve safety and extensibility.
Transitioning from existing Cairo 1 code to the new syntax should be fairly easy and straightforward; only the “outermost layer” of the contract is affected.

The new syntax will take effect in Cairo’s next compiler version (v2.0.0), that will become available on Starknet v0.12.0.

The existing and new Cairo 1 syntaxes will live side by side for at least six months. That is, we encourage developers to migrate over to the new Cairo 1 compiler syntax, and you have six months to do so. This guarantee will hold for any future breaking changes on the compiler; contracts compiled with an old compiler version will be accepted on Starknet for at least six months after deprecation.

The new syntax will come in two phases. Only the first phase includes breaking changes.

The first phase focuses on safety (e.g., enforcement on view functions, clear distinction between pure functions and functions that modify the state)

The second phase focuses on extensibility - allowing smart contracts to use components written in external libraries.

We’re working with Cairo 1 auditors to ensure that re-auditing of Cairo 1 code will be painless and inexpensive.

This is a technical post intended for developers and anyone who likes reading about smart contract languages; proceed at your own peril!

Heavily discussed StarkNet Improvement Proposals

Useful links & articles

Developer resources

Dates and Events

You can check out all of the past updates here.

None of the content of this newsletter is financial advice. Always do your own research.

Thank you for reading, and see you next week. ⏳

Would you like to sponsor this newsletter? Reach out to me.

Join the conversation

or to participate.