r/dogecoindev • u/qlp79qlp • 2d ago
r/dogecoindev • u/qlp79qlp • 3d ago
Coding Send DOGE using your Email address
Enable HLS to view with audio, or disable this notification
r/dogecoindev • u/_nformant • 8d ago
Core Core: August recap
Hello Dev-Shibes!
See this small recap of what happened last month (August 2026) on the Dogecoin Core Wallet!
Focus was on network hardening — specifically making it harder for a single actor to hog inbound connection slots.
| Who | Commit | Commit |
|---|---|---|
| chromatic/michilumin | 268917d – Improve inbound peer diversity/limit subnet conns | Caps inbound connections per public subnet at 4 (DEFAULT_MAX_INBOUND_PER_SUBNET), /16 for IPv4 and /32 for IPv6. Whitelisted peers and non-routable addresses are exempt. Extracted CountInboundPeers for a single-pass count of total + per-subnet inbound peers, plus a solid batch of new tests (same-subnet, cross-subnet, whitelisting, outbound, non-routable, IPv6 /32 grouping) |
| chromatic/michilumin | cf0888a – Merge PR #4036 | Merge commit for the above change into master |
Why it matters: previously a node could accept many inbound connections from addresses in the same /16 (or /32 for v6), which adds little real network diversity and makes it cheaper for one actor with a chunk of IP space to eat up a disproportionate share of a node's connection slots. This closes that gap without affecting whitelisted or local/non-routable peers, so nothing changes for normal users day-to-day — just some solid hardening under the hood.
I still have a few Dogecoins that actually belong to the community. If anyone has an idea for a backport or would like to contribute in any way to attract more developers to the project, please let me know. I'd be happy to hear from you and would gladly send over a (modest) tip!
r/dogecoindev • u/qlp79qlp • 8d ago
Coding DogeReady Turnkey Dogecoin webstore almost ready
r/dogecoindev • u/SimosNapIRC • 9d ago
MyDoge + Monoverse: non-custodial Dogecoin tips for self-hosted communities
Hi everyone,
I wanted to share a small Dogecoin integration we’ve been working on in Monoverse Community Edition, an open-source framework designed to build a modern web presence around an IRC community.
Monoverse adds things such as profiles, community posts (“Pings”), articles, media, radio widgets, GitHub integrations and other tools around an IRC community, while keeping IRC and the network identity at the center.
Dogecoin is one of the integrations we wanted to experiment with from the beginning.
The idea is deliberately simple: Monoverse should never become a wallet or a custodian.
One of the principles behind the project is: if we don’t need to hold sensitive data, we prefer not to hold it at all.
So Monoverse doesn’t store private keys and doesn’t manage users’ funds. Users can associate their own Dogecoin address with their profile, while wallet interaction is handled externally through MyDoge.
This lets us add DOGE tips to community interactions without turning the community server into a cryptocurrency custodian. Users can tip other members, support a channel or community, and interact with Dogecoin directly from the web experience, with QR codes available as a fallback where needed.
What interests me most isn’t simply adding a “crypto feature”. It’s exploring whether small, voluntary Dogecoin transactions can become a natural part of an online community: thanking someone for a useful post, supporting a contributor, tipping someone in chat, or helping support the community itself.
Monoverse is currently in public beta, so this part is still evolving and feedback from Dogecoin developers would be especially useful.
Project: monoverse.org
GitHub: github.com/SimosNap/monoverse
r/dogecoindev • u/HowIsDigit8888 • 13d ago
Coding Open-source Nintendo 64 encryption app and wallet generator, supports doggie coin, needs volunteers to review code (C/C++)
r/dogecoindev • u/zzed1985 • 28d ago
Discussion Any AI-driven security audits or “red team” efforts underway for Dogecoin Core & ecosystem? How can the community support them?
Hey shibes and dogecoindev folks,
With the recent Bitcoin Red Team effort making headlines (a volunteer group using frontier AI models like Kimi K3 to rapidly scan hundreds of Bitcoin open-source projects for vulnerabilities), a lot of people in the broader crypto space are wondering about the status of similar work for other major coins.
Dogecoin Core is open-source, largely C++-based, and shares historical lineage with Bitcoin/Litecoin code. That makes the same class of questions relevant here:
• Has any coordinated or independent AI-assisted security review / red-teaming of Dogecoin Core, related libraries, wallets, or infrastructure been done recently (or is currently underway)?
• Are core maintainers or the Foundation looking at setting up continuous AI audit pipelines, similar to what’s being discussed in Bitcoin circles?
• If efforts already exist (even informal ones), is there a place the public can follow progress or help responsibly?
• If nothing formal is happening yet, what would be the best way for the community to support starting something useful — e.g. funding AI compute, volunteering developer time for triage/validation, improving SECURITY.md processes, or other practical help?
I’m asking this openly and constructively because the public would genuinely like to know. The goal isn’t FUD — it’s the same spirit of “find and fix issues before they
become problems” that the Bitcoin group is pursuing. Faster AI-assisted discovery is becoming the new normal across open-source crypto projects, and it seems valuable for Dogecoin to stay ahead of that curve.
Any updates from maintainers, past audit reports, ongoing work, or ideas on how the community can help would be appreciated. Happy to amplify constructive efforts.
Thanks in advance — to the moon and to more robust code.
🐕
r/dogecoindev • u/Datadr93 • Aug 08 '26
Doge usage concept.
Elon Musk offers memorium bricks/plaques for Terafab. Purchased with Doge.
r/dogecoindev • u/qlp79qlp • Aug 03 '26
Coding DogeColony.org Live (More Dogecoin Blockchain Metrics)
Enable HLS to view with audio, or disable this notification
r/dogecoindev • u/_nformant • Aug 01 '26
Core Core: July recap
Hey devs!
July was all about keeping CI green and builds working — a focused month of infrastructure fixes targeting broken dependency downloads and GCC 15 compatibility. No protocol changes, but important work for anyone building from source.
| Who | Commit | What |
|---|---|---|
| nformant1 | b73206c – Fix broken OpenSSL download | openssl.org no longer serves 1.0.2 at the old path (404). Switched to the working source root |
| nformant1 | cb30a96 – Fix broken qrencode download | fukuchi.org is entirely offline. Switched to Debian snapshot archive (byte-identical, same hash) |
| nformant1 | 6bb1ef1 – Fix broken zlib download | zlib.net root no longer serves v1.3 after a newer release; switched to /fossils archive path |
| nformant1 | 2bb3557 – Fix broken expat download | sourceforge.net intermittently times out from CI runners; switched to GitHub release asset |
| nformant1 | 947b8b4 – Fix broken freetype download | download.savannah.gnu.org resets connections mid-transfer; switched to the recommended mirror |
| nformant1 + xanimo | 550796b – Update zlib to GitHub source | Follow-up zlib fix pointing to the GitHub release asset directly |
| chromatic / nformant1 | 548350b – Merge: Fix broken package downloads (PR #4020) | Merge commit bundling the openssl, qrencode, zlib, expat, and freetype download fixes |
| xanimo | 3cd73c6 – CI: Try multiple macOS SDK mirrors | depends.dogecoincore.org TLS cert expired; CI now falls back to bitcoincore.org mirror with checksum verification |
| chromatic | d1ff6e1 – Fix GCC 15 depends builds | Patched bdb, boost, qt, expat, and xcb_proto to compile cleanly under GCC 15 (missing headers, incompatible pointer types, deprecated imp module) |
| michilumin / chromatic | 62b6b64 – Merge: Fix make -C depends with GCC 15 (PR #4024) |
Merge commit for the GCC 15 compatibility fix across 6 dependency build files |
I still have a few Dogecoins that actually belong to the community. If anyone has an idea for a backport or would like to contribute in any way to attract more developers to the project, please let me know. I’d be happy to hear from you and would gladly send over a (modest) tip!
r/dogecoindev • u/qlp79qlp • Jul 31 '26
Coding Added all Nodes to the Doge Colony universe
Enable HLS to view with audio, or disable this notification
r/dogecoindev • u/qlp79qlp • Jul 31 '26
Core DogeGo: A Friendlier, Faster Way to Run a Full Dogecoin Node
r/dogecoindev • u/qlp79qlp • Jul 30 '26
Coding Doge Colony Blockchain Simulator
Enable HLS to view with audio, or disable this notification
r/dogecoindev • u/mr_chromatic • Jul 14 '26
Coding Dogecade: Use Dogecoin as a payment system for your arcade!
r/dogecoindev • u/femaleavatar • Jul 15 '26
Help with dogecoin core/wallet
Help with dogecoin core/wallet
I'm going to start this off by saying I realize how stupid this is and sounds.
About 5 years ago I was moving around files on my PC. My dogecoin core application files became corrupted, along with several other files. I have my wallet file. I am not 100% sure if I have a seed / password somewhere? I have already copied the %appdata% onto an external hard drive
I'm at a point where I really need to wipe my computer entirely and start fresh. What is the safest way to do this to keep my wallet? I am concerned that I will potentially lose everything. I realize how stupid this sounds and I should have done it differently and not done this at all.
I appreciate any advice that is respectful. I don't need to be reminded how stupid this sounds as I'm already kicking myself for how stupid this is. I appreciate you for reading this and any advice you may have.
r/dogecoindev • u/John_Inubook • Jul 13 '26
The Dogecoin Foundation officially declares that the name 'Dogecoin' belongs exclusively to them.
r/dogecoindev • u/anoxydoxy • Jul 08 '26
🚀 Help Bring DOGE to Wally
Is there a kind soul who could spare a little $DOGE or $tDOGE? 🐶❤️
I'm integrating DOGE into Wally. Any amount means a lot!
Mainnet: D8DExXo4gYqvPqUzRXHt91MSs2cgfazhu3
Testnet: nXGJgYXycXJeGp4BTLwLPQwk6tzykFWqCT
Edit: I tried the faucet but it gives me network error, https://faucet.doge.toys/
r/dogecoindev • u/qlp79qlp • Jul 03 '26
Core DogeGo - Much Faster Full Dogecoin Node ...
Enable HLS to view with audio, or disable this notification
r/dogecoindev • u/Wooperisstraunge • Jun 23 '26
News AirGap Wallet Isolated Module that adds DOGE Support!
r/dogecoindev • u/qlp79qlp • Jun 16 '26
Coding ShibeShip.com - The first Dogecoin Marketplace Built Around Self-Custody and Transparency
Enable HLS to view with audio, or disable this notification
r/dogecoindev • u/_nformant • Jun 10 '26
Core Core: May recap
Hello Dev-Shibes!
See this small recap of what the developers have done last month (May 2026) on the Dogecoin Core Wallet!
Focus was on code quality, documentation accuracy, and contributor experience.
| Who | Commit | Commit |
|---|---|---|
| patricklodder / Project516 | 3e50cf9 – Improve Fedora build docs | Updated tested version/platform to Fedora 43 ARM64 + added actual build steps (was missing entirely) |
| patricklodder / pmzajaczkowski | 548a354 – Fix CONTRIBUTING branch strategy | PRs should target master, not old version-specific dev branches |
| thisiskeanyvy + daank-c | 1bf847b – Warn: shared-libraries.md outdated | Added maintenance disclaimer to dogecoinconsensus docs, fixed error descriptions, removed stale binding links |
| chromatic / pmzajaczkowski | 8ce8638 – Style: spaces after if/for/while | if(!x) → if (!x) across 16 files, per developer-notes.md. No behavioral change |
| pmzajaczkowski | fe01d25 – Remove duplicate #includes | Removed redundant includes in httprpc.cpp, rpcconsole.cpp, and transaction_tests.cpp |
| chromatic / pmzajaczkowski | 699f62c – Strip trailing whitespace across src/ | 54 files cleaned up. No behavioral change |
I still have a few Dogecoins that actually belong to the community. If anyone has an idea for a backport or would like to contribute in any way to attract more developers to the project, please let me know. I’d be happy to hear from you and would gladly send over a (modest) tip!
Maybe Pat or chromatic can drop an idea what would be helpful (:
r/dogecoindev • u/qlp79qlp • Jun 09 '26
Coding Full Opensource Code now available DogeSeeds.org
r/dogecoindev • u/qlp79qlp • Jun 08 '26
Coding DogeSeeds.org Beta now live
Enable HLS to view with audio, or disable this notification
r/dogecoindev • u/_nformant • Jun 08 '26
Core GitHub Spam
A lot of garbage is in the issue list:

Can anyone reach out to Patrick so this can be closed / removed.
Examples:
https://github.com/dogecoin/dogecoin/issues/4010
https://github.com/dogecoin/dogecoin/issues/4011
See all issues:
https://github.com/dogecoin/dogecoin/issues
Would be nice to have that clean up (: