Starknet (STRK)

Privacy shouldn’t require moving to a different chain or using a separate protocol. With STRK20s, every asset on Starknet can switch between transparent and private whenever you choose. Builders don’t need to reinvent DeFi. They can simply add privacy to the apps users already know. This feels less like a new product, and more like a new primitive for onchain finance.

Another week. Another reminder that capital follows builders. Starknet ranks #2 in bridged net inflows over the past 7 days. https://t.co/2mcXB9AEbu

I saw a prediction-market privacy wrapper in the Starkware labs. for the biggest prediction market in the industry. Public wallets leak the strategy graph around a trade. Funding path, timing, sizing, exits, and profit movement. The wrapper routes through a the STRK20 shielded pool and fresh accounts, so the trade can happen without exposing the full path onchain. the VPN of crypto, dropping this summer.

StarkWare is committed to ensuring Starknet will be quantum-ready. Why go through the effort? Because the migration process will be short, at least compared to other chains, thanks to ZK-STARKs and native AA, and the value -- reassuring Starknet is future-proofed -- is high. https://t.co/6lK8V6xjnX

Breaking: Starknet v0.14.3 is going live on Mainnet today 🚨 The upgrade is currently planned for 8:10am UTC, with expected downtime of up to 8 minutes. This is a performance, fee-fairness, and infrastructure hardening upgrade. What changes: > Block times drop by 25%, from 2 seconds to 1.5 seconds, reducing network latency. > Starknet closes another post-quantum roadmap item by replacing Pedersen with BLAKE for the OS config hash in the Starknet Core Contract. > Dynamic L2 gas base fee goes live, following SNIP-35, making pricing more adaptive during congestion (based on $STRK price) > Keccak support is added for client-side proving. For users, this means a faster and more stable network. For the ecosystem, this means Starknet’s definition of a full block now better matches real network limits, improving stability without unnecessary price spikes. For builders and infra operators, there are a few important actions to take: > Upgrade full nodes to the latest recommended versions: Juno 0.16.4 or Pathfind

Starknet v0.14.3 is going live on Mainnet this Wednesday, the 8th of July.\n\nThis upgrade improves fee predictability, lowers latency, adds proving support for new privacy flows, and includes breaking changes some projects must prepare for.\n\nHere’s what changes and how to be prepared 🧵

How Extended is building differently When Extended launched, the aim was to make the product trust-minimised, seamless, high-performance, and broad enough to support perpetuals, spot, yield products and portfolio margin. That foundation is now in place. The protocol combines a high-performance trading experience with on-chain settlement and verification. User funds are held in smart contracts, while the trading logic and risk engine are implemented on-chain. Every transaction is verified and settled directly on @Starknet - transparent, verifiable, and open source. One part of that foundation has remained more centralised than the target architecture: the sequencer. Extended is now working to decentralise the sequencing layer, separating transaction sequencing from settlement. The settlement chain will continue to handle custody, with final verification and settlement performed on the underlying public blockchain, while sequencing will be performed by Extended's native network. On-chain order books exist t