ZKsync (ZK)

monday mindshare: - biggest winner: ZK (with aztec + miden). now, the undisputed top 3 narrative - big spike for EVM with monad launching today - prediction markets heating up again, about to reenter the top 10 - biggest loser: AI, which hit a yearly low this week https://t.co/ru4eqiDMv5

The @brevis_zk has already done 125M+ proofs and supports billions in activity. This is why everyone is integrating with them. Clear sign it’s becoming core infrastructure for modular blockchains. https://t.co/jgvExoVXX2

I spent weeks researching why ZK rollups sometimes stall when everything *should* be fine The personal discovery? Most ZK infra is fundamentally fragile when provers drop, return corrupted outputs, or face network partitions They pray, essentially This is why finding @cysic_xyz was such a lightbulb moment They realized resilience wasn't optional it was the bottleneck Instead of fixing the software stack, they built fault-tolerant infrastructure from the ground up > Layered redundancy is non-negotiable > Parallel proof replicas run simultaneously > Erasure-coded task sharding handles data loss > Deterministic verifiers constantly crosscheck all outputs > Slashing + fast checkpointing ensures auto-recovery without halting the finalization pipeline The result is rollups that keep finalizing during real-world prover churn This isn't optimization, it's building the verifiable ComputeFi infrastructure Web3 actually needs #ZK #ComputeFi

What Airdrop Projects actually taught us: · Monad = Taught us that the best "Community Contribution" is using a hot girl PFP to farm engagement · EigenLayer = Taught us that "Points" are infinite, but our liquidity is locked forever · Jupiter = Taught us that being a degenerate trader pays better than being a node runner · LayerZero = Taught us to snitch on our neighbors for a $10 bounty · ZkSync = Taught us that "Randomization" is their favorite eligibility criteria · Starknet = Taught us to check our wallet balance before the snapshot (0.005 ETH rule) · Linea = Taught us that we need a Passport, Face Scan, and DNA test to claim tokens · Blast = Taught us that a Ponzi scheme with a nice dashboard is called "Innovation" · Hyperliquid = Taught us to lose $5,000 in trading fees to earn 50 points · Sui = Taught us that "Community Access" actually means "Public Sale" (No Airdrop) · Manta = Taught us that "New Paradigm" just means "Worthless NFTs" · Polyhedra = Taught us to pay $15 gas to bridge a $0.01 NFT · Worldcoin = Taught us that iris data is worth exactly $60 · Scroll = Taught us that earning "Marks" is harder than actually making money · Zora = Taught us that minting 500 zero‑purpose JPGs makes us look active · Debank = Taught us that social credit scores exist and cost money · Grass = Taught us that an IP address sells for the price of a cup of coffee · Magic Eden = Taught us that "Diamonds" are forever… waiting forever for the TGE · Taiko = Taught us that Galxe quests are unpaid full‑time labor · Orderly = Taught us that "Merits" is another term for "exit liquidity"

Wallet Delegation for Abstract XP: One standout technology from @AbstractChain is Wallet Delegation for Abstract XP, a feature that enhances user security and flexibility in managing blockchain interactions. How It Works: - Users can link any EVM-compatible wallet (e.g., MetaMask, Ledger) to their Abstract Global Wallet (AGW). - This allows transactions and XP accrual (experience points for ecosystem participation) to be credited to the AGW while keeping primary assets in cold storage. - It supports seamless bridging between security-focused storage and active on-chain activity, reducing exposure to hot wallet risks. Why It's Innovative: - Addresses a common pain point in consumer crypto: balancing convenience with security. - Enables "set-it-and-forget-it" cold storage for high-value holdings while still earning rewards and engaging in dApps. - Built on Abstract's zk-rollup foundation (via ZKsync), ensuring low-cost, fast confirmations without compromising Ethereum's security. This tech went live in Jul

Wallet Delegation for Abstract XP: One standout technology from @AbstractChain is Wallet Delegation for Abstract XP, a feature that enhances user security and flexibility in managing blockchain interactions. How It Works: - Users can link any EVM-compatible wallet (e.g., MetaMask, Ledger) to their Abstract Global Wallet (AGW). - This allows transactions and XP accrual (experience points for ecosystem participation) to be credited to the AGW while keeping primary assets in cold storage. - It supports seamless bridging between security-focused storage and active on-chain activity, reducing exposure to hot wallet risks. Why It's Innovative: - Addresses a common pain point in consumer crypto: balancing convenience with security. - Enables "set-it-and-forget-it" cold storage for high-value holdings while still earning rewards and engaging in dApps. - Built on Abstract's zk-rollup foundation (via ZKsync), ensuring low-cost, fast confirmations without compromising Ethereum's security. This tech went live in Jul

< Coupang 33.7 million personal data leak incident, what if Zama's FHE technology had been applied? > @zama #ZamaCreatorProgram Today, it has emerged that the personal data of 33.7 million Coupang users was illegally leaked, causing a growing societal shock (my personal dataㅠㅠㅠㅠ). This essentially represents the entire user base of Coupang and is among the worst cases of large-scale security incidents. The vulnerabilities of the Web2 data management architecture have been fully exposed. A hack implies that at some point, customer data appeared in the internal system in 'plain text' or a state similar to plain text. So, what would have happened if Coupang had used ZAMA's FHE technology? 🔐 Data is encrypted from start to finish. FHE never decrypts data during storage, transmission, or retrieval. Consequently, even within Coupang's internal systems, no plain text data exists. Even if the data of 33.7 million customers were leaked, the actual content would be an indecipherable ciphertext, and hackers would obtain no information. Even if leaked, one could say it was effectively not a leak. 🔐 The 'decryption phase' that caused the incident disappears. Currently, the security weakness of companies lies in the need to decrypt data again during the computation process. However, if FHE technology is used, computations are performed on encrypted data, making hacking practically impossible. < Conclusion > 1. Prevent hacking attempts from the outset using FHE technology. 2. Even if data is leaked, it remains safe because the ciphertext cannot be recovered. A dual-defense architecture can be realized. From Upbit to Netmarble to Coupang... personal information has become public information. Even in Web3, let's protect our privacyㅠㅠㅠ