We think the EVM is doing too much work in ZK.
Modulus is exploring another route: express computation as logic and prove that directly.
zkFOL is already public: https://t.co/X0PsYQwujV
Working toward proofs that cost less and reveal less.
ZK Basics | Ep. 8: Why ZK proofs cost so much
Verifying a proof takes milliseconds. Creating one is the expensive part. Here's where the money goes:
1. The computation gets rewritten. Your program has to be turned into a form math can prove — a circuit. Nothing about this step is free.
2. Proving is heavy. Building the proof can take thousands of times more compute than just running the program normally.
3. Specialized hardware. Serious proving runs on GPUs and custom chips, which is why there's a whole industry around proving infrastructure.
4. It's dropping fast. Costs have fallen by orders of magnitude in a few years, which is exactly why ZK moved from papers to production.
The tradeoff: pay once to prove, let everyone verify cheaply forever.
Save this one💜
zkFOL
~20 lines stating sudoku rules. Solves 17-clue puzzle, proves & verifies it, from that statement alone
The same fib spec runs forwards & backwards off one witness
fib(10,000) ~10ms vs 3.69s-49.24s. 370x-4,930x
Prover memory <10MB vs 17GB. 1,700x
Do you feel in charge?
We’re pleased to report that @moduluszk's zkFOL tech stack is now public for review at https://t.co/Z4fEVjbS0q.
The paper draft is also online at https://t.co/CKqxsrhlqZ
Our docs and website have been updated inline.
We’re pleased to report that @moduluszk's zkFOL tech stack is now public for review at https://t.co/Z4fEVjbS0q.
The paper draft is also online at https://t.co/CKqxsrhlqZ
Our docs and website have been updated inline.
Chainalysis: blockchains are becoming malware command-and-control infrastructure
Chainalysis documents “blockchain dead drops”: malware reads C2 pointers or encrypted instructions from transactions/contracts instead of relying on a takedown-able domain. One DPRK-linked implementation uses TRON and Aptos as redundant pointers to BSC, where encrypted instructions live
A rhyming tale of logic old,
Of paths made straight, not bent or bold.
From Turing’s shelf to proofs anew!
A Christmas Gift from us, to you 💝
Merry Christmas from all the team @ModulusZK 🎄🎅
Modulus is being rebuilt as an L1. Contracts are first-order logic predicates, enforced with ZK proofs. No bytecode & no VM. This can solve every smart contract level exploit in existence.
Currently updating website, docs & deciding what we want to make public on GitHub.
The largest digital asset manager in the world literally said "transparent ledgers + AI = permanent financial surveillance" and you're still writing it off as anon babble?
Every wave of technological change brings new privacy risks. This time, AI is the threat. $ZEC is the response.
Wave 1: 1970s. Computers digitized records and automated financial systems.
Wave 2: 1990s. Rise of the internet brought concerns of online identities.
Wave 3: Today, AI can track financial activity at scale.
$ZEC shielded transactions were designed for exactly this. Read more: https://t.co/KgENEZ4fFG
On every other chain, a broken contract pays the attacker. On @Moduluszk, a broken contract refuses to act.
A mistake becomes a delay, never a loss.
That single sentence, is why the whole blockchain world, has been waiting on this.
The great hacks of this industry all lived in one place.
The gap between what a contract promised & what its code did.
This update, we publish that gap’s deletion. On @ModulusZK, the rule you read is the rule the chain enforces. A transaction that can’t be proved never happens.
When a protocol is hacked, you tend to see blame placed on either:
A) The team
Or
B) The auditors
Nobody ever asks “should the coding language itself, allow for so many unforced errors?
Same constraint applies to everyone else.
If the base layer broadcasts every move, serious capital will not use it for anything that matters.
Privacy is not a feature request.
It's a requirement for the system to function.
Central banks cannot run modern monetary policy on a fully transparent ledger. Every large transfer, reserve movement, or intervention becomes visible to rivals in real time. Adversaries can front-run, counter, or weaponize that information. Privacy is a strategic necessity.
Ownership and accountability matter.
The work has begun to integrate a @ModulusZK verification protocol into Totem LLM to prove that a text, image or video has been created by a specific Totem instance.
Much more to come. Just getting started.
Support is active duty.
First you read.
Then you use that knowledge as a weapon.
You find the holes in flawed narratives and you hammer them relentlessly in public.
You take point and clear the landing zone.
It's crazy seeing "a community" come out to offer support & give pats on the back when a project shuts down. As a founder, I'd be thinking "where were you when I needed you most?"
Support the projects you "claim" to love when they still exist & maybe... they won't shut down?