Why are programming languages like Cairo from @StarkWareLtd important for modular blockchains?
A π§΅π
A π§΅π
Solidity is a great language, and one that was custom-built for smart contract development, but it's tailor-made for the EVM.
This means it's great for a lot of things:
Basic state machine functions
Gas management
Standardization of contracts
Composition (meaning contracts can talk to each other easily)
However, by being purpose built for the EVM, there are some quirks that can't be worked around.
Basic state machine functions
Gas management
Standardization of contracts
Composition (meaning contracts can talk to each other easily)
However, by being purpose built for the EVM, there are some quirks that can't be worked around.
Solidity can compile better into SNARKs than STARKs. If we want to truly unlock the power that STARKs provide, we need to build on top of this base layer.
Welcome to Cairo.
Welcome to Cairo.
ZK rollups build on top of the state layer with a new term called provable computing. While you could transpile Solidity to Cairo, it's better to use a purpose-built language that skips Solidity's quirks.
STARKs are much more scalable than the EVM, and need a language that can scale alongside it. Along with scaling more efficiently, it allows access to STARK-exclusive primitives.
This means that developers, previously constrained by gas and Solidity limitations, can build ANYTHING using Cairo.
ZK Rollups are a key piece of the endgame, and languages like Cairo are vital in increasing scalability.
ZK Rollups are a key piece of the endgame, and languages like Cairo are vital in increasing scalability.
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
γ
