Here we report on the progress of the leading builders in the zkL1 ecosystem, documenting recent significant releases, technical breakthroughs and general updates
@AleoHQ has released its 2025 technical roadmap, with key milestones including enhancing the AleoBFT consensus mechanism, streamlining the developer experience with AleoVM, expanding Leo’s tooling, and scaling the prover network.
These efforts aim to boost security, scalability, and usability, supporting developers in building privacy-focused apps for mainstream use: https://aleo.org/post/introducing-the-aleo-roadmap/…
The project also announced a simplified way to deploy an Aleo node using a one-click solution on @googlecloud Marketplace.
Users can quickly set up a snarkOS node on Canary, Testnet, or Mainnet with customizable settings. This option removes the need for technical setup, making participation in Aleo’s network more accessible. Users only pay for computing resources: https://aleo.org/post/one-click-aleo-node/…
Finally, @ProvableHQ has announced snarkOS v3.7.x for the Aleo blockchain, featuring an increase to 35 validators and improved throughput: https://provable.com/blog/announcing-snarkOS-v3.7.x…
Developers benefit from import management updates and syncing enhancements. Validator security has been strengthened, with improved RAM usage and deserialization fixes. New API changes make tracking rejected transactions easier. The release goes live on mainnet around May 21, 2025.
@MinaProtocol has introduced two new tools for its ecosystem, developed by @dfst_io: a privacy-focused NFT Standard and a no-code token launchpad.
The NFT Standard uses ZKPs for secure data verification, while the launchpad allows easy creation of custom tokens without coding. All critical security issues were addressed following an audit by @VeridiseInc. Both tools aim to support developers and creators, with further improvements to the ecosystem expected: https://minaprotocol.com/blog/mina-nft-standard-and-token-launchpad-enter-mainnet-beta…
House of ZK recently published a presentation from @Zk_Hub_Global, where @bkase_, CEO of @o1_labs & @MinaProtocol, spoke about the role of ZK in managing access, privacy, and coordination for AI agents: https://x.com/HouseofZK/status/1914679755787424215…
Instead of proving model execution, ZK can provide control over data, payments, and identity, as well as create a private memory layer for agent coordination.
@horizenglobal announced the integration of @fermah_xyz’s universal proof market into its new appchain, Horizen 2.0, launching on @base: https://x.com/horizenglobal/status/1914801640873631813…
This partnership will provide developers with cheaper, faster, and more reliable ZKPs. It supports Horizen’s mission to make privacy tools simple and accessible, helping developers build scalable, privacy-first applications with lower costs and better performance across the ecosystem.
Horizen also partnered with @singularityzk to develop privacy tools for institutional DeFi. Together, they aim to enhance onchain finance by introducing privacy at both the base and transaction layers, creating new standards for compliant and programmable confidentiality in decentralized financial systems:https://x.com/horizenglobal/status/1917563595002634660…
Finally, @ZKVProtocol is hosting a Hacker House in Ho Chi Minh City from May 19-26, with a hackathon scheduled for May 20-22: https://blog.zkverify.io/posts/verified-zk-hacker-house-before-ethvietnam…
Developers will build Web3 applications using zkVerify’s public ZKP verification system. Participants can attend workshops, collaborate with peers, and compete for prizes totaling $1,750. Selected projects may also receive further support through a follow-up incubator and grants program aimed at turning ideas into real products.
ZK Educator @0xMilica recently released a comprehensive thread about verifiers, using @ZKVProtocol as a key example: https://x.com/0xMilica/status/1924525005271961953
@Common__App by @Aleph__Zero is now live on both Arbitrum One and Aleph Zero EVM. The Common Web App lets users shield assets like ETH, USDT, and USDC, breaking links between wallets and future transactions. Supporting popular wallets, it enables private activity across chains without mixers. Users can further protect privacy by withdrawing to fresh addresses and spacing transactions. A mobile app and more features are planned next: https://common.fi/blog/common-web-app-live-on-arbitrum-one-and-aleph-zero-evm/…
In a recent thread, @KubaKulesza_ of Common explored the problem of blockchain privacy, explaining why it remains unsolved despite growing adoption: https://x.com/KubaKulesza_/status/1922635403883876564…
Kulesza explained that while shielding tools and privacy habits offer protection, they require effort and awareness. He calls for better product design that makes privacy easier and automatic, ensuring users aren’t exposed by default while interacting on transparent networks like @ethereum.
@ZcashFoundation has released Zebra 2.3.0, introducing improvements to regtest mode with new methods for managing blocks and a fix for serving certain transparent transactions.
The update restores mining on testnet and regtest and expands RPC methods to support validator nodes after zcashd is deprecated. It also changes Docker defaults, updates tag naming, and removes the getblocktemplate-rpcs flag, since its functionality is now always available: https://zfnd.org/zebra-2-3-0-release/…
@LeastAuthority completed an audit of the FROST Demo code, including the frost-client and frostd components - tools intended to help wallets enable communication between participants and coordinators.
The audit found no high severity issues, and all identified findings are reflected in the current main branch of the frost-zcash-demo repository: https://zfnd.org/frost-demo-audit-frost-client-and-frostd/…
Finally, @ElectricCoinCo shared an article explaining the growing importance of financial privacy in a world dominated by data collection: https://electriccoin.co/blog/private-money-in-a-public-world/…
The article highlights how personal and financial data is routinely harvested without consent. ECC promotes @zashi_app, a wallet built on @Zcash, to help users protect their transactions. They are also developing a Risk Model to educate users about privacy risks and invite community feedback for improvements.
@DuskFoundation has completed ten independent security audits on its entire technology stack, covering consensus, cryptography, networking, privacy, and economic design. All critical and major issues were resolved, with auditors praising the code quality and documentation. These audits validate Dusk’s readiness for institutional-grade applications.
Now live on mainnet, Dusk positions itself as secure, scalable infrastructure for compliant, privacy-preserving financial services. Full reports are publicly available on GitHub: https://dusk.network/news/audits-overview…
The project also released a new node installer with updated Rusk and Rusk wallet binaries, addressing various bugs and introducing new features. Node operators are advised to upgrade following the official instructions provided in the documentation on the Dusk Network website:
https://x.com/DuskFoundation/status/1923375843348222102
@namada announced that testnet upgrades are now finished and the mainnet upgrade will start soon, with phases 4 and 5 expected to follow quickly:
https://x.com/namada/status/1922974481422680082…
Four new assets were also added to Namada's privacy ecosystem: USDC (@circle via @noble_xyz), NYM, UM, and NTRN. This marks the platform’s first stablecoin integration, and increases access to Namada’s privacy tools across multiple blockchain communities:
https://x.com/namada/status/1923049977418317942
@GravityChain has released its latest technical update, showcasing recent progress toward building its scalable, real-time L1 blockchain: https://x.com/GravityChain/status/1920893034406809982…
Updates include bug fixes, new testing modes (Solo and AptosBFT), and performance improvements like RPC compression and LRU caching. Gravity achieved 20,000 TPS in Solo mode but identified storage and pipeline bottlenecks. Next, they’ll improve state root parallelization, pipeline concurrency, and on-chain config to support web3 mass adoption.
Hyli (formerly Hylé) has officially rebranded, simplifying its name while preserving the essence of its original meaning: https://blog.hyli.org/becoming-hyli/
@hyli_org introduces a new L1 blockchain centered on proofs, aiming to make computation verifiable, scalable, and customizable. With native proof verification, fast data availability, and an appchain-by-default architecture, Hyli challenges the blockchain status quo - offering developers a fresh foundation shaped by the industry’s hard-earned lessons.
