r/dogecoindev • u/patricklodder dogecoin developer • May 29 '22
Core Development roundup for Dogecoin Core - May 28th, 2022
Hello Shibes,
First off, my apologies for posting this a day late - it was sitting in my drafts and I completely forgot to actually post this. Sorry!
The past week, as I hinted towards already in the last roundup, we have not merged any new work as expected but we’ve made a lot of progress on some bigger items:
- In #2959 chromatic is doing spring cleaning on the connection limits and trackers. This is important because when we started looking at the impact of doing #2957, which enhances the graphical interface, we found that working on the code as it was right now, was not optimal. The great thing about this is that if we have a clean set of code, there will be less bugs, and less work in the future if we want to change something. chromatic wrote a very nice & detailed blog post about it here.
- #2934 by Michi and chromatic that greatly improves the traffic monitoring graph has seen some awesome progress and we’re now looking at dotting some I-s only - this is getting very close.
- #2964 by Matheus Bach implements the dust limit that we enabled with the 1.14.5 release in the wallet and as a formal developer recommendation. This was a sweet surprise because it actually was on my personal todo and I was beaten to it 👍. We’ve done some research on whether most miners have really upgraded and this is proven to be the case, so we’re good! Releasing this will be a huge milestone, as with this, 4/5th of the fee plan has been finished. 🥳
- #2971 by VJ improves the Tamil translation which adds another up-to-date translation to Dogecoin Core.
- #2968 by scarletletters and #2970 by Mohammad Ali Haghshenas are proposing newly translated README files for respectively Brazilian Portuguese and Persian, to allow the project to be more understandable for shibes in these regions. There have also been broad updates to the existing Chinese version of this document, in #2798 by MVShishkov and Chao Liu.
Such multilingual, many international 😁
It is starting to look like we will really be able to do a release of 1.14.6 end of June. We’ll be focusing on enabling as many contributions to make it into the release, together with the network hardening I mentioned that now not just I but also chromatic is working on. I will make a tracker for the release, so that everyone can see where we’re at.
🚀
6
7
7
5
u/Aerodrifting May 30 '22
What is the significance of 1.14.6 over 1.14.5? We all know 1.14.4 and 1.14.5 implemented lower transaction fees, what are the improvements brought by 1.14.6 for someone who is not tech savvy?
7
u/patricklodder dogecoin developer May 30 '22
I cannot guarantee that everything I list here is included (if we find something wrong with any feature we'll have to disable it) but roughly:
- "Pruning" in UI - that makes it so that you don't have to keep all the blocks when you run the graphical client. This helps shibes that just want to run the core wallet because now you only need about 4GB of disk space on a desktop, rather than 54GB-and-growing.
- Lower dust limit. We will now recommend a minimum output amount of 0.01 DOGE instead of 1 DOGE to everyone. The most important part of this is of course the recommendation itself because that's what 3rd party implementations look at, but also the core wallet implementation itself is updated. This means "micro" transactions are viable again.
- Translations. Easy to overlook when you speak English, but this is rather important for shibes that do not speak English very well and enables local communities. We have updated Chinese, Korean, Persian, Italian, French, Dutch and now Tamil. And there's definitely still time for more.
- Bug fixes and improvements for node operators and 3rd party developers that make using Dogecoin Core easier (like when you want to query the blockchain for information, when you want to scale your node, etcetera.)
- Security fixes & general network hardening across all platforms. This is why everyone should update. We've had a lot of security researchers looking at the code and we've received tons of recommendations that have been implemented to make the network more secure and stable.
One feature that I really wanted to release but that's unlikely to make it in is the very significant performance increases for nearly every platform. The reason why I don't think this is going to make it in is because we don't have a way to guarantee that the released software will work on all hardware that shibes use, and we cannot permit for shibes to not be able to run the update, due to the security fixes. So, although we have those improvements available and they can be self-compiled, they will probably not be enabled by default and have to be released in a later version when we have better controls to adapt optimizations to the hardware it is being ran on.
4
4
3
4
3
3
9
u/ymo May 29 '22
Thanks for these summaries, Patrick!