Protocol

Dogecoin Core, DIPs, and what is not a proposal

The reference client on GitHub, a small 2014 DIP repo for BIP-70 payment protocol, and a Foundation Trailmap that is not a soft fork.

Last reviewed 2026-09-194 min readprotocol · dogecoin · core · history

Jump the story
Mechanic cartoon Shibas assembling a gold node from gears and a scrypt pickaxe

Dogecoin Core is the C++ reference node: scrypt proof-of-work, one-minute blocks, AuxPoW with Litecoin since 11 September 2014. Anyone can compile a tagged release. Dogecoin Improvement Proposals live in github.com/dogecoin/dips, created 12 April 2014. The README is strict: copy BIPs for a static reference, write a DIP only where a minor BIP change is needed for Dogecoin, and send innovative work toward RFCs. As of this review that repo holds BIP-0070/71/72 plus DIP-0070/71/72 — payment-protocol variants — not a living catalog of consensus changes. The work that actually ships is pull requests on github.com/dogecoin/dogecoin. The Foundation Trailmap is a third object.

What Core is

Dogecoin the asset is a UTXO chain. Dogecoin Core is the software most people mean when they say “the node.” The README, as of this review, warns that from August 2024 the master branch is the unstable integration branch; compile a tagged version for production. Development is public: GitHub Projects for planned work, GitHub Discussions for features. Four branch types: master (unstable), maintenance (`*-maint`), development (`*-dev`), archive (immutable old tags). Submit pull requests against master. That is the living proposal process. A tweet is not a BIP.

After the founders left, a small volunteer set kept the client compiling. Names that recur in this encyclopedia’s sources: Michi Lumin, Ross Nicoll, Patrick Lodder, Max Keller. Nicoll told Decrypt he had been in Musk’s DMs since the 2019 honorary-CEO week; the Foundation later posted that he stepped back from a director role in February 2022. Personnel overlap with the Foundation is real. Control of Core by the Foundation is what the Foundation’s 2021 post denied.

What people confuse

MisconceptionRecord
DIPs are like Bitcoin’s BIP board, hundreds deepThe dips repo, as listed on GitHub at this review, is BIP-0070/71/72 plus DIP-0070/71/72 and a paymentrequest.proto. Payment protocol. Not a second constitution.
The Trailmap is a Core roadmapLibdogecoin and GigaWallet are dogecoinfoundation GitHub projects. Community staking PoS in the Trailmap prologue is a Foundation sketch with Buterin. Dogecoin is still PoW.
Musk submits Core PRsHe told people to submit ideas on GitHub and Reddit in 2021. That is a celebrity pointing at the door. The door is still GitHub.
House of Doge ships CoreHODO is a stock. Releases are git tags.
Inscriptions are a Core featureDoginals are a metaprotocol. Core validates scripts. Indexers invent the rest.

What a DIP actually is

The dips README, in full force: three file types. BIPs copied in so DIPs have a static parent. DIPs only for minor modifications to an existing BIP so it fits Dogecoin. Innovative or significantly divergent work should be prepared as standards-track RFCs, not as a DIP with a new number. That is why the repo looks empty next to bitcoin/bips. It is a 2014 payment-protocol drawer, not a failed congress.

DIP-0070/71/72 sit next to BIP-0070/71/72 (Payment Protocol / MIME types / URIs). If you arrived here looking for a numbered plan to add staking, an L2, or a supply cap, you are in the wrong cabinet. Look at Core PRs, Discussions, and — separately, labeled as such — the Foundation Trailmap.

The upgrades that actually shipped

The encyclopedia’s Core facts that are already dated: random block rewards ended at block 145,000 (version 1.6, 17 March 2014) because pools cherry-picked high-subsidy blocks — see Random block rewards. AuxPoW, Dogecoin Core 1.8, 11 September 2014, from block 371,337: Litecoin miners can secure both chains. The perpetual 10,000 DOGE tail after block 600,000 is the issuance Core still implements. Palmer argued against a 100 billion cap; Markus later called the tail a leftover bug they left in. Those are history on the Dogecoin page. This page adds the clerk: none of them were DIPs in the 0070 family. They were client releases.

Foundation software beside the node

Libdogecoin’s own README: Core inherited heavy C++ libraries; the Foundation wanted a C library with few dependencies so other languages and embedded targets could speak Dogecoin without shipping the full wallet. GigaWallet describes itself as the backend for a Dogecoin business. Those can be useful and still not be consensus. If a merchant stack uses GigaWallet, that is an integration. If a node requires it, that would be a different encyclopedia sentence, and this review does not have that sentence.

Questions

Where do I submit a Core change?

Pull requests against master on github.com/dogecoin/dogecoin, per the project README. The dips repo is for BIP-derived payment-protocol variants and RFC-bound standards, not a general wish list.

Is the Foundation’s staking idea live?

Not as consensus. The December 2021 Trailmap prologue described a community-staking PoS sketch with Vitalik Buterin. As of 19 September 2026 Dogecoin remains scrypt proof-of-work with AuxPoW.

Sources

Primary texts for this chapter. The full index lives on Doginals sources.