Cairo lang ships with support for writing tests in Python. I think it’s in many ways superior to the other ways of testing Cairo code. In this post, I share some testing tips and techniques I hope others find useful as well.

Cairo isn’t an object oriented language, yet we can still have mixins. Essentially, it’s possible to do the equivalent of Solidity’s is Ownable in Cairo. All that’s necessary is to explicitly import all the public functions you want to have in your contract.

Cairo is a young language so best practices and conventions are still evolving.

I have a strong opinion that every new programming language should ship with a standard code formatter. Golang does. Rust does. And yes, Cairo does as well 💪

I couldn't attend StarknetCC, so instead I binge-watched all the talks.

Did you know that with every Cairo release, there’s also a new version of the VS Code plugin? If you’ve set up your development environment before the latest version was released (0.9.1, roughly a week ago), chances are your Cairo plugin is outdated. It still works, but you’re missing out.

This blog is dedicated to the practice of writing smart contracts for StarkNet using Cairo lang. I will go beyond the basics and focus on more advanced topics around development, security, and testing of smart contracts, Cairo patterns and tips, StarkNet ecosystem tools and more. If you’re serious about building on StarkNet, you should definitely subscribe.