The more you understand the $Cult , the more indifference you have to all Alts. You understand that everything is in vain and no project deserves that much enthusiasms ...
We are $cult dao
CULT is Noah's ARK , get in teh lifeboat, NOW .
$btc $eth $cult
$CULT DAO FOUNDER @MrOmodulus HAS ALREADY DONE THAT.
#zkFOL a custom high-level language where smart contracts are written directly as first-order logic (FOL) predicates (logical conditions with quantifiers, relations, conjunctions, etc.).
These compile straight into polynomial constraints and ZK proofs
(using the Zinc/Zinc+ proving stack and arithmetisation techniques from Dr. Murdoch J. Gabbay’s work, who used to work with @IOHK_Charles in the past ).
There is no intermediate bytecode, virtual machine, or separate execution layer—the logical specification is the contract.
A state transition is accepted only if a proof shows the predicate holds.
The implementation is public on GitHub (https://t.co/rrIrqKiJZI), written primarily in Elixir (with Rust components for the prover).
Examples include compact predicates for things like Uniswap-style swaps or Sudoku solvers that can both check and generate solutions.
The claim is large performance gains over #zkVM s (orders of magnitude faster proving and lower memory) by skipping the VM emulation step.
This is the approach that IS ALREADY addressing intents-style verifiable conditions via cryptographic proofs, without the traditional smart-contract language + VM stack.
Nullum est iam dictum quod non sit dictum prius
@IOHK_Charles reviewed Dr. Murdoch Jamie Gabbay’s work on arithmetising first-order logic into polynomial constraints (the foundation of #zkFOL ), built a Lean EDSL around it in 2025, and judged the complexity IMPRACTICAL.
Now he’s developing a new #Cardano language described as “the first of its kind” that enables intents and proof-carrying data via Groth16 proofs...
THE EXACT toolchain Gabbay’s approach feeds into (R1CS → Groth16/PLONK/etc.).
#zkFOL (by @ModulusZK ) is the DIRECT PUBLIC IMPLEMENTATION of that FOL-to-polynomials idea:
Contracts as logical predicates, No bytecode/VM, state transitions only when proved.
@IOHK_Charles ' announcement lands right as that stack goes public with strong desktop-CPU benchmarks against zkVMs.
find the 2024 research paper here:
https://t.co/TLjMmX2ho4
find documentation here: https://t.co/n3yjif0CPL
github: https://t.co/xwGaQqMYKy
PROOF of REWIEW: Post ID: 1925621350695108951
Date: May 22, 2025
@Justin_Bons@CryptoHayes@cobie@zachxbt@WatcherGuru@TheBlockCo@CoinDesk@WuBlockchain@tier10k@scottmelker@sassal0x@HsakaTrades@lookonchain@DecryptMedia@DLNews@BeInCrypto@CryptoSlate@Bankless
@nic__carter
@CoryKlippsten
@unusual_whales
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.
To those who didn't see my message in the telegram. Just awaiting sign off from Dr Chad on the technical elements of the updated docs & website copy, then good to publish and flip public.
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.
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.
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?