TL;DR; Account Abstraction is a win for usability in web3 and on Starknet it has been supported from the beginning at the protocol level. For a smart contract to be considered an account contract it must at least implement the interface defined by SNIP-6. …

In part I of this series [1], I showed you the different traits that a smart contract must implement to be considered an account contract. In this article I’ll create an account contract from scratch following the SNIP-6 and SRC-5 standards. Project Setup In order to be able to compile an account…

On part I of this series [1] I showed you the standards associated with Account Abstraction while on part II [2] I walked you through the creation of a new account contract from scratch. …

Part 1: An essential layer to produce safe CASM — Introduction I recently attended two conference talks at Starkware’s Sessions about Sierra: Enforcing Safety Using Typesystems by Shahar Papini and Not Stopping at the Halting Problem by Ori Ziv. I highly recommend you watch these videos if you want to understand more about the Cairo stack. The following post is the…

By Mathieu Saugier and Edgar Barrantes. Special thanks to Jorik Schellekens for reviewing. Earlier this year, StarkWare announced Cairo 1.0 as an improvement to the Cairo programming language that will make it safer, better, and easier for writing contracts. With an improved syntax and a fully-fledged type system, Cairo 1.0…

Guiding Devs through the Expansion into Cairo Programming — Tl;dr Developers are expanding their skills to include Cairo, driven by Starknet’s increasing prominence. Solidity enabled globally interoperable smart contracts but required extensive computation repetition. Cairo’s efficiency stems from its ability to create verifiable transaction execution proofs using a single machine. Both Cairo and Solidity are smart contract languages, but their…