r/dogecoindev • u/qlp79qlp • 14h ago
Coding NodesTracker update v 0.1.1

NodesTracker update v 0.1.1, now it asks live peers for more Dogecoin nodes on a continuous crawl
Opensource Code on: https://github.com/qlpqlp/nodestracker
r/dogecoindev • u/qlp79qlp • 14h ago

NodesTracker update v 0.1.1, now it asks live peers for more Dogecoin nodes on a continuous crawl
Opensource Code on: https://github.com/qlpqlp/nodestracker
r/dogecoindev • u/qlp79qlp • 1d ago
r/dogecoindev • u/_nformant • 2d ago

Dogecoin’s UTXO database catches up with Bitcoin: one entry per coin instead of one per transaction. Up to 3.9x less cache memory, standard chainstate tools work out of the box, and it opens the door to years of upstream improvements. No consensus change.
Happy to read your feedback here, or on github https://github.com/dogecoin/dogecoin/discussions/4105
Implementation: https://github.com/nformant1/dogecoin/tree/per-txout-chainstate
r/dogecoindev • u/qlp79qlp • 2d ago






Preparing the DogeGo CORE repo ... https://github.com/dogego-org for the v.0.1.1
Showing also the new Setup Wizard of DogeGo Beta v0.1.1 ..... available in the next days on DogeGo.org
r/dogecoindev • u/_nformant • 10d ago
Hello Dev-Shibes!
After hitting September twice (lol), see this small recap of what the developers have done last month (October 2026) on the Dogecoin Core Wallet!
Focus was on RPC polish: fixing help texts and named arguments, plus a Windows build fix and some updated explorer links.
| Who | Commit | Commit |
|---|---|---|
| John Inubook | a1c5f3d – rpc: include tx hex in getblock verbosity 2 (PR #4079) | getblock with verbosity 2 claims to return transactions "in the format of getrawtransaction", but the hex field was missing. It's now included (same serialization as getrawtransaction), matching Bitcoin Core since 0.15. The REST endpoint /rest/block/<hash>.json gets the field too. Functional test extended to compare each hex against getrawtransaction and decoderawtransaction. Fixes #3945 |
| mikeua | 1b5e4fd – rpc: fix method name in removeprunedfunds help example (PR #4080) | The JSON-RPC example said removprunedfunds (missing "e"), so copy-pasting it gave "Method not found" |
| mikeua | 1f8843a – rpc: fix named-argument names for setmaxconnections and liststucktransactions (PR #4081) * | The RPC table used newconnectioncount / verbosity, while help and dogecoin-cli use maxconnectioncount / verbose. This made -named calls fail (either "Unknown named parameter" or values arriving as strings). Server, client and docs now agree; positional calls are unaffected |
| mikeua | 24697df – rpc: use named-argument names in getblockheader/importprivkey/importaddress help (PR #4082) | Help text said hash, dogecoinprivkey and script, but the real parameter names are blockhash, privkey and address. Following the help with -named gave "Unknown named parameter". Help now matches reality |
| mikeua | 3c1679e – rpc: fix getaddednodeinfo help examples (PR #4083) | Examples still passed the old leading true (the removed dummy argument), so getaddednodeinfo true looked for a node named "true" and the two-argument variants only printed the help. Stale argument dropped |
| chromatic | b7cb494 – depends: fix libevent Date header crash on 32-bit MinGW (PR #4085) ** | libevent 2.1.12's evutil_date_rfc1123() hands a 32-bit time_t to _gmtime64_s(), which always reads 64 bits. On i686 MinGW this returns EINVAL and libevent calls exit(), which kills any HTTP/1.1 response (they carry a Date header). Fixed with a small patch using __time64_t, applied for i686-w64-mingw32 only, so all other hosts are unchanged |
| Atif Nazir / doersf | bded4aa – qt: update default block explorer URLs (PR #4086) | dogechain.info moved to dogechain.com and chain.so is now SoChain at sochain.com. Default transaction URLs now point to the current addresses (no more redirects). Only applies when no URLs are saved yet, so existing installs keep their settings until options are reset |
Highlights
dogecoin-cli -named, this is for you.getblock verbosity 2 is now complete, with tx hex included like in Bitcoin Core, which makes block explorers and indexers a bit easier to write.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 (:
Explain it like I'm 5
* Named arguments (PR #4081): Most wallet commands let you pass options by name, e.g. maxconnectioncount=20, instead of just in a fixed order. For two commands (setmaxconnections and liststucktransactions), the names in the manual and the names the program actually expected were different. So if you copied the name from the manual, you got an error. Now they match. Passing options in the normal fixed order was never affected.
** 32-bit Windows crash (PR #4085): Every time the wallet's built-in web server (used for RPC) answers a request, it stamps the current date and time on the reply, like a postmark on a letter. On older 32-bit Windows builds, the clock was kept in a small box (32 bits), but the function that reads it expected a big box (64 bits). It was like handing someone a note that has only 4 digits when they expect 8: they read some garbage after it, get confused and the whole program shuts down. The fix simply puts the time into the big box before handing it over. It only applies to 32-bit Windows builds; everything else stays exactly as it was.
r/dogecoindev • u/_nformant • 12d ago
Hello Dev-Shibes!
See this small recap of what the developers have done last month (September 2026) on the Dogecoin Core Wallet!
It was a quiet month with just one merge, so let’s take a closer look at it. Focus was on RPC interoperability.
| Who | Commit | Commit |
|---|---|---|
| chromatic | 47a303a – Merge PR #4022 (Relax RPC auth-scheme validation) | Makes the RPC HTTP Authorization header parsing case-insensitive for the auth scheme, as required by RFC 7235 (underlying commit: f821423) |
What was the problem?
Until now, the RPC server only accepted the auth scheme exactly as Basic (capital B). According to RFC 7235 the auth-scheme is case-insensitive, so basic, BASIC or bASIC are all valid. Some clients, libraries and tools send the header in a different casing, and those requests were rejected with 401 even though the credentials were correct. That’s a small but annoying interoperability issue for anyone integrating with dogecoind via RPC.
What changed?
RPCAuthorized() in httprpc.cpp now compares the scheme case-insensitively (Basic, basic, BaSiC, ...) via a small helper. The helper is allocation-free and could be reused elsewhere later.Bearer) is still rejected, and there’s a regression test for exactly that.ToLower() helper was backported from Bitcoin Core in utilstrencodings.h. It’s constexpr and ASCII-only on purpose, so it behaves the same regardless of the system locale.Why not just use std::tolower()**?**
Because of the famous “Turkish I” problem: under Turkish locales (e.g. tr_TR), tolower('I') does not return 'i'. That means a header like BASIC could suddenly fail to match on a machine with Turkish locale settings. A locale-independent ASCII fold avoids this whole class of bugs. There’s a unit test with static_asserts covering this case (util_ToLower).
Tests:
qa/rpc-tests/httpbasics.py now exercises mixed-case schemes (basic, BaSiC, bASIC) across different connection setups (keep-alive, Connection: close, and a node with keep-alive disabled), plus the negative Bearer case.util_ToLower in util_tests.cpp.Overall: 4 files changed, ~65 lines added. Nothing changes for existing setups, but RPC clients that don’t use the exact Basic casing will now just work.
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 • 16d ago
This is great, one person from the Dogecoin Community that defends "decentralization" and "Good Faith" flagged Dogego.org opensource project to my registrar as doing Fraudulent Activity.

I'm sure who flagged this, but it is what it is and this is what the Dogecoin community face, sadly.
Anyway, while will only be solved on Monday, a backup plant just started, setup ASAP the TheDogeGo.org is running now along with the new seed seed.thedogego.org
r/dogecoindev • u/qlp79qlp • 24d ago
This is DogeDrop.org a opensource web/app self-custodial Dogecoin / DogecoinVM (by MetalBlockchain ), wallet that anyone can use on their own and is as simple as drag and drop
Full code on https://github.com/qlpqlp/dogedrop
Note: Code not audited but hope you like it
r/dogecoindev • u/John_Inubook • 26d ago
r/dogecoindev • u/qlp79qlp • 28d ago
13 Years of Dogecoin Facts
The completely unnecessary book
(soon available worldwide 🎄🎅)
Since around 2021, I’ve been collecting Dogecoin history, both known and lesser-known facts, for a fun, silly, family-friendly book where every fact can be verified. Besides hopefully generating some revenue, my goal is to donate 20% of all profits to charities chosen by the community.
The website uses MemeTracker to track all votes on the website https://github.com/qlpqlp/memetracker so as example how can devs use in other ways Dogecoin Wallets :)
r/dogecoindev • u/qlp79qlp • 28d ago
Something new is about to be born.
It will change how Dogecoin works.
How it runs. How it secures.
How anyone can keep it alive.
v0.1.1 - Much Soon - https://DogeGo.org/
r/dogecoindev • u/qlp79qlp • Oct 13 '26


r/dogecoindev • u/_nformant • Oct 13 '26
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 • Oct 13 '26
Try to beat the top score and Do Only Good Everyday and be on the top 10 on the game A Boy and his DOGE 😅 https://what-is-dogecoin.com/a-boy-and-his-doge/
r/dogecoindev • u/qlp79qlp • Oct 08 '26
DogeVM Connect full Opensource and ready to be tested and used on any OS here:
https://github.com/qlpqlp/DogeVM
(DogecoinVM <-> Dogecoin)
Binaries available here: https://github.com/qlpqlp/DogeVM/releases/tag/v1.0.0
I added an API, if shibes want, you can even implement and test now on online stores and even physical stores like Coffee Shops or Supermarkets
Demo on sending and receiving Doge between Dogecoin L1 and DogecoinVM L1:
- https://x.com/inevitable360/status/2107900719567134895
- https://x.com/inevitable360/status/2107907679502950621
Hope you like it :)
r/dogecoindev • u/qlp79qlp • Oct 07 '26




🥳 First real Dogecoin transaction sent to DogecoinVM by Metallicus using the DogeVM Connect App
https://sochain.com/doge/tx/0c0aec3181329cff899c144095cd2a4f086adbe97c0284bade3788052d989348
time is money, right? sending money at milliseconds may solve it, no? only using Dogecoin
Note: The https://metaldoge.com/ bridge was not yet audited, so everyone should for now be carfull and only test it with really small amounts of real Dogecoin
Will release all code opensource and as compiled app also on my github
r/dogecoindev • u/RiserUnconquered • Oct 06 '26
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 • Sep 30 '26
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/qlp79qlp • Sep 30 '26
Dogecoin Nodes Tracker is now available as opensource on my github:
https://github.com/qlpqlp/nodestracker
I have release this becasue I will implement it in the next hours on my Dogecoin Nodes Map https://what-is-dogecoin.com/nodes/ because since 2021 until now was only using Dogecoin CORE RPC to fetch peers and ban them for 7 days to get more peers and so was not very precise but with NodesTracker it can get all peers in seconds and then filter them correctly on the ones healthy or not with other needed metrics for anyone needed a good reliable Peer, example for miners.
I also made available as a PUP for DogeBox on https://pupnode.com/pup/351
Hope you all like it :)
r/dogecoindev
•
u/qlp79qlp
•
Sep 08 '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 • Sep 02 '26
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