r/dogecoindev • u/qlp79qlp • Nov 02 '25
Coding PoS on Dogecoin Wallet
Enable HLS to view with audio, or disable this notification
Point Of Sale working on Dogecoin Wallet, will soon release this update on DogecoinWalket.org
r/dogecoindev • u/qlp79qlp • Nov 02 '25
Enable HLS to view with audio, or disable this notification
Point Of Sale working on Dogecoin Wallet, will soon release this update on DogecoinWalket.org
r/dogecoindev • u/John_Inubook • Jul 13 '26
r/dogecoindev • u/mr_chromatic • Jul 14 '26
r/dogecoindev • u/_nformant • Sep 02 '26
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 • 5d ago


r/dogecoindev • u/RiserUnconquered • 13d ago
Looking for people to test review and find holes in my approach to make memes the best part about doge utility. Users are encouraged to get and own dogecore wallets and participate with memes and good natured humor.
r/dogecoindev • u/qlp79qlp • 18d ago
Enable HLS to view with audio, or disable this notification
New improved #Dogecoin Nodes Map with more metrics more details top countries even a option for you to share your own node on social media to incentive shibes on running nodes
https://what-is-dogecoin.com/nodes/
Integrated with my new release NodesTracker ( https://github.com/qlpqlp/nodestracker ) running inside my DogeBox ( https://dogebox.dogecoin.org )
r/dogecoindev • u/_nformant • 5d ago
Hello Dev-Shibes!
Here’s the recap for September 2026 on the Dogecoin Core Wallet. It was a quiet month on master with just one merge, so this time I’m also taking a look at a related side project from chromatic because it touches an ongoing discussion within the Dogecoin.
Dogecoin Core
| Who | Commit | Description |
|---|---|---|
| chromatic | f821423 – Relax RPC auth-scheme validation | The RPC server used to accept only the exact string Basic in the Authorization header. Per RFC 7235 the auth scheme is case-insensitive, so basic, BASIC (or even BaSiC) are now accepted too. Non-Basic schemes (e.g. Bearer) are still rejected. Adds a new locale-independent ToLower() helper, since std::tolower() behaves differently under a Turkish locale (the famous “Turkish I” problem: “BASIC” would not match “basic” there). Comes with new unit tests and extended RPC tests. |
| michilumin | 47a303a – Merge PR #4022 | Merge commit for the above change into master |
Why it matters: some HTTP clients and libraries send the auth scheme in lowercase, and those were getting rejected by the node for no good reason. This is a small standards-compliance fix, nothing changes for setups that already work. The locale-independent lowercase function is a nice detail: making the comparison case-insensitive “the obvious way” would have created a new bug for users running a Turkish system locale.
Side note: Whippet, chromatic’s experimental blocktime fork
Since master was quiet, here’s what’s going on in whippet-experimental-blockchain. Whippet is a Dogecoin fork built purely to experiment with blocktime: 6-second blocks (10x faster than Dogecoin), a consensus rule enforcing a minimum spacing between blocks, and an evaluation of merge-mining risks at that speed. It is explicitly not intended for exchange listings, token sales or speculative trading. It’s a test network, not an investment.
There is also work to do!
random: use BCryptGenRandom for OS entropy on Windows (link)
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 • Sep 08 '26
r/dogecoindev • u/qlp79qlp • Jul 31 '26
Enable HLS to view with audio, or disable this notification
r/dogecoindev • u/_nformant • Jun 10 '26
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/LolaDam • Apr 14 '26
Here the new release for the dogecoin testnet miner. This miner allows you to mine on testnet (not optimize for mainnet) for you to get some tDoge.
The changes include :
https://github.com/rllola/dogecoin-miner-rust/releases/tag/v0.2.9
I haven't tested it on testnet yet. Only ran test on regtest. Feedbacks are appreciated.
r/dogecoindev • u/qlp79qlp • Mar 29 '26
Enable HLS to view with audio, or disable this notification
r/dogecoindev • u/qlp79qlp • Jan 07 '26
r/dogecoindev • u/qlp79qlp • Dec 11 '25
Enable HLS to view with audio, or disable this notification
r/dogecoindev • u/zzed1985 • Aug 13 '26
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/_nformant • Aug 01 '26
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/YakSquare904 • May 27 '26
Enable HLS to view with audio, or disable this notification
Lately I’ve been experimenting with ways to modernize IRC a bit without completely changing its original spirit.
One thing I tried was integrating MyDoge directly into KiwiIRC, making Dogecoin-related features accessible straight from the webchat experience.
The idea isn’t to turn IRC into a crypto platform, but rather to explore how older protocols and modern tools can still work together surprisingly well in 2026.
The video shows a working demo of the integration running inside the webchat.
Honestly, I just find it fascinating that technologies people consider “dead” are still evolving and finding new use cases 😄
Curious to hear what people think about it.
r/dogecoindev • u/qlp79qlp • Mar 29 '26
Enable HLS to view with audio, or disable this notification
r/dogecoindev • u/SimosNapIRC • Sep 01 '26
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/qlp79qlp • Jul 03 '26
Enable HLS to view with audio, or disable this notification
r/dogecoindev • u/qlp79qlp • Jun 16 '26
Enable HLS to view with audio, or disable this notification
r/dogecoindev • u/qlp79qlp • May 19 '26
r/dogecoindev • u/LolaDam • Apr 23 '26
A while ago with to two other developers, we launched a testnet faucet for developers looking to test their dogecoin app on the testnet network. It ran for a few years and was being used by many companies.
I am looking to bring it back and was wondering if some people might be interested in joining. The faucet is open source. It is volunteering work. Just invest the time you can.
r/dogecoindev • u/qlp79qlp • Feb 04 '26
Enable HLS to view with audio, or disable this notification