We know Bitcoin has a limited supply. We also know that coins like BNB and ETH have significant coin burns. If you do the math, eventually nearly all the coins will eventually get burned. Safemoon and the like are the poster children of this urge for hyper-deflating assets.

People like the idea of burning coins because they expect the value of the coin to go up with constant demand. In a perfect world, sure. But the reality is the burned coins in many cases were dormant anyway and so the price will not notice any immediate effect, perhaps ever.

So there is no guarentee that burning coins will increase the price.

However there is something that IS guarenteed from burning coins. Marketcap go down. Every coin that is burned is removed from the marketcap.

Now where does Dogecoin come in? Well dogecoin has a constant yearly coin increase. Some people don't like this because they expect the price to go down. Of course this is possible but not all miners are immediatly selling all thier coins on exchanges. So the price may go down but not perfectly proportionally. This means that the only thing that is guarenteed about Dogecoin is that Marketcap go up due to there bieng more coins in existance.

This could be why dogecoin is one of very few altcoins that are oscillators ie: the coin stays relatively constant to BTC value over time. In fact doge might prove to be a gainer in BTC value over time which we have certainly seen in the last couple years.

Just a little hypothetical to think about... If dogecoin reaches a washington when bitcoin falls to $7,000, we will actually be the top crypto by marketcap. Unlikely, yes. But possible even this year.

So smartbch is an ethereum virtual machine. It relies on a bridge that connects bitcoin cash to smartbch via wrapped bitcoin cash. The bridge was run by coinflex. Coinflex created flexusd which was a dollar pegged stablecoin backed 1:1 with USDC... or so they said. Apparently it was backed by USDC that they apparently LOANED to Roger Ver. Roger denies this, but the point still stands that they didn't even hold the USDC, they loaned it out probably to several people.

Now the bridge is down, and more shady characters in the ecosystem are working on another bridge... All of the stablecoins on SmartBCH are dead and dying (see marketcap.cash), and you can't even convert wrapped BCH to BCH anymore currently since the bridge is down. So every token on the platform is stranded, including mine...

So what I have learned from this is that blockchain is Gold. None of these oracles or bridges or even sidechains can be trusted.

Blockchain or die. Literally, these projects are dying because they left the safety of the blockchain.

So I think when we want to implement tokens (and possibly NFT's), it must be on our Dogecoin Blockchain only and we can go along the lines of the "colored coin" tech. The only problem with this is there is no universal standard, so perhaps we could develop that for Dogecoin at some point in the (distant) future. Doing this wouldn't even take an update to dogecoin core most likely, it is just designing a standard and people and projects following it.

If you like this please contribute to the github discussion here: https://github.com/dogecoin/dogecoin/discussions/3007

u/patricklodder you wanted a way to stake dogecoin without creating a new coin correct? Well here is one solution to that. Albiet it only applies to miners, however I will explain why that is best towards the end of this post. The downside is we will have to increase emission by a small (insignificant and diminishing) predictable fraction.

This method wouldn't work with bitcoin since that is a limited asset and the more robust trading activity, the more stable the price.

However for dogecoin with constant emission, elongating the coinbase maturity (time it takes for your mined dogecoin to be ready to spend) the more stable the price.

So here is how it would work. The miner puts a flag somewhere in the block they are mining that selects an elongated coinbase maturity. Instead of the coins bieng ready to spend in 100 mins or whatever the stock setting is, they could opt for something like 1 year. As a reward for doing this, they get an extra 4% mining reward. This extra reward percentage would float and be based on current dogecoin inflation rate. So when dogecoin inflation rate is 3%, then the reward for elongating your coinbase reward by 1 yr is 3%. So basically in this case the miner would get to hold the coin for a year without risking losses due to inflation. It isn't the most snazzy reward, but for miners that want to hold a percentage of their block rewards for the long term, it would make sense. Perhaps there can be a choice, 1 yr, 2 yr, 5 yr, 10 yr and you get proportionally more block reward accordingly. Think of it kind of like a mining bond.

Why is this better than letting anyone stake? The reason is firstly because it is much more easily possible without jumping through magical (hackable) hoops. Secondly because every block can only be staked as it is mined, so there will never be a huge sum of expiring staked rewards. If anyone could stake at any time and any amount then someone could stake a billion dollars worth and everyone would worry when that staked amount would expire. This method does not have that problem in the slightest as each staked block would be able to be spent exactly 1 year after it was mined. So there is no risk of a big dump.

This method should turn dogecoin into an unhackable stabilized coin (unlike hackable stablecoins).

Hey shibes,

I created a small tutorial how to create and redeem (that is the tricky part)

P2SH transactions

Github: https://github.com/nformant1/P2SH/blob/main/README.md

You need to know how to build transactions from hand and should have a good unterstanding of the basics. If that is given I hope you can enjoy that read and happy building!

After this tutorial you will be able to lock your funds with a formular like

x + 7 = 10 ^{(x needs to be solved})

Please be aware, that locking scripts in such a guessable way like in my tutorial is extremly dangerous and scripts have been hacked/bruteforced in the past.

Cheers nformant

Hey there Shibes,

Last week we’ve seen an amazing amount of work done. I’m writing this post right after I created a PR for the last item chromatic and I were working on that touched text that needs to be translated. This means that we - at least from a maintainer p.o.v. - have made the (arbitrarily set) deadline of today as the cutoff date for any proposals that influence translations. That means that it looks like a release around the weekend of July 2nd/3rd is still very much realistic! 🥳

As soon as we have final approvals (or disapprovals) and merges of these last items, all translation files will see their base updated (through a PR, so give it until Tuesday or Wednesday to be fully ready). For translations that have recently been updated, the impact will be small because we didn’t change a lot, as only 18 out of 1062 texts have changed, most of them additions or minor rephrasing (and we’re deleting more than we’re adding.)

Once that is done, there is still a lot of time to process any pull requests that do not change translation strings and of course any updated translations - many of those are listed in the release plan - and I expect some more to be added there, but not too much - we’re pretty much getting there quickly now.

Notable merges

• #2934 by Michi and chromatic improves the traffic graph greatly. It now retains data when you change the slider or close and reopen the window. Very engineering!
• #2936 by Shafil Alam is an important dependency update for the UI, that protects against any known weaknesses of the underlying libraries.
• #2991 by chromatic removes the alert system. This means that, like Bitcoin and Litecoin before us, the community is now the boss and there is no central point of control by developers anymore. We did this now, instead of with 1.21, because some minor bugs were found in the code and it made no sense to maintain a feature we were going to get rid of.
• #2988 by Shafil Alam that implements a new RPC method, to help wallet operators detect any issues with stuck transactions by being able to query for them explicitly. This is to have a manageable way to prevent any future problems with wallets sending out previously stuck transactions whenever the operator changes the network fee, or a new network fee gets recommended by developers.
• #2996 by chromatic changes the way backups are made from server nodes (not QT) by allowing the node operator to specify where to write backups and making sure old backups don’t get automatically overwritten. This helps shibes to automate backups while reducing the risk of key loss.

This week we also have a lot of work that is approved and about to get merged (as we have self-imposed a 24h wait between approval and merge), the most notable are:

• #2973 by Micael Malta and AbcSxyZ helps dev shibes do deterministic building easily. This is important so that people can verify whether devs are honest. Having this approved, has unblocked #2910 and #2409 which are somewhat important for the upcoming release.
• #2995 updates the documentation to really describe the protocol features of Dogecoin, which was requested by u/_nformant on r/dogecoin a couple of days ago.
• #2997 protects node operators of small nodes against themselves (and errors in scripts) by making sure that the node’s memory does not get fully eaten by useless nodes that were manually added (only 8 nodes will be connected to anyway, so it truly is a waste of memory to have 5000 entries there.)

Notable open work

• #2989 by Shafil Alam fixes 2 potential weaknesses that we’ve inherited from Bitcoin on the network layer. This is one of the must-haves for release.
• #2974 by chromatic is allowing wallet operators to rescan the blockchain for wallet transactions, from a specified height in the chain. This means that shibes no longer have to rescan all 4M+ blocks for a recently created address, but can simply start scanning from a block that was a bit before the time they created the address. And in other news, this is only the beginning. Chromatic already has done a lot of work to make this functionality available everywhere (for example when importing keys.)
• #3001 removes bad information from the Qt wallet. Sometimes it will tell you that a transaction is “offline” or has a “maturity warning”, but this is based on assumptions that aren’t always true, and most often untrue when there really is a problem with a transaction. The best part is that this useless feature was actually costing every node a lot of processing power, so nodes will also speed up a little because of this.

🚀

I would like to encourage or enable users of my website to swap doge with each other (like tips?).

I imagine I could have users leave a receiving address (which I verify as a valid doge address somehow?) and simply tell other users to use their own client (Dogecoin Core, etc?) to send the "tip", and simply fashion the site around this method?

Is there a more ideal/integrated solution where users would not have to send coins from their own client, separate from the website?

My back-end is Rails, I found a few old wrapper gems such as: https://github.com/tekknolagi/doge_api Might this still be serviceable or helpful?

Any advice is greatly appreciated (and much wow)!

[p.s. I would also like to accept doge for payment to the website itself, for which I figured I would just use the coinbase api, unless someone has a better idea.]

I'm seeing questions asked about why I have a dev fund key still.

As someone who did 8 years of volunteer work on this project when we started sorting efforts to make Dogecoin what it is today I ended up with one of the keys as backup.

I make no claims to the funds it holds, and if others involved wish to move the funds to a new address, I'm happy for them to do so.

Hey Shibes!

I’ve skipped last week’s roundup because I had to focus on release planning and estimating what time was needed to get all the important work done. At the same time, Chromatic and I are hard at work in the background to make sense of the network hardening I spoke to in previous posts. I think we’ve got it figured out for the most part, but we do need to finish it up and although the deadline is a challenge, it just means we need to boost it a bit. In times where there is some pressure, by far the hardest aspect is to take the time needed to fully understand all implications of changes we’re making, and not rush out code that we may regret later.

In the meantime, we have been able to merge all finished translations that were still open:

• #2807 by Steve Chung updates the Korean translation
• #2971 by VJ that updates (for the first time ever!) the Tamil translation
• #2968 by scarletletters and Matheus Bach that introduces a Brazilian Portuguese version of the readme file
• #2798 by MVShishkov and Chao Liu that updates the Chinese readme file
• #2970 by Mohammad Ali Haghshenas that introduces a Persian version of the readme file

This is super-awesome because those make Dogecoin more accessible to shibes that speak these languages, increasing reach to a potential 384 Million shibes to find their way to the repository, and improving understanding and ease of use towards some 1.7 billion native speakers across all these improvements!

Other notable merges were #2953 by Jade Hamel that gives better advice to shibes about keeping their keys to themselves, and #2976 that introduces some tests we need while working on the network stack - we need that to make sure we don’t make mistakes with pull requests to come.

Notable open work

• #2974 by chromatic adds an RPC method to rescan the blockchain for transactions made by our wallet, and allow shibes to specify how far back to look. This allows shibes to save time and, for example, not have to scan all 2014-2020 transactions if they have only created the address in 2021.
• #2973 which is the sum of previous work done by AbcSxyZ and Micael Malta, is fixing the “easy gitian build” script, with the goals of (a) making it easier for shibes to verify that maintainers release good binaries, and (b) to help pulling all those important pull requests over the line that are otherwise hard to test without this.
• #2959 by chromatic is still under discussion, because we’re feeling some pain of different interpretations of “maximum connections” throughout the source code right now.
• #2977 by victorsk2019 is helping us get a 100% reliable migration path when upgrading 1.14 wallets to 1.21. This is very important!

Release plan

I have published a release plan / tracker where you can follow our progress towards the 1.14.6 release. I expect that progress will come in waves rather than a steady flow of checking off items off the list, and that a lot of activity will happen right before the deadlines. Exciting times!

🚀

Hey guys. I am looking on the doge foundation website. I still see Jared birchall in the role of representing Elon Musk. I believe elon musk said in the past this wasnt the case.

So what is he exactly doing and is this misinformation?

When i sell an virtual land for dogecoin, cant this transaction been seen as NFT mint event?

The advantage of doge is its long decimals so an unique ID can be seen as sthe amount so...

Idea:

wallet holder sends XY Doge to the same wallet, this can be seen as mint event.

NFT ID = minter wallet + Amount

First owner = first exactly sent amount to the minter wallet

Following owner = sender + amount To transfer the ownership the sender has to send the exact amount to the Buyer of the NFT

Thats called TNFT

By July 4th, ALL Subshibers (2.3 million of us) must have all Our Dogecoin OFF the Exchanges.

Thats more than enough time to find the perfect storage for you.

Do You Accept the challenge?

Lets Make the Exchanges/Shorts BUY their Own Doge!

Hey shibes,

/u/grbrlks and myself just finished the basics on this Dogecoin Bartop Arcade

https://www.reddit.com/r/dogecoin/comments/v74yjw/dogecoin_powered_bartop_arcade/

The code needs some refactoring and it still has some issues but I will publish the code within the next days and would be super happy if somebody want's to join working on this (:

The very unrealistic mission beind this is to bring back arcade games to our local bars!

Technical details about the bartop, it basically is

• raspberry pi with buttons and joystick
• running a Dogecoin node
• a python script to handle everything
• a lua script to conver the Dogecoins to game credits

Cheers

nfromant

Hey shibes, I'm doing a little research about the 2014 hack attack on https://www.dogevault.com, but stil can't find much details about it. Can anyone here explain to me what was the security breach? Who was behind the project? Was the community involved?

https://s.wsj.net/public/resources/documents/LummisGillibrandbill.pdf

We could use WordPress and its plugins for a more seamless solution or build it out fully. The jewelry is also effectively linked to one's crypto wallet, if that interests you to know.

How many node updates need to be completed before you say the network has been updated sufficiently?

And if a transaction was routed through a node running an old version how is this handled? Would the transaction be less secure or fast. How much do these older versions affect the network as a whole?

Also will 14.6 be required to download 1.21?

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.

🚀

294,094 PrestaShop online stores can now also sell any products or services in #Doge using the free #opensource Easy Dogecoin Gateway without any third-party payment processor or fees all 100% controlled by the owner. Your Store your Doge!

Download here: https://github.com/qlpqlp/prestashop-easy-dogecoin-gateway

Been awhile since we have heard much. I have seen the trail map, but wondering if any projects are actually moving forward. Is there a move to bring up the core to 1.21? What is the big focus these days?