Social and ecosystem @StarkWareLtd Crypto survivor from the 2017 wave views are my own, nfa, dyor, stay safu
Everything on Starknet 👉
Joined March 2022
- Tweets14.2K
- Following590
- Followers11.6K
- Likes28K
Pinned Tweet
1/ Privacy, quantum security, and Bitcoin: three of crypto’s hardest problems, representing trillions in potential economic value.
Starknet is going after all three with $STRK sitting at the center of it.
I put the entire thesis into one place:
starknetthesis.io/
***** coded.
People already trade together.
Someone finds a coin. A friend knows the team. Another spots something everyone missed. You talk, disagree, change your mind.
Then it's all scattered across chats screenshots and trading apps.
With XXXXX, we want to bring more of that together. from "look at this" to deciding what to do with it.
99% evidence that we live in a "simulation":
- ICE, the owner of the NYSE, partners with TradeXYZ to bring Hyperliquid perps to the US. Legendary investor Stan Druckenmiller makes his first-ever tweet to announce his investment. Elon Musk reacts.
- Hours later, Binance suffers the biggest CEX hack in crypto history, with $6.3B stolen.
this planet has way too many low probability "coincidences".
Brother Lyskey 🥷 retweeted
People are suspicious of this observation because it seems like consensus, but it's still true:
If you told someone a few months ago that we'd have the largest hacks ever, Clarity Act fail, the internet breaking down, an economic war of attrition in the middle east, oil sitting over $100, bond yields exploding, and AI making math breakthroughs that threaten the foundation of the digital world
And then you showed them the chart
They just wouldn't believe you.
The price has to be telling us something. Right?
Damn, crazy what the Starknet ecosystem shipped on quantum security in a single month.
*checks notes*
→ Post-quantum L1 research initiated
→ Quantum-safe transactions signed from a phone achieved internally
→ STARK proofs generated on a phone
→ Post-quantum wallet migration demonstrated on testnet
→ Quantum-safe Bitcoin costs reduced by 82%
→ Falcon verification costs cut by 50%
→ Post-quantum mainnet transactions for $0.027
The Starknet ecosystem is clearly leading in the quantum space.
Falcon verification costs cut by 50%:
nitter.cf/starkwareltd/status/21…
Post-quantum signatures are getting cheaper on Starknet.
In less than a week, the Falcon Challenge has reduced Falcon-512 verification costs by 50.2%, from 48.4M to 24.1M gas. And we're just getting started.
Bring your AI agents and join the challenge: starkware.co/blog/closing-th…
Post-quantum mainnet transactions for only $0.027: nitter.cf/tanya25519/status/2111…
today, i got a fully spec-compliant falcon-512 account to transact on starknet mainnet for $0.027.
tx: voyager.online/tx/0x2631f4a7…
Brother Lyskey 🥷 retweeted
remember the 267M $STRK staked within one minute on tuesday night?
traced it onchain. every token landed in one validator pool: Bitwise Onchain Solutions
> pool went from 37.6M to 308M STRK in 4 blocks
> now 320M, the most STRK of any Starknet validator (18% of STRK stake)
not retail. a few very large holders (474) picked an institutional operator
for scale, Ready has ~31.8k delegators and 140M STRK
Bitwise is now the #2 validator on Starknet.
And it holds more ethereum:0xca14007eff0db1f8135f4c25b34de49ab0d42766 than any other validator.
Pay attention to who's building a position here.
Ekubo is becoming the infrastructure other AMMs build on.
Fynd’s new AMM runs on Ekubo and adjusts its fees after seeing competing quotes, aiming to win more trades and maximize LP revenue.
Already live on Ethereum, Base, Arbitrum and Robinhood Chain.
For Ekubo: a new channel for order flow, potentially more volume and fees, and a concrete example of teams choosing its tech to build new AMM models.
The ticker is $EKUBO.
nitter.cf/PropellerSwap/status/2…
Opus is one of the very few Starknet protocols sharing revenue with users: 75% goes to stakers.
Now you can earn your share privately, currently offering 28% APY on stablecoin.
The most underrated DeFi protocol on Starknet.
Privacy is live on Opus.✨
Borrow privately. Stake privately.
Do everything privately.
Switch on private mode and your positions sit under a shadow account, not your main wallet.
Built on Starknet’s STRK20 🥷
app.opus.money
Brother Lyskey 🥷 retweeted
propAMM on top of Ekubo
Why? If you are undercutting the competition, might as well do it on the most capital efficient DEX
Extensions make this trivial to build. You can wrap your swap in any kind of function and use a different ABI, using Ekubo's secure foundation
LPs risk very little by depositing in these custom pools on top of Ekubo (at most you lose swap fees) and it inherits Ekubo's efficient AMM infrastructure
Ethereum's Glamsterdam upgrade timeline:
→ Initially targeted H1 2026
→ Delayed to September 2026
→ Delayed again to December 2026
→ Now likely pushed to 2027
And that's just ONE upgrade.
How can anyone realistically expect Ethereum to become fully post-quantum secure by 2029 at this pace?
Especially when post-quantum security requires fundamental changes to Ethereum's cryptography.
No wonder Starknet is exploring becoming an L1, especially in an era where AI is accelerating everything.
nitter.cf/nero_eth/status/211463…
Last week, core devs had to delay forking the Hoodi testnet to Glamsterdam to study a report by @chain_security which revealed some problems with how EIP-8037 interacts with a few contracts.
Over the weekend, ppl tried to get a better picture of the impact and by now it's quite well understood. So here's what you need to know:
What's been known is that contracts which hardcode forwarded gas are affected by repricings, e.g. making state writes (SSTORE) more expensive.
What's new is that some coding patterns rely on specific invariant which were broken with EIP-8037.
Gas already spent can come back mid-tx, so gasleft() can go up. This causes two problems:
(1) a before / after gas counter underflows and reverts
(2) a failed sub-call hands gas back, so a path that should've been unreachable runs, and the tx looks like it succeeded
Related but different: (3) measuring the gas usage of a call using GAS - before and after the call - might undercount because the state gas reservoir is not visible during execution (e.g. gas_left).
It's now about deciding how to proceed. Delaying hoodi bought time but won't resolve the issue. This week, we have to dig deep into contracts and make sure nothing is missed. Eventually, this might just need some coordination among the involved parties (dapps, core devs, auditors, people running nodes, etc.), or worst-case, spec changes.
If you're an app dev or auditor, check your contracts for issues with EIP-8037/EIP-8038, and report them.
Also, share this with your favorite app dev to spread awareness.
