StarkNet has been around for over a year and a half and the community has grown like crazy.

Here is an attempt to summarize 1.5y of @Starknet (and apologies in advance if I forgot some).

Thread 🧵 StarkNet started on June 14, 2021 (medium.com/starkware/star…), and afaik the first contract deployed by a person external to StarkWare was made by @kobigurk (kobi.one/2021/07/14/sta…) a month later. 1/25

For the nerds among you, a couple of days ago, someone in the #StarkNet community asked: "What's difference between zk proof, succinct proof, and validity proof?"

Here is my answer... 🧵👇 So for semantic
- a Validity Proof is a cryptographic proof verifying that a computation was done correctly
- a ZK Proof is a Validity proof that, in addition, doesn't reveal knowledge about the computation out of what was agreed upon
- a Succinct Proof is a proof fast to verify

Personal Tip using Stable Diffusion:
So I have been trying to make some nice images using it with the objective of decorating my apartment with some, but I somewhat kept failing with images with a lot of artifacts which would make it weird to print.

Found a solution 🧵... To start, instead of running it on my Mac (which I did and is very slow), I started to use replicate.com which is awesome and makes everything simple.

Step 1: Write a prompt and find a result that you like using SD (replicate.com/stability-ai/s…)

How will you practically run #StarkNet?

A thread⬇️⬇️⬇️ 1/8 Like with any network, StarkNet has an L2 node. This is what the network indexers, block explorers, hobbyists, and all other network participants will run to see the latest transactions in the network. This node will run every transaction and update its state accordingly. 2/8

As promised, a thread on data availability, or: How I Learned to Stop Worrying and Love Ethereum

Let start with a definition. We call the State, the current set of elements stored on the chain. It can be UTXO, ETH balance in an account, or active storage of a contract. 1/7 On StarkNet, the state is compressed using a Merkle Root and every state transition must update the state Merkle root on Ethereum, making it final.

Therefore, to continue pushing the chain forward, users must know all the current elements to recompute the Merkle tree. 2/7

I received quite significant questions about the advantages zkRollups bring compared to regular smart contracts writing.
Here an attempt at exploring such differences. 1/9 ZK-Rollups are blockchain (technically, they are commitchain @stonecoldpat0) which leads to the same dichotomy as any smart contract blockchain. We have:
- L2 calldata: data send within a tx by a user to the L2
- L2 computation: computation done in the L2 2/9

Another random thread on Scalability

Crypto keeps discussing Scalability but often seems to miss the point. One proof: People compare TPS between Bitcoin, Ethereum, and Solana.
Please don't do it!!!

So, let try to define Scalability better:

Here is my definition: 1/11 Scalability = More transactions verified on the worst expected machine in the network.
So what is the hardware we are talking about?
- For Bitcoin, it is a Raspberry Pi
- For Ethereum, it is a $40/month machine
- For Solana, it is a $3k/month on AWS 2/11

Because this is how a weekend should look like, here a random thread on StarkNet architecture:

StarkNet is the result of our work on Cairo. Cairo is a language/VM optimized for ZKPs.
Cairo as a VM has the structure of CPU (CPU-AIR --> Cairo). 1/8 As a consequence, it can run with a single circuit (called AIR in the context of Starks) and prove multiple programs within the same proof.
Since we have a CPU, we can now program an Operating System. This is why the official name for StarkNet is StarkNet OS. 2/8

An interesting fact, little known in the community:
Roughly, half of ERC20 in the market are implementing the standard called ERC-20 Snapshot (docs.openzeppelin.com/contracts/3.x/…).
1/9

https://twitter.com/StarkWareLtd/status/1447911018185863170

You may not believe me but @Uniswap Uni is using it, @AaveAave stAave is using it and all tokens used in Snapshot right now are implementing this standard.
Here is Uni implementation
2/9

1/n We just publish the new extension of dAMM on which I have been working for some time with @Brechtpd from Loopring. I believe it could be a groundbreaking design in the upcoming multi L2s.
A quick thread 🧵:

https://twitter.com/StarkWareLtd/status/1420716961990860807

@Brechtpd 2/n For those who follow @StarkWareLtd work, we publish a few months back the first version of dAMM: an L2 AMM design where the restrictions are enforced on L1, simplifying greatly the AMM design of a constrained system like StarkEx.