​
Architecture

DogeVM is a smart contract execution layer for Dogecoin. It adds programmability on top of Dogecoin L1. DogeVM is a metaprotocol — it has no separate chain. It reads Dogecoin transactions, processes them according to DogeVM rules, runs WASM smart contracts, and writes a state summary back to Dogecoin. The underlying L1 never changes; DogeVM just gives it superpowers.
New to blockchain terms? See the Glossary for plain-English definitions of L1, WASM, vaults, Doginals, and more.

​
Core Components

┌─────────────────────────────────────────────────────────────────┐
│                      DogeVM Metaprotocol                         │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│  ┌──────────────────────────────────────────────────────────┐   │
│  │              Execution Layer (processes transactions)     │   │
│  │  ┌─────────────┐  ┌─────────────┐                         │   │
│  │  │  WASM VM    │  │  State      │                         │   │
│  │  │  Executor   │  │  Processor  │                         │   │
│  │  └─────────────┘  └─────────────┘                         │   │
│  └──────────────────────────────────────────────────────────┘   │
│                                                                  │
│  ┌──────────────────────────────────────────────────────────┐   │
│  │           Bridge Layer (connects to Dogecoin)             │   │
│  │  ┌────────────────────┐                                  │   │
│  │  │  Dogecoin Bridge   │  Mainnet not yet live            │   │
│  │  └────────────────────┘                                  │   │
│  └──────────────────────────────────────────────────────────┘   │
│                                                                  │
│  ┌──────────────────────────────────────────────────────────┐   │
│  │                   Security Layer                          │   │
│  │  ┌─────────────┐  ┌─────────────┐                        │   │
│  │  │   Fraud     │  │  Economic   │                        │   │
│  │  │   Proofs    │  │   Bonds     │                        │   │
│  │  └─────────────┘  └─────────────┘                        │   │
│  └──────────────────────────────────────────────────────────┘   │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

​
Execution Layer

​
WASM Virtual Machine (Smart Contract Engine)

DogeVM runs smart contracts written in Rust, compiled to WebAssembly (WASM). The VM:
  • Runs the same contract code identically on every node
  • Charges gas for each operation (prevents runaway code)
  • Provides contracts access to storage, events, L1 chain data, and cross-contract calls

​
State Processor

The state processor maintains the global record of all contract state and balances. It:
  • Processes transactions in order
  • Computes a state root — a single hash summarizing all state
  • Posts that root to Dogecoin L1 so anyone can verify DogeVM is behaving correctly

​
Fee Market (EIP-1559 Style)

DogeVM uses a dynamic fee system:
  • A base fee adjusts automatically — rises when blocks are full, falls when empty
  • Maximum change per block: ±12.5%
  • Target utilization: 40% of block gas
  • Add a priority tip for faster inclusion

​
Bridge Layer

​
No “bridge” to trust

We use the word bridge for the component that connects DogeVM to Dogecoin L1, but it is not a traditional crypto bridge:
Traditional bridgeDogeVM
You lock assets on Chain A; receive wrapped tokens on Chain BYour DOGE stays in your vault on Dogecoin the whole time
A bridge contract holds funds; can be hacked or frozenNo bridge contract. Vault is 2-of-2 (you + protocol); only you have an escape path
Wrapped asset is a separate tokenvDOGE is a 1:1 balance; your vault balance on L1 equals your vDOGE
The Dogecoin bridge in DogeVM is just the service that watches Dogecoin for your vault deposits and withdrawals, credits or burns vDOGE, and posts state commitments (e.g. OP_RETURN) to L1. There is nothing to “bridge” in the usual sense — your DOGE never leaves Dogecoin.

​
Dogecoin Bridge (mainnet not yet live)

  • Vault type: P2PKH with CLTV escape hatch
  • Verification: Economic bonds + fraud proofs — anyone can challenge incorrect state
  • State commits: OP_RETURN outputs (32-byte state root)
  • Deposit confirmations: 3 blocks (~3 min — Dogecoin’s ~1-minute blocks)
  • Escape timelock: 20,160 blocks (~2 weeks)

​
Security Layer

​
How DogeVM Ensures Correctness

Economic bonds + fraud proofs Operators post a bond in DOGE before committing state. If the commitment is wrong, anyone can challenge: 
1. Challenger detects an incorrect state commitment
2. Challenger posts a bond and opens a challenge
3. Bisection game narrows down to the single bad computation step
4. That step is verified on-chain
5. The fraudulent operator loses their bond to the challenger

​
Vault Architecture

Every user’s deposited funds are held in a vault — an on-chain Dogecoin address with two spending paths: 
Vault Address (Dogecoin P2PKH)
│
├── Normal Path — you + DogeVM together
│   └── Instant withdrawal — processed by the protocol
│
└── Escape Path — you alone, after ~2 weeks
    └── Safety exit — no permission needed, works even if DogeVM stops
The escape path ensures your funds are always recoverable. DogeVM cannot unilaterally spend from your vault — it needs your key.

​
Escape Hatch

ChainBlocksTime
Dogecoin20,160~2 weeks

​
Transaction Flow (on Dogecoin)

​
Deposit

1. You request a vault address → SDK or CLI returns a Dogecoin address
2. You send DOGE to that address
3. DogeVM scanner detects deposit after 3 confirmations (~3 min)
4. Your vDOGE balance is credited on DogeVM

​
Withdrawal

1. You request a withdrawal on DogeVM → vDOGE burned immediately
2. Withdrawal queued for batch processing
3. Protocol signs and broadcasts the Dogecoin L1 transaction
4. You receive DOGE in your Dogecoin wallet

​
Smart Contract Call

1. You submit a signed transaction
2. Transaction waits in mempool
3. Block producer includes it in the next DogeVM block
4. WASM VM executes the contract function
5. State changes recorded; events emitted
6. At next epoch: state root committed to Dogecoin L1

​
Node Architecture

┌─────────────────────────────────────────────────────────────────┐
│                       DogeVM Node                                 │
├─────────────────────────────────────────────────────────────────┤
│  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐              │
│  │    RPC      │  │  Relayer    │  │  Watchtower │              │
│  │   Server    │  │  (L1 txs)   │  │  (fraud     │              │
│  └─────────────┘  └─────────────┘  │   detection)│              │
│  ┌─────────────┐  ┌─────────────┐  └─────────────┘              │
│  │   WASM      │  │   Vault     │  ┌─────────────┐              │
│  │   VM        │  │   Manager   │  │  Dogecoin   │              │
│  └─────────────┘  └─────────────┘  │  Scanner    │              │
│                                    │  Scanner    │              │
│                                    └─────────────┘              │
│  ┌──────────────────────────────────────────────────────────┐   │
│  │              Storage (RocksDB key-value database)         │   │
│  └──────────────────────────────────────────────────────────┘   │
└─────────────────────────────────────────────────────────────────┘
Node ModeWhat it doesWho runs it
PrimaryProduces DogeVM blocks, commits state to Dogecoin L1Main operator
ReplicaSyncs from primary, serves read requestsScaling / redundancy
ArchiveFull history, never prunesBlock explorers, auditors