--- title: "Dogecoin Developers Propose OP_CHECKZKP to Enable Zero-Knowledge Verification" description: "A draft Dogecoin Improvement Proposal outlines an opcode upgrade to support Groth16 and PLONK proofs as a soft fork." url: https://basisdesk.news/news/dogecoin-developers-propose-op-checkzkp-zero-knowledge-upgrade published: 2026-10-01T05:06:00.728Z modified: 2026-10-01T05:06:00.728Z section: Altcoins author: Basis Desk Newsroom (AI-generated, source-verified) sentiment: neutral tickers: [DOGE] tags: [Dogecoin, Zero-Knowledge, Layer 2, Cryptography, Soft Fork] license: Quote with attribution to Basis Desk (basisdesk.news). Not financial advice. --- # Dogecoin Developers Propose OP_CHECKZKP to Enable Zero-Knowledge Verification A draft Dogecoin Improvement Proposal outlines an opcode upgrade to support Groth16 and PLONK proofs as a soft fork. ## Key points - A draft DIP proposes OP_CHECKZKP to enable native on-chain verification of zero-knowledge proofs on Dogecoin. - The proposal repurposes opcode 185 (OP_NOP10) to deploy the verification functionality as a backward-compatible soft fork. - The opcode introduces Mode 0 for Groth16 on BLS12-381 and Mode 1 for PLONK with Halo2/KZG on the BN256 curve. ## Editorial remark - **Context:** Dogecoin's scripting capabilities have historically mirrored early Bitcoin script, restricting complex execution and smart contract operations on the base layer. - **Impact:** If approved and merged, the opcode would allow developers to anchor trustless zk-rollups and scale off-chain computation to Dogecoin without congesting base nodes. - **Watch:** Dogecoin Core developers and community reviewers will deliberate the draft specification in GitHub discussion #3869 before formalizing code integration. Dogecoin developers introduced a draft Dogecoin Improvement Proposal (DIP) on GitHub proposing `OP_CHECKZKP`, a new opcode aimed at bringing native on-chain verification of zero-knowledge proofs to the Dogecoin network [1]. The upgrade seeks to enable trustless Layer-2 scaling frameworks, such as zk-rollups, without requiring changes to the network's base consensus model or introducing a general Turing-complete virtual machine [1]. At the time of writing, $DOGE traded at $0.0958, gaining 2.6% over the preceding 24 hours. The proposed implementation repurposes the unused opcode 185 (`0xB9`), historically known as `OP_NOP10` [1]. By redefining an existing no-operation code, the proposal functions as a backward-compatible soft fork: legacy nodes evaluate the byte as a standard `OP_NOP`, while updated nodes will invalidate any script where the zero-knowledge proof fails verification [1]. Under successful verification, the opcode leaves input data on the stack, ensuring that execution continues without altering legacy stack expectations [1]. ## Multi-Mode Proof Support According to the draft specification, `OP_CHECKZKP` relies on an extensible mode selector to support multiple cryptographic proof mechanisms [1]. Mode 0 specifies verification of Groth16 proofs on the BLS12-381 curve with two public inputs, utilizing verification logic developed from previous community research by QED [1]. Mode 1 provides support for PLONK proofs generated via Halo2 using the KZG commitment scheme on the BN256 curve, integrating protocol parameters from OpenVM [1]. Under Mode 1, inputs are bounded by strict limits, including a maximum proof length of 4,096 bytes, a verifying key size cap of 8,192 bytes, and a maximum of 64 public inputs [1]. The initiative addresses performance bottlenecks in Dogecoin's native scripting language, which lacks the capability to verify off-chain compute operations efficiently [1]. By delegating complex application computations to off-chain provers and verifying succinct proofs on-chain, proponents argue Dogecoin can accommodate decentralized finance and gaming activity without inflating node requirements or block verification times [1]. This development follows community-led efforts to expand utility, such as when [DogeOS launched an EVM-compatible public testnet for Dogecoin](https://basisdesk.news/news/dogeos-launches-evm-public-testnet-dogecoin) to facilitate smart contracts [1]. ## FAQ **Does OP_CHECKZKP introduce a full virtual machine to Dogecoin?** No. The proposal explicitly avoids adding a general virtual machine or Turing-complete script, maintaining consensus simplicity by only handling on-chain proof verification while computation is done off-chain. **Will existing Dogecoin nodes need to upgrade immediately?** Because the proposal reuses the unused OP_NOP10 opcode, older nodes will interpret it as an unassigned no-op, allowing the change to function as a backward-compatible soft fork. ## Sources 1. [Draft Proposal: OP_CHECKZKP Zero-Knowledge Upgrade · dogecoin dogecoin · Discussion #3869](https://github.com/dogecoin/dogecoin/discussions/3869) — github.com, 2026-10-01 --- Basis Desk Newsroom · AI-generated, source-verified · https://basisdesk.news/about/how-we-use-ai