Ξigen Network

Functional Encryption Overview. #FE #Privacy #MPC #ZKP link.medium.com/l3mKWsNAROb

🚀Run @openclaw in 30 seconds 🆓Free coupons are available. Check out: clawup.org

zkGM

#ETHDenver2025 #ZKVM @HouseofZK

zk is the endgame.

Happy Holiday!

Privacy WIN! #zkp #privacy #TornadoCash #zkvm Summaries about the legal analysis, ca5.uscourts.gov/opinions/pub/2… The International Emergency Economic Powers Act and the North Korea Sanctions and Policy Enhancement Act vest the President with the authority to regulate “property” in which a foreign “national” or “person” has an “interest.” The court must determine if Tornado Cash and its smart contracts fall within this definition. Analysis of “Property” Definition: The court starts with the statutory text and the ordinary meaning of “property,” which is something capable of being owned. The dictionary definitions and the Supreme Court's interpretation support this understanding. The immutable smart contracts at issue are not property because they are not capable of being owned. More than one thousand volunteers participated in a “trusted setup ceremony” to make the code unchangeable and uncontrollable, so no one can exclude others from using the contracts. Even with the sanctions, the contracts continue to operate, and some users may become liable when digital assets are transferred to them via Tornado Cash without their knowledge or consent. OFAC's Regulatory Definition: The court also considers OFAC's regulatory definition of “property,” which includes “contracts of any nature” and “services of any nature.” However, the court finds that even under OFAC's definition, the immutable smart contracts do not qualify as property. They are not ownable, not contracts (as they lack an agreement between two or more parties), and not services (as they are merely tools used in providing a service and Tornado Cash does not own the services). The court rejects the Department's attempt to conflate “interest” with “property” and emphasizes that the catch-all for “any other property” still requires the item to be property. Conclusion: The court holds that OFAC exceeded its statutory authority in designating Tornado Cash. The immutable smart contracts are not “property” under the common or regulatory definitions, so the court need not address whether Tornado Cash qualifies as an “entity” or has an “interest” in the contracts. The court reverses and remands the case to the district court with instructions to grant Van Loon's partial motion for summary judgment based on the Administrative Procedure Act.

I curated a list of zkVMs to learn from github.com/rkdud007/aweso…

@rel_zeta_tech @nico_mnbl @powdr_labs @mmagician @NPLabs_ @MinaProtocol @lagrangedev @powdr_labs announced the release of powdrVM version 0.1, their zkVM with multi-prover support (#Plonky3, #Halo2, @0xPolygon PIL STARK, @Eigen_Network Starky). Tweet: x.com/powdr_labs/sta… Article: powdr.org/blog/powdrvm

@TheBlock__ Why not 1 million?

Vitalik Buterin outlines ambitious goal of 100,000 TPS for Ethereum’s rollup-centric scaling roadmap theblock.co/post/321648/vi…

@zkPass Congrats

We’re thrilled to announce that zkPass has successfully secured $12.5M in a Series A funding round! This brings our total funding to $15M and will accelerate zkTLS development across Web3 ecosystems. Shipping matters more than storytelling. 🧵 1/10

#TEE vs #ZK 1. Transparency&Security TEE: trust the hardware vendor, but no one provides an opensourced audit report for the hardware’s security implementation. Especially, some enclaves use its own certificate server to manage the hardware’s identifies. Think about that what we can do if there’s a backdoor in the CPU. ZK: trust the math, and everything is transparent, and the proof can be verified by anyone. 2. Performance TEE: can even do LLM inference, like Llama 7B with less than 10% efficiency overhead. Basically it can offers several hundreds TFlops in a single GPU TEE instance. Note, this is from some benchmark only, not from production environment. ZK: can proving with several millions HZ in a single GPU server. 3. Use cases TEE: #Oasis, #SECRET network, #flashbot ZK: #Zksync, #Starkware, #R0, #ZKM, #Scroll, #Zcash,….. We released a SGX framework github.com/0xEigenLabs/ei… three years ago, and then built github.com/0xEigenLabs/ei…. We have to say, just choose the RIGHT tech stack for your customers.

The ZK Infrastructure Map V2 - Mapping the ZK pioneers of the past, present and future 🔲🔳 This map showcases 42 projects that have captured our attention for their novel approaches and promising contributions to the field. If you feel we've missed a deserving project, please comment below, reach out at contact@hozk.io, or fire us a DM 🤝 Featured projects: @ProjectZKM, @RiscZero, @SuccinctLabs, @a16z, @NexusLabsHQ, @Lita_xyz, @Eigen_Network, @MinaProtocol, @AleoHQ, @Aleph__Zero, @horizenglobal, @Citrea_xyz, @goatnetwork, @aztecnetwork, @taikoxyz, @Scroll_zkp, @Starknet, @0xPolygon, @nil_foundation, @zksync, @union_build, @zkLink_official, @zcash, @AlpenLabs, @BVMnetwork, @KakarotZkEvm, @MantaNetwork, @LineaBuild, @gevulot_network, @lagrangedev, @zan_team, @MarlinProtocol, @SindriLabs, @PolyhedraZK, @hyle_org, @spaceandtime, @lagrangedev, @zircuit, @HelloTelos, @babylonlabs_io, @fermah_xyz, @brevis_zk

Three months ago, Apple #PCC pushed its trustless cloud AI to another security level with its secure enclave, this is a huge step. For #zkVM, there is no doubt that we can take the advantages of TEE's native auditability for prover.

Check the our latest post about Binius Stark Scheme. eigenlab.medium.com/binius-stark-p… #zkp #stark #zkvm

@VitalikButerin Is it possible to decrease the gas fee for zkRollups?

I take this seriously. Starting next year, I plan to only publicly mention (in blogs, talks, etc) L2s that are stage 1+, with *maybe a short grace period* for new genuinely interesting projects. It doesn't matter if I invested, or if you're my friend; stage 1 or bust. Multiple ZK-rollup teams have told me they're on track to be stage 1 by year end. I'm excited to see that happen! Of course we should not throw away training wheels become we're actually confident that the proof systems are secure; that would be irresponsible. But stage 1 (75% threshold on council to override the proof system, 26%+ of council must be outside the rollup team) is a very reasonable moderate milestone. The multisigs I'm in have not had a single liveness failure in years, let alone 26%. The era of rollups being glorified multisigs is coming to an end. The era of cryptographic trust is upon us.

L2s are a game-changer.

Check out our pure Rust #eSTARK implementation. ZK Hack Montréal: Polygon - The eSTARK Proving System & Plonky3 youtu.be/2WjcXZYo7eA?si… via @YouTube

The ZK Infrastructure Map Mapping the foundational pioneers of ZK innovation in blockchain:

Introduce to Circle Stark link.medium.com/MUmiAdn0VLb