greg cult dav zK 🩸🩸🩸🏴 retweeted
Not many people talk about it, but the $Cult DAO @ModulusZK ecosystem has been quietly building for years without the usual VC circus.
While the built is quiet the community has been loud about it since '22.
That's when $CULT started as a fully decentralized funding DAO.
No team keys, community proposes and votes, 0.4% tax feeds a treasury that invests in other decentralized projects.
Now @MrOmodulus & team are working on our own chain, @ModulusZK, where $CULT is the gas token.
Imagine #ZK in a completely new way.
Compiling first-order logic #zkFOL straight into polynomials instead of routing everything through a traditional VM, aiming for cheaper and simpler proofs.
There’s also $MOD token for specific utilities in the works.
It’s still early, community-driven and worth keeping an eye on if you’re looking for something groundbreaking that’s been grinding in the background.
greg cult dav zK 🩸🩸🩸🏴 retweeted
Check out @ModulusZK and their Zk Fol chain , and its builder @MrOmodulus and the gas token @wearecultdao
greg cult dav zK 🩸🩸🩸🏴 retweeted
In 1689 they wrote "for ever" and "in all times to come" into the Bill of Rights. Not once, three times. They meant it. So who gave later governments the right to scrap it in the small print? Should those rights be put back? Yes or no 👇
greg cult dav zK 🩸🩸🩸🏴 retweeted
why not start with @moduluszk then? The L1 that prevents a large class of smart-contract attacks structurally, rather than detecting or countering them after the fact.
greg cult dav zK 🩸🩸🩸🏴 retweeted
Solar is a big step for the EVM. At the same time, @ModulusZK is showing what happens when you stop optimizing the VM and remove it entirely.
Contracts become pure first-order logic predicates.
A transaction only goes through if it can be proved to satisfy them.
No bytecode,
no interpreter,
no Stack Too Deep,
no gap between the spec and the implementation.
The #zkFOL approach is also orders of magnitude faster to prove than zkVMs on the same hardware.
Worth keeping an eye on if the goal is to close the class of bugs that come from code not matching intent.
greg cult dav zK 🩸🩸🩸🏴 retweeted
the next 6 months. However it could be up to 2-3 years data & world event dependent.
Sell rallies, use stop losses, don’t use leverage & don’t get greedy with green.
Back to $CULT 👇🏼
It has been built for maximum bear market efficiency. That does not mean only up by any means
greg cult dav zK 🩸🩸🩸🏴 retweeted
Yeah ! Who needs a VM ? Not @ModulusZK and their ZkFol chain .
greg cult dav zK 🩸🩸🩸🏴 retweeted
We’re pleased to report that @moduluszk's zkFOL tech stack is now public for review at github.com/zkFOL/zkfol/.
The paper draft is also online at github.com/zkFOL/zkfol/blob/…
Our docs and website have been updated inline.
greg cult dav zK 🩸🩸🩸🏴 retweeted
After the Binance HACK, the queue for building on @ModulusZK should be 5.6Billion Miles long.
Developers in all Industries MUST see the NEED for the Tech developed by @MrOmodulus and his Incredible Team.
"Can't beat a physical vault"
@wearecultdao
greg cult dav zK 🩸🩸🩸🏴 retweeted
🚨 Crypto hacks expose a bigger problem: code can fail.
What if transactions had to PROVE they satisfy security rules before execution?
That's the vision behind @ModulusZK.
🧠 First-Order Logic
🔐 Zero-Knowledge Proofs
🔥 $CULT as planned gas
The future is verifiable.
#CULT
greg cult dav zK 🩸🩸🩸🏴 retweeted
This is what long-term $CULT supporters have been waiting on. I’ll still ask the obvious question though… why does so much of this industry keep ignoring what’s being built?
I found CULT, studied the tokenomics, utility and vision myself. It wasn’t hard to see the potential.
Sometimes it feels like the “big dogs” would rather ignore something they didn’t create or discover first.
I’m bullish, but I’ll admit I’m also frustrated that this hasn’t even earned enough attention yet to push CULT into the hundreds of millions in market cap.
Maybe that changes when people are finally forced to look. 🤷♂️
greg cult dav zK 🩸🩸🩸🏴 retweeted
😏 @ModulusZK
By CultDAO
greg cult dav zK 🩸🩸🩸🏴 retweeted
🚨 Crypto hacks expose a bigger problem: code can fail.
What if transactions had to PROVE they satisfy security rules before execution?
That's the vision behind @ModulusZK.
🧠 First-Order Logic
🔐 Zero-Knowledge Proofs
🔥 $CULT as planned gas
The future is verifiable.
#CULT
这黑客把所有人都耍了，钱冻住了，黑客人却跑了
黑客偷完币，没傻乎乎把U放钱包里等着被冻。
他把USDT存进Aave了。
然后拿这堆U当抵押，借了一堆ETH出来。
借完就走。
人没了。
后面Tether和Circle才开始动手。
一个冻了15亿USDT。
一个冻了8亿USDC。
冻得挺快，数字也吓人。
看着像是把钱给锁死了对吧。
但你仔细想。
冻住的是什么。
是Aave池子里那堆抵押品。
不是黑客手里的ETH。
ETH这玩意儿，没发行方，没客服，也没人能按个按钮给它冻上。
所以就变成现在这个鬼样子。
Aave手里攥着一堆动不了的U。
黑客兜里揣着能随便花的ETH。
协议被卡死了，人跑了。
很多人夸这黑客聪明。
我说这不叫聪明，这叫把所有人都知道、但没人愿意提的那个窟窿给捅开了。
稳定币有发行方。
发行方有冻结权。
DeFi又拿稳定币当抵押品。
那一冻结，清算就卡壳。
这不是Aave一家的事。
是所有吃稳定币抵押的DeFi协议，都得面对的破事。
发行方要合规，协议要自由。
这两边一撞，坏账就出来了。
那最后谁掏这个钱。
不是黑客。
是存钱的人，是持币的人，是整个协议。
这才是最恶心的地方。
他压根不用赢，他只要把这烂摊子甩给别人就行了。
当然，也没那么神。
借钱要付利息，ETH价格也会晃。
链上还全是痕迹，想变现没那么容易。
但这事真正吓人的，不是丢了多少钱。
是它把一个事实摆到了台面上。
中心化发行方的冻结权，和去中心化协议的清算逻辑，到现在根本就没接上。
黑客只是第一个把这层窗户纸捅破的人。
到底是不是他干的，细节对不对，还得等链上数据和官方说话。
但道理已经在那了。
能冻的资产，换成了冻不了的资产。
风险扔给协议，流动性自己带走。
这一手，确实够脏，也够狠。
greg cult dav zK 🩸🩸🩸🏴 retweeted
The $6.3B Binance hack shows how even top exchanges remain vulnerable when systems can approve unauthorized withdrawals after a compromise. No private-key leak reported, yet hot wallets were drained in ~20 minutes.
This is exactly the class of gap @ModulusZK is built to close.
On #Moduluszk , the contract IS the specification:
First-order logic predicates #zkFOL
no bytecode
no VM
no execution layer between intent and enforcement.
A transition only happens if it can be proved.
Defects refuse rather than lose funds.
That architectural difference is still heavily overlooked while the industry keeps patching the same traditional models.
Curious how @binance, @cz_binance, @heyibinance, @_RichardTeng, and the broader team think about verifiable-by-construction approaches for future infrastructure.
Worth a look? @ModulusZK
moduluszk.io
documentation: docs.moduluszk.io/
github: github.com/zkFOL/zkfol
greg cult dav zK 🩸🩸🩸🏴 retweeted
Removing the VM makes this impossible. Only @moduluszk is doing this.
The Binance $5.6B drain is a masterclass in modern EVM exploitation.
It wasn't a complex logic bug. It was an EIP-7702 delegation hijack:
1. Setup: Attacker funds 0x7c86 via Tornado Cash, deploys a sweep contract (0x63e8), and runs three live dry-runs on external wallets.
2. Execution: Attacker submits an EIP-7702 batch with 50 pre-signed authorizations (nonce n to n+49) to hit Binance 14's moving nonce window.
3. One authorization hits. Instantly, Binance 14 (an EOA) is reprogrammed to run the attacker's contract bytecode.
4. Execution looks totally organic: Binance 14 sweeps itself clean. Internal threshold alerts don't trigger because, from the nodes' perspective, the hot wallet is just executing its own transaction.
5. Binance 16 immediately auto-refills 28,000 ETH due to automated treasury rebalance scripts, feeding the exploit loop.
The cold truth: you cannot forge an EIP-7702 delegation list.
For this to execute, the attacker already held the raw private key or unconstrained signing access to Binance 14's HSM/KMS.
But hey, 5.64 billion drained across ETH, BTC, and Tron. 2.54 billion frozen by Tether, Circle, Ripple, and World Liberty within hours.
Code is law until the stablecoin admin keys log in.
Binance got bailed out by the very centralized choke points the cypherpunks warned you about.
Hardware wallets leak your home address.
Centralized exchanges leak the keys to the kingdom.
Self-custody on native, non-delegated chains remains the only honest baseline.
At least you know what to avoid.
