DogeOS has opened its Chikyū public testnet, giving developers an EVM-compatible environment for building smart-contract applications around Dogecoin while leaving the underlying Layer 1 unchanged. The September 30 launch introduces programmable execution with testnet DOGE as the native fee currency, but it is not a Dogecoin Core upgrade or a DogeOS mainnet launch. Official documentation lists chain ID 6281971 and supports standard Ethereum development tools including Hardhat, Foundry and ethers.js.
According to the official DogeOS launch announcement, teams are developing trading, lending, stablecoin, prediction-market and gaming applications for the network. Chikyū gives those projects a public development environment before mainnet rather than demonstrating that the applications are already operating with real economic activity. DogeOS comes from the team behind MyDoge and previously raised $6.9 million in a May 2025 round led by Polychain Capital.
Chikyū Still Uses a Permissioned Security Model
DogeOS describes the network as a zero-knowledge rollup designed to settle around Dogecoin, but its current trust model includes components outside the Dogecoin consensus system. Chikyū presently relies on a permissioned sequencer, validators and a trusted execution environment, while Dogecoin itself does not verify the rollup’s ZK proofs. Bridge state transitions require a valid proof together with signatures from a validator majority and a TEE signer.
That makes the distinction between testnet infrastructure and the longer-term architecture particularly important. DogeOS documentation says the application layer targets roughly 300 transactions per second and three-second blocks, compared with approximately 30 TPS and one-minute blocks on Dogecoin Layer 1. Those are project-reported performance characteristics for the application layer, not evidence that Dogecoin’s base chain has increased its throughput. Similar separation between execution layers and underlying consensus is central to other zero-knowledge Layer 2 architectures.
DOGE’s role is also limited by the testnet environment today. Developers use valueless test DOGE for contract deployment and transaction fees, with a bridge connecting the Dogecoin testnet and Chikyū. There is no live DogeOS mainnet using real DOGE yet, and DogeOS has not published a firm mainnet launch date. Its own developer materials say the team is working toward mainnet while the public environment remains focused on testing.
OP_CHECKZKP Could Change the Security Boundary
DogeOS’s longer-term design depends on a proposed Dogecoin Core change called OP_CHECKZKP. Submitted for community discussion in July 2025, the draft would repurpose the unused OP_NOP10 opcode to let Dogecoin scripts verify zero-knowledge proofs natively. The initial specification proposes Groth16 verification on the BLS12-381 curve, potentially allowing Dogecoin nodes to validate proofs representing computation performed outside the base chain.
That proposal remains exactly that: a proposal. It has not been incorporated into Dogecoin Core consensus or activated across mainnet. If adopted, miners running upgraded validating nodes would enforce the new verification rules when accepting blocks, potentially allowing DogeOS to reduce its current reliance on a separate validator and TEE structure. It would not mean that Dogecoin’s mining ASICs themselves perform zero-knowledge computation; proof verification belongs to node validation rather than proof-of-work hashing.
The distinction matters for Dogecoin’s existing security infrastructure, which includes a mature proof-of-work ecosystem and merged-mining relationships with Litecoin. Dogecoin has also gained traditional financial access through products such as the physically backed TDOG ETF, but adding a programmable application layer is a fundamentally different proposition because it introduces new bridges, execution logic and security assumptions.
Chikyū therefore gives developers something Dogecoin itself does not currently provide: an EVM-compatible environment where DOGE can sit inside smart-contract workflows. What remains unresolved is the most consequential part of the architecture: whether the Dogecoin community will accept the consensus change needed for the base network to verify DogeOS proofs directly. Until that happens, the public testnet can demonstrate applications and performance, but its security model remains meaningfully different from the miner-anchored design DogeOS ultimately wants to build.
