Layer 1 blockchain
Dogecoin ticker DOGE
Summary
Miners search for blocks using a proof of work based on a simplified scrypt function, with difficulty readjusted every block toward a one-minute target. Since block 371,337 (2014) blocks can also be merged-mined through auxiliary proof of work, which lets miners of other scrypt chains such as Litecoin submit the same work to Dogecoin. Dogecoin Core is adapted from Bitcoin Core: value is held as unspent transaction outputs guarded by Script inherited from it, and nodes follow the valid chain with the most accumulated work. 1234613
Design
- System
- Layer 1 blockchainDogecoin is its own proof-of-work chain with its own blocks and fork choice. Wrapped DOGE tokens on other networks and application layers that use DOGE are separate systems and are not described by these cells.
- Settlement family
- Bitcoin family
- Scarce resource
- Work (proof of work)
- State model
- UTXO
- Finality
- Probabilistic
- Who makes blocks
- Miners, usually through pools and often merged-mining with other scrypt chains, propose blocks by proof of work; every fully validating node checks each block, including the merged-mining proof, against its own rules.
- Fork choice
- Valid chain with the most accumulated work, not the greatest height. Confidence grows with each one-minute confirmation but no depth is mathematically final.
Qualifications
- Settlement family · Partial. Dogecoin Core is adapted from Bitcoin Core and keeps its output-based settlement, but it uses a scrypt-based proof of work, accepts merged-mined blocks and has not activated segregated witness, Taproot or relative timelocks, so features that depend on those upgrades are not available on Dogecoin.
Tradeoffs
- Emphasizes
- Decentralization and Security
- Gives up
- Base-layer expressiveness and off-chain scaling: the chain's script, adapted from an older Bitcoin Core release, has no relative timelocks or segregated witness, which payment channels rely on, so there is no production channel or proof-verified second layer. Throughput stays bounded by ordinary one-minute blocks that home nodes can check.Security leans on merged mining: much of the work protecting Dogecoin can come from miners whose main target is another scrypt chain. How concentrated that hashpower is was not measured here. A 2021 plan to activate relative timelocks and segregated witness has not shipped in any release.
- Full node at home
- Practical at home 122431Dogecoin.com's undated node guide asks for 2 GB RAM, at least 60 GB of disk and an unmetered connection (a popular node can upload up to 1 TB a month), and warns the first sync can take over 24 hours. That disk figure is stale: on 27 September 2026 Trezor's Dogecoin status page showed about 204 GB on disk for its Dogecoin Core 1.14.9 node, indexes unstated. A pruning option can delete old blocks to save space. Plan for about 200 GB unpruned, which home hardware can still hold.
- Throughput claims
- No classified figure recorded
Scaling layers
- DogeOS (testnet) · Unknown family, testnet 1127282930
An EVM layer from the team behind the MyDoge wallet. Its docs call it a rollup whose proofs Dogecoin verifies, and describe a Chikyu testnet that posts data to Ethereum and treats blocks as final after proof and withdrawal transactions on Dogecoin. But Dogecoin script cannot verify zero-knowledge proofs today (the opcode is only a draft), and the testnet bridge guide calls itself very early without saying who controls deposited DOGE. How withdrawals are secured is unverified, so its design family is left open. No mainnet was confirmed.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Independent softwareLimited scope | Independent software, limited: Komodo Platform's AtomicDEX lists DOGE among the assets it swaps with hash-locked, time-locked contracts; no first-party implementation is cited. Script supports hash locks, and absolute timelocks (CHECKLOCKTIMEVERIFY) have been enforced since block 3,464,751 after the soft fork shipped in Dogecoin Core 1.14.0. The limit: segregated witness is not active, so the malleability fix it brings to protocols that pre-sign dependent transactions is absent. 357918 |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Built into the protocolLimited scope | Protocol, limited: consensus produces the proof-of-work header chain that simplified payment verification clients check; the node has served bloom filters for them since version 1.4.0, and libdogecoin ships a lightweight SPV node with a REST interface. Limits: bloom filters leak which addresses a client cares about, and compact block filters are not in Dogecoin Core's list of implemented improvement proposals. 516 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | The earlier note said absence was not verified, so the rule that absence needs a source makes this unknown. Earlier finding: no payment or state channel network running on Dogecoin was found. The maintainers' 2021 consensus plan calls relative timelocks a must-have for payment channel networks, and they are not active. 59 |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Outputs carry Script conditions inherited from Bitcoin Core, including pay-to-script-hash, multisig and absolute timelocks. Segregated witness, Taproot and relative timelocks are not active. A draft proposal to add zero-knowledge proof verification to Script is under discussion and not adopted. 351011 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under the current definitions; only absolute timelocks are active, building blocks with which wallets can build escrow or refund-after-a-date paths with multisig and a timelock. Relative timelocks are not active, which rules out the delayed-spend patterns that depend on them. No cited source shows a sender-reclaim window or recovery path live, and the protocol cannot reverse a confirmed payment. 359 |
| Rollups | Unknown | No proof-verified rollup on Dogecoin mainnet was found. DogeOS calls itself a rollup, but it is an EVM layer on testnet that posts data to Ethereum, and Dogecoin cannot yet verify zero-knowledge proofs in script, so it is not counted as a rollup here. 112729 |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | Unknown | No source was cited for absence, so the rule that absence needs a source makes this unknown. Earlier finding: Dogecoin's base layer has no token or contract layer for an AMM; wrapped DOGE traded on other chains' AMMs is outside Dogecoin, and apps on the DogeOS testnet were not reviewed. |
| Issuer-native stablecoins | None found | The protocol has no native token issuance, and neither Tether's supported-protocol list nor Circle's USDC address list includes Dogecoin. Inscription-style tokens tracked by off-chain indexers were not reviewed. 2122 |
| Algorithmic stablecoins | Unknown | No source was cited for absence, so the rule that absence needs a source makes this unknown. Earlier finding: no algorithmic stablecoin with material usage on Dogecoin was identified; absence was not exhaustively verified. |
| Bridges | Established in the ecosystemCoinbase Wrapped DOGE (cbDOGE) on Base, THORChain, NEAR Intents, wDoge (Ethereum, status unknown) | cbDOGE is a token on Base backed one to one by DOGE held by Coinbase; Coinbase customers wrap and unwrap through their accounts. THORChain lists Dogecoin among the chains it swaps natively, receiving DOGE into its own vault addresses. NEAR Intents lists Dogecoin among the chains its proof-of-authority bridge supports. wDoge was a DAO-governed wrapper on Ethereum that the Dogecoin Foundation joined as a key holder in 2022; no current project page was verified (the wdoge.tech domain now redirects to an unrelated site), so its status is unknown. Risk: None of these is trust-minimized, and Dogecoin cannot verify anything about the other side. cbDOGE depends on Coinbase's custody and redemption. THORChain depends on vaults signed by threshold signatures among its validators, who bond RUNE. NEAR Intents' bridge depends on the approved operators behind its proof-of-authority model; the reviewed page does not say who holds deposited DOGE. wDoge depended on its DAO key holders. 171920323334 |
| Block explorers | Established in the ecosystemDogechain, Trezor Blockbook (Dogecoin), SoChain, BlockCypher | Dogecoin.com links SoChain, Dogechain, BlockCypher, Blockshibe and Blockchair; Dogechain and Trezor's Blockbook instance (run for Trezor Suite, on Dogecoin Core 1.14.9) loaded at review, while SoChain, BlockCypher and Blockchair blocked automated retrieval and Blockshibe's content could not be read. A public explorer's view is provider data, not independent validation. 142324 |
| Hardware wallets | Established in the ecosystemLedger, Trezor, Cypherock | See the Ledger and Trezor custody entries in this profile: both vendors list Dogecoin on their own pages. Dogecoin.com also lists Cypherock, which was not checked against the vendor's site. 152526 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Native supportSame as native: Yes | Can: Send and receive DOGE through the Ledger Wallet app while the private keys stay offline on the Ledger device Can: Manage DOGE on the Ledger hardware wallets listed on Ledger's Dogecoin page 25 |
| Trezor | Native supportSame as native: Yes | Can: Send and receive DOGE on all Trezor models Can: Manage DOGE in Trezor Suite or supported third-party wallets 26 |
Public data
iKnow Blockchain has no public-data lookups for Dogecoin yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
Dogecoin Core development branch caps inbound peers per network subnet
A change merged into Dogecoin Core's master branch limits how many inbound connections a node accepts from the same public network range, so a node's peers come from more varied networks. It is not in any release yet.
- Proposal:pull request 4036
- Implementation:merged into the development branch
- Release:not in any release (latest release 1.14.9)
- Activation:no activation needed; applies only to nodes running a future release that includes it
Sources: Dogecoin Core developers — Improve inbound peer diversity/limit subnet conns, pull request 4036 (external site) · Dogecoin Core developers — Dogecoin Core releases (external site)
-
Dogecoin Core 1.14.9 released with fixes for bugs inherited from Bitcoin and Namecoin code
Dogecoin Core 1.14.9 is a minor release of the reference node and wallet. Its notes say it fixes bugs that Dogecoin Core inherited from upstream Bitcoin Core and Namecoin Core, and they describe no consensus rule change. It predates this review's one-year news window but is kept because it was still the latest Dogecoin Core release at review; no release was published in 2025 or 2026.
- Implementation:shipped in the tagged v1.14.9 release
- Release:released 2024-12-01; marked Latest on the release page at review
- Activation:no activation needed; no consensus change described; applies to nodes that install it
Sources: Dogecoin Core developers — Dogecoin Core 1.14.9 (external site) · Dogecoin Core developers — Dogecoin Core 1.14.9 release notes (external site) · Dogecoin Core developers — Dogecoin Core releases (external site) · Dogecoin Core developers — Dogecoin Core releases (Atom feed) (external site)
Topics your AI can explain
Your AI can explain these topics for Dogecoin through the connection, with sources.
Known gaps
What this profile's review did not establish:
- No throughput figure is listed; no primary-source rate was classified for this profile.
- The node guide's 60 GB disk figure is undated and out of date. The only current size seen was the figure on Trezor's explorer status page, which does not say which optional indexes it includes; the minimum storage for a pruned node was not verified.
- The share of Dogecoin's hashpower that comes from merged mining, and pool concentration, were not measured.
- Confirmation counts that exchanges require for DOGE deposits were not verified from a primary source.
- DogeOS mainnet status, bridge security and sequencer operation were not verified; only testnet documentation was reviewed.
- The wDoge wrapper's current status is unknown: no current project page was verified, and the wdoge.tech domain now redirects to an unrelated site.
- Who holds DOGE deposited through the NEAR Intents bridge, and how many operators sign for it, is not stated on the reviewed page.
- Other wrapped DOGE tokens, such as exchange-issued pegged tokens on other chains, and separate EVM chains that use wrapped DOGE, were not reviewed.
- Inscription-style tokens tracked by off-chain indexers on Dogecoin were not reviewed.
- SoChain and BlockCypher explorer pages blocked automated retrieval; they are named from dogecoin.com's links only. Blockshibe and Blockchair, also linked there, could not be read either.
- Cypherock's Dogecoin support was not checked on the vendor's own site.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Dogecoin Core repository (README) (external site)
- Dogecoin Core FAQ (external site)
- Dogecoin Core chain parameters (src/chainparams.cpp) (external site)
- Dogecoin Core block validation (src/validation.cpp) (external site)
- BIPs implemented in Dogecoin Core (external site)
- Dogecoin Core 1.8.0 release notes (external site)
- Dogecoin Core 1.14 release (external site)
- Dogecoin Core releases (external site)
- Consensus plan for next major release (1.21), issue 1798 (external site)
- Consensus plan for next major release (1.21), discussion 2264 (external site)
- Draft Proposal: OP_CHECKZKP Zero-Knowledge Upgrade, discussion 3869 (external site)
- Operating a Node (external site)
- Mining Dogecoin (external site)
- Dogecoin.com (external site)
- Dogecoin wallets (external site)
- Development Blog - April 2025 (external site)
- Dogecoin Foundation to join the wDoge DAO (external site)
- What Is AtomicDEX? (external site)
- cbDOGE Proof of Reserves (external site)
- Coinbase Wrapped Assets (external site)
- Supported Protocols (external site)
- USDC Contract Addresses (external site)
- Dogechain: Dogecoin Block Explorer (external site)
- Trezor Dogecoin Explorer (Blockbook) (external site)
- Dogecoin wallet (external site)
- Supported coins and assets (external site)
- Ethereum and DogeOS differences (external site)
- State of Doge - August 2025 (external site)
- DogeOS overview (external site)
- DogeOS Chikyu testnet bridge guide (external site)
- Dogecoin Core 1.14.9 startup options (src/init.cpp, pruning help text) (external site)
- UTXO chain clients (external site)
- What is THORChain and RUNE (external site)
- Bridging overview (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding