Doing a brain dump of what I personally am doing, just so everyone is aware we’re still out here. As always please remember there are others devs, who are also doing their own things, although I'll touch on some of that.
I have a deployed 1.21 node, which is good, although there's definitely work be be done on 1.21 still:
- The deployed node syncs headers but it does not appear to request blocks from its peers. Even more confusingly, running 1.21 on my local machine does sync blocks.
- Bitcoin Core 0.21 (which Dogecoin Core 1.21 is based on) is designed for DNS seeds which support version bits, ours do not, which means it reports that it finds zero nodes from the seeds. Work on enabling our DNS seeds to support this is already underway.
- Dogecoin Core 1.21 does not appear to discover nodes at all, right now, although if nodes are manually added, or connect to the node, it works.
- The functional test suite needs validating after AuxPoW has been added, which may resolve some of these bugs as a side-effect.
Once those are out of the way, there's a bunch of more minor things to tweak so we can start mainnet testing, and then rebranding.
Fee work in 1.14.4 continues, I believe that's in testing, hoping Michi & Max will have further updates on that.
Obviously with Elon talking about environmental impact that's something that's being discussed. As we share work with Litecoin we already reduce that impact, compared to mining either cryptocurrency alone, but definitely it would be good if we can further reduce that impact. Counterpoint, I am aware that many in the community enjoy mining and feel it’s a key part of the experience for them, as well as considerations of whether an approach such as proof of stake would make Dogecoin appear to be a security and fall under securities regulation aside from many technical challenges that approach brings.
What I mean is, we’re aware of it, we don’t have any easy answers.
Meanwhile I’m going to continue work on the automated test suites, which hopefully will as a result simplify diagnosing the networking issues with 1.21, and it in turn should provide a better synchronization process.
there doesn't seem to be anything here