• Leave the Old Digibyte Behind
• Improve Supply Chain Issues
• Community Understands Nothing

Josiah Spackman expressed:  This could also be THE chance we need, myself included, to leave that old digibyte behind. To be better! So, Jared Tate, I’ve been a bit of a dick. I’m sorry. I still want you to acknowledge the supply cap issue, but it’s not worth all of this. You especially can unite everyone.

Jared Tate Responds to Josiah Spackman:  I genuinely appreciate the redress, & I fully agree I could have been much better at communicating w/ everyone. I am sorry for not listening attentively & focusing. There are undoubtedly issues we all must address & work through. I truly wish us all unity to work together.

As for the supply cap issue, I have acknowledged it multiple times, however until we all have a full understanding of it as it is a multifaceted problem, it’s dishonest of me to say anything assertively publicly. Your own definition has changed multiple times, as have others.

First, the original timeline is off because of the relativity of time in computer systems. Calculations made in 2014 for when the final reward was to be made in 2035 are now off in 2021 because block timing has not been perfect for the past 7 years. It needs to be adjusted & accounted for.

2nd the rate of decay itself needs to be adjusted, calculated, and refined as a part of the current consensus. As well as a community agreed to set a date that rewards should be dropped to 0 like your proposed date of Dec of 2035.

3rd, We need to fully test a modified client to determine for sure if the subsidy bug code goes to 0 or 1 at the end. It looks like it stays at 1, but I have seen weirder unexpected things happen many times w/ a full client running in the wild. We have a good idea. Need full test.

4th part of the issue is how too hard cap the limit itself, which should not be a simple 1 line cap that can be removed and compiled by miners to bypass. It needs to be for sure intertwined in consensus/ decay & PoW.

5th, I have been working on a write-up for all this as it is a multifaceted challenge to address. But I haven’t had time with everything else going. It’s a very deep technical issue we need to address, and will address. But it takes time. We will get it fixed together.

Community Response:  You guys had me worried there for a bit. Thanks for showing the Community that we are Good People working towards a Good Common Goal. We might not be as popular and backed as Doge but let’s be Better and Stronger.

I wish I understood and can help, lol but just seeing you guys acknowledge we need to stay civil and work together and keep building is incredible. I’m so bullish on DigiBytes future! Thank you all for caring so much