Skip to content
Blockchain Posts

protocol

DogeOS opens Chikyū public testnet, bets Dogecoin DeFi on OP_CHECKZKP

DogeOS opened its Chikyū EVM zkVM testnet for Dogecoin DeFi on Sept 30. Current trust: permissioned sequencer, TEE, Security Council. Miner-verified state waits on OP_CHECKZKP in Dogecoin Core.

by 4 min read
protocoldogecoinrollupzkinfrastructure

DogeOS, the Dogecoin DeFi project led by the MyDoge wallet team, opened its public Chikyū testnet on September 30, 2026, exposing an EVM-compatible zero-knowledge rollup for a stack of lending, perps and prediction-market apps that pay fees in DOGE. The pitch of eventual Dogecoin-miner security is real but conditional: the "miners secure the apps" story hinges on a Dogecoin Core proposal, OP_CHECKZKP, that is not yet merged. Until then Chikyū runs with a permissioned sequencer, trusted-hardware enclaves and a Security Council — the opposite shape from what Dogecoin's own base layer offers.

What happened

DogeOS CEO Jordan Jefferson opened the testnet with a public faucet dripping 42.069 test DOGE per day, documentation at docs.dogeos.com, and an SDK at sdk.dogeos.com. The chain is pitched as an "Application Layer rollup network on Dogecoin": EVM semantics on top of a zkVM, with the long-term aim of settling proofs back to Dogecoin itself.

The named launch partners that Decrypt lists:

  • Superposition Finance — lending.
  • Derps — perpetual futures.
  • USDoge — CDP-style stablecoin.
  • Snag — prediction-market aggregator.
  • PlaysOut — around 15 Doge-themed casual games.

No DogeOS token has been announced. Mainnet has no public date.

Mechanism — zkVM rollup, not merged mining

Chikyū is not merged mining and not restaking. It is an EVM-equivalent rollup executed on a zkVM, with the following current trust assumptions, per CoinDesk's technical read:

  1. Sequencer: one permissioned operator orders transactions. Users do not have a trust-minimised forced-inclusion path on day one.
  2. Trusted execution environments: parts of the stack run inside TEE hardware that bounds the sequencer's ability to censor or reorder.
  3. Validator set: off-chain validator operators that attest to zkVM state.
  4. Security Council: governance body with upgrade and pause powers over the rollup contracts.
  5. Settlement anchor: today, off-chain — not Dogecoin consensus.

That last point is load-bearing. Dogecoin miners do not currently verify DogeOS proofs or state. The project's own roadmap says they could, but only if Dogecoin Core gains a new opcode: OP_CHECKZKP.

OP_CHECKZKP — the opcode the roadmap is pinned to

In July 2025, DogeOS published a Dogecoin Core discussion proposal for OP_CHECKZKP, an opcode that would let Dogecoin script verify zero-knowledge proofs of off-chain computation. A reference implementation submitted in December 2025 is explicitly a draft, with a placeholder proof checker. Only after that opcode ships in a Dogecoin Core release — and is adopted by miners — would DogeOS state be checkable at the base layer. The schedule is a Core-process schedule, not a DogeOS one.

Until then, "miners eventually secure its apps" is a design-doc promise. The security model that users touch today is the permissioned sequencer, the TEE enclave, and the Security Council.

Numbers

- Testnet name              : Chikyū
- Launch date               : 2026-09-30
- Chain type                : EVM-compatible zkVM rollup
- Native fee token          : DOGE (test DOGE on testnet)
- Faucet drip               : 42.069 test DOGE / day
- Settlement to Dogecoin    : not live; requires OP_CHECKZKP (Dogecoin Core proposal, July 2025)
- OP_CHECKZKP status        : discussion + draft reference implementation, no Core merge
- Current sequencer         : permissioned, single operator
- Hardware trust            : TEE enclaves + Security Council
- Launch partners (named)   : Superposition Finance, Derps, USDoge, Snag, PlaysOut
- Token                     : none announced
- Mainnet                   : no date

What to watch

  1. OP_CHECKZKP progress in Dogecoin Core. The relevant signals are a formal BIP-style doc, a non-draft reference implementation, and node operator discussion on dogecoin/dogecoin. Without that path, the "Dogecoin-secured apps" claim stays aspirational.
  2. Sequencer decentralization. The current permissioned sequencer is the single largest trust assumption on the Chikyū UX. Watch for a sequencer rotation plan, forced-inclusion inbox, or shared sequencer integration.
  3. TEE assumptions. TEEs have a non-trivial history of sidechannel and remote-attestation breaks. The specific hardware vendor and attestation chain DogeOS depends on are the material disclosures here.
  4. Bridge model. DOGE enters and leaves the rollup through something. Until proofs settle to Dogecoin, that bridge is multisig-shaped. Who holds the keys, under what threshold, is the thing to ask before putting real DOGE in.

Context — Bitcoin-adjacent rollups keep arriving before their base-layer path exists

The pattern across BitVM, BitVMX, Citrea and now DogeOS is the same: a rollup ships, apps ship, UX ships — and the base-layer verification path is a soft commitment that depends on an opcode or soft-fork that has not yet been adopted. In each case the operational security during that gap looks like a conventional L2 (sequencer + enclave + council), not a trust-minimised L1 extension. For Dogecoin specifically, the political path to a Core change is distinct from Bitcoin's and historically slower; DogeOS has placed itself upstream of that conversation rather than waiting on it. The thing to measure is whether the Chikyū testnet produces enough developer and miner interest to actually move OP_CHECKZKP along, or whether the project runs the rollup indefinitely in its current trust model.

Sources

Related stories