<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Modulus ZK on Medium]]></title>
        <description><![CDATA[Stories by Modulus ZK on Medium]]></description>
        <link>https://medium.com/@moduluszk?source=rss-de6e46557599------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MI8JCDujlz9JqXt4Mn6XJA.jpeg</url>
            <title>Stories by Modulus ZK on Medium</title>
            <link>https://medium.com/@moduluszk?source=rss-de6e46557599------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:38:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@moduluszk/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[BitLogic: Bitcoin’s Quantum Defense Layer]]></title>
            <link>https://moduluszk.medium.com/bitlogic-bitcoins-quantum-defense-layer-4a4d32f86284?source=rss-de6e46557599------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a4d32f86284</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[quantum-resistance]]></category>
            <category><![CDATA[modulus]]></category>
            <category><![CDATA[bitlogic]]></category>
            <dc:creator><![CDATA[Modulus ZK]]></dc:creator>
            <pubDate>Tue, 23 Dec 2025 15:23:01 GMT</pubDate>
            <atom:updated>2025-12-23T15:23:01.983Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>How Our Soft Fork Proposal Protects Bitcoin from Quantum Computing Threats.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gjxJZP-3mobydtTVWMBRzw.png" /></figure><p>When we published the<a href="https://x.com/ModulusZK/status/1991853424468771265?s=20"> BitLogic whitepaper</a> in November, we focused on two breakthrough capabilities: optimal privacy through zero-knowledge proofs and Bitcoin-native programmability through First-Order Logic arithmetization (<a href="https://x.com/ModulusZK/status/1992965575350354347?s=20">covered here</a>,<a href="https://x.com/ModulusZK/status/1993309988983394511?s=20"> here</a>, and<a href="https://x.com/ModulusZK/status/1998812476042080436?s=20"> here</a>).</p><p>What we haven’t emphasized enough is that BitLogic’s architecture provides something equally critical: <strong>native quantum resistance without additional protocol changes</strong>.</p><p>The same three opcodes (OP_POLYEVAL, OP_FIELDVERIFY, OP_COMMITCHECK) that enable privacy and programmability also make Bitcoin quantum-resistant. Quantum security falls out of the design naturally.</p><h3>Why This Matters Now</h3><p>Quantum computers capable of breaking ECDSA are estimated 5–15 years away. Bitcoin soft forks take 18–36 months from proposal to activation. User adoption of new address types takes another 3–5 years to reach meaningful penetration.</p><p>We’re looking at roughly 7–12 years minimum to get quantum-safe addresses into widespread use. The window to start this process is closing.</p><h3>Cryptographic Agility: The Core Defense</h3><p><strong>BitLogic enables Bitcoin to adopt any post-quantum signature scheme without additional soft forks.</strong></p><p>We don’t know which post-quantum algorithms will remain secure long-term. NIST has standardized Dilithium, Falcon, and SPHINCS+, but cryptanalysis continues. New attacks emerge. Algorithms get deprecated.</p><p>Traditional blockchain upgrades require new opcodes for each signature scheme. Want to add Dilithium? New opcodes. Switch to a better algorithm in five years? Another soft fork.</p><p>BitLogic’s opcodes verify polynomial commitments over finite fields, not specific signature schemes. Any signature algorithm that can be expressed as polynomial constraints works natively. Dilithium, SPHINCS+, Falcon, future algorithms we haven’t invented yet all work with the same three opcodes.</p><p>This is cryptographic agility. One upgrade. Permanent flexibility.</p><h3>Zero-Knowledge Privacy as Quantum Defense</h3><p><strong>Zero-knowledge proofs hide public keys on-chain, eliminating the attack surface quantum computers need.</strong></p><p>Quantum computers break ECDSA by deriving private keys from public keys using Shor’s algorithm. But Shor’s algorithm requires having the public key in the first place.</p><p>BitLogic transactions never expose public keys on-chain. The zero-knowledge proof demonstrates that a valid signature exists without revealing the public key itself. Only polynomial commitments and evaluation points appear in the transaction data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rmejdLwSoui-tsCOp1uzVw.jpeg" /></figure><p>An attacker monitoring the blockchain sees commitments but no public keys to attack. This isn’t just quantum resistance — it’s quantum immunity through information hiding.</p><p>Even in multi-party contracts where traditional systems would expose all signers’ public keys, BitLogic reveals only that the threshold was met. A 3-of-5 multisig shows proof of three valid signatures, not which three keys signed or what those keys are.</p><h3>Block Space Efficiency</h3><p><strong>Post-quantum signatures compress to 300–800 bytes through polynomial commitments, achieving similar efficiency to current ECDSA transactions.</strong></p><p>Raw post-quantum signatures are massive. SPHINCS+ signatures: 7–17KB. Dilithium: 2–3KB. Falcon: approximately 1KB. Direct integration into Bitcoin Script would bloat blocks catastrophically.</p><p>BitLogic’s polynomial commitments compress these signatures into succinct zero-knowledge proofs. Instead of including the full signature verification computation on-chain, we verify a polynomial evaluation that proves correct signature verification happened off-chain.</p><p>The on-chain footprint: approximately 300–800 bytes depending on complexity. This is competitive with current 65-byte ECDSA signatures when accounting for script overhead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zg447ZfE3suETrCeMcVXMw.jpeg" /></figure><p>Block space efficiency means quantum resistance doesn’t come at the cost of network capacity. Miners can process quantum-safe transactions without significantly reduced throughput.</p><h3>Backward Compatibility</h3><p><strong>All existing Bitcoin addresses remain valid indefinitely while enabling quantum-safe alternatives.</strong></p><p>BitLogic is a soft fork. Every P2PKH, P2WPKH, P2SH, and Taproot address continues working exactly as it does today. There’s no forced upgrade, no mandatory transition period.</p><p>The soft fork adds new capabilities without removing old ones. Users generate quantum-resistant addresses when they choose to. Wallets can default to quantum-safe addresses for new users while maintaining compatibility with legacy addresses.</p><p>This is the same adoption pattern as Segwit and Taproot. Early adopters get new benefits. Late adopters have years to transition. No one is forced to upgrade on a timeline they don’t control.</p><h3>Linear Verification Complexity</h3><p><strong>Post-quantum signature verification remains O(n) complexity, keeping node operation decentralized.</strong></p><p>Quantum-resistant signatures typically require thousands of hash operations. Direct verification in Script would mean nodes spending seconds per transaction, not milliseconds.</p><p>BitLogic opcodes verify polynomial evaluations, not full signature algorithms. One field operation. Bounded complexity. Predictable cost.</p><p>O(n) scaling means Raspberry Pi nodes can validate quantum-resistant transactions. No mining centralization pressure from expensive verification. Network decentralization is preserved.</p><p>Compare this to alternative proposals requiring full SPHINCS+ or Dilithium verification in Script. Those approaches would create node operator classes: high-resource operators who can keep up with verification costs, and everyone else who gets priced out.</p><h3>Hybrid Security Models</h3><p><strong>BitLogic supports combining multiple post-quantum algorithms simultaneously, protecting against single-algorithm breaks.</strong></p><p>Defense in depth requires algorithm diversity. If Dilithium gets broken by new cryptanalysis, you don’t want your entire security model to collapse.</p><p>BitLogic’s FOL framework lets you express: “Valid if (2-of-3 Dilithium signatures) OR (5-of-7 SPHINCS+ signatures) OR (3-of-5 Falcon signatures).”</p><p>One predicate. One proof. Multiple security assumptions.</p><p>This composability extends to migration strategies. During the transition period when quantum computers are emerging but not yet dominant, you can require: “Valid if (quantum-safe signature) AND (legacy ECDSA signature).”</p><p>Users who want maximum security today can implement hybrid schemes immediately after soft fork activation. Users who prioritize simplicity can use single-algorithm approaches. The system accommodates both.</p><h3>Voluntary Adoption Timeline</h3><p><strong>No protocol deadlines or forced upgrades. Users choose when to adopt quantum-safe addresses.</strong></p><p>Bitcoin’s strength is voluntary participation. BitLogic maintains this principle.</p><p>After soft fork activation, wallets implement quantum-resistant address generation. Users who want quantum protection immediately can generate new addresses and move funds. Users who prefer to wait can continue using existing addresses.</p><p>There is no sunset date for ECDSA addresses. No protocol rule forcing adoption. No consensus change that makes old addresses invalid.</p><p>Market forces and quantum threat assessment drive adoption. When users perceive quantum risk as real, they’ll upgrade. Until then, the option exists but is not mandatory.</p><p>This voluntary approach has precedent. Segwit activated in 2017. In 2024, approximately 85% of transactions use Segwit addresses, but legacy P2PKH addresses still work. The same adoption curve will apply to quantum-resistant addresses.</p><h3>Deterministic Verification</h3><p><strong>Polynomial evaluation has bounded complexity, preserving Bitcoin’s consensus guarantees.</strong></p><p>Bitcoin’s consensus depends on deterministic verification. Every node must reach identical conclusions from identical data. No non-deterministic computation. No unbounded execution.</p><p>BitLogic maintains this guarantee. Polynomial evaluation over finite fields Fp is deterministic. Given a polynomial P, evaluation point a, and field prime p, the result P(a) mod p is unique and computable in bounded time.</p><p>The Schwartz-Zippel lemma provides cryptographic soundness: for a polynomial of degree d over field Fp, the probability of false acceptance is bounded by d/p. With p &gt; 2²⁵⁶ and reasonable degree constraints, this probability is negligible.</p><p>Verification cost is determined entirely by the polynomial structure, which is visible before execution. No runtime surprises. No gas estimation uncertainty. No consensus failures from computation timeouts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TkvQvb6Jcnr95b7_3z9PQQ.jpeg" /></figure><h3>SHA-256 Remains Secure</h3><p><strong>Mining and block structure protected through SHA-256’s quantum-resistant properties.</strong></p><p>Grover’s algorithm affects symmetric cryptography differently than Shor’s algorithm affects public-key cryptography. Shor’s algorithm completely breaks ECDSA. Grover’s algorithm reduces SHA-256 security from 2²⁵⁶ to 2¹²⁸.</p><p>2¹²⁸ operations remain computationally infeasible. Even with quantum speedup, finding a SHA-256 preimage requires more energy than exists in the solar system.</p><p>Bitcoin’s mining function (double SHA-256) maintains security. Block hashes remain quantum-resistant. Transaction IDs remain quantum-resistant. Merkle trees remain quantum-resistant.</p><p>The only vulnerability is signature verification. BitLogic addresses this specific weakness without requiring changes to Bitcoin’s proof-of-work or block structure.</p><h3>Two-Tier Security Model</h3><p><strong>Active Bitcoin supply becomes quantum-safe while preserving legacy address compatibility.</strong></p><p>Post-soft-fork, Bitcoin’s security becomes bifurcated.</p><p><strong>Quantum-resistant tier</strong>: New addresses using post-quantum signatures through BitLogic opcodes. Institutional holdings, exchange wallets, active users. Based on Segwit/Taproot adoption patterns, we’d expect 70–80% of economically active supply within 5–10 years.</p><p><strong>Legacy tier</strong>: Existing addresses using ECDSA. Remains valid indefinitely. Includes old coins, unclaimed UTXOs, and users who choose not to upgrade.</p><p>Users who need quantum protection can get it. Users who prioritize simplicity or have different risk assessments can keep using current approaches. Both groups coexist without conflict.</p><p>The important metric is not<em> “percentage of total supply that upgrades”</em> but <em>“percentage of economically active Bitcoin that upgrades.</em>” Lost coins and abandoned addresses may remain in the legacy tier indefinitely. That’s acceptable. What matters is protecting coins that are actually being transacted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nR6oTarQoyt3FvBiyxN3CQ.jpeg" /></figure><h3>Implementation Path</h3><p>The technical foundation exists today. Dr. Jamie Gabbay’s FOL arithmetization research is peer-reviewed and published. The BitLogic whitepaper provides full specification of the three opcodes. Implementation can begin immediately.</p><p>Requirements:</p><ol><li>Bitcoin Core implementation of OP_POLYEVAL, OP_FIELDVERIFY, OP_COMMITCHECK</li><li>Soft fork activation mechanism (BIP9 or Speedy Trial)</li><li>Wallet integration for quantum-resistant address generation</li><li>User education on adoption benefits</li></ol><p>Timeline: 18–24 months from implementation start to soft fork activation. Another 12–24 months for major wallet adoption. Bitcoin could be quantum-ready by 2027–2028, assuming we start now. Every month of delay extends that timeline.</p><h3>Why BitLogic Over Alternatives</h3><p>Other quantum resistance proposals exist. They fall into three categories:</p><p><strong>Category 1: Single-algorithm integration</strong> (e.g., dedicated SPHINCS+ opcodes)</p><ul><li>Requires 8–12 new opcodes</li><li>Locks Bitcoin into one algorithm</li><li>High verification costs (thousands of hash operations)</li><li>Future algorithm changes require new soft forks</li></ul><p><strong>Category 2: Generic covenant systems</strong> (e.g., OP_CAT enabling recursion)</p><ul><li>Enables quantum resistance theoretically</li><li>Unknown verification costs</li><li>High consensus risk from Turing-completeness</li><li>Complex security analysis</li></ul><p><strong>Category 3: Do nothing, upgrade when quantum computers exist</strong></p><ul><li>Catastrophic if quantum breakthrough happens faster than expected</li><li>Forces emergency protocol changes under crisis conditions</li><li>No time for proper testing or community consensus</li><li>High risk of chain splits or centralized decisions under pressure</li></ul><p>BitLogic provides quantum resistance with minimal opcodes, cryptographic flexibility, bounded costs, and proven mathematical foundations. It’s the conservative choice that provides maximum protection.</p><h3>Conclusion</h3><p>Bitcoin’s $1.3 trillion security model depends on cryptographic assumptions that quantum computers will break. Not theoretical. Inevitable.</p><p>BitLogic gives Bitcoin the tools to survive. Three opcodes. Cryptographic agility. Voluntary adoption. Backward compatibility.</p><p>The architecture we built for privacy and programmability happens to be exactly what Bitcoin needs for quantum resistance. This convergence isn’t coincidental. It emerges from using mathematically sound foundations (First-Order Logic, polynomial commitments, zero-knowledge proofs) instead of ad-hoc script extensions.</p><p>We’ve laid out the technical case. The implementation path is clear. The timeline is urgent but achievable.</p><p>Bitcoin can build these defenses now, or wait until quantum computers force emergency protocol changes. We think the choice is obvious.</p><p><strong>Technical Foundation</strong></p><ul><li>Research: Dr. Jamie Gabbay, “Arithmetization of First-Order Logic” (2024)</li><li>Published: <a href="https://eprint.iacr.org/2024/954.pdf">https://eprint.iacr.org/2024/954.pdf</a></li><li>BitLogic Whitepaper: <a href="https://github.com/ModulusZK/BitLogic-from-Modulus-zkFOL-Bitcoin/">https://github.com/ModulusZK/BitLogic-from-Modulus-zkFOL-Bitcoin/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a4d32f86284" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Yield Generation Works Natively on Bitcoin with zkFOL]]></title>
            <link>https://moduluszk.medium.com/how-yield-generation-works-natively-on-bitcoin-with-zkfol-7681cc1344d2?source=rss-de6e46557599------2</link>
            <guid isPermaLink="false">https://medium.com/p/7681cc1344d2</guid>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[modulus]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[zkp]]></category>
            <dc:creator><![CDATA[Modulus ZK]]></dc:creator>
            <pubDate>Wed, 10 Dec 2025 15:05:30 GMT</pubDate>
            <atom:updated>2025-12-10T15:05:30.086Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xv7olh0Vqby92dc5lCIsLg.png" /></figure><h3>Overview</h3><p>zkFOL enables<strong> native Bitcoin yield</strong> directly on Layer 1 without bridges, wrapped tokens, or external custody. Following the activation of OP_POLYEVAL, OP_FIELDVERIFY, and OP_COMMITCHECK, all yield operations execute and verify within Bitcoin’s base protocol.</p><p>Yield generation emerges from <strong>provable state transitions in formal logic</strong>: proofs that redistribute value based on deterministic performance functions, enforced through First-Order Logic (FOL) and verified natively in Bitcoin Script via finite-field algebra.</p><p>Every yield action (deposit, compound, withdraw) is expressed as a mathematical predicate that compiles to a polynomial constraint, verified directly by Bitcoin nodes. Returns are verifiable, proportional, and noninflationary. BTC never leaves user custody; it remains locked in script conditions governed by mathematical proofs.</p><h3>Step-by-Step: zkFOL Native Yield Lifecycle</h3><h4>1. Yield Pools as Native Bitcoin Scripts</h4><p>A yield pool is defined as a logical relation between participants’ shares, accumulated returns, and total yield over time.</p><p>Each participant holds a UTXO encumbered by a zkFOL script proving their proportional claim:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*IQl5BdwPHKU0a5Zt9jgSxw.png" /></figure><p>Where:</p><ul><li>α = total yield rate for the period</li><li>share_i = individual’s contribution (BTC locked in zkFOL script)</li><li>S_total = total shares across the pool</li><li>All variables exist as <strong>polynomial commitments verified in Bitcoin Script</strong>, not external state.</li></ul><h4>2. Depositing BTC into the Yield Pool</h4><p>When a user deposits BTC, they create a transaction with a zkFOL-encumbered output:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/1*wjYRbX294OV-PjHhK1yPjA.png" /></figure><p>The deposit predicate:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*n_Y48msHztP283Du9vYkpQ.png" /></figure><p>This creates a proof-verified position:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/1*pPVncDRvT9xpeoUC8SF46g.png" /></figure><p>representing the user’s proportional share in the pool.</p><p><strong>The BTC remains in a native Bitcoin UTXO. </strong>No bridges, no wrapped tokens, no external custody. The script conditions enforce that funds can only move when valid zkFOL proofs are provided.</p><h4>3. Accrual of Yield via Mathematical Predicate</h4><p>Yield is not inflation or arbitrary interest. It is computed and proven as a function of time and pool performance:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/1*v_cnlP4GmX5sW7DYSQAaFw.png" /></figure><p>The polynomial constraint:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/1*YCb4cFpMOzKMsCY1qLH8hA.png" /></figure><p>Verification occurs directly in <strong>Bitcoin Script:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/747/1*OXwylukf2mw9PnLAki4Bbg.png" /></figure><p>Bitcoin nodes verify the proof natively. No external validators required.</p><h4>4. Native Zero-Knowledge Proof Verification</h4><p>Every reward distribution is proven via zkSNARK and verified on-chain:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*vx_LGOo2hUzydrQdKN6XDQ.png" /></figure><p>The proof is included in the Bitcoin transaction and verified by all nodes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/751/1*NLGdOlsXGEC3X_hupVapJw.png" /></figure><p>Each participant can verify that total yield equals distributed rewards:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*iS47ukojSOo_csB4TpPS1Q.png" /></figure><p>without learning any individual’s balance. <strong>Privacy preserved natively on Bitcoin.</strong></p><h4>5. Auto-Compounding Predicate</h4><p>Auto-compounding proves that reinvested yield matches new share allocation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*CLvUQc6w5W8EfZD0eKf1Ww.png" /></figure><p>If P = 0, the compound step is valid. The new UTXO is created with updated share commitment:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*7czMfwbDAjLQmfFILwrmuw.png" /></figure><p>Zero fraud, no hidden inflation. Enforced by Bitcoin consensus.</p><h4>6. Withdrawal and Settlement</h4><p>When a user withdraws, a proof is generated showing:</p><ol><li>The user’s reward has been properly accrued</li><li>The withdrawal respects proportional ownership</li><li>The pool invariant remains satisfied</li></ol><p>Predicate:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/1*o6olZ70PTC5SbONJlL6EMA.png" /></figure><p>The spending transaction includes the proof:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/1*VQuFUKlI3MKeJM_6KS4K2A.png" /></figure><p>Bitcoin nodes verify the proof and release the BTC directly to the user’s address.<strong> Single-layer settlement with no bridge delays.</strong></p><h4>zkFOL Native Verification Model</h4><p>Each yield operation compiles to a polynominal over a finite field:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*D8YOqf16vqFhivAwyZ7oLw.png" /></figure><p>Verification checks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*BAgvSb1IaBy_SEU2d0_VKQ.png" /></figure><p>By the Schwartz-Zippel lemma, any false proof passes with probability ≤ deg(P)/p, which is negligible for 256- bit fields.</p><p><strong>Bitcoin nodes perform this verification natively </strong>using OP_POLYEVAL and OP_FIELDVERIFY.</p><h4>Security and Determinism</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/1*bAQdYzGeWKkC1cMW4cxLsw.png" /></figure><h4>Timing and Performance</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*A2KQccGA26ueSGhdw5tHDg.png" /></figure><p>Yield accrues per-block with <strong>immediate Layer-1 finality.</strong> No batching, no optimistic windows, no bridge delays.</p><h4>Mathematical Invariants Summary</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/1*rUhrxmg_Jnpd944plsWRFg.png" /></figure><h4>Conceptual Model</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*UCALjnqlrDb5UybQ4k4peg.png" /></figure><h4>Summary</h4><p>With native opcode support, zkFOL’s yield system proves that<strong> Bitcoin can produce financial returns entirely within its own protocol.</strong></p><p>No bridges, no wrapped tokens, no external validators. All gains are provably derived from pool performance and algebraically enforced through finite-field proofs verified by every Bitcoin node.</p><p>It’s not yield by inflation or staking. It’s <strong>yield by mathematics:</strong> deterministic, private, and secure within Bitcoin’s native execution environment.</p><p>The soft fork transforms Bitcoin from a simple transfer ledger into a <strong>provable financial logic system</strong> while preserving its fundamental properties: simplicity, determinism, and predictable cost.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7681cc1344d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing BitLogic]]></title>
            <link>https://moduluszk.medium.com/introducing-bitlogic-13cbe8648928?source=rss-de6e46557599------2</link>
            <guid isPermaLink="false">https://medium.com/p/13cbe8648928</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[modulus]]></category>
            <category><![CDATA[zks]]></category>
            <dc:creator><![CDATA[Modulus ZK]]></dc:creator>
            <pubDate>Fri, 21 Nov 2025 16:02:26 GMT</pubDate>
            <atom:updated>2025-11-21T16:02:26.442Z</atom:updated>
            <content:encoded><![CDATA[<h4>The verification mechanism Bitcoin didn’t know it needed</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AuO9-OSTfK9iCbs0YfDQNg.png" /></figure><p>The beauty of Bitcoin is its simplicity. When other smart contract blockchains suffer from the weight of bugs inherent in their VMs, Bitcoin has been chugging on without fail.</p><p>This simplicity has provided security and kept Bitcoin’s blockchain state small compared to its modern counterparts. Yet it has also limited the amount of logic that can run on top of the most decentralized and longest-standing blockchain.</p><p>Current Bitcoin scripts are limited, no loops, no state, which means no DeFi, no multi-sigs.</p><p>Still, the desire to do more with one’s coins has persisted. While the likes of Saylor might be okay stacking their Bitcoin, praising the values of self-custody while keeping their own coins with trusted third parties, this can’t be the way for everyone else.</p><p>DeFi is a key revenue driver for other chains, and the elephant in the room for Bitcoin’s security model is that mining rewards aren’t awarded forever. Once they run out, what’s there to incentivize miners economically? Will they continue mining out of the goodness of their hearts?</p><p>The typical response is that eventually transaction fees will make up for that, but if there’s not much to do on Bitcoin itself, is that realistic?</p><p>That aside, there’s already a thriving ecosystem of solutions to allow users to do more with their Bitcoin, including:</p><ul><li>Sidechains</li><li>Wrapped BTC: centralized bridges holding Bitcoin to allow its usage in DeFi on other chains</li><li>Lightning network: a complex p2p solution on top of Bitcoin to facilitate payments</li><li>Ordinals: allowing the storage of small NFTs/static data in Bitcoin blocks</li><li>L2s: with their own consensus mechanisms, often different trust assumptions</li></ul><p>All of these break part of what makes bitcoin great: the trustlessness and the disintermediation. Instead of doing any of that, we propose BitLogic.</p><h3>BitLogic: Formal Logic on Bitcoin</h3><p>The above approaches all rely on moving significant activity off-chain with little trust guarantees for users. Limitations of the Bitcoin script mean that advanced computation cannot be executed in Bitcoin itself.</p><p>Currently, Bitcoin script can check whether signatures match public keys, but it can’t check whether a trade adheres to certain rules or other necessary DeFi logic.</p><p>To circumvent that, we propose expressing contract rules in formal logic and using cryptographic mechanisms to prove their validity off-chain.</p><p>With BitLogic, you specify your contracts in pure mathematics, then translate them to polynomials using Dr. Jamie Gabbay’s mathematical breakthrough from 2024, which enables direct cryptographic translation of polynomials. You then generate a cryptographic proof of the conditions, which Bitcoin can verify.</p><p>In essence, the computation takes place off-chain, but is cryptographically proven to be correct on-chain.</p><p>This differs from the typical L2 or sidechain approach in that it generates a proof that no one can fake, and anyone can verify.</p><p><strong>What does this add to Bitcoin?</strong></p><p>The main benefit of BitLogic is that it brings programmability to Bitcoin without requiring drastic changes. It doesn’t break the trust assumptions as it relies entirely on verifiable proofs, which are again based on pure mathematics.</p><p>Such programmability then unlocks not only DeFi but also enhanced privacy and the creation of time-locked vaults.</p><p>Last but not least, there’s significant potential for privacy gains when ZK is used to verify computation outcomes rather than compute everything transparently on-chain. The degree of which hinges on the implementation choices of app developers.</p><p>Added programmability as well as privacy gains are achieved without breaking the simplicity of the Bitcoin script, maintaining backward compatibility, and giving users the choice to opt into these more advanced options.</p><h3>How will BitLogic realize this idea?</h3><p><em>Ideas are easy, execution is hard.</em></p><p>Therefore, we split ours into two phases.</p><p><strong>Phase 1: Temporary L2</strong></p><p>We also know that unproven technology won’t stand a chance of affecting OP Code changes. Therefore, we plan to start with an interim Layer-2 on Bitcoin using the zkFOL to achieve cryptographic soundness on all fund movements.</p><p><strong>Phase 2: Submit BIP</strong></p><p>Once the technology has been proven in the wild, we’ll move on to write a Bitcoin Improvement Proposal to propose adding three OP codes that would allow us to enshrine polynomial verification on the base layer without any L2s.</p><p>Polynomial verification is minimal in cost, and unlocks native DeFi, a significant potential revenue driver contributing to Bitcoin’s security model once rewards run out.</p><h3>Ok, this sounds great but…</h3><p><em>“Bitcoiners don’t like L2s and sidechains.” — </em>yes and no. Some Bitcoiners created their own sidechains. That aside, for us, the L2 is just a temporary solution that ideally results in a minimal soft fork to bring verifiability directly to Bitcoin. They did it before with lightning, so why wouldn’t it happen again?</p><p><em>“Bitcoin doesn’t need smart contracts.” — </em>The puritans of Bitcoin exist, and they can rest assured that this does not mean Bitcoin’s base layer will run the computation. It’s just the verification Op Codes.</p><p>“<em>This will bloat the chain.” — </em>a sensible worry as we’ve seen with the rise of Ordinals. But proofs are succinct and more efficient than any script you could run directly onchain for the same logic.</p><h3>Do the math yourself</h3><p>BitLogic doesn’t propose to trust people to do the right thing with your coins.</p><p>We ask you to rely on sound mathematics and cryptography — the foundations that carry Bitcoin. BitLogic merely extends what Bitcoin can do without breaking any of its core philosophies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/0*ltLHsS1BfdLr7pAM.jpg" /></figure><p>For more on the technological basis, <a href="https://github.com/ModulusZK/BitLogic-from-Modulus-zkFOL-Bitcoin/blob/main/BitLogic%20from%20Modulus%20-%20zkFOL%20Bitcoin.pdf">check out the Whitepaper.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13cbe8648928" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[$MOD]]></title>
            <link>https://moduluszk.medium.com/mod-60533793585b?source=rss-de6e46557599------2</link>
            <guid isPermaLink="false">https://medium.com/p/60533793585b</guid>
            <category><![CDATA[modulus]]></category>
            <category><![CDATA[zks]]></category>
            <category><![CDATA[cryptography]]></category>
            <dc:creator><![CDATA[Modulus ZK]]></dc:creator>
            <pubDate>Tue, 11 Nov 2025 13:38:31 GMT</pubDate>
            <atom:updated>2025-11-11T13:38:31.053Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h4lfBBWO8gVJ8gACJyd9xA.png" /></figure><h3>Core Design Principles</h3><ol><li><strong>Dual-Token Economy</strong>: $CULT for gas, $MOD for specialized utilities &amp; team Dapps</li><li><strong>Value Accrual</strong>: Direct correlation between network usage and token demand</li><li><strong>Revenue Balance</strong>: Split between token holder benefits and team sustainability</li><li><strong>Competitive Advantage</strong>: Leverage our superior ZK technology for unique utilities</li></ol><h3>The Goal</h3><p><strong>Apply features and learnings</strong> from CULT as a protocol &amp; other blockchains to <strong>maximize positive outcomes</strong> for the ecosystem whilst <strong>preventing abuse. </strong>We’re applying:</p><ol><li><strong>The reciprocal funding model</strong> from CULT, where projects return value to the ecosystem</li><li><strong>The protocol fee sharing model</strong> from Optimism/Arbitrum, creating ongoing revenue streams</li><li><strong>The rewards and airdrop systems</strong> from Cosmos</li><li><strong>A unique automatic follow-on funding mechanism</strong> that self-regulates based on ecosystem performance. Providing the key support &amp; longevity that builders need.</li><li><strong>The unique, passionate, and maniacal support</strong> of our ecosystem and community. Builders need to know that Modulus is not a chain that will let good ideas die in darkness. <strong>We shine the light. Always.</strong></li></ol><h3>Token Utilities</h3><h3>1. Zero-Knowledge Proof Generation &amp; Verification</h3><p><strong>Primary Utility</strong>: Payment for ZK proof generation using our revolutionary polynomial translation technology</p><ul><li><strong>Proof Request Payments</strong>: Users pay $MOD for proof generation</li></ul><p><strong>Prover Network</strong>:</p><ul><li>Provers stake $MOD to participate in proof generation</li><li>Minimum stake: TBC $MOD (adjustable via governance)</li><li>Delegation allowed for smaller holders</li></ul><p><strong>Pricing Model</strong>:</p><ul><li>Base fee: TBC $MOD per proof (adjustable)</li><li>Dynamic pricing based on complexity and network congestion</li><li>20% discount for stakers holding &gt;TBC $MOD</li></ul><p><strong>Revenue Split</strong>:</p><ul><li>50% to provers</li><li>20% to protocol treasury</li><li>20% to MOD stakers</li><li>10% burn mechanism</li></ul><h3>2. AI Oracle Access</h3><p><strong>Unique Differentiator</strong>: Access to AI-blockchain interface oracles</p><ul><li><strong>Query Fees</strong>: Pay $MOD to access AI oracle services</li></ul><p><strong>Subscription Tiers</strong>:</p><ul><li>Basic: TBC $MOD/month — 100 queries</li><li>Professional: TBC $MOD/month — 2,000 queries</li><li>Enterprise: TBC $MOD/month — unlimited queries</li><li><strong>API Access</strong>: Developers stake TBC $MOD for API keys</li><li><strong>Data Provider Rewards</strong>: AI nodes earn $MOD for accurate data provision</li></ul><p><strong>Revenue Split</strong>:</p><ul><li>50% to oracle operators</li><li>20% to protocol treasury</li><li>20% to MOD stakers</li><li>10% burn mechanism</li></ul><h3>3. Team built dapps</h3><ul><li>MOD will at a minimum apply discounts across fees on any team implemented dapps</li><li>Integration with all team implemented dapps, where appropriate</li><li><strong>We will not compete with builders.</strong> Our dapps come from the weird mind of Mr O’Modulus &amp; he doesn’t tend to build anything that has been seen before</li></ul><h3>4. Governance &amp; Builder Incentives</h3><h3>Governance</h3><ul><li>Propose and vote on Modulus builder applications</li><li>Participate in protocol parameter adjustments</li><li>Direct ecosystem development</li></ul><h3>Builder Incentives</h3><ul><li>Treasury funds promising projects building on Modulus</li><li>Projects return value to token holders and burn supply</li><li>Automatic adjustment of funding amounts based on ecosystem success</li></ul><h3>Staking Structure</h3><p>The MOD governance system employs a three-tier staking structure:</p><h3>A. Guardians (Top 50 MOD stakers)</h3><ul><li>Submit funding proposals</li><li>Coinvestment reduces consensus need from 60% to 50%<strong>*1</strong></li><li>0 voting power, but can advocate for proposals</li><li>Receive proportional returns from protocols funded.</li><li>Guide ecosystem development</li></ul><h3>B. Shield Wall (Top 51–100 MOD stakers)</h3><ul><li>Vote on funding proposals</li><li>0.75 starting voting power, with 0.5–1 range decided on monthly by The Many</li><li>One monthly funding proposal unlocked by 60% activity consensus<strong>*2</strong></li></ul><h3>C. The Many (All other MOD stakers)</h3><ul><li>Vote on funding proposals</li><li>Receive proportional returns from protocols funded.</li><li>Monthly pause/unpause ability for submission rights and rewards for individual Guardians<strong>*3</strong></li><li>Monthly decision on The Shields voting power<strong>*4</strong></li></ul><h3>Initial Funding Cycle</h3><p>The MOD funding cycle creates a sustainable ecosystem funding mechanism:</p><h3>1. Proposal Phase</h3><ul><li>Guardians submit proposals for protocols building on Modulus<strong>*5</strong></li><li>Proposals detail project aims, three roadmap hurdles, token model &amp; return schedule</li><li>Must demonstrate alignment with values</li></ul><h3>2. Voting Phase</h3><ul><li>The Many vote on proposals</li><li>60% approval required for funding, 50% if Guardian is co-investing</li><li>Transparent on-chain voting process</li></ul><h3>3. Funding Phase</h3><ul><li>Approved projects receive 20% MOD tokens upfront, three 20% MOD call options based on roadmap<strong>*6</strong> &amp; a final 20% call option that enacts at 2X MOD price at time of proposals approval to maintain dual alignment &amp; responsibility</li><li>Funds used for development and growth</li><li>Project implements return mechanism in tokenomics</li></ul><h3>4. Return Phase</h3><ul><li>Projects return value through their native tokens</li><li>Returns processed through treasury contract</li><li>50% of returns burned, 50% distributed to stakers</li></ul><h3>Return Process Flow</h3><ol><li>Project completes milestones</li><li>Returns distributed as agreed upon vesting</li><li>Treasury values tokens in USD equivalent</li><li>50% of tokens converted to MOD and burned</li><li>50% of tokens converted to MOD and distributed to stakers</li><li>Treasury checks if ROI = 1+</li><li>If ROI = 1+ Follow-on Funding Option opens</li></ol><h3>Follow-on Funding</h3><p>It is clear to those who have experienced crypto cycles that the market can be cruel. A good protocol can go from hot to not, even if they deliver on their roadmap and even if they have a good sustainable product or business. We should commit to buying low and not just buying high or early.</p><h3>1. Return Tracking</h3><ul><li>Smart contract records total MOD invested by USD amount at the time</li><li>Also tracks total value returned to stakers<strong>*7</strong> (in USD equivalent upon each distribution)</li></ul><h3>2. Follow-on Trigger</h3><ul><li>When stakers receive 50% of total invested amount (since the other 50% is burned)</li><li>Our Follow-on OTC market opens</li></ul><h3>3. Term setting</h3><ul><li>Protocols that have at a minimum, broken even with their values returned to stakers can offer OTC deals to our follow-on market.</li><li>The protocol requesting funding sets a discount rate e.g. 25%.</li><li>As with the original investment given via MOD to the protocol, 20% of the OTC tokens are granted to MOD treasury upfront, three options are granted with price levels offered by the protocol, and a fifth option vests regardless of price at month 4</li></ul><h3>4. Voting Phase</h3><ul><li>The Many vote on proposals</li><li>60% approval required for funding, 50% if Guardian co-invests, however a Guardian is not required for OTC submission as protocol has already demonstrated returns</li><li>Transparent on-chain voting process</li></ul><h3>Value Accrual Mechanisms</h3><p>MOD token value is supported through multiple mechanisms:</p><h3>1. Token Burns</h3><ul><li>50% of all returns from funded projects buyback &amp; burn</li><li>Decreases circulating supply over time</li><li>Creates deflationary pressure</li></ul><h3>2. Protocol Fee Sharing</h3><ul><li>TBC% of Modulus sequencer fees converted to MOD</li><li>Distributed to all MOD stakers proportionally</li><li>Creates passive income stream for stakers</li></ul><h3>3. Ecosystem Airdrops</h3><ul><li>Projects built on Modulus commit to airdrops for MOD stakers</li><li>Creates additional incentive for staking</li><li>Aligns ecosystem project success with MOD holders</li></ul><p><strong>4. Zero-Knowledge Proof Generation &amp; Verification</strong></p><ul><li>MOD stakers can delegate to provers</li><li>Earn portion of MOD fees from provers</li><li>Additional utility beyond governance</li></ul><p><strong>5. AI Oracle Access</strong></p><ul><li>Pay $ETH or stables to access AI oracle services</li><li>Discounted Subscription Tiers ranked by $MOD ownership</li><li>Portion of $ETH or stables used to buyback $MOD</li></ul><p><strong>6. Team Built dapps*8</strong></p><ul><li>Discounted fees on any &amp; all team implemented dapps</li><li>Full integration with all team implemented dapps from a utility and buyback level where appropriate</li></ul><h4><strong>Comparison to Other Chains &amp; Models</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*93XyTS4aO5rQb0pjEjOUkQ.png" /></figure><h4>Distribution</h4><p>Max Supply: <strong>666 million MOD</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PtHk7ez83XtENjqXm4-p3Q.png" /></figure><h3>Conclusion</h3><p>We have designed the $MOD token model to create a self-reinforcing ecosystem where builders feel comfortable that we have their back so that they feel safe having ours. The more builders we foster, the more customers we can reach, the more use of our chain, the more use of our services, the more demand for both CULT &amp; MOD.</p><p>The larger our user and developer footprint grows, the faster our network effect compounds. By balancing user incentives with sustainable revenue generation, Modulus will build a lasting and established presence as an independent novel blockchain, whilst rewarding our die hard early supporters and maintaining operational and mathematical excellence.</p><p><strong><em>Please read the </em></strong><a href="https://moduluszk.medium.com/cult-mod-3fc89c7a02c9"><strong><em>following Medium post for information on how $CULT &amp; $MOD</em></strong></a><strong><em> complement each other</em></strong></p><h3>Appendix: References/Expansions for *numbers</h3><p><strong>*1) Coinvestment reduces consensus need from 60% to 50%</strong></p><p>To build trust and show belief in the project, the Guardian can choose to coinvest, where they put up a certain amount of their MOD, ETH or Stables alongside the proposal. This will drop the voting consensus needed to pass by 10%. From 60%+ Yes to 50%+ Yes. Whether the proposal passes OR fails. The Guardians investment will still go to the project even if MOD does not invest. This will help to maintain faith in the Guardian system.</p><p><strong>*2) One monthly funding proposal unlocked by 60% activity consensus</strong></p><p>At the commencement of every month there will be a 48 hour opt in for The Shields. If the shields demonstrate they are active by 30+ out of the 50 opt ins, then they can also propose once a month.</p><p><strong>*3) Monthly pause/unpause ability for submission rights &amp; rewards for individual Guardians</strong></p><p>The Many will have the power to hold Guardians accountable for their actions if they believe there has been deviance or malintent with their proposal power. To action a suspension vote against a Guardian from the Many, there must be voting power equivalent to the 50th top stakers token value that has “voted to suspend” this will be actionable as a button within the voting dapp for the first 48 hours of every month.</p><p><strong>*4) Monthly decision on The Shields voting power</strong></p><p>To hinder and disincentivise the spreading of voting power amongst multiple wallets just under the Guardian Threshold, for the first 48 hours of every month The Many will be able to set a governance handicap for The Shields. The maximum handicap being 50% and the minimum being no handicap.</p><p><strong>*5) Guardians submit proposals for protocols building on Modulus</strong></p><p>Unlike CULT &amp; RVLT with fixed or fixed variable funding amounts, MOD will have a $500,000 maximum cap. This is not by any means a target. There has to be extraordinary evidence as to why and how this would be spent, and we have implemented the call option model to make sure the full amount of funding is never given up front.</p><p><strong>*6) Approved projects receive 20% MOD tokens upfront, three 20% MOD call options based on roadmap</strong></p><p>It is important to foster long term relationships between a chain and its builders. 20% is paid upfront. Another three payments of 20% are unlocked after the protocol seeking funding must ties three realistic and achievable milestones to them. Once achieved, the protocol should inform the DAO when it has hit its milestone and submit the evidence for review. Once this has been done, the protocol can implement their call option to be voted upon by the DAO to release. So to reconfirm; 20% upfront not tied to roadmap or performance. 20% as a call option that enacts at 2X MOD price at the time of the proposals approval, to maintain dual alignment &amp; responsibility. Three roadmap and performance based 20% unlocks. The DAO can vote on each roadmap unlock and can also vote to remove the 20% 2X performance option, if trust is lost in the project or its team.</p><p><strong>*7) Also tracks total value returned to stakers</strong></p><p>It is typical for a token upon launching to make many multiples of return on investment, only for the price to fall just as quickly in the months that follow. Many people wanted to buy the token at its launch price, but when or if it drops below that price suddenly the queue that once formed has disappeared. This is where a good chain helps to support its builders. Not when the going is easy, but when the going gets tough. This is why any protocol that has returned 50% to stakers and 50% burnt in USD equivalent is automatically allowed to submit for OTC funding from MOD without needing a Guardian to sponsor it. The vote goes straight to The Many.</p><p><strong>*8) Team Built dapps</strong></p><p><strong>We will not compete with builders.</strong> Our dapps come from the weird mind of Mr O’Modulus &amp; will be novel and concepts and designs not seen before</p><p><strong>*9) Silent Heroes Airdrop Campaign</strong></p><p><a href="https://docs.google.com/document/d/1C2V5Wu2IkCyxKsrFy9OUQw5Gzw46bJYqjEZAS8wMwNo/edit?usp=sharing">https://docs.google.com/document/d/1C2V5Wu2IkCyxKsrFy9OUQw5Gzw46bJYqjEZAS8wMwNo/edit?usp=sharing</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60533793585b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[$CULT & $MOD]]></title>
            <link>https://moduluszk.medium.com/cult-mod-3fc89c7a02c9?source=rss-de6e46557599------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fc89c7a02c9</guid>
            <category><![CDATA[modulus]]></category>
            <category><![CDATA[cult]]></category>
            <category><![CDATA[zks]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Modulus ZK]]></dc:creator>
            <pubDate>Tue, 11 Nov 2025 13:36:10 GMT</pubDate>
            <atom:updated>2025-11-11T13:36:10.651Z</atom:updated>
            <content:encoded><![CDATA[<h3>Core Principles and Values</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i5tY6PmK6jCGAAuXLew6Lw.png" /></figure><p>$CULT is $CULT. Simple. Beautiful. Radically decentralized.</p><p>It works because we all work on it together. It is not me, it is not you, it is all of us, and more than any of us. Mutual owners and mutual beneficiaries. I have had numerous offers to purchase CULT as a brand and IP, from private investors to sell CULT tokens or equity to privately. But as soon as that decision would be made then CULT would cease to exist. What has allowed CULT to succeed is its full community ownership and management.</p><p>For me to raise funds against it as a business, or to privately sell tokens to investors would be the ultimate centralization of power. Taking the only 100% decentralized and autonomous protocol and public good on Ethereum, and turning it into a for-profit business would destroy the values and mission we started with. So I will not allow that to happen.</p><p>I must also be realistic, as much as I would like to take Vitaliks advice and “go back to 2021”. I cannot. In 2021 money was flowing, alts were running and what was once impossible became possible for a brief moment. It is no longer the same market.</p><p>Now, I understand if this is not what you signed up for, that is why I will not force anybody to take part. I will not ask you for money, in fact, I will give you some. Do with it as you wish.</p><p>When ZK started being hyped, others raised millions with scribbles on a napkin, rarely delivering on what they sought out to build, yet creating an increasingly hostile environment for those who are serious about actually innovating. We’re seeing that the current crop of ZK infrastructure builders all build iterations of the same thing. The second you deviate, your chances diminish. And yet, when’s the last time a big innovation was born out of conformity? It’s at the fringes, and that’s where we thrive.</p><p><strong>Nothing Changes For $CULT Within Modulus</strong></p><p>Most importantly; <strong>NOTHING CHANGES FOR $CULT WITHIN MODULUS. </strong>It is still the gas token, it is still burnt with gas expenditure. Our team has grown and evolved and as have the services we will be providing on ModulusZK. It is these services the $MOD token will have utility for. Modulus is the institutional facing and revenue producing business born from Cult DAO. We build the world and the blockchain in our image. We don’t build “on”. We compete to become the largest blockchain in the world. With that goal achieved, our gas burns for CULT and MOD burns from the services will dwindle both supplies slowly, down to fractions of numbers.</p><p>My goal will remain the same as it has always been. The pursuit of true freedom, in all its various forms, for whoever puts their faith in me to achieve it for them. I have assessed all scenarios, measured all risks and rewards, and this is the way I believe I can achieve that goal for us all.</p><blockquote>“I would say to the House… I have nothing to offer but blood, toil, tears and sweat… You ask, what is our policy?</blockquote><blockquote>I will say: It is to wage war, by sea, land and air, with all our might and with all the strength that God can give us; to wage war against a monstrous tyranny never surpassed in the dark and lamentable catalogue of human crime. That is our policy.</blockquote><blockquote>You ask, what is our aim? I can answer in one word.</blockquote><blockquote>It is victory, victory at all costs, victory in spite of all terror, victory, however long and hard the road may be, for without victory there is no survival.”</blockquote><blockquote>– Winston Churchill</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fc89c7a02c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unpacking zkVMs]]></title>
            <link>https://moduluszk.medium.com/unpacking-zkvms-113de3006527?source=rss-de6e46557599------2</link>
            <guid isPermaLink="false">https://medium.com/p/113de3006527</guid>
            <category><![CDATA[kvm-z]]></category>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[arithmetic-circuits]]></category>
            <dc:creator><![CDATA[Modulus ZK]]></dc:creator>
            <pubDate>Tue, 04 Nov 2025 09:56:25 GMT</pubDate>
            <atom:updated>2025-11-04T09:56:25.816Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y5Uk1GD7P4k3N8FQsw3j4w.png" /></figure><p>You are probably thinking, why should I care about zkVMs?</p><p>For one, across the board, crypto people who normally can’t agree on much at all, have come to the conclusion that Zero-Knowledge cryptography is our best bet for scaling blockchains.</p><p>Zero-Knowledge cryptography, as the name implies, verifies that a prover has a piece of knowledge or has executed a task without revealing the actual details, and then generates a (Zero-Knowledge) proof that can be used to verify that all has been done as instructed.</p><p>As an idea, they’ve been around for a while, first implemented in privacy coins such as Zcash. More recently, as we realized that they’re useful for scaling as well, the focus has shifted toward building zkVMs that’d allow developers to bring about the zk-enabled future.</p><p>With all the excitement around zkVMs (and EVMs as a subsection thereof), it’s easy to start focusing on doing the same thing as the others, with slight modifications on where to optimize to speed up the infrastructure.</p><p>We beg to differ. But to explain why, we must start with what zkVMs are. Before we do that, a few words of caution to safeguard yourself against hype, and unnecessary implementation of ZK where it is not warranted.</p><h3>When don’t I need ZKPs…</h3><p>Quite simple. There is no reason to add zero-knowledge proofs to an application in:</p><ul><li>High trust environments</li><li>When there’s only one verifier: outsourcing your compute to an untrusted server and then using ZKP to verify it was done correctly is nonsensical when you end up paying twice as much. The benefits gained must offset the additional computational costs.</li><li>Realms with sufficient other alternatives, with strong enough other incentives to avoid wrongdoing.</li></ul><p>As so often, once a word becomes hyped, it’ll be used by marketers left, right ,and center to increase the perceived attractiveness of their product. It’s gone so far that even in academic papers we find references to this reality.</p><blockquote>“Numerous applications highlight ZKPs as a groundbreaking technology. However, we observe that recent applications misuse the term zero-knowledge, such that some applications do not demand zero knowledge at all, but rather rely on other properties such as non-interactivity and succinctness to facilitate the use case in question.”</blockquote><p>(<a href="https://eprint.iacr.org/2024/050.pdf">https://eprint.iacr.org/2024/050.pdf</a>)</p><p>Zero-Knowledge cryptography is about revealing nothing, and still proving something. That’s why using it just to compress is, as some might say, not very zero-knowledge at all.</p><p>Terminological feuds aside, the above leaves plenty of use cases where zero-knowledge cryptography does make a whole lot of sense.</p><h3>When do I sensibly use Zero-Knowledge?</h3><p>Here are a handful of scenarios where it makes sense to rely on zero-knowledge cryptography:</p><ul><li>Outsourcing computation to others you don’t trust</li><li>Verifiable credentials, and KYC (you go through verification once, then only present the proof going forward)</li><li>Cross-chain bridging</li><li>For networking: to prove, for example, data provenance, a potentially useful thing for AI companies to start doing to prove the sets their models were trained on at the risk of exposing their copyright violations.</li></ul><p>In the crypto context, the first scenario is particularly relevant to how decentralized systems work. There are thousands of nodes contributing to them, and no guarantees that each single one has been executing programs correctly.</p><p>At the same time, as Dr. Gabbay pointed out in a podcast, we cannot expect all nodes to be supercomputers, allowing them to re-run the entire computation to verify. Instead, what’s needed is a way to input information from such powerful servers and prove its correctness. As such, ZK helps maintain the crypto maxim of <em>“trust, but verify”,</em> even for those with less powerful nodes.</p><p>Sounds great in theory, but still begs the question:</p><h3>How did we end up with zkVMs?</h3><p>zkVMs are not, despite what you’d assume looking at Crypto Twitter, the only way to code zero-knowledge proofs. Yet, they’ve become the dominant approach because the other one was very optimized, but a skill the vast majority of crypto devs lacked. Before crypto x zk took off, the way cryptographers proved zero-knowledge was the circuit approach.</p><p>And the language of cryptography is math. That’s why all logic is turned into mathematical expressions, in a process called arithmetization. It makes further sense when we think about how computers work deep down: it’s all just 0s and 1s.</p><p>The way to prove anything then becomes a question of establishing whether it’s a valid bit, meaning whether it translates to 0 or 1, the electric flows inside the machine. That’s the math part.</p><p>To do so, cryptographers enforce so-called constraints that represent a program. The most basic one is to verify that a value is actually 0 or 1.</p><p>0 = x(x-1)</p><p>The only values that resolve this equation are 0 and 1. Naturally, the real proving constraints are much more complex. Assuming you’d want to prove that three numbers add up to 10 without revealing what they are.</p><p>You’d write:</p><p>a+b+c = 10</p><p>That’s not enough, though, as there remains the need to prove that every variable is valid (a bit or field element), so each would come with its own set of constraints. You can see how this quickly spirals into thousands of constraints working together.</p><h3>Arithmetic Circuits</h3><p>All these constraints aren’t just thrown into one big field; instead, they are combined in what’s called an arithmetic circuit. It’s similar to a flow chart where at each stop (they call them gates) a mathematical operation is performed, and each line carries a value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*jFOwRTjjaOqtyJpg.png" /><figcaption>From Hadas Zeilberger: <a href="https://medium.com/web3studio/simple-explanations-of-arithmetic-circuits-and-zero-knowledge-proofs-806e59a79785">Simple Explanations of Arithmetic Circuits</a></figcaption></figure><p>The constraints enforce that the in- and outputs at each gate follow the rules, and when correct values are entered, all constraints are fulfilled, and the computation is provably correct.</p><p>With thousands of constraints, this would appear to be quite an arduous task. That’s why cryptographers combine them into polynomials, allowing them to represent hundreds of constraints with one single polynomial equation.</p><p><em>We’ll dwell on the importance of polynomials in the next post; just know that they are a key element of cryptography, and the reason we can run verifications relatively efficiently.</em></p><p>Reading about these equations can make the average person with nightmares from high school math feel like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*K5Pn-bMfZZGi8WRm.jpg" /></figure><p>As such, you can imagine how many crypto developers don’t feel up to the task of coding their own arithmetic circuits. They still don’t want to miss the perks of ZK, so they came up with zkVMs.</p><h3>How zkVMs work</h3><p>zkVMs pitch is that they allow anyone to code zk-proven programs without needing to know zero-knowledge cryptography themselves. Instead, they can use high-level programming languages, and the VM handles the rest.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/0*gWj6cX9NH1LT0_NF" /><figcaption>Diagram of zkVM (<a href="https://www.alchemy.com/overviews/zkevm">src</a>)/ <em>Witness = the values that resolve the equations correctly</em></figcaption></figure><p>Since the first practical implementation of a zkVM in 2013, the space has come a long way, with the latest iteration integrating the RISC-V architecture and parallelizing proving efforts to speed up computation.</p><p>Compared to the approach of directly writing circuits, zkVMs offer benefits such as a shallow learning curve (if any, when common programming languages are supported) and reduced need to create dedicated constraints for each program.</p><p>Naturally, moving further away from the machine comes with downsides, too, as VMs require translating high-level programming languages into all the things we just discussed.</p><ol><li>The compiler turns the source code into VM bytecode.</li><li>This is then executed, resulting in an execution trace.</li><li>In the next step, it’s handed off to the prover, which represents it as a set of polynomials, once again translating, this time from computation into algebra.</li><li>The provider then runs a polynomial interactive proof protocol on it (usually a STARK or a SNARK)</li><li>The proof is thus generated, and can now be verified by the verifier using the verification protocol.</li></ol><p>In the end, the VM outputs a final-state commitment and the proof.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_kjuPGEDqmNENbQKDBPJ_w.jpeg" /></figure><p>While this approach has been great for furthering zk adoption and enabling more builders to leverage zk, it’s also highlighted the potential challenges yet to be overcome. One of the largest looming threats is security. zkVMs are prone to bugs affecting their security and soundness.</p><p>Therefore, it’s not uncommon for zkVM builders to add additional layers using Multi-Party-Computation or TEEs to the mix. This, then again, heightens the complexity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/0*ScDiYwhCBPZof4_A.jpg" /><figcaption>Henderson Sensei (<a href="https://de.pinterest.com/pin/716283515773093435/">src</a>)</figcaption></figure><blockquote>“Not elegant”</blockquote><blockquote>— Henderson sensei (Spy x Family)</blockquote><p>Not that this would ever deter crypto builders from using a technology. For those especially inclined toward building on Ethereum, a subsection of zkVM has been developed, the zkEVMs. They’re just another flavor of zkVMs designed to cater to Ethereum.</p><p>They’re everywhere these days and are becoming increasingly indistinguishable. Yet one thing they all share is the complexity and computational overhead introduced by their approaches to make ZK easier to use for anyone.</p><p>Ultimately, Modulus is not here to completely replace zkVMs.</p><p>But we’re here to introduce a new way to more elegantly, more efficiently go from business logic to zk proving onchain.</p><p>We believe this will unlock a new range of use cases, while offering institutions with much higher security demands than the average crypto degen dev, the necessary tools to enter this industry.</p><blockquote>“Tell me, Simon. Do you know why people have eyes in front? It’s ’cause you have to move forward to see the landscape in the distance.“</blockquote><blockquote>— Kamina</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=113de3006527" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Modulus’ story: The courage to build differently]]></title>
            <link>https://moduluszk.medium.com/modulus-story-the-courage-to-build-differently-acb65b8df656?source=rss-de6e46557599------2</link>
            <guid isPermaLink="false">https://medium.com/p/acb65b8df656</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[modulus]]></category>
            <category><![CDATA[rethinking]]></category>
            <dc:creator><![CDATA[Modulus ZK]]></dc:creator>
            <pubDate>Mon, 20 Oct 2025 12:54:26 GMT</pubDate>
            <atom:updated>2025-10-20T13:07:27.661Z</atom:updated>
            <content:encoded><![CDATA[<h3>How the CULT community fosters a radical rethinking of crypto architecture.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TQRBWZ_x2tGDi2LsNFtmOQ.jpeg" /></figure><blockquote>Let thy step be slow and steady, that thou stumble not.</blockquote><blockquote><em>Tokugawa Ieyasu</em></blockquote><p>A common mistake in crypto is treating speed as an ultimate virtue. Everyone seeks to build as fast as possible, scale as fast as possible, and build their community with the same 0-to-1-million desire one would apply to growing nodes in a network.</p><p>The names for the programs we believed would speedrun the community changed from quest-to-points programs to now asking aspiring airdrop recipients to place high on the AI yapping boards.</p><p>In such a climate, the second someone does it differently, they stand out like a sore thumb. CULT has a long-standing history of such deviant — or shall we say commonsensical — behavior, launching with maximum dedication to community governance, taking bets on guardians, and distributing $7.5 million in funds to public goods initiatives on Ethereum, amidst largely being ignored by bigger Ethereum accounts.</p><p>CULT remained committed to the values that started it, a project by the many, for the many, with a belief that the goodness of ideas can’t be valued based on one’s ability to raise funds for them quickly.</p><p>If we’ve learned anything from events such as SoftBank pouring billions into WeWork or SV investors believing a Wi-Fi-connected <a href="https://en.wikipedia.org/wiki/Juicero">juice machine warranted $120 million in funding</a>, it’s that investors can err horribly in the marketplace of ideas.</p><p>Where, though, does this leave a community committed to making the things happen that actually should exist?</p><h3>How Modulus came about initially</h3><p>After the launch of Cult, its founders quickly realized they’d created something beautiful that’d grow only stronger over time, leaving us 2 years later with a highly committed, <em>real</em> organic community.</p><p>The foundation was already in place early on, so the founders figured the best way to take this forward would be to create a dedicated chain that’d embody CULT’s values. Modulus was born.</p><blockquote>“We wanted to create something meaningful beyond the community.”</blockquote><blockquote>— Artorias.</blockquote><p>In crypto people’s terminology, the idea was to enshrine CULT’s ideals in an immutable, permissionless L2. The most appropriate, advanced option at the time was Polygon’s zkEVM. Instead of just creating yet another fork, the plan was to fork and then later enhance the existing layer with advanced privacy features.</p><p>However, things wouldn’t play out like that. After the first iteration of the testnet was live, it crystallized that sticking to the original idea would come at significant cost, especially in form of technical debt.</p><p>Fast forward to today, and Polygon Labs has sunset zkEVM altogether, highlighting that departure from that route was, in the end, a forward-looking decision. Still, with that avenue shut, the project entered a state of hibernation.</p><h3>The paper that’d breathe new life into Modulus</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*lZZOYPbKXZECHU24.gif" /></figure><p>Such a blow would spell death for others’ aspirations. Still, even with the small team and limited funding, Mr O’Modulus and Artorias continued speaking to people about Modulus, their idea. Eventually, they concluded that the only way to realize it might be to raise the necessary funding.</p><p>One of the many people they talked to this way would introduce them to Dr. Jamie Gabby, remarking that he’d written <a href="https://eprint.iacr.org/2024/954.pdf">a paper </a>that would completely change how people think about architecting a chain.</p><p>Suffice it to say, his assessment was spot on.</p><p>Artorias instantly knew, after reading the paper, that this was worth pursuing, offering a unique feature and raison d’être for Modulus.</p><blockquote>“I, of course, needed AI to help me make sense of the paper, but as soon as I read it, I knew that we were onto something big. This impression further hardened once we spoke to Jamie and he laid out in Layman’s terms what changes his approach would bring.”</blockquote><blockquote>— Artorias</blockquote><h3>The next iteration of Modulus…loading</h3><p>If you’re not fluent in Academic Math, here’s the short version of what Dr Gabby lays out in his paper: it’s quite simple. He suggests using math to cut out unnecessary steps in how blockchains currently operate.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FSUshjgObk2YoiSQl6H%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2FSUshjgObk2YoiSQl6H&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExbWRzY3NhczdqYjIwYzlpdmdpaWJ1Y2UxcnpjdDN6cmVhOW92dWlneiZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FSUshjgObk2YoiSQl6H%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/6cbbe8520d9da45f30a4dcc93209993e/href">https://medium.com/media/6cbbe8520d9da45f30a4dcc93209993e/href</a></iframe><p>People often forget: it’s all math. They focus on the hardware or figuring out fixes to the technical debt accumulated, but rarely venture out to ask the academics venturing ahead at the frontier of mathematics what they’re up to.</p><p>Bypassing the VM entirely and translating Polynomials directly to Polynomials will allow Modulus’ ZK to generate proofs 10x faster while reducing their size by 90%. This matters not only because Zero-Knowledge-Proofs are hot stuff, but it’s also important because they offer the most promising way to scale blockchains while providing a path to privacy.</p><p>However, so far, they’ve been hindered by inefficiency.</p><p><em>Polynomials are just the mathematical expressions of logic used to interact.</em></p><p>Now you’re probably wondering, why is no one else doing it? Look into the leading zkVMs, and you might quickly conclude the same as (Y)our Buddy Conner.</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//x.com/YourBuddyConner/status/1957144455745859706&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/2d7f6b2adef07189dfbf0ee0bb0b238a/href">https://medium.com/media/2d7f6b2adef07189dfbf0ee0bb0b238a/href</a></iframe><h3>Taking the road less travelled</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/541/1*e1ZY96tY0_spIWmRKO-ATw.png" /><figcaption>Robert Frost: The Road not taken</figcaption></figure><p>We can all agree that Ethereum has built a vast, resilient network with network effects that encourage new builders to adopt similar choices to achieve interoperability. After all, why build a new VM from scratch (in recent years, Fuel is one of the few teams on Ethereum who’ve dared to and with modest success), if you can just lean into what’s already there?</p><p>Conforming with the majority is a very humanly understandable choice, but not for innovation. When Vitalik said that in the future we should all move to RISC-V, he might have shaken a few out of their EVM-induced slumber, but so far in the realm of VMs, the most we get is new native VMs on separate blockchains with all the baggage that comes with that.</p><p>CULT has always stood a little outside the typical crypto ethereum bubble, giving the team a unique outsider perspective on the discussions around zkVMs and other L2s. To the point of seeing that, hey, if the VMs are the bottleneck… why not get rid of them?</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//x.com/MrOmodulus/status/1977637441738858504&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/e17b087a5841b4cbcdc892727ac4206e/href">https://medium.com/media/e17b087a5841b4cbcdc892727ac4206e/href</a></iframe><p>Easier said than done, yet what gives us at Modulus the confidence that we’re the team to bring Dr Gabbay’s ideas to life is the community that’s stuck with us through thick and thin.</p><blockquote>“There’s thousands of tokens that launched in 2022, but the vast majority of them faded, have gone to dust, and are forgotten. For any blockchain project, the community is foundational to what you do.”</blockquote><blockquote><em>Artorias</em></blockquote><p>We know they’re in it for the long run, to see radical ideas through, and to build the tech that ought to exist.</p><p>Thanks for reading and being part of the community!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acb65b8df656" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcoming Naomiii to the ModulusZK team]]></title>
            <link>https://moduluszk.medium.com/welcoming-naomiii-to-the-moduluszk-team-a2ae254aeb0c?source=rss-de6e46557599------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2ae254aeb0c</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Modulus ZK]]></dc:creator>
            <pubDate>Tue, 07 Oct 2025 14:02:07 GMT</pubDate>
            <atom:updated>2025-10-07T14:02:07.700Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zh7axF9VoQKzsVwLARoSFQ.png" /></figure><p><em>When you want to go fast, go alone. When you want to go far, go with others. </em>Or so the saying goes. That’s why we continue to grow our team, ensuring that ModulusZK will indeed go far.</p><p>Today, we’re happy to announce that Naomi Oba (the user known as Naomiii.eth onchain) is joining us as a <strong>littérateur</strong>.</p><p>Naomi is what they call a crypto-native, having spent most of her career since 2017 writing and marketing crypto projects across verticals.</p><p><strong>Highlights from her time in crypto</strong></p><p>Her career started in Tokyo as an Overseas Sales associate, where she helped localize international projects to the local market and facilitated exchange listings. Realizing that sales wasn’t her calling, she started writing, which paved the way to becoming a Marketing Manager at Bitcoin.com, where she single-handedly ran the marketing for their centralized exchange, managing all their social channels, email marketing, and later, a rebranding.</p><p>Since then, she has worked on numerous additional projects, helping them expand their community and conveying the necessity of often highly technical products in a way that anyone can relate to. Among them are alt-L1s such as Minima, Astar Network and Ternoa.</p><p>She’s also no stranger to building a standing in an ecosystem from zero, having turned herself into a NEAR ecosystem KOL through contributing quality threads and writing, which later got her on stage at their conferences and a writer’s gig with NEARWeek.</p><p>Most recently, she has worked at SQD as a marketing manager, overseeing social media, running marketing campaigns, and organizing co-marketing initiatives. When given creative leeway, she once created an NFT series minted by hundreds of thousands of wallets.</p><p>On the side, she continued to write, both personally and professionally. As of now, she’s won three crypto writing contests across different ecosystems (Solana, Lens, Nouns), but we’re sure those won’t be the last.</p><p>This year, she has also returned to the stages of crypto events, speaking at Eth Dublin about the alienation we foster, and at Dappcon’s privacy stage about how crypto culture has lost its way. In an attempt to not just critique but create, she joined other crypto writers in developing a manifesto outlining what culture <a href="https://www.sapphirepunk.com/">post-cypherpunk</a> could look like.</p><p>Speaking of culture…</p><p><strong>Cultural alignment</strong></p><p>Anyone who has been in crypto for a long time will have a hard time shaking the sense that we’ve taken a wrong turn. What used to be an aspirational industry with grand dreams of making the world a better place has broadly adopted Big Tech’s worldview and is cheering on this space, which is about to be subsumed into TradFi.</p><p>We believe the tech is not so much about reinforcing current power structures, but about actually empowering users, and re-thinking finance.</p><p>Naomi has spoken up numerous times against this tendency, and as someone from a humanities background, she consistently emphasizes the need not to forget the human element. This also enables her to think outside the paradigms that often guide crypto. As a hobby philosopher and literature fanatic, she’s bringing a valuable perspective to the team that’ll help us build something to last.</p><p><strong>Looking forward</strong></p><p>As our littérateur (this is a synonym for writer), Naomi will focus on:</p><ul><li><strong>Narrative Creation: </strong>how we present ourselves, the vision, and how we tell the story across all the channels.</li><li><strong>Community: </strong>running socials, growing the community through sensible co-marketing initiatives, and highlighting practical use cases.</li><li><strong>Creativity: </strong>exploring creative ways to establish the brand, and make a dent in crypto</li></ul><p><strong>Welcome to ModulusZK</strong></p><p>We can’t wait for Naomi to start working with us. Her critical thinking skills, her experience, and connections will all be invaluable as we enter our next phase of growth.</p><p>For a first impression, you can check out highlights from her writer portfolio <a href="https://docs.fileverse.io/0x22c3e3290bEecAA3aD5B1879A672Fc9139368AD2/53#key=TuQq6pVWOpGcM3aTnFwajS1DXa0CwS-7RsPkMREHQTLzZOmpcidDX0beQU_v_CZA">here.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2ae254aeb0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcoming Adam Funnell as Chief Business Development Officer at ModulusZK]]></title>
            <link>https://moduluszk.medium.com/welcoming-adam-funnell-as-chief-business-development-officer-at-moduluszk-3f5d562c44b6?source=rss-de6e46557599------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f5d562c44b6</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[zero-knowledge-proofs]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Modulus ZK]]></dc:creator>
            <pubDate>Mon, 08 Sep 2025 16:27:46 GMT</pubDate>
            <atom:updated>2025-09-08T16:27:46.559Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*AJpCO9iygGN_dqBMQL_87Q.jpeg" /></figure><p>Today, we’re thrilled to announce that Adam Funnell has joined ModulusZK as our Chief Business Development Officer.</p><p>Adam brings over a decade of blockchain experience to our team, having entered the space in 2014 when the industry was still finding its feet. His journey through the evolution of Web3 has given him a unique perspective on both where we’ve been and where we’re heading.</p><h3>Deep Industry Experience</h3><p>Most recently, Adam served as Head of Business Development at the Secret Network Foundation, where he restructured their business development operations to focus on strategic partnerships that drive real adoption. His work there centered on promoting Secret Network’s Confidential Computing Layer, an experience that aligns closely with ModulusZK’s mission to build privacy-preserving infrastructure.</p><p>Prior to Secret Network, Adam’s career spans impressive achievements across the blockchain ecosystem. At Accubits Technologies, he secured over $2M in new business within 15 months and built strategic partnerships with major layer-one foundations including Cardano, Lisk, Hedera, Stellar, Near, and Tezos. His ability to identify opportunities and execute complex deals has been consistent throughout his career.</p><p>Adam’s advisory work demonstrates his strategic thinking beyond direct employment. As an advisor to Flight3 (previously Zebu Digital), he helped guide their NFT strategy from inception. He witnessed the company grow from zero to their acquisition to the Flight Story Group.</p><h3>Bridging Web3 Innovation with Traditional Business</h3><p>What distinguishes Adam is his ability to operate effectively across both Web3-native environments and traditional business settings. His experience at Zumo developing sales strategies for enterprise products, combined with his deep crypto roots, gives him the rare ability to translate between these often disparate worlds.</p><p>This dual fluency is crucial for ModulusZK. As we build zkEVM infrastructure that needs to serve both crypto-native protocols and enterprises exploring blockchain adoption, we need leadership that understands both audiences intimately. Adam has proven this capability repeatedly, from working with DeFi protocols to securing funding from traditional venture capitalists.</p><h3>The Right Leader at the Right Time</h3><p>Adam joins ModulusZK at a critical juncture in our growth. With our technology maturing and market interest in zkEVM solutions accelerating, we need someone who can translate our technical capabilities into meaningful partnerships and ecosystem growth.</p><p>His track record speaks for itself: building and managing portfolios worth millions, scaling teams from 5 to 30+ members, and consistently identifying partnerships that create genuine value rather than just press releases. These aren’t just numbers; they represent real relationships and sustainable growth strategies that align with ModulusZK’s long-term vision.</p><h3>Looking Forward</h3><p>As our Chief Business Development Officer, Adam will focus on several key areas:</p><p><strong>Partnership Development</strong>: Building relationships with protocols, enterprises, and institutions that can benefit from ModulusZK’s infrastructure.</p><p><strong>TVL Growth</strong>: Implementing strategies to increase Total Value Locked through targeted ecosystem development and partner onboarding.</p><p><strong>Team Building</strong>: Growing and leading our business development team as we scale operations globally.</p><p><strong>Market Expansion</strong>: Identifying and pursuing opportunities in new markets and verticals where zkEVM technology can create significant value.</p><h3>A Shared Vision</h3><p>When we spoke with Adam about joining ModulusZK, what stood out wasn’t just his impressive track record. It was his genuine enthusiasm for what we’re building. He understands that infrastructure isn’t exciting because of the technology itself, but because of what it enables. His vision aligns perfectly with ours: making blockchain technology so seamless and effective that users benefit from it without needing to understand the underlying complexity.</p><p>Adam’s long-standing commitment to the blockchain space, having weathered multiple market cycles since 2014, demonstrates the kind of dedication and perspective we value at ModulusZK. He’s not here for short-term gains but to build something lasting.</p><h3>Welcome to ModulusZK</h3><p>We couldn’t be more excited to have Adam join our team. His expertise, network, and strategic thinking will be invaluable as we enter our next phase of growth. To our community, partners, and future collaborators: Adam is eager to connect and explore how ModulusZK can support your goals.</p><p>For partnership inquiries or to connect with Adam, please reach out through our official ModulusZK channels. He’s already hard at work identifying opportunities to expand our ecosystem and would love to hear from you.</p><p>Welcome aboard, Adam. We’re looking forward to building the future of blockchain infrastructure together.</p><ul><li><a href="https://moduluszk.io/">Modulus - Privacy-first zkEVM blockchain</a></li><li><a href="https://x.com/moduluszk">JavaScript is not available.</a></li><li><a href="https://x.com/MzkAdam121">JavaScript is not available.</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f5d562c44b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Vision for Modulus Layer X]]></title>
            <link>https://moduluszk.medium.com/the-vision-for-modulus-layer-x-601d677fc4f8?source=rss-de6e46557599------2</link>
            <guid isPermaLink="false">https://medium.com/p/601d677fc4f8</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[mathematics]]></category>
            <category><![CDATA[zero-knowledge-proofs]]></category>
            <category><![CDATA[starknet]]></category>
            <dc:creator><![CDATA[Modulus ZK]]></dc:creator>
            <pubDate>Tue, 02 Sep 2025 13:21:41 GMT</pubDate>
            <atom:updated>2025-09-02T13:21:41.988Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*AJpCO9iygGN_dqBMQL_87Q.jpeg" /><figcaption>ModulusZK — Layer X</figcaption></figure><h3><strong>Our Vision vs. What Exists</strong></h3><h4>Current Blockchain Layers:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4HsHUw9G_mz9yQj4bjDHKA.png" /></figure><p><strong>Problem:</strong> Each layer is “stuck” in a hierarchy. L3 needs L2, L2 needs L1.</p><h3>Our Layer X:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lZt37FC5RhmzrkNfc4jGNQ.png" /></figure><p><strong>Solution:</strong> Not stuck anywhere. Can send proofs to any chain.</p><h3>Why This Matters</h3><h4>Traditional Approach:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*USVFgm7ykvZFYLGAb9sNxg.png" /></figure><p><strong>Our Layer X Approach:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FLpZueOJ9hU9VdSYre97Sw.png" /></figure><h3><strong>Real World Analogy</strong></h3><p><strong>Traditional Layers = Like a building</strong></p><ul><li>L3 sits on L2</li><li>L2 sits on L1</li><li>Can’t move floors around</li></ul><p><strong>Layer X = Like email</strong></p><ul><li>Write once</li><li>Send anywhere</li><li>Not stuck to one provider</li></ul><h3><strong>The Technical Magic</strong></h3><p>Our FOL (First-Order Logic) system creates proofs that are:</p><ol><li><strong>Portable</strong> — Work on any blockchain</li><li><strong>Flexible</strong> — Can split them up (some here, some there)</li><li><strong>Efficient</strong> — Cheaper than current methods</li></ol><h3><strong>Why “Layer X”</strong></h3><ol><li><strong>“X” = “cross” — </strong>Cross-chain, cross-layer</li><li><strong>“X” = “unknown”</strong> — Not L1, L2, or L3… something new</li><li><strong>“X” marks the spot — </strong>The missing piece in blockchain</li></ol><h3>Benefits for Users</h3><h4>Now:</h4><ul><li>Stuck with high Ethereum fees OR</li><li>Stuck with less secure L2s</li></ul><h4>With Layer X:</h4><ul><li>Put important stuff on Ethereum</li><li>Put big data on Celestia</li><li>Put frequent updates on cheap chains</li><li>All using <strong>THE SAME SYSTEM</strong></li></ul><h3>The Business Opportunity</h3><p>Instead of competing with existing chains, we’re:</p><ul><li><strong>Helping</strong> all chains work better</li><li><strong>Connecting</strong> different blockchains</li><li><strong>Reducing</strong> costs for everyone</li></ul><h3><strong>Simple Example</strong></h3><p>Imagine a user building a game:</p><p><strong>Without Layer X:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FhRYugp1aTr9fcThpm5FPw.png" /></figure><p><strong>With Layer X:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DdXfVBkdcuofjvl6cE0kMg.png" /></figure><h3><strong>Why This Is Revolutionary</strong></h3><p>Our math (FOL) breakthrough should mean:</p><ol><li><strong>One proof system</strong> works everywhere</li><li><strong>Cheaper</strong> than existing methods</li><li><strong>More flexible</strong> than anything else</li></ol><p>Think of Layer X as the “USB standard” for blockchain proofs. Works everywhere. Makes everything easier.</p><p><a href="https://x.com/moduluszk">https://x.com/moduluszk</a></p><p><a href="https://x.com/moduluszk">https://x.com/mromodulus</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=601d677fc4f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>