SadestDAO💥

for anyone still unsure why we spend time on quantum you dont have to believe q-day arrives next year to see the need. migration itself takes years. good time to keep shipping.

@StarkWareLtd What’s the e2e meaning here?

Quantum computers will break much of the cryptography securing the blockchains we know today. Starknet is making sure it becomes end-to-end post-quantum secure well before that happens.

Privacy everywhere. With Starknet’s privacy SDK and Wallet API now live, there’s no excuse left not to add a privacy mode to your app. strk20.starknet.io/build

Docs load 5x faster now 🏃‍♀️⚡️ End-to-end encrypted. Uncensorable. Sovereign.

there's a whack-a-moley of new ethereum-aligned organizations splintering off from the @ethereumfndn last year, @Etherealize_io & @ethcforg; last month, @ethlabs_org; last week, @ethereuminsti meanwhile the EF just cut 20% of its staff... wth's going on? 🥬 explain 👇

Starknet will be post-quantum secure by 2027. Watch @EliBenSasson explain the roadmap in under two minutes.

Push for Privacy.

ELI5 of ZK (Zero Knowledge): I can prove in ZK I know the combination of a lock. Here's how: I take the lock, turn around, open it, and show you it's opened while hiding the combination with my thumb. Then I close it and shuffle. The hard and magical part is that ANY COMPUTATION can be proved correct in ZK. I can prove to you that the whole blockchain of Bitcoin from Genesis till the latest block is correct, without giving you any detail about the blocks and txs there.

Quantum computers will break certain cryptographic protocols, but some will stay safe. Which cryptography is quantum-resistant and which isn't, and why? Watch my explanation

TL;DR'ing this one: - Quantum is a migration - Starknet has a very unfair advantage - The proving layer uses STARKs, and Starknet has Native AA - The differences between chains look boring until the market asks who can move to PQS without panic - Starknet has one of the clearest post-quantum readiness paths among major smart-contract networks gud article.

On a public blockchain, every balance and every counterparty is readable by anyone, forever. Finance never worked that way. Today STRK20 is live on Starknet mainnet. A pool product on the Starknet Privacy Stack. Regular ERC-20s enter shielded mode, trade against existing Starknet liquidity, and exit as the token that was deposited. No liquidity island. Confidentiality is on by default, with a predefined disclosure path for legitimate regulatory requests. Pricing is a flat usage fee. Shield more, pay the same. Starknet enables applications that cannot exist on other chains. Confidential finance is where that starts. If you are building a financial product whose flows cannot be public, talk to us.

👩‍💻Your webapps should always work.. Even with no WiFi Esp when writing Accessing docs Editing fanfics Wen in a cave 𝗱𝗱𝗼𝗰𝘀․𝗻𝗲𝘄 > 𝗱𝗼𝗰𝘀.𝗻𝗲𝘄 Comparison #3: offline access 🔊Sound on if u like lanad3lr3y

A few unique choices we made when we designed @Starknet and why I think they'll be the popular and obvious choices in the future: 1. 𝗦𝗧𝗔𝗥𝗞𝘀. Mentioned before but it's really remarkable so worth saying again. In the early days of StarkWare we were the only ones building and advocating for STARK-tech. The crypto ecosystem doubted the scale STARKs can deliver, privacy was not prioritized back then, and quantum computers seemed like they are light years away. Other scaling solutions choose to go with fraud proofs or SNARKs. Over time we proved the massive scale that STARKs are capable of and the high security that comes with. Gradually the ecosystem acknowledged the benefit of ZK for scaling. Fast forward to today: Privacy became a priority and quantum-resistance is becoming an urgent requirement. So, with high certainty, most teams starting to build new projects will want tech that can deliver massive scale, privacy and post-quantum security. and they will choose STARKs. This is something we're already seeing. 2. 𝗖𝗮𝗶𝗿𝗼: 𝗭𝗞-𝗳𝗿𝗶𝗲𝗻𝗱𝗹𝘆 PL and VM If you're scaling with ZK proofs, the logical thing to do is create a VM that can process ZK efficiently. Sadly, EVM can't. So we decided to go with Cairo - a ZK-friendly programming language and VM. Going with a zkVM instead of EVM is challenging when you want to grow an ecosystem because with so many EVMs around, it's easier for builders to build with solidity. But for the long-term future of a chain, scaling with ZK would require an efficient tools and infrastructure to process it. You can already see more and more teams choosing to build a zkVM. 3. 𝗡𝗮𝘁𝗶𝘃𝗲 𝗔𝗔. EOAs offer a very challenging UX to users. The way to resolve it is to add the option for Account Abstraction. But if AA is not the default, builders constantly need to take into account accounts that can have amazing flexible UX, and in addition to that -- EOAs with their strict UX. So we choose to build Starknet with Native AA, meaning AA is the default. Builders design UX only for user accounts that are smart accounts. This is an obvious advantage for the task of designing UX for your app or wallet, but it's becoming an even bigger advantage when you think about required upgrades, or creating schemes builders did not predict. The flexibility in designing UI/UX is the key to unlocking mass-adoption. Simple UX means more people can use your app. So we made a few unique choices when we started building Starknet, and my bet is they will become the popular choices for projects in the future.

[Shield Rush] is live. A campaign where anyone can participate in daily activities using Shielding to earn a share of rewards. This campaign is powered by @StarkWareLtd. Getting started is easy 🧵

Go crypto: Excited about the $1T+ mega-IPOs? Don't. Total market cap of NASDAQ+NYSE = $69T. If each of Anthropic, SpaceX and OpenAI IPO at $2T, there isn't enough money in the whole market for each to do 10x. DYOR, not investment advice.

5 years from now every project will have to have (i) privacy, and (ii) post-quantum security.

I'm a simple man. I love world models. So I opened Fei-Fei Li's new "A Functional Taxonomy of World Models" and ran Ctrl+F: JEPA → 0 latent → 0 LeCun → 0 You cannot write the definitive taxonomy of world models and leave out the entire representation school. That's not a taxonomy. It's a territory claim. Context for the newcomers: LeCun left Meta in Nov 2025 to start AMI Labs, betting everything on JEPA. World Labs shipped Marble the same month. Same prize, opposite bets. She generates pixels and 3D geometry. He refuses to, and predicts in latent space instead. Her taxonomy sorts by output (renderer / simulator / planner), and JEPA is an architecture, not an output. Ok fair. But she names Genie 3, Marble, RTFM, Nano Banana, NVIDIA’s Omniverse. Naming almost every artifact except the most-discussed rival paradigm is a choice, not an accident.

gm gm @dappcon

The first challenge was to create 𝗱𝗲𝗰𝗲𝗻𝘁𝗿𝗮𝗹𝗶𝘇𝗲𝗱 systems. Then the challenge was to 𝘀𝗰𝗮𝗹𝗲 them. Now it's time to enure they offer 𝗽𝗿𝗶𝘃𝗮𝗰𝘆. Next step will be ensuring they're 𝗽𝗼𝘀𝘁-𝗾𝘂𝗮𝗻𝘁𝘂𝗺 𝘀𝗲𝗰𝘂𝗿𝗲.