<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Josiah Spackman on Medium]]></title>
        <description><![CDATA[Stories by Josiah Spackman on Medium]]></description>
        <link>https://medium.com/@josiah-digibyte?source=rss-714d4d4beb3e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0yV-Mg1HH-kkhr0BK4RUdQ.jpeg</url>
            <title>Stories by Josiah Spackman on Medium</title>
            <link>https://medium.com/@josiah-digibyte?source=rss-714d4d4beb3e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 07:31:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@josiah-digibyte/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[12 months and the core security of DigiByte still isn’t fixed]]></title>
            <link>https://josiah-digibyte.medium.com/12-months-and-the-core-security-of-digibyte-still-isnt-fixed-727d5f85f332?source=rss-714d4d4beb3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/727d5f85f332</guid>
            <category><![CDATA[digibyte]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Josiah Spackman]]></dc:creator>
            <pubDate>Tue, 28 Dec 2021 20:09:32 GMT</pubDate>
            <atom:updated>2021-12-28T21:20:45.441Z</atom:updated>
            <content:encoded><![CDATA[<p>Also known as “Did you know DigiByte can be rent-attacked?”</p><p>So, it’s time to share this document with everyone, which will hopefully explain why I’ve been so frustrated with, well, everybody… from the Founder, to the other “developers” (All of whom are noticeably absent from committing any code with the exception of Barry / Yoshi), the DigiByte Foundation who were in all the discussions, there were multiple members of the DigiByte Awareness Team, and also most of the DigiByte Alliance (though it wasn’t formed at that stage).</p><p>Yep, almost everybody who should have been deeply and proactively caring for the blockchain, and wanting to see things progress, see the security maintained, was there. They have known about this for 12 months now, since I made a video on ProgPoW / RandomX and I talked with them about it. Some knew prior to that given we had 1:1 talks, but this was the day the first real serious discussions took place aroud it.</p><p>But alas, here we are, 12 months on from when I first made the “Importance of ProgPoW / RandomX” video (365 days to the day):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jagQWI4jo9iDLzJ-3Ip92w.png" /></figure><p>Where I showed just what an issue SHA256 is for DigiByte:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s-cjUlXEuWahhPXcKNOM-A.png" /><figcaption>DigiByte had approx 0.06 to 0.07% of the global SHA256 hashrate at the time</figcaption></figure><p>This image directly shows the crux of the problem, and all the aforementioned were all made aware of this 365 days ago now. The little black blip, is the pixel representation of how much hashrate DigiByte has in SHA256, as opposed to the orange being worldwide available.</p><p>There’s something in the computer industry known as “responsible disclosure”. All you have to do is look at the likes of <a href="https://bitcoincore.org/en/2018/09/20/notice/">Bitcoin CVE-2018–17144</a> to see how rapidly they respond (A release with a fix is published in under 12 hours). This, despite being a multi-trillion dollar blockchain. Keep in mind there’s no hard-fork there for Bitcoin, but you get the picture.</p><p>The picture that something serious was disclosed, and a solution was already 95% ready with the work Barry had done that the community crowdfunded for, and it was discarded… roadblocked intentionally by Jared.</p><p>Now, many other places have responsible disclosure timeframes of 7 days (Linux kernel etc) for severe issues where you should give the vendor 7 days to fix the issue and release an update. That’s why it’s “responsible” disclosure. Others have 30 days. Not 365 days. Not a whole year!</p><p><strong>Please allow me to just reiterate here</strong>: <em>a blockchain should never rely on security through obscurity</em>. That’s a fundamental design flaw if it does and you should run a mile. Instead, it should rely on sound cryptographic principals, and in DigiBytes case solid irrefutable Proof of Work to determine who is the longest chain (It’s different for PoS but you get the picture).</p><p>Just as it was the last time Jared introduced a vulnerability in the difficulty code (from a mess of a merge he made pulling in BTC code no less), it wasn’t an issue until it was an issue and being exploited. Similarly, this isn’t an issue until it’s being exploited, which could be any moment.</p><p>You see, this isn’t just one lone-wolfs attempt at quickly getting GPU mining here for some selfish purpose as Jared has tried to portray over the past year, but rather, a twofold solution: 1/ To resolve this security issue that SHA256 in particular presents. 2/ Bringing back GPU mining to further decentralize and distribute the mining, of which the community as a whole crowdfunded on 3x separate occasions over the last 2.5-odd years.</p><p>Let that sink in for a moment, 2.5 years since Odocrypt! What has been done since on the Core codebase outside of the work Barry has done? Nothing.</p><p>Even Ethereum with its much higher market cap has done <a href="https://ethereum.org/en/history/">8x hard forks since then</a>. This upgrade <strong>is not </strong>the sort of thing that needs to take years, especially as the community clearly showed it was happy to fund this sort of upgrade. To suggest otherwise simply reeks of incompetence, or intentional deception.</p><p>Yes, all the DigiByte crowdfunding attempts were successful, and goals met. The 3x fundraisers were raised for ProgPoW, for RandomX, and for getting it all implemented in to 8.20 (which was the going version at the time).</p><p>In October 2019, we had Barrystyle working on all of the things we crowdfunded for, taking over ProgPoW from Kristy-Leigh Minehan. He got most of those items finished in just a few short weeks time (<a href="https://josiah-digibyte.medium.com/in-pursuit-of-gpu-mining-a-timeline-pre-odocrypt-digibyte-v8-186e9a499647">Full timeline here</a>). <strong>That’s what happens when a competent person is working full-time on things</strong>, and not Jared half-assing two days worth when he says he’ll focus 110% on the Core codebase and won’t do anything else until the upgrade is out.</p><p>In this completed work that Barry had done by December 2020 was: an implementation into the Core codebase of ProgPoW, an implementation of RandomX, stratum code for each algorithm respectively, major memory-use improvements, huge start-up optimizations, faster sync, and best of all it was based off the latest BTC Core and included those improvements as well.</p><p><strong><em>Again, the issue is not funding. We crowd funded, successfully!<br>The issue is not developers. We’d found someone who was willing to do it, who is incredibly talented, and who did all of that solo over a few short weeks.</em></strong></p><p>To bring up a point by GTO90 and Gary, they had both previously expressed an interest in ensuring the code was well reviewed &amp; tested, not rushed at all, with which I wholeheartedly agree(d). There was never any doubt that would happen, and in addition to writing a whole lot of manual testing procedures I’ve also helped spearhead the release of 7.17.3 which includes fully operational unit-tests. However the suggestion from GTO90 &amp; Gary that they want a codebase to be reviewed is pretty ironic given we’re 12 months down the line now with a different codebase that isn’t going to be, nor is it able to be, reviewed. It’s a monolithic mess of a merge that is genuinely impossible to code-review.</p><p>You do not wear the “We changed several hundred thousand lines of code” as a badge of honor. That sounds like several hundred thousand ways a merge could have been messed up, and a major vulnerability introduced that directly affects the security blockchain, as Jared has done in the past.</p><p>But back to the topic at hand. In 2019 there were talks about furthering decentralization of DigiByte. Talks of improving the security. Talks of lowering the onboarding of users through GPU / CPU mining so that people can obtain DGB in a KYC-free manner. Talks of improving the security and resolving the issues. Talks of improving the distribution of the DigiByte asset. Talks of a faster, more secure, forward-thinking DigiByte, implementing ProgPoW, another CPU algorithm, and something further. Those talks continued many times over since.</p><p>To some of us, we acted on those talks and did all we can to progress things and bring about the security improvements, raising funds for it, working with developers to bring it to bear, educational and informational videos and content about the benefits and the need for it.</p><p>To others, they were just talks which to this day have not been progressed on.</p><p>So, it’s been a year, and the way I see it there are two possibilities right now based on what I’m alleging:</p><p>1There’s not any security issue, everything is fine and the blockchain is perfectly secure. In which case, releasing this document isn’t actually an issue. It’ll be easily debunked, I’ll eat humble pie, gravely and repeatedly apologize for the misunderstanding, and never say anything about DigiByte ever again.</p><p>2 It is actually an issue, and those involved have done absolutely nothing. Even worse, they’ve actively stood in the way and roadblocked progress that would secure the blockchain. In which case, they’ve been the worlds worst stewards of the blockchain and need to be called out for it so they can be sidestepped, the Founder included. Because 12 months and zero progress is atrocious and completely unacceptable.</p><p>Which one that is, you can do the numbers on, it’s not difficult.</p><p>I was asked originally in February of this year to make this document as a way to help explain the issue to the other members of the Foundation / Alliance / DGBAT. So I made it for them the very next day. They wanted something that was impartial, that just focused on IF there is an issue, which is why a lot of the phrasing is incredibly generic. There was no finger-pointing, no blame, and yet here we are 10 months later since this document was made and still no solution in sight.</p><p>The numbers may be slightly off now given the timeframe, but you’ll see in the document (despite Jareds numerous misguided slander attempts) that it contains some hard numbers for you to work with.</p><p>At last check on whattomine, I saw DigiByte hadd 72PH/s in SHA256, vs Bitcoins 174,621PH/s. Keep in mind you can rent 631PH/s right now on NiceHash alone. So when he throws out ridiculous statements like “We need hard data”, I’m sure you as an astute reader know by now based on Jareds history to take that with a grain of salt, because as we’ve seen countless times even over the last 12 months, he’ll outright ignore any data that doesn’t support his ignorance (as Jared did with the infinite supply):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*Ybgmu9Lv1Iwu74yOvfVLFA.png" /></figure><p>With that in mind, here it is for you to review, with the exchange details redacted. Keep in mind this: The hashrate needed to get blocks doubles ever 5 consecutive blocks.</p><p>This means if you start with “1” hash per second, you’d need 2 per second to ensure you’re going to be finding the next blocks, then 4 per-second to ensure you get 5 in a row, 8 per-second if you want to ensure you get 10 in a row, or if you can find 16 hashes per-second then you’ll get 15 in a row. <strong>With one algorithm.</strong> Adding a second algorithm greatly reduces the hashrate needed.</p><iframe src="https://drive.google.com/viewerng/viewer?url=https%3A//dgbwiki.com/AlgoProposal-Redacted.pdf&amp;embedded=true" width="600" height="780" frameborder="0" scrolling="no"><a href="https://medium.com/media/cce52841121fdf0478728c7f69178ad3/href">https://medium.com/media/cce52841121fdf0478728c7f69178ad3/href</a></iframe><p>This was shared in February as I mentioned. It’s now December, and nothing has happened to address it. So if it was *actually* an issue, if security was at stake as I allege it is, then you’d think they would have acted on it over the past 10 months (365 days from the video when we first truly discussed it in-depth).</p><p>Again, please take the numbers in the document with a grain of salt, naturally they change over time, they go up and down and I don’t expect them to be 100% accurate for December 29th 2021… However in fact they’ve now gotten worse if you ask me.</p><p>Where DGB was previously 0.07% of all the worldwide SHA256, it now makes up ~0.04%. From what I can see, renting all the SHA256 hashrate on NiceHash alone could get 10+ odd blocks reorged, without even looking at including Scrypt which would significantly increase the number of blocks.</p><p>The real difficulty here is that Jared still doesn’t understand how MultiShield works. He didn’t write it, MentalCollatz did, and as seen from these chats I had with Jared back in May discussing this, he misguidedly believes if the hashrate available to rent by an attacker is halved, that you halve the blocks. That’s wrong, you only lose the tail end, as the difficulty is what “ramps up” effectively:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/0*vnxar1QpyIRK_CYl" /><figcaption>He’s also dumb enough to think he can see a double-spend attempt happening before it does</figcaption></figure><p>Which is why it’s time to share that document today, because apparently there’s no issue whatsoever!</p><p>Allegedly (according to him at least) all my math and numbers are all totally wrong. So according to the DigiByte Founders reasoning, then it shouldn’t matter if I share the document given there’s no issue at all right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/556/1*GvAVPJQ6lxsWTp0RprU2Tg.png" /><figcaption>His math is askew, as is his understanding of how double-spends work</figcaption></figure><p>He asked for the data that I provided in the document:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/1*I02qvKbQZ5l4E3QI6AlHLA.png" /><figcaption>Hard data seems a reasonable ask? In fact, the example is in the document</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*zmDEMLEZY30mWCCr0HcEDw.png" /><figcaption>And this is where it breaks down, he’s delusional. Also, this hasn’t tapped 6 months energy, he’s so full of shit</figcaption></figure><p>So DigiByte community: Jared, the Foundation, the Alliance, DGBAT members, they’ve all known for 12 months now about what I allege is actually a serious enough issue that it should be acted on immediately. Yet, there is no solution in sight at all.</p><p>Development only happens when Barry does something (he was still further on his 8.20 in December 2020, than Jareds merge is this year that Barry / Yoshi have been cleaning up). There’s been zero discussion around any form of resolution for this outside of that which I instigated earlier this year.</p><p>But you wait, Jared will run some twitter poll tomorrow about Algo upgrades, and then promptly forget about the results, which is what he always does.</p><p>So if Jared is right about these numbers of mine being totally off, then cool, me sharing this is only going to put egg on my face.</p><p>If he’s wrong, and the numbers check out, then I hope this motivates some actual action because he has been pathetically absent while virtue-signalling and posturing as being “busy working on DigiByte” on a daily basis.</p><p>Just remember: Every 5 blocks the hashrate needed for a single-algo attack doubles. That’s something Jared can’t wrap his head around for some reason (as seen above in the screenshots). Not to mention, the difficulty of carrying out an attack <em>decreases significantly</em> if you have more than one algorithm.</p><p>So take a read of the document, it’s really just some basic multiplication using numbers from whattomine and the NiceHash marketplace to verify.</p><p>Good luck, DigiByte community. I hope that this is either the end of any further comment from myself about DigiByte if I retreat with apologies and egg on my face from being wrong about the numbers. Or, that you use this as the motivation to overthrow your tyrannical founder from his current centralized positions of power, side-stepping his roadblocks and finally getting some true progress! After all, that’s why the Dev process was made right? So that the project could be improved? So that code could be reviewed, thoroughly, before being accepted? Coz that sure as hell hasn’t happened to date with that mess of a merge that he’s been loosely involved in since July.</p><p>Again, like I’ve said all along: A rebase is the way, with ProgPoW, RandomX, and an upgraded Odocrypt. You can even include the three-line fix I wrote for the infinite supply issue 6 months ago.</p><p><strong><em>This doesn’t need to take years</em></strong> (as has been the case), it could easily be finished in just a couple of weeks with some actual dedicated time put into it. Remember, Ethereum being a multi billion dollar chain has done 8x upgrades in the last 2.5 years. If funding is an issue, go crowdfund, it’s been done it before! I just so happen to know of a few really good devs (*cough* Barry / Yoshi *cough*) who could possibly be funded to code and then review the work.</p><p>The choice… is yours!</p><p>But if my math is off, please do let me know because so far none of the aforementioned parties have been able to say-so.</p><p><strong>Final note</strong>: To date, we don’t have concrete evidence of any ASICs on Odocrypt. The last two known mining pools that joined in Q2 of 2021 are based out of China and are using BlackMiner F1+ FPGAs, one of which currently as of December accounts for approx 25% of the hashrate. However, that didn’t stop me and others (Barrystyle, mctrivia etc) from proactively looking at ways we could ensure there aren’t ASICs by replacing the Keccak in Odocrypt back in December last year / January this year. That PR has sat there, with no real action from the “main” developers, also since January.</p><p><strong>EDIT:</strong> Someone has asked if an increase in price will solve things. This point is addressed in the document itself, and the short answer is no.</p><p>Despite what others might suggest, a temporary Pump &amp; Dump does <strong>not</strong> make for good security:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*6YHzKquoKscf0Cx6mKlHGA.png" /></figure><p>Especially when you look on CoinGecko and see it’s down almost 80%:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/399/1*QqE_airvWFZMm3Tw2oXufg.png" /></figure><p>No, a real solution would be to fix the problem, not hope for a price-pump to band-aid over the issue.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=727d5f85f332" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maintaining the security of DigiByte]]></title>
            <link>https://josiah-digibyte.medium.com/maintaining-the-security-of-digibyte-b8cb18e35551?source=rss-714d4d4beb3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8cb18e35551</guid>
            <category><![CDATA[digibyte]]></category>
            <dc:creator><![CDATA[Josiah Spackman]]></dc:creator>
            <pubDate>Wed, 24 Nov 2021 23:58:57 GMT</pubDate>
            <atom:updated>2021-11-24T23:59:49.645Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s now a year since Barry had all but finished DigiByte Core 8.21 code (Dec ‘20). This includes ProgPoW and RandomX, along with other actual feature &amp; performance improvements. The genuine progress, and how to get there, is what this post is about.</p><p><em>(This was originally written 5+ months ago but never published, I’ve now updated it and finally gotten around to getting it out there for the world)</em></p><p>Contrast that to the ongoing delays we’ve seen with the alleged “DigiByte 8.22” from Jared, which in reality is not even a “7.22” given it’s got no actual improvements and none of the code for the fork / upgrade. In fact, it’s gone backwards, and they’ve removed Dandelion at the moment.</p><p>It’s also been pretty unfortunate to see that the improved development process of DigiByte has been co-opted. Where the intentions were to ensure all code was thoroughly reviewed (not just “does it run”), it’s now become as bad as it ever was. So I want to give you a little history into some of the previous fails, and provide you with the answers you need for <strong>a solution to ensure they don’t happen again</strong>.</p><p>This can be summarized with: <strong><em>Big merges are bad, rebases should be the defacto process.</em></strong></p><p><strong>Side note</strong>: Some of this didn’t make it into <a href="https://www.amazon.com/BLACK-WHITE-INTERIOR-DigiByte-Introductory/dp/B09FSCF2CQ/">the History of DigiByte book</a>, but you should go and support Chris and pick up a copy of this coz it’s a pretty good read.</p><p>Hopefully I can explain all of this with minimal images, but in a simple way that somebody with even just basic knowledge of blockchain / DigiByte can understand.</p><h3>How does a merge differ from a rebase?</h3><p>I’m glad you asked because that underpins a lot of this!</p><p>A merge is where you take all of the code changes that have happened from upstream Bitcoin, and apply them all to DigiByte. Where Bitcoin changes the name of a file, or moves some code from one file to another, or refactors certain parts of it, those changes then get laid over the top of DigiByte.</p><p>Sounds straight-forward enough, except it’s not.</p><p>Merges are great if you’re doing smaller or more isolated changes. For example if you’re working on RandomX and I’m working on ProgPoW, but we both make changes to the way the consensus will be activated, it’s easy to look at it and go “Ah yeah we should actually do this slightly differently to accomodate both of what we’re trying to accomplish”.</p><p>However when you’re merging the code from hundreds of thousands of commits, each commit could possibly break things if not carefully reviewed in the context for which it was intended at the time. It becomes a nightmare to have someone else review those changes afterwards too.</p><p>Rebasing though, is different, more streamlined.</p><p>You take a “known good” starting point (Bitcoin Core) and apply JUST the changes needed to make DigiByte “DigiByte”, leaving behind all the stale / unused code.</p><p>You’ve probably seen the drum being beaten about DigiShield, how it was the greatest thing since sliced bread, and MultiShield too now for MultiAlgo. You’d be forgiven for thinking it’s tens of thousands of lines of code. You know how many it is?</p><p>A thousand?</p><p>A hundred?</p><p>A dozen?</p><p>Less!</p><p>In fact, the Ethereum difficulty adjustment code was just a single line:</p><blockquote>block_diff = parent_diff + parent_diff // 2048 * max(1 — (block_timestamp — parent_timestamp) // 10, -99) + int(2**((block.number // 100000) — 2))</blockquote><p><em>(It wrapped though here on Medium, coz it’s a long line)</em></p><p>So when you talk about a rebase bringing across DigiShield (which it has to do because it needs to validate the older blocks), we’re bringing across just a couple of lines. MultiShield isn’t even a dozen.</p><p>Rebasing is what Litecoin was doing too. They would take Bitcoin, add in Scrypt, change the max supply / supply emissions / block timing, and that’s basically it. Thrasher- churned out the last Litecoin Core in 2020 in what looks like less than two days worth of effort. What a champion!</p><p>That’s the way DigiByte should be proceeding too.</p><h3>So why is merging bad then?</h3><p>Well, because so much fluff gets left in for starters, but also because it’s going to be <strong>impossible </strong>to review the code. Things can get slipped in there, intentionally or inadvertently, which you naturally don’t want.</p><p>Let me explain, with some historical examples:</p><h4>DigiSpeed code removed</h4><p>When DigiByte merged in the code from BTC Core in 2017, the SegWit code broke DigiSpeed block size doubling. As such, that block size increase code was removed.</p><p>The reason?</p><p>SegWit changes block “max size” to “ max weight”, and by Jareds own admission at the time they didn’t fully understand how that worked, nor how it interacted with DigiSpeed (because DigiSpeed increased the block max size, not the max weight).</p><p>It would have been simple enough to adjust that block max-size to max-weight but because of the myriad of changes happening as part of the merge, when the SegWit code came up for merging it was a case of “Hmm dunno what this does, let’s just bring it in and we’ll fix what breaks later”. Which happened. The max block size code, despite being unused, was still there until I removed it cleaning things up a little back in 2019.</p><p>That’s part of what I mean about historical “fluff” being left there, which can in time cause bugs, security issues and more.</p><h4>Double spends on DigiByte</h4><p>I’ve <a href="https://josiah-digibyte.medium.com/in-pursuit-of-gpu-mining-a-timeline-pre-odocrypt-digibyte-v8-186e9a499647">talked about this before</a> in depth (at the end of the article), but it needs repeating:</p><p><strong><em>Jared merging BTC code caused the DigiByte double spends of 2018</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/1*iERjtIIzDAAN8Qo-AhjNLw.png" /><figcaption>Jared sent me this screenshot, he was the green, and the person reporting the security issue was in white on the left.</figcaption></figure><p>It’s just another reason why merges are less than ideal, given it broke the way that MultiAlgo looked at the weighting of SHA256. The <a href="https://github.com/digibyte/digibyte/commit/96fa4e56">merge was done in 2017</a>, but it wasn’t exploited until 2018.</p><p>This wasn’t just one double spend either, to my knowledge it occurred 16x over the course of several weeks, hitting several exchanges:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SLZQ7IFnk-mpEq_ysoh17g.png" /><figcaption>DigiByte Orphan chart from 2018 when the double spends were happening</figcaption></figure><p>Yes, that’s right:<em> Jared merging code caused over a dozen major double-spends on DigiByte</em>. But he still wants to proceed with merging as a plan?</p><p>These double spends are yet another reason why merges are bad. Bringing in that code on-top of DigiBytes effectively overrode the MultiShield code. Rebasing wouldn’t have had that issue given you apply the DigiByte changes on top of the Bitcoin code, ensuring you have brought across what you need in the codebase.</p><p>The crazy thing? This was an earlier merge from 2017. More code merges had been done since, and it had been in there the whole time.</p><h4>Code can easily be slipped through when merging</h4><p>Unless somebody is looking over <strong><em>every single line of code</em></strong>, and vetting it thoroughly, you can slip through a LOT of things. It might not be malicious, it may be inadvertent issues that get through, but it can still happen.</p><p>In fact that was how the fix for the aforementioned double spends went through: As part of a large merge, to hide it, so people didn’t see it!</p><p>Knowing nobody would review the code (Because frankly nobody could) for a big merge, the code for the double spend fix was included in an attempt to get it incorporated and keep it all on the down-low. This is why anybody trying to tell you (<em>*cough*</em> <strong>Jared</strong> <em>*cough*</em>) that all the code from a merge will be reviewed, is lying to you.</p><p>This is <a href="https://github.com/digibyte/digibyte/commit/8feb18dc0a028adfad361034388dfec31c093c7c">the merge that was done pulling BTC Core 0.16.2</a>, and included in it is the fix for the double spend issues. Did you know it was in there?</p><p>I bet you didn’t, because even by the time you get to see it on GitHub it doesn’t show you it by default because of the size of the code merge:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z_dHZt6LzbFt4q55egNW8w.png" /><figcaption>GitHub won’t show you the file by default, the merge was too big to even show on your PC</figcaption></figure><p>But it was in there!</p><p>Now imagine if somebody wanted to slip in something malicious, given there’s hundreds of thousands of lines changed, how would you ever know?</p><p>Or what if it was an accident that caused some other major security issue, how would you ever know?</p><h4>Inability to import older wallets</h4><p>Merging also broke the ability to restore wallets with private keys from the earlier 2014 days of DigiByte!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/731/1*mWdnpHNFWvcSgqy-Fmi5qg.png" /><figcaption>Couldn’t import the older private keys</figcaption></figure><p>Yep, if you had your private keys from being an early DigiByte supporter, restoring those keys wouldn’t work in 6.16.2, the fix for that came in 6.16.3.</p><p>Yay chalk up another win for merging.</p><h4>Broke fresh blockchain syncing</h4><p>Yep, did you know that when 6.16.5 was released, further code from upstream was merged which broke the ability for DigiByte to sync from scratch?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*PeP4-Og1cgjIaQeg9BOQ_Q.png" /><figcaption>Release of 6.16.5.1 fixed the new client sync issue</figcaption></figure><p>Yep, the testing was great on that one… rather than just adding the one-line fix to prevent the crash from duplicate inputs, code was merged, and it <a href="https://github.com/digibyte/digibyte/commit/c6f84cc483db91583ede41c090dad29534e91b42">broke the ability to sync DigiByte from scratch</a> for two whole days until the new release was pushed out. It was fine if you were upgrading, but you couldn’t delete your blocks directory and start a sync from the beginning of the blockchain, it just wouldn’t work!</p><p>Again that’s far less likely to have occurred with a rebase (not to mention some half-decent testing).</p><p>Thanks to Murat who found and reported that issue back in the day 🥰</p><h3>So why do Jared and GTO90 insist on a merge?</h3><p>I genuinely don’t know. It’s completely asinine at this point.</p><p>I’ve clearly shown a myriad of issues that have all stemmed from merging BTC Core code, one of which literally resulted in the blockchain being exploited and double spent on for several weeks. Who knows what else may be hiding there from a previous merge? You can go and view and verify these things I’ve asserted for yourself too, they’re even talked about in the <a href="https://github.com/digibyte/digibyte/releases">Release Notes of DigiByte</a> too.</p><p>There is no good reason at this stage for the merge to continue, especially given <a href="https://github.com/digibyte-project/digibyte-rebase">Barry had shown a rebase can be done</a>. <strong>It’s now 12 months since the 8.21 rebase was all but completed (Dec ‘20).</strong></p><p><strong>TWELVE MONTHS!</strong></p><p>This merge drama from Jared has been a complete sideshow, just so that his ego doesn’t get bruised, because he’d become and still is irrelevant.</p><p>What work has been done on the merge in July this year, when Jared said he was giving 110%, was actually mostly Yoshis work (thanks Yoshi!). Yoshi too has previously stated he’d be fully onboard with a rebase.</p><p>Plus, that merge work done on 8.22 is realistically still a 7.22 because there’s no other fork upgrades / improvements, no algo swaps, nothing.</p><h3>Will a rebase really solve these issues though?</h3><p>Great question, and I’ll ask you another in return before answering:</p><p><strong>What was the point of changing the development process?</strong></p><blockquote>It was to get ALL the code thoroughly reviewed before it was accepted.</blockquote><p>There is not a chance in hell of that happening with that merge. Jared would sooner denounce his conspiracy theories, than that code has of getting reviewed line-by-line.</p><p>A rebase on the other hand, means there’s significantly less to review and less to break. At worst, you’d be bringing across earlier “unknown” issues, but there’s way less chance of bringing in new ones.</p><p>In fact, the DigiByte repository shouldn’t have the full BTC Core code there, it doesn’t need it. Ideally it would be a set of build-scripts that simply applies the DigiByte changes on-top of Bitcoin Core at build-time.</p><h4>Sounds scary, how the heck would that work?</h4><p>It’s pretty straight-forward actually:</p><p>99% of the code in that repository is still Bitcoin (excluding the hashing algo libraries).</p><p>Take Bitcoin Core (let’s say 0.22) and use that as a base. However, rather than having a monolithic set of code in DigiByte repository, ideally it would only have the changes to Bitcoin needed to make DigiByte “DigiByte”, such as the changes to the maximum supply, algo changes etc</p><p>Those could be applied, as a series of patches during the build process. The libraries pulled (such as for Keccak, used in Odocrypt) would be pulled as a whole file, untouched, and can be hashed against earlier versions to see that no changes have been made.</p><p>You could even save those file hashes to the DigiByte blockchain so that people can see the hashes in perpituity for those files to ensure they haven’t been changed.</p><p>What DigiByte would be left with is a far, far smaller set of changes. It would be an infinitely more easily reviewable codebase, and it would be significantly simpler to upgrade things in the future to base off a new version of BTC Core too. The DigiByte “changes” would be packaged up nice and neatly so they could be reviewed, without having to go through all of the hundreds of thousands of changes that BTC Core have already done and reviewed themselves.</p><p>Barry even <a href="https://github.com/digibyte-project/digibyte-rebase">started on this back in July</a>, pulling most of the hard yards already. It would take far less to get that ready to roll than it would to finish the 8.22 (7.22) merge. <a href="https://github.com/digibyte-project/digibyte-rebase/commits/develop">It’s already far closer to what Litecoins rebase commits look like too</a>!</p><p>There would be further effort needed to fully segregate the DigiByte code from Bitcoin, and optimize it for in the future, but it would make DigiByte improvements SIGNIFICANTLY simpler in the future because there’s no wondering “Is this something Bitcoin related I’m changing? Or am I changing DigiByte?”. Not to mention it will still be less work than the merge has been, or still needs, and it would be able to be reviewed.</p><p>The <a href="https://github.com/digibyte-project/digibyte-rebase/blob/develop/src/crypto/KeccakP-800-SnP.h">files for things like Keccak</a> can be <a href="https://github.com/digibyte-core/digibyte/blob/develop/src/crypto/KeccakP-800-SnP.h">compared against existing ones</a> (Looks the same to me) automatically too with a build-script to ensure they’ve not changed, removing 99% of the effort as well.</p><h3>So what’s the way forward?</h3><p>Demand better.</p><p>Don’t settle for the lies Jared keeps shilling on Gitter and Telegram.</p><p>Demand that the Foundation and DGBAT members who have stood by and watched this all since January actually step up and step in. Rudy, Hans, Rutger, they were all there in the chat watching when Jared torpedo the development in January, and they stood by idly. Time those Core Values of the Foundation were put to use. I point blank told them to get a 3rd party opinion, they didn’t, and opted to blindly follow Jared who has let them down again.</p><p>The DigiByteCoin Twitter account that dgb_ycagel primarily runs, needs to stop sharing Jareds nonsense and giving the community the false impression that Jared is still involved. Throw down the gauntlet, and if Jared throws a wobbly (haha that’s never happened before has it?) then move on and start a new DigiByte twitter account that he isn’t pulling the strings on.</p><p><strong><em>Jared’s been absent from the project for the years</em></strong>, simply giving the illusion of involvement.</p><p>Nobody can tell me anything over the last 3 (nearly 4) years he’s actually done. <strong>Why</strong>?</p><p>Because even when it came to 7.17.2 and Odocrypt, he wasn’t really even involved back then in 2019. I was helping him setup his Cyclone-V FPGA prior to the countdown livestream that took place, just 30 minutes before the algo upgrade was due to be activated (It was already locked-in) and he still had no idea how it worked!</p><p>Build a better future, without having him pulling the project down. Without him getting it delisted from the likes of Poloniex, or hamstringing the Binance listing progress.</p><p>Ever stopped to wonder about why Coinbase hasn’t listed DigiByte?</p><p>I wonder if it’s because of the history of merge issues, and the code can’t be reviewed? Or maybe it’s because of Jared, as it was for Binance? I don’t know for certain, but it’s not that far-fetched is it?</p><p><strong>But you can do this community!</strong> I believe in you.</p><p>Just to clarify though: I don’t want to have access to any of this. I won’t be pushing it (I’m actually working full-time on a non-crypto business now sorry), but for all those who’ve reached out to me asking about the way forward that will ensure the <em>security of the blockchain</em>, ensure that the code is reviewed and is more maintainable in the future: That’s how you do it. You don’t do it with the merge. It’s impossible to review it.</p><p>The question is: <strong><em>will the DigiByte community settle</em></strong>?</p><p>Or will the “<em>faster, more secure, forward thinking</em>…” mantra finally come back to life?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8cb18e35551" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DigiByte accomplishments over the last 3 years]]></title>
            <link>https://josiah-digibyte.medium.com/digibyte-accomplishments-over-the-last-3-years-76d3c1e94693?source=rss-714d4d4beb3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/76d3c1e94693</guid>
            <category><![CDATA[digibyte]]></category>
            <dc:creator><![CDATA[Josiah Spackman]]></dc:creator>
            <pubDate>Wed, 11 Aug 2021 07:46:56 GMT</pubDate>
            <atom:updated>2021-12-27T22:38:52.407Z</atom:updated>
            <content:encoded><![CDATA[<p>Talking with my wife, and she made a suggestion: Why not finish your time with DigiByte with more of a “celebration” of what you’ve done?</p><p>So, that’s what this is, a bit of a look at some of the main things I’ve been involved with, directly pushing forward or making happen.</p><p>It’s also a great opportunity to look back over the last 3 years and see just how far DigiByte has come! So that’s what this is, an ode to success, if you will! 🙂 It’s not a complete list of all the contributions I’ve made, but it’s something!</p><h4>DigiByte Infopaper (like a whitepaper, but not)</h4><p>Back in November 2019 I began to write the DigiByte Infopaper. I finished writing most of it over a few days between Christmas / New Years. Jared got wind, asked me to stop, until he’d released his book which he wanted to base the infopaper off.</p><iframe src="https://drive.google.com/viewerng/viewer?url=https%3A//digibyte.org/docs/infopaper.pdf&amp;embedded=true" width="600" height="780" frameborder="0" scrolling="no"><a href="https://medium.com/media/240ce0ce1bd6aebf2c09efc3627ad4c9/href">https://medium.com/media/240ce0ce1bd6aebf2c09efc3627ad4c9/href</a></iframe><p>12 months later and he was still nowhere to be seen and the finish of his book nowhere in-sight, so I tidied it up with the help of a few friends, and Nigel / Demi spruced up the look of it giving us what we have today.</p><p>This is hosted on the DigiByte website:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Js33fPwRrV8W2YXThLl5yg.png" /></figure><p>And it’s a fantastic introduction for people into DigiByte, along with an abbreviated history, and a look into the future.</p><h4>Over 500 videos / interviews</h4><p>I want to start by thanking all those who followed me on YouTube:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XifK4ZbNgFzdGS98V7CFiw.png" /></figure><p>Although not all that I participated in ended up on my own channel (A good number, at least one a week, were me being a guest speaker on others channels talking about DigiByte), I started a DigiByte-related podcast, did over 250 update videos, and was interviewed countless times. All up totalling over 500 across the last couple of years. What started as a friend simply suggesting I step up and fill the void in 2019 became a near daily occurrence keeping people updated with what was going on.</p><h4>CreateDigiAssets, DigiAssetDividends &amp; DGBData</h4><p>When DigiAssets were announced at the DigiByte Summit, they were still unable to be issued by the general populace.</p><p>Gary (DigiContributor, not to be confused with Barry) had issued the first assets that were used there with DigiVault that he was working on, an application which tied directly in to the Core Wallet. That was never finalized and released properly and wouldn’t sync right. Then, support was partially added to DigiByte Go, but that was never finalized either and the DigiByte Go wallet ended up being abandoned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iOEiPmPChAmGFrz4lIAvFQ.png" /><figcaption>CreateDigiAssets, SUPER simple</figcaption></figure><p>So we’d been told “Here’s DigiAssets, it’s amazing, go use it”, but there was no way for normal people to <em>actually </em>use it and issue assets.</p><p>So I took a small bank loan and paid a developer privately to make the CreateDigiAssets.com website, which allows people to easily issue assets NFTs on top of DigiByte (for a small ~$5 fee which goes back towards paying off that loan).</p><p>It’s grown a bit since, we’ve added animated images, and video support too (Also to the mobile wallets as a result of this website), but this was something that was a HUGE hole in the DigiByte ecosystem that needed filling.</p><p>I also paid someone privately to create the DigiAssetDividends.com website which allows people to issue dividends to DigiAsset holders in a fast and easy manner. Again another huge hole in the DigiAsset ecosystem.</p><p>Lastly I also personally funded the creation of the DGBData.me website to allow people to store a hash on the blockchain quickly and easily. It’s a very simple manner of confirming a document has not been tampered with, since X time etc and works really well.</p><h4>Bounties for mobile SPV wallet</h4><p>This was how we found Yoshi, with him claiming some bounties for fixing the SPV sync issues (where it was stalling previously). He also updated the iOS wallet for us too in many ways, and later began doing a lot of work on Core too.</p><p>I fundraised / crowd sourced when nobody else would (I don’t believe anybody outside of the DGBAT overall have done crowdsourcing / raises in the last few years). We posted some bounties to help get a few showstoppers finished + fixed, and it’s why we have the apps today.</p><h4>Mobile UI redesign contest</h4><p>We had a HUGE turnout of people submitting designs for Android &amp; iOS wallets. It was absolutely fantastic, and we were able to do a “knock-out” voting style. The bounties raised were all distributed to the winner + runner-ups and the mobile apps got a great UI overhaul as a result that made it really stand out.</p><p>The winner, Damir, would go on to help with Digi-ID logo / website, some demonstration icons for use with DigiAssets, the DigiAssets logo, and was involved to begin with in the new logo proposal that spiral later would make for DigiByte.</p><p>Thanks again to Yoshi and Noah for the implementation of the UI redesign.</p><h4>DigiFacts</h4><p>I wrote a list of over 70 easily shareable “facts” about DigiByte that would encourage others to start sharing details on social media etc</p><p>Then I asked a friend through Telegram to create nice images from these facts (see more at <a href="https://github.com/digibyte-core/digifacts">https://github.com/digibyte-core/digifacts</a>):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1K5vXQrm8sALn90j.jpg" /></figure><p><em>Fun fact</em>, one of them originally said we were early adopters of the ProgPoW algorithm because work was underway with it, but that was replaced before being shared on social media due to it being torpedoed by the Founder. You can still see it in the GitHub history.</p><p>Update: As of October 2021 these are now all being re-shared for a second time by DigiByteCoin on Twitter, just without the images (so they’re less effective at grabbing attention)?</p><h4>iOS App Store listing</h4><p>One of the main struggles was we got the Android app submitted to the Google Play store, but despite GTO90’s best efforts he’d been unable to get the iOS app accepted. I had to create a business here in New Zealand specifically for this! I then registered it with the New Zealand Companies Office, obtained a DUNS and more… then after a bit of back and forth arguing with Apple, I finally got the iOS app listed on the App Store as a result!</p><h4>Binance listing</h4><p>Ever since early 2018, I was submitting listing requests for Binance. These are no small feat, they’re massive listing requests, often 30-odd pages in length. As the listing requirements changed, each time I would fill it out again. 5x in total in fact!</p><p>I can’t claim sole responsibility for this though, as we still don’t know specifically why Binance listed DigiByte, but DigiByte was finally listed in 2020 a couple of weeks after Jared made an announcement he was not going to be involved with the DigiByte project.</p><h4>Digi-ID front &amp; center</h4><p>One of the things I pushed for in 2018 was for Digi-ID to be brought into the spotlight as it was basically invisible in the apps.</p><p>Now, the Android &amp; iOS apps have Digi-ID front-and-center, and we had a few plugins created for things like Wordpress, WHMCS etc.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FoRGq1-WvQOQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DoRGq1-WvQOQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FoRGq1-WvQOQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4069e3ac522bddec91316bb53a7d2162/href">https://medium.com/media/4069e3ac522bddec91316bb53a7d2162/href</a></iframe><p>I’ve also authored the <a href="https://www.digi-id.io/">Digi-ID.io</a> website with Damir, to help introduce people to Digi-ID. Another great success!</p><h4>Translations in mobile</h4><p>Although this was something I was pushing, and setup / got started with POEditor, a lot of other people were actually involved. Hundreds of people in fact.</p><p>But, this was something I was passionate about us having, along with Rutger, Murat, Nigel and especially Glenn, we now have DigiByte in 50+ languages covering close to 99% of the worlds population!</p><p>Huge shout-out to those gentlemen for all their massive effort involved.</p><h4>Donations to David Hay / Venezuela</h4><p>We managed to raise several thousand US dollars which was amazing, and we gave thousands of bottles of water to the red cross who distributed it to people crossing the border.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FjMVFx8hW7no%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DjMVFx8hW7no&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FjMVFx8hW7no%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d07b42ed3d5e20031ddd33a04dfa4914/href">https://medium.com/media/d07b42ed3d5e20031ddd33a04dfa4914/href</a></iframe><p>We also provided food to feed 160 children in an orphanage for an entire month. This still warms my heart seeing this video, I wish we could have done more.</p><h4>Proposal for DigiBytes use as a currency</h4><p>One things not many are familiar with was the proposal to use DigiByte as a currency, specifically for use in Venezuela, as part of an initiative that David Haye was attempting to get off the ground. I wrote this document and then had Damir spice it up, as well as some help from others translating it:</p><p><a href="https://drive.google.com/file/d/1D6uKItzqLFqAR3JWLTJKx8PsFd9HHJn1/view?usp=sharing">DGB_Proposal_v1.1_EN.pdf</a></p><p>If you haven’t looked it over I’d highly recommend it. It’s old but it’s aged relatively well and has a lot of still key points.</p><h4>DigiByte Wiki</h4><p>2018 saw me start off the DigiByte Wiki! We needed somewhere to point people to that wasn’t centrally controlled by just one or two people, that we could spread the load with (say for updating pool details or exchange information), and so the wiki was born.</p><p>While I’m not alone in contributions, this is something I still host, and helped with a lot of the article creation.</p><p>Big thanks to Nigel &amp; Murat especially who’ve also done so much to keep it updated.</p><h4>Further help in Venezuela</h4><p>We did so much to help, I can’t list it all, but everything from more fundraising to help a school, providing tablets to children to learn English and Spanish, along with resources like tablets, scissors, chairs, pens and more:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F8ooaf30EAzw&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8ooaf30EAzw&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2F8ooaf30EAzw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/47740cbbcf0d2d7c2273309e5ca14cd4/href">https://medium.com/media/47740cbbcf0d2d7c2273309e5ca14cd4/href</a></iframe><h4>More fundraising / development goals + Trezor support</h4><p>There was 10 development initiatives setup, most of those were claimed too. This was for everything from an initial Stats site (mctrivia), through to wallet recovery tools (also mctrivias DigiSweep), and Trezor support. I worked closely with the Trezor team to get that support across the line (it took SO long to do the sync initially during testing but we got there).</p><p>Trezors Blockbook is what’s currently running on DigiExplorer &amp; the Testnet Explorer, which brings me to the next item:</p><h4>Running DigiExplorer + Testnet Explorer</h4><p>A few old hands who’ve been around will remember how badly the DigiExplorer server was maintained previously, with consistent issues such as crashing entirely, not being fully syncd… I took over running the servers in 2020 and we had zero downtime for over 12 months! A far cry from the fortnightly issues of days prior when Jared was maintaining it.</p><p>Often times it could be a week or more of it being offline, before Jared could be reached back in the day (an early foreboding) and then get DigiExplorer subsequently restarted /brought back to life. The server costs were astronomical too, with it reaching over USD$1,000 a month at times.</p><p>We had our first fault with DigiExplorer while under my control, in the 2nd quarter of 2021, where it crashed and needed resyncing. We then had another issue a month later so the Insight server was replaced with Blockbook (due to Jared and DigiContributor being otherwise unavailable / unresponsive), and again it’s been solid since.</p><p>I also then started up a Testnet Explorer to help with exchanges integrating DigiByte, and I have also run the primary (and at many times sole) Testnet node, Testnet-1.us.digibyteservers.io</p><p>Side note: more Testnet nodes would be great</p><p>It’s all running beautifully now, and I’m quite proud that we went from a couple of issues a month when I wasn’t looking after it, to one in a year on the server. All of this while shaving the server-costs down to around 10% of what they were, meanwhile the utilization is over 10X more than what it was at it’s previous peak. Roughly a 100X improvement, all while being more stable!</p><h4>Multiple DigiByte Core releases</h4><p>Throughout 2018 we had a number of releases that I was directly involved with helping test, get shipped out the door, bugfix, contact exchanges / pools / wallets (alongside others previously noted in my last Medium post). That in and of itself was quite the accomplishment.</p><p>For example, the reason that DigiByte was the first altcoin outside of Bitcoin / Bitcoin Cash (whos’ developers alerted BTC to the issue) was because I jumped on the issue immediately, provided the one line of code that needed fixing (brough from BTC) to DigiContributor, and he merged it. He and I tested it and rapidly got it released before any other Altcoin (I think we actually only got it out before LTC by a little under an hour).</p><p>Following this, and other releases, would require COUNTLESS hours with contacting Exchanges, Mining Pools, Service providers and the likes, to ensure that they all updated. Especially where we had the likes of the CVE-2018–17144, we needed mining pools to update and FAST.</p><p>Preparation for Odocrypt with the reservebits softfork happened, as well as:</p><h4>Odocrypt &amp; Dandelion</h4><p>This was one of the biggest time-consumers throughout 2019, getting that all ready. MentalCollatz and I did SO much work together testing, resetting the testnet, but he’s definitely the brains behind the code. Same goes for Yoshi and the Dandelion implementation that he and I spent countless hours bugfixing.</p><p>I also spent considerable time working with other 3rd parties to ensure Odocrypt would be supported out of the gate, and it’s great to see the success that Odocrypt has been. I was also working with mctrivia, barrystyle, and the BlackMiner team, on an update for this throughout the end of 2020 / early 2021, which would further allay any fears that it is being ASIC mined.</p><p>As of June 2021, the latest mining pool that began to mine, was using BlackMiner F1 FPGA’s, and they were finding ~20% of all Odocrypt blocks, so it still seems to be FPGA-mined.</p><h4>What is DigiByte / Digi-ID videos</h4><p>Aside from having done over 500 videos in the course of 2.5 years, some of my favorites were the creation of the “What is DigiByte” and “What is Digi-ID” videos:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpLrQycud5GI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DpLrQycud5GI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FpLrQycud5GI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7e7de827dc9f83be3f31ed5877ac62b3/href">https://medium.com/media/7e7de827dc9f83be3f31ed5877ac62b3/href</a></iframe><p>I wrote the scripts for the videos, had the audio professionally recorded by a radio DJ, and even paid for a large chunk of the animations directly myself too.</p><p>There were a number of other videos done where AmonUnlimited did the animations for, that I wrote all of the scripts for too. These videos have had hundreds of thousands of views across the various platforms and are great introductions to key aspects of DigiByte.</p><h4>Coinbase listing attempts</h4><p>Throughout 2018 / 2019 I was the <a href="https://josiah-digibyte.medium.com/digibyte-and-the-enthusiasm-for-coinbase-d3c54faf9ef6">primary author of a document here </a>that ended getting us to the “shortlist” for a Coinbase listing.</p><p>It took countless hours to write the several dozen pages and have it authored to all look nice. I know that it was even printed, bound, and physically handed to several Coinbase employees back in the day.</p><p>I have to wonder if their reasonings for not listing DigiByte are either security-related or founder-related (like Binances was) at this stage?</p><h4>Decentralization metrics</h4><p>There were a number of articles throughout 2019 / 2020 around the decentralization metrics of DigiByte, from the unique miners, to block-time accuracy, I documented a whole bunch of things that I know have been read / referenced countless times by the community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IfCOcr9P2JrbU8y9XTa7ow.png" /></figure><p>Unfortunately as those metrics are declining, I’ve “raised the alarm&quot; and attempted to do things to improve them, such as bringing back CPU / GPU mining. Sadly these have been stifled and stonewalled, by Jared primarily.</p><h4>DigiStats</h4><p>The DigiStats server shows off historical information about the DigiByte blockchain in a beautiful format. It has several years worth of data now graphed that you can utilize, as it pulls it from my personal node.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8vtpitP8yomLhQf0ndYTIg.png" /><figcaption>DigiStats</figcaption></figure><h4>Championing ProgPoW / RandomX</h4><p>This has literally been 2 years in the making (since Odocrypt was implemented on Mainnet), and while ProgPoW / RandomX never got to completion prior to my departure (Thanks Jared…) it was great to be able to do so much and represent the community and the communities desires for a stronger, more secure, decentralized blockchain, with a broader participation of miners.</p><p>Somebody had to be there, pushing things along, and big shout-out to Barrystyle for all his hard work on getting that implemented. I hope one day the old-guard see your code for what it’s worth and stop stonewalling the progress over trivial and irrelevant matters.</p><h3>That’s not all…</h3><p>But it’s not a small list nonetheless. A lot of it has been shortened for brievity, but there’s still a lot in there.</p><p>It disappoints me gravely for people to so blindly follow a single individual who hasn’t been around, and does nothing but post hate-filled messages and conspiracy theories. Like lemmings being led off a hill.</p><p>Still, I can hold my head high with all of these massive accomplishments over the last 3 years with my involvement, and I wish DigiByte all the best for the future. I just hope Jared gets out of the way so the project can finally thrive.</p><p>To those who remain, I wish you all the best of luck. To the friends I’ve made along the way, I’ll truly miss you.</p><p>To those who’ve written me kind words on Twitter or in the YouTube comments: Thankyou! I’ve appreciated every single one of them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76d3c1e94693" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[In pursuit of GPU mining, a timeline pre Odocrypt -> DigiByte v8]]></title>
            <link>https://josiah-digibyte.medium.com/in-pursuit-of-gpu-mining-a-timeline-pre-odocrypt-digibyte-v8-186e9a499647?source=rss-714d4d4beb3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/186e9a499647</guid>
            <category><![CDATA[digibyte]]></category>
            <dc:creator><![CDATA[Josiah Spackman]]></dc:creator>
            <pubDate>Wed, 04 Aug 2021 03:41:22 GMT</pubDate>
            <atom:updated>2021-08-04T09:17:49.250Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been asked a lot lately about what’s been happening with a CPU / GPU mining algorithm that we’ve all been waiting for what seems like years to implement. This will cover some of the history there, as well as the development of DigiByte version 8. I’ll also include a spiffy little timeline at the end, so we can clarify a few things and provide people with both some insight into the history as well as a comprehensive perspective of events.</p><h3>The lead up to, and release of Odocrypt</h3><p>DigiByte had evolved to be at a point where it was faced with 5x ASIC-mineable algorithms since all the way back in 2017. Immediately after all of the fervor of DigiByte briefly reaching the Top 10 in CoinMarketCap around July of 2017 had begun to die down, rumors began to swirl of ASICs (or at least highly optimized FPGAs) on all the remaining algorithms.</p><p>Everyone knew that SHA256 and Scrypt were ASIC mineable, this was the case when MultiAlgo was originally implemented in September 2014. However of the 5x algorithms, one was originally CPU mineable (Qubit), while the remaining 2x were GPU mineable (Skein and Myriad-Groestl). That changed in 2015 with Qubit being GPU mineable as well, however towards the tail end of 2017 in September / October, the relative ‘difficulty’ of the Skein and Myr-Gr algorithms rocketed upwards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*zbaFBObdOxaU2UQGvIOyrg.png" /><figcaption>The Baikal X10 Giant product page at release</figcaption></figure><p>Come November 2017, the Baikal X10 Giant was released, with a power to hashrate ratio that destroyed even the likes of the GTX1080Ti by an order of magnitude. I recall being away on my honeymoon at the time talking with Jared, GTO90, Ycagel, DigiContributor, DiscovernowDigiByte and a few others about how we needed to bring back GPU mining.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/445/1*1oJ3KiLxwX88mpwVxc-hjA.png" /><figcaption>Some earlier messages of mine in the Mining channel on Telegram about the X10 Giants efficiency</figcaption></figure><p>Even back then, despite linking Jared to the buy-page for the devices, I recall he wouldn’t believe they even existing, iwth support for Myr-Gr, Qubit and Skein, 3x of our 5x algorithms.</p><p>I’ve talked a lot about why GPU / CPU mining is beneficial but here’s a few quick recaps of why it’s important:</p><ol><li>It vastly improves the distribution of the mined asset, compared with ASICs</li><li>It greatly distributes the hashrate globally because of better distribution channels for CPU / GPU vs ASIC / FPGA</li><li>It encourages a decentralization of mining thanks to participation from hobbyists or people testing the waters of mining</li><li>Users can participate in the network without needing a costly investment in single-purpose hardware</li><li>Ease of onboarding to the network, without requiring KYC purchases from an exchange</li></ol><p>…just to name a few.</p><p>At the time in November / December 2017, I looked at the likes of Ethash &amp; Equihash, both of which had placeholders in the codebase already for. I also began looking into CryptoNote, Lyre2RE, BlueMidnightWish, and SkunkHash-Raptor. You’ll note that some of those clearly achieve the goal of being a CPU / GPU focused algorithm and stood the test of time better than others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/441/1*b2Rq93Yru29sW46GLtg1pQ.png" /><figcaption>Some earlier messages of mine around alternative PoW algorithms</figcaption></figure><p>Unfortunately though, not a lot happened throughout the next 12-odd months, in 2018.</p><p>We had a few minor updates in the 6.x releases which were basically all small bugfix releases across the course of 2018. Then, on the 5th of November 2018, MentalCollatz (the brains behind MultiShield) <a href="https://github.com/digibyte/digibyte/pull/159">submitted a pull request for Odocrypt</a>.</p><p>Collatz was the driving force behind the Odocrypt upgrade for sure! Originally the theory was that it could potentially also be GPU mined, though FPGAs were definitely the key focus. I began to work with him after we caught up on Telegram about a week after his pull request was submitted, testing it, and testing it, and testing it some more. I ordered several different FPGAs based on the Cyclone-V architecture so that we could test competitive mining against each other. It took a while but we got a fully simulated testnet setup!</p><p>Collatz also identified a minor security issue, and so the <a href="https://github.com/digibyte/digibyte/tree/v6.17.2">ReserveBits soft-fork was created with the 6.17.2 release</a>. This was probably the 4th time in the previous 12 months that myself and half a dozen others had contacted Exchanges / Pools etc to get them to upgrade. This upgrade would mean a tighter <a href="https://github.com/digibyte/digibyte/pull/162">upgrade in the future as we replaced Odocrypt</a>, and replaced subsequent algorithms.</p><p>The ReserveBits upgrade got locked in without too much issue, in preparation for the Odocrypt upgrade, however because we’d been doing a bunch of bugfixes with the algorithm weighting issue, then the bitcoin inflation bug, now this, there was “<strong>upgrade fatigue</strong>” setting in for sure.</p><p>Still, Collatz and I began with a testnet-upgrade replacing Myriad-Groestl with Odocrypt. The first time around the initial difficulty was set way too low, meaning a whole bunch of Odocrypt blocks were found all in a row, so we <a href="https://github.com/digibyte/digibyte/pull/186">adjusted it again setting the difficulty requirements to be much higher</a>. This testing Collatz and I did throughout March / April confirmed the upgrade a second time, working perfectly with the adjusted difficulty, so mainnet was set higher in order to accomodate the fact that significantly more people would be mining.</p><p>There was also significant testing going on with Dandelion, and I was spending most days working with Collatz and Yoshi testing it. It took a bit to get to the bottom of a few crashes there due to the reference-implementation being for an older Bitcoin codebase, but we got there in the end and it’s been solid ever since, also included in the Odocrypt upgrade.</p><p>With the Odocrypt signalling, we missed the originally expected upgrade time because that mining signalling hadn’t reached the 70% threshold. Despite myself and half a dozen others reaching out to all possible mining pools (And there was approx 80% “known” sources for mining hashrate) it was difficult to get people to enact this upgrade. I believe this was mostly due to the aforementioned “upgrade fatigue”, as we never had any written / verbal pushback etc.</p><p>However a couple of signalling epochs later, the mining signalling threshold was reached. We had the one-week lock-in period, and we scheduled a count-down livestream in July 2019.</p><p>I recall on that day helping Jared get his Cyclone V Intel Starter Kit operational immediately beforehand, because he’d never setup Odocrypt mining. I was assisting him with the process of getting it setup right up until the start of the livestream, as all the testing had been Collatz and I.<br>If memory serves me right, there were 3x Odocrypt blocks in a row at the cut-over point (far better than our first testnet migration), the livestream was a success, the changeover was a success, Odocrypt was operational, and we had completed the first algorithm replacement in almost 5 years since MultiAlgo was activated back in 2014! As of 22nd July 2019, Odocrypt was live.</p><h3>What happened to GPU support?</h3><p>Well we very quickly noted even pre-activation of Odocrypt that it would be heavily favoring FPGAs to the point where GPUs couldn’t keep up. Had the Cyclone V based hardware been where things remained, it might have been a different story, however we were seeing even the AtomMiner coming out and being over twice as efficient, then BlackMiner announcing support for Odocrypt and being an order of magnitude more efficient. I immediately began the hunt again, even before the activation of Odocrypt, for a GPU-focused algorithm.</p><p>Looking back in hindsight over the other algorithms being investigated, it had become clear that a lot of them were not fit for purpose: Lyra2RE became Lyra2REv2, Equihash had ASICs, BlueMidnightWish was being mined as part of X16R on FPGAs, and even Ethash had ASICs (although they displayed the smallest benefit compared with GPUs).</p><p>Despite these ASICs, placeholders for Ethash and Equihash remaining in the codebase, it was clear we’d need something fresh!</p><p>In June of 2019, the two main algorithms I was pushing for adoption after Odocrypt were SIGMA for CPU mining, and ProgPoW for GPU mining, though consideration was being given to Cuckaroo / Beam algorithms as well. This was a little over a month prior to the activation of Odocrypt, and it has remained a priority (in my mind at least) ever since.</p><h3>Enter: ProgPoW</h3><p>Following on from Odocrypt (once activated on mainnet), I began a bit of a deeper dive in to the algorithms. Over the coming months, I discovered this video of Kristy-Leigh Minehan at Ethereums Devcon4 which had me sold on the idea of ProgPoW as the next major upgrade for DigiByte:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fpe1pDGDy6iE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dpe1pDGDy6iE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fpe1pDGDy6iE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7edb1198ba684ee5d3b9c46985e97a73/href">https://medium.com/media/7edb1198ba684ee5d3b9c46985e97a73/href</a></iframe><p>If you haven’t seen the video, I would highly encourage you check it out!</p><p>I reached out to Kristy-Leigh back in August / September, we got talking, and in <a href="https://www.youtube.com/watch?v=cWi8h0-Pn0M&amp;list=PL8xahtUlbHa9NP8bGM6xfZktKmJnFqpE4&amp;index=8">October of 2019 she came on to my podcast for DigiByte and Friends</a>. It became abundently clear we needed to implement ProgPoW, and she offered to <a href="https://josiah-digibyte.medium.com/proposals-confidential-transactions-and-what-is-digibyte-doing-a295c25683de">assist us with the implementation of it all the way back in October 2019</a>.</p><p>We gratefully accepted her volunteering, and she began to work on that in her spare time. There was a sense of progress finally, heading in to 2020 that we might be able to get something out the door in the new year that supported GPU mining again finally, further improving our dwindling mining decentralization.</p><p>Over the Christmas period of 2019, was a good opportunity for me to review the Community Whitepaper (now renamed to the Infopaper) I had begun to write the year prior, and reflect upon the long-standing desire (and even need) for a GPU-based algorithm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*AmlyviFRq7v5-M1fcp79Dw.png" /><figcaption>Excerpt from the DigiByte Infopaper I began writing in 2018</figcaption></figure><p>Although this isn’t directly related to ProgPoW, I had mentioned it in the document when I drafted this originally in 2018, coupled with the DigiFacts I was was making around the same time. In fact, one of the original DigiFacts I wrote incorrectly stated DigiByte was an “early adopter” of it, as the prevailing theory was it would have been introduced sufficiently within the following few months prior to that DigiFact being sent out by DigiByteCoin twitter. This naturally has since been replaced with a different fact.</p><p>When the Infopaper was being written at the time in 2018, Jared had asked I not do any further work on it, but rather asked that I give him 4 weeks to finish his book in January 2019. Reason being he wanted to use parts of his book, Blockchain 2035, to make such an Infopaper. Blockchain 2035 ended up being released in November 2019, and the Infopaper coming out in Q2 of 2020 without any of Jareds involvement. For those curious about why I’d mentioned the Infopaper back in 2018 but it took 18 months to eventuate, this was why.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VuU6euCUk20A-0h4H3iL1A.png" /><figcaption>The Infopaper I wrote was originally created in 2018 but released in 2020 Q2</figcaption></figure><p>Carrying on though to the start of 2020, on January 4th 2020 I was writing about the <a href="https://josiah-digibyte.medium.com/why-i-believe-progpow-is-the-next-step-forward-for-digibyte-63d299247d4f">implementation of ProgPoW and how following that I strongly believed that RandomX would be the next</a> after ProgPoW. This is because RandomX was to CPUs as ProgPoW is to GPUs. However, we weren’t blindly charging in to algorithm upgrades just for the sake of it, <a href="https://josiah-digibyte.medium.com/pros-and-cons-of-digibyte-algorithm-upgrades-in-2020-af399eacef96">with me intentionally seeking out people who would try and convince us not to change</a>, to highlight down-sides and negatives. Still, it remained a priority for the community, for myself, and it simply made good sense to pursue!</p><h3>The start of DigiByte 8</h3><p>Jared, ycagel, DigiContributor and myself all jumped on a video call, as DigiContributor worked with Jared to do a whole lot of initial work on DigiByte version 8 on the 31st of January. The video call went on for around 4 hours, which I recorded as Jared was wanting to document some of the ways that he and DigiContributor worked through merging the code. Sadly, because I was at work on the day and remotely accessing my PC, I didn’t notice that I wasn’t recording desktop sounds, and so the entire recording had no audio.</p><p>This work on January 31st was merging Bitcoin Core 0.19 at the time, to give us version 8.19. Unfortunately at the conclusion of January, the code was left still completely non-functional, with 8.19.0 not compiling in any way. This was also the last time we would see Jared contributing code throughout 2020.</p><p>I sought out further assistance, predominantly with the 8.19 codebase. The theory was that if Kristy-Leigh was to implement ProgPoW against 8.19, we needed it to <strong><em>actually work</em></strong>. In April, SmartArray began working on tidying up the many outsanding issues, then in May I found AkshayNexus who also began to assist. They re-merged OpenSSL which was a main showstopper, as this library had been removed by Bitcoin Core and yet we needed this as the basis for our Scrypt (basically, the key parts of the blockchain).</p><p>April rolled around and I wanted us to <a href="https://josiah-digibyte.medium.com/fundraising-for-progpow-implementation-68cc86d7a8d1">do a fundraiser to show some gratitude for her effort going into ProgPoW</a>.</p><p>We managed to fundraise to reach the goal amount before too long, and I’d been keeping in regular touch with Kristy-Leigh about ProgPoW and the progress being made. However, without a functioning 8.19, it made progressing quite difficult for all parties.</p><p>I continued to write about <a href="https://josiah-digibyte.medium.com/updating-digibyte-with-progpow-randomx-5ecdae281d25">ProgPoW and then subsequently RandomX </a>in DigiByte at the end of April. Again this was a clarifying article for people who were asking when it could be expected, clearly there was a lot of enthusiasm, and people just wanted to know “When can I mine with my graphics card again?”.</p><p>The one part that I wasn’t completely transparent about was that although I mention the need for 70% mining lock-in, even as far back as April 2020 I was discussing with others how we should proceed given we knew of only ~50% of the mining hashrate source (at the time) since the Odocrypt upgrade. Because there is no way to reach out and find the remaining 50% unfortunately, or at least 20% to push us over the 70% threshold, it would make any signalled upgrade incredibly difficult to find mining consensus on.</p><p><strong>Fun fact</strong>: Odocrypt was the only signalled hard-fork DigiByte has ever done, the remainder were all activated at a block-height.</p><p>I also reached out to a friend I had gotten to know who predominantly worked on Verge (XVG) to see if he’d be up for helping. He committed some <a href="https://github.com/DigiByte-Core/digibyte/pull/5">Continuous Integration testing for us at the end of June</a>. This was fantastic as it identified a lot of the previous Unit Test issues we had not addressed, while also providing something to enable more rapid testing in the future. Very grateful for Marpme_ setting us on the right path there.</p><h3>When things had completely stalled</h3><p>Then in May 2020 we saw Jared getting furious at Exchanges for not “giving back” to projects such as DigiByte and <a href="https://josiah-digibyte.medium.com/on-jared-taking-a-sabbatical-f35e5e7e0caa">announcing he would take a sabbatical from DigiByte</a>. He had, however, not contributed code since January, but nonetheless choosing to intentionally step away seemed positive at the time.</p><p>It was indeed a positive for the community because despite him returning to Twitter almost immediately talking about non-blockchain things, <a href="https://www.binance.com/en-AU/support/announcement/61dab303cffb4582b77afe3e4e830e1f">Binance listed DigiByte the following month</a> in June now that he was publicly stepping away from the project (given his prior highly public distaste for them). DigiByte was the last project in the Top 50 of CoinMarketCap to be listed on Binance (<a href="https://coinmarketcap.com/historical/20200621/">holding a position of 44 at the time</a>).</p><p>Since then we have seen DigiByte plummeting down the list, even briefly exiting from the Top 100 for half a week in July of 2021. Although the Market Cap has quadrupled in size since the June 2020 sabbatical, due to more recent stifling of progress in 2021, DigiByte has found itself unable to keep up with other projects increases.</p><p>Even though there was a wave of excitement from the Binance listing that continued throughout Q3 of 2020, there was absolutely no development work happening on the Core wallet at that time, nor mobile wallets, nor DigiAssets (Aside from mctrivia working on DigiAssetX). Kristy-Leigh Minehan had unfortunately been unable to carry on with the work, coupled with fact that the 8.19 branch had remained broken since January, meant we were stuck.</p><p>Despite my best efforts to find developers and people who would be willing to contribute or help with either DigiByte version 8 as well as ProgPoW / RandomX, I was coming up short. DigiByte was effectively “treading water” at a code-level, with more and more <a href="https://josiah-digibyte.medium.com/some-updated-digibyte-mining-stats-graphs-comparisons-7f0c902b7554">centralization of mining occurring</a> every day.</p><h3>Progress starts up again in Q4 2020</h3><p>In October I was contacted by someone through Reddit. This person, barrystyle, had heard we were looking for someone to help with a <a href="https://josiah-digibyte.medium.com/randomx-for-cpu-mining-on-digibyte-75c6a0d6e29c">RandomX implementation and had begun work on it</a>. Barry caught me up to speed on where things were at with what he’d done already and what more needed to be done. In particular he was doing a bunch of extra work to ensure that it would work “out of the box” with existing XMRig and other Monero-expecting mining software implementations.</p><p>So we took up a small fundraiser to pay Barry for his time implementing RandomX which I believe was reached just two days later, a real record.</p><p>Barry got to work right away basing it off version 7.17.2, and at the first milestone just 4 days later I sent half the funds his way when blocks were being minted with RandomX on a private testnet.</p><blockquote>Progress was truly being made, for the first time in 9 months!</blockquote><p>However, Barry quickly identified that the existing 8.19 was very broken and offered to assist further there. Given Akshaynexus had been attempting to re-add OpenSSL, and that all development had completely stalled since May (6 months with no end in sight), in November Barry asked if I’d mind him rebasing from Bitcoin Core 0.20.</p><p>I told him that sounded fantastic for a few reasons:</p><ol><li>More up-to-date codebase to work from of Bitcoins, zero objections there</li><li>Bitcoin was using that as the basis for their Schnorr signature work (which we were also interested in), and it would minimize effort there</li><li>The codebase Jared left in January for 8.19 was in quite a state, so much so that SmartArray and Akshaynexus were at a loss with how to proceed</li></ol><p>It’s worth noting that both the Master as well as the 7.17.2 branch were both still fully functional throughout that time. I had previously seen a lot of untrue accusations about this. It was only the 8.19.0 that Jared had started and abandoned that did not ever work. You can still test this to this very day, as the branches are available, with the <a href="https://github.com/DigiByte-Core/digibyte/commits/archive/master_old">old Master</a> and the <a href="https://github.com/DigiByte-Core/digibyte/tree/feature/8.19.0">8.19.0</a> both still visible.</p><p>Nonetheless, things were truly starting to ramp up, and genuinely new achievements + accomplishments being done, the likes of which DigiByte had not seen in the longest time.</p><p><strong>Fun fact:</strong> Odocrypt was the first “new code” written for DigiByte (by MentalCollatz) since the DigiSpeed upgrade in 2015. All other upgrades were purely merging of pre-existing Bitcoin code. Dandelion, which was also a proposal for Bitcoin, was also implemented by SmartArray and MentalCollatz.</p><p>Aisde from that, everything since 2015 was taking Bitcoin code and “making it work” with DigiByte.</p><p>So, Barry began to work instead on the Bitcoin Core 0.20 code in October as a more “stable” base for RandomX to be built against, which would mean we could also implement Schnorr more easily too.</p><p>But even better, Barry had begun to work on a number of other improvements, things that were genuinely “firsts” and not just code pulled from Bitcoin, such as:</p><ul><li>Improvements to the sync of the blockchain from scratch so it occurred in half the time on a normal machine, and in a fraction of the time where you were re-syncing to test code (important for developers)</li><li>RAPID start up of the blockchain, taking it from 12 minutes on some test machines to 60 seconds flat.</li></ul><p>That alone, outside of Odocrypt, <em>is more new / fresh / unique code that had gone in to DigiByte in the previous 5 years</em>.</p><h3>Undertaking ProgPoW and RandomX</h3><p>Throughout October / November, Barry managed to get a really good 0.20 base working for DigiByte, which was then being used for RandomX development. SmartArray had also made a pull request with a replacement of hashmap with btree, as he’d been loosely working with Barry at that time in the same Telegram channel.</p><p>I’d also been talking with Kristy-Leigh about ProgPoW throughout October about the progress there. She actually suggested towards the end of the month that if Barry was doing well with RandomX that he might like to also undertake ProgPoW. Kristy-Leigh had some personal things taking priority, so I guess not having me asking every week how things were progressing would probably be one less stress (my bad). We’re still on great terms and keep in touch on the regular, and I’d encourage anybody to <a href="https://twitter.com/OhGodAGirl">follow her on Twitter</a> too.</p><p>I ran the suggestion past Barry, he agreed, and then in November he undertook ProgPoW as well.</p><p>A lot of work went in to the Stratum for RandomX, which was where a lot of the magic happens to allow RandomX mining with existing miners (such as XMRig) where usually they would require some modification from the normal Monero blockchain. This again is a very unique implementation, with the stratum all being written from scratch, and will be another unique part to DigiByte that has not simply been merged from Bitcoin Core code.</p><p>ProgPoW happened throughout November / December, and I paid Barry out all of the outstanding bounties at this point given we were pretty close to completion.</p><p>We’d been doing mining on testnets we’d setup, we’d setup mining pools and tested rolling the blockchain forward to implement these algos, we’d tested mining on XMRig, SRBMiner-Multi and NanoMiner. Issues had been identified and were being cleaned up, we’d probably done a few hundred compiles at this point.</p><p>Barry had also done some other major work with things like the removal of OpenSSL. Bitcoin Core had removed the OpenSSL library from 0.19, which the Scrypt algorithm uses. This is part of what had caused so many issues with 8.19 for Jared back in January of 2020, and Akshaynexus had attempted to readd as a “quick fix” to get things working again. Instead of taking the quick route, Barry implemented a single-file scrypt copy, which had an integrated sha256d function, which got us by, so that OpenSSL would no longer be required. This was no mean feat, and not the kind of thing some junior coder could accomplish (We saw relatively skilled people simply trying to add it back in), nor is it the sort of thing someone could ‘fluke’. This is the kind of thing that requires a LOT of skill and intricate knowledge of how all of the pieces tied together, and making the hashes match what they should be.</p><p>We had a fresh implementation, with new code, and outside of Odocrypt, DigiByte had not seen this kind of improvement in the last half a decade.</p><p>Things were looking really good, and progress was being made!</p><h3>Odocrypt upgrades</h3><p>In December of 2020, I got together with Matthew, SmartArray, and Barry, with the goal of getting to the bottom of the Odocrypt “Is there an ASIC?” question.</p><p>Despite the fact that a large mining pool had just started up a month prior, and we knew they were using BlackMiner F1+ and F1-Ultra’s FPGAs, and were getting around 20% of all Odocrypt blocks, I took this very seriously as did the other gentlemen.</p><p>The theory being: If there are ASICs, then changing Odocrypt will stop them from being able to mine.</p><p>If there are no ASICs for Odocrypt, then because it’s a FPGA-targetted algorithm that changes every 10 days as it is, there’s no problems with tweaking it slightly, due to the fact it changes every 10 days as-is.</p><p>Then on the 3rd of January we created a Telegram group and invited the BlackMiner team (who specialize in FPGAs) to join us.</p><p>We got to work, and on the 26th of January, an initial <a href="https://github.com/DigiByte-Core/digibyte/pull/10">submission for an upgrade of Odocrypt was created</a>. It still needed some more work, but thanks to Matthew and Barry who were there and immediately replied.</p><p>You’ll note that the “other” developers didn’t respond for 6 months after it had been submitted, and even then only because I had talked with Laura asking why they were refusing to even acknowledge it. We even had the 250th DigiByte update on June 19th with Jared Tate on it, talking with him about Odocrypt v1.1, but it took another 4 weeks before “the” devs acknowledged it?</p><p>We’d got a proposal for an Odocrypt upgrade, it still needed a bit of work, but yet again: Progress was being made!!</p><h3>Planning the release of 0.21, Jareds return</h3><p>On January 14th 2021, Barry messaged me to say that 0.21 had been released by the Bitcoin Core team. Given things were working so well with 0.20 at this point, we were both kind of loathe to do things based off 0.21, but at the same time if doing a larger release such as we were with DigiByte version 8, it kind of makes sense to be as “up to date” as possible.</p><p>Unfortunately, Bitcoin changed a lot about the way that transactions are handled, doing rebroadcasts and the likes, which directly impacts how Dandelion transactions work.</p><p>Still, Barry got to work on it and had things mostly operational.</p><p>In early January of 2021, Jared claimed he would setup a new social network based on Mastodon, but he hadn’t been able to get it to work. He was claiming that Amazon could not be trusted, Telegram could not be trusted, which is especially ironic given he has since setup a Telegram channel “for his followers, because he keeps getting censored”. Despite all of our differences, in the second week of January, I unblocked him from Signal and offered to help him with libre earth. He gave me server access, and I setup the libre earth server for him so it was ready to go. The relevance of this will be clear soon.</p><p>At this point Jared had still not been involved with DigiByte since he spent half a day on the video-call working on 0.19, some 12 months earlier.</p><p>Now there was a signal group-chat created with a bunch of people to discuss how DigiByte 8 would be supported with it’s release, the testing that needed to be done, how we could contact exchanges / pools etc. This groupchat included the likes of Rudy, Hans &amp; Rutger from the DigiByte Foundation, ycagel &amp; js555, Laura &amp; Michelle from DGBAT, DigiContributor (the gentleman who’s arguably committed the most code to DigiByte over the last half a decade), gto90 who originally started the Android / iOS wallets, and also myself.<br>As Barry wasn’t on Signal, he wasn’t participating in this, but seeing as these were mostly non-coding related discussions, he hadn’t been too concerned. After a little while, seeing as Jared had emerged from his slumber like a Michael Bublé christmas carol, he was invited to the group too.</p><p>Barry had been <a href="https://github.com/DigiByte-Core/digibyte/tree/feature/8.20.1">working on the 8.20 code on the DigiByte-Core GitHub</a>, and while still not a completely perfect “release-ready” codebase, it was highly functional with just a handful of minor bugfixes needed, which had already been explained to the team in that chatgroup, Jared included.</p><p>Jared, to his credit, initially sounded like he wanted to help Barry with the codework being done on 8.21. He asked on the 18th of January if Barry could commit the work he’d been doing rebasing off Bitcoin 0.21 to the DigiByte-Core repository, to which Barry agreed with the disclaimer that it was far from operational and that the most functioning tree was 8.20. This was because Bitcoin Core had only released it on the 14th of January, a few days prior.</p><p>So with that disclaimer, we advised Jared (and the others in the groupchat) what we knew needed fixing still from 0.20:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BLNAjkPgLyDKnqMbyWuw-g.png" /><figcaption>Letting Jared know where things were at</figcaption></figure><p>We had advised there were issues with MacOS building which were being worked through, we had already identified the changes needed in Dandelion, and a few other things. However for being a rebase on top of code that was released just a few days prior, it was still very much operational!</p><p>From the above messages of his, we can see Jared initially seemed like he would work with Barry and help with the 8.21 codebase. Instead things very quickly took a turn for the worse, we saw the very opposite, with allegations of “nothing work” and being broken in “thousands of places”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*6pZ0AKmZqKQOKD8adgMFig.png" /><figcaption>Jared beginning to lose the plot</figcaption></figure><p>Which was funny given I had it working, SmartArray had it working, Barry had it working, and I’d even posted <a href="https://twitter.com/dgb_chilling/status/1352849550751408129">screenshots on Twitter about it</a>. We later learned that Jared had been talking with ycagel, and advised him that Jared had broken his build-environment on his Mac, and he apparently couldn’t even get DigiByte version 7 building (Which was why he never participated in 7.17.3, but more on that later).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cLl4ZgBuwQ10kiKRw4ripw.png" /><figcaption>Sharing proof that 0.21 was working on January 23rd</figcaption></figure><p>Things VERY quickly became hostile, with Jared throwing out things such as:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*mFUvwZOzuDPsWyc4OIOfTw.png" /><figcaption>It will only take Jared 3–5 hours to get 8.21 working!?!</figcaption></figure><p>However, we have concrete proof, because Jared has been working with BTC 0.22 codebase for two weeks now at the end of July ’21 (with SmartArray doing most of the heavy lifting) and it’s still not as operational as the work that Barry had done. Jared has since also stated this to both me and ycagel, in May 2021:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*F67R1bUHuItFru59rj3KHA.png" /><figcaption>So it’s gone from 3–5 hours to 2–3 months?</figcaption></figure><p>A far cry from the 3–5 hours.</p><p>The unfortunate thing is that there was nobody else technical enough to call out Jared in the 8.21 groupchat (as gto90 usually simply ignored it, and DigiContributor rarely checked in) when he would make ludicrous statements such as that.</p><p>In addition, I have to wonder, if it would only take 3–5 hours to get things working, why Jared left 8.19 in such a mess after the 4 hours of effort in January of 2020 the year prior?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wgoSIvCJac9sUhk-jE24Cg.png" /></figure><p>I was on a video-call with Jared, ycagel, and DigiContributor as they did the work, in January 2020. There is <a href="https://github.com/DigiByte-Core/digibyte/commits/feature/8.19.0">nothing further from Jared, on his 8.19 branch</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*48z5Zuojf8MPiXXh5oP9rA.png" /><figcaption>DigiByte 8.19, nothing from Jared despite it allegedly only taking “3–5 hours” to get things working</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1006/1*UhFvL1gLjrGD5VYtaqFTkg.png" /><figcaption>First commit on Jan 29th, 2020 (the year prior)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*MOMvecsHQKqUgBYuuFzhkw.png" /><figcaption>Second commit on Jan 29th, 2020 (the year prior)</figcaption></figure><p>It also raised the question of why Jared hadn’t done this if it was such a priority over the previous 12 months, despite <em>allegedly</em> working on DigiByte? To this day we still haven’t been able to find any commits from Jared after January of 2020 throughout that year.</p><p>Nonetheless, back to 2021 we can see that Barry committed code for 8.21 originally on the 19th of January, just 5 days after Bitcoin released it, and only the day after Barry had begun working on it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/971/1*JpOW5B0AV4F3QFVD_-ymrw.png" /><figcaption>The 19th of January when Barry committed the work for 8.21</figcaption></figure><p>Jared looked at it and decided to throw it all out, that he didn’t want to work with Barry, SmartArray or myself, and would start over from scratch himself:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/879/1*ouQCwDaRMpAKjnCIioveEg.png" /><figcaption>Jared saying he wouldn’t work with the rest of us</figcaption></figure><p>Jared seems to imply that I “wouldn’t let him communicate” with Barry? It’s worth clarifying I had advised Jared several times that Barry was on Telegram, but not Signal:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rTF018QLJyJJfxO6" /><figcaption>Advising Jared on Monday 18th Jan that Barry was only on Telegram</figcaption></figure><p>Meanwhile, Jared was on Telegram, and trying to promote it on Twitter:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*YfuzPnkt0QioAoo2zxaJWA.png" /><figcaption>Jared recommending Telegram on Jan 14th</figcaption></figure><p>But oddly enough later on in July of this year, Jared tried to say that he doesn’t trust Telegram, and didn’t want to be on Telegram, despite never mentioning that at the time (as he was busy promoting it?):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/785/1*_PO-UggAujGVYG-7RxFYSg.png" /><figcaption>Allegedly wanting to work together??</figcaption></figure><p>The irony that he’s now started a Telegram Channel for one-way communications with people after claims of being censored, does not escape me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/879/1*F2UpuGpR37Y85Shx_0vEbA.png" /><figcaption>Jared is now using Telegram for when he thinks he’ll eventually be kicked off Twitter</figcaption></figure><p>So there was actually <strong>no attempt </strong>by Jared to reach out to Barry at all, but yet he says that <em>I’m trying to stop Jared communicating with Barry</em>? If you don’t understand how all these kinds of mental gymnastics takes place, then good, we’re both on the same page.</p><p>Back to January though, we had the division really starting to show once Jared had started to work on things without anyone else. It was this following comment that specifically had the others in the groupchat most worried, because Jared had clearly gone off, on his own at this stage:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ti5FrIiXzmvqQ3u-" /><figcaption>Jared trying to imply yet again that the code wasn’t working, not realizing at the time he’d broken his Mac</figcaption></figure><p>This was the first time Jared drew a line in the sand, creating the division.</p><p>Jared decided to throw out all of the work that (predominantly) Barry had been working on, and on the 20th of January, Jared began to work on his *own* unique DigiByte update, without anyone else (Almost 12 months to the day after he had been working on 0.19). Again this flies in the face of his comments above saying that nobody wanted to work with Barry, quite the opposite when it was Jared who started working on his own.</p><p>This is very important because the narrative of “I’ll work with people, let’s all work together” at this point was well and truly shattered, and we could see it was just lip-service while Jareds actions showed a completely different story:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YiJpMhdHi5P_lX5VanlGcA.png" /><figcaption>Jared began working on 0.21 after suggesting he would help Barry</figcaption></figure><p>Jared did some very basic fixes over the next 3 days, but everything was still VERY broken and wouldn’t even compile. All this, despite claims from Jared that it would work after 3–5 hours. The final commit he did was on the 23rd of January:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NGMkB9EDw1WY8P9M7mACFQ.png" /><figcaption>Jareds last commit towards 8.21 in January</figcaption></figure><p>Again, we were told he wanted to be “working together”, just not working with SmartArray, Barry or myself. Jared, instead, opted to work solo, of his own volition.</p><p>This has become a common theme, that things must be done “Jareds way” and under his name, or otherwise he throws a tantrum. This original code is <a href="https://github.com/digibyte/digibyte/commits/8.21.0">still available online and still does not compile</a> despite us being told it would take 3–5 hours (Or was it 2–3 months?).</p><p>Despite all of this, the version 8.20 that Barry had been working on was mostly done, with a few minor bugfixes still needing to be polished off. Again this code too is still available and can be compiled by anyone to test as we had been doing extensively.</p><h3>More delays, and the new dev process</h3><p>Following on from this drama from Jared, several members eventually expressed grave concern, predominantly from Jareds aforementioned comments about two competing codebases now that he was starting solo. This concern was mostly due to the fact that outside of myself and Jared (who were clearly at odds), gto90 wasn’t commenting on Jareds antics, and DigiContributor had been busy and not around the groupchat (as DigiContributor is usually uninterested in the ‘personality politics’ and just likes to write good code). There was nobody else who could really independently advise them on if Jared was telling the truth when he said things would take 3–5 hours or not. Similarly there was nobody who could advise if the 8.20 / 8.21 that Barry had been working on was “broken in thousands of places” vs the existing codebase (or that which Jared had started on himself).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GkwQn_pxVYgVQTxyC4rfXQ.png" /><figcaption>DigiByte 7.17.2 fails the tests in 14,529 ways</figcaption></figure><p>Oddly though, despite the fact Jared claimed to want to work with others, no alarm bells went off for the others in the group after Jared threw out all the work of Barry, myself, and SmartArray, and started solo?</p><p>Despite sharing evidence of things such as this, with DigiByte 7.17.2 failing the tests in 14,000+ ways, nobody else in the groupchat would question Jared.</p><p>Instead, on the last week of January, the other non-technical people basically asked for a “time-out” on development. Basically, that no further development from anyone continue until they had a better understanding of things (makes perfect sense) and that Jared wouldn’t cause any further division.</p><p>As a move to have something more ‘independent’ that even non-technical people could understand, a suggestion was floated around the first week of February for a new development method where all code would be reviewed by independent sources from the people who wrote it. Not only would one person need to review it, but two would. GTO90 was spearheading this suggesting, and said that he would put together a presentation discussing why this was needed, and how it would all work.</p><p>In the middle of February, he put together a document, predominantly asking questions around “how do other projects do this?”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*Y29tlZPFi5EYjMP6NxJXqg.png" /><figcaption>First few slides from the development suggestion PDF</figcaption></figure><p>Although there were no direct proposals in this document itself, the suggestion eventually became “we should basically adopt the same method as Bitcoin, and stick with the Atlassian GitFlow Workflow process”. This is something I’ve been a fan of, as having code audited and checked by others is always a good idea. Again, this just makes good sense.</p><p>However, getting everyone together to discuss this didn’t happen throughout February. March rolled around, and no further progress was being made around what process should be adopted, just more waiting.</p><p>April rolled around, and by then I was personally incredibly frustrated that nothing more had happened. I’d been advised the PDF would be updated with more details, a more in-depth description, but 7 weeks later there was nothing. Talking with Js555, and then GTO90, they confirmed the proposal was for the Atlassian GitFlow Workflow method, and I suggested to them that we needed to just go ahead with it and make it happen. There was no sense in waiting longer for a more in-depth document, nobody had any objections (we just hadn’t all been able to get on a video-call to discuss it at the same time) and frankly I was incredibly frustrated with so much waiting for 7 weeks with seemingly no advancements. So, it was a case of “Let’s just do it”, and we could tweak and adjust things if we needed to down the line.</p><p>This was what spurred the Medium article talking about <a href="https://josiah-digibyte.medium.com/a-new-development-era-for-digibyte-fb50a23bdbe8">a new development era for DigiByte</a> at the start of April.</p><p>Fantastic, so this new document is out, nothing has happened for a few months, now what?</p><h3>Fixing the Unit Tests</h3><p>Well, in March, Barry had already begun to work on fixing some of the unit tests (despite the request of no further coding from the others in that groupchat, but still…) in a version 7.17.3, based on 7.17.2. Then, SmartArray continued this in April. The goal was to have 7.17.2 effectively re-released but with fixed and working unit tests.</p><p>These fixed unit tests would provide us with a good baseline to work from, as we would need to ensure DigiByte version 8 also adhered to those same tests, and wouldn’t break the consensus inadvertently before whatever upgrade-point. However, with going up a major version, and the plan to hard-fork and bring in a new algorithm means that the tests would have to be modified regardless.</p><p><strong>Clarification:</strong> Hard forking basically means that previous clients won’t work after the fork-date, not specifically that the upgrade is contentious. For example, replacing SHA256 with ProgPoW, is a “hard fork” because 7.17.3 and 7.17.2 don’t understand the hashes generated by the ProgPoW algorithm.</p><p>However, basically all of those who were previously in the now disbanded DigiByte 8.21 channel were all in agreement that we needed baseline to work against, with the exception of Jared who has stated that he doesn’t feel 7.17.3 should ever have existed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/509/1*BkS0XbNQFV-nizToOyl0Fw.png" /><figcaption>Jared clearly mad about 7.17.3 shipping</figcaption></figure><p>Yoshi volunteered to carry on with fixing up all of the other unit tests, and this was all done in April following the new development process, as Pull Requests with independent reviews before accepting the code.</p><p>During this time most of the unit tests were reviewed with an ACK from DigiContributor, and a utACK from GTO90. Although we should have an ACK from two people as part of the process, having one ACK and one utACK was enough in a pinch given we were unable to find anybody else technically competent to go through and review them all. This would have held us up, however, it was a concession even GTO90 was happy to make, adjusting our process a small amount so we could proceed.</p><p><strong>Allow me to explain the meanings:</strong> <em>ACK</em> (short for “acknowledged + accepted”) means “I have looked over this all, I have reviewed the code, I have tested it thoroughly myself, and this is good to proceed”. On the other hand, <em>utACK</em> (short for “untested acknowledgement”) means “I have not tested this at all, but agree with the principals behind this that are being proposed”. This is roughly enough the industry standard for these meanings.</p><p>Why is this important?</p><h3>The infinite supply issue</h3><p>Jared had already disappeared again since the January events, a move not uncommon for him. However, he returned halfway through the unit tests being completed to ACK just two requests, one of which was the fabled infinite supply issue:</p><p><a href="https://github.com/DigiByte-Core/digibyte/pull/33">Refactor Subsidy Code by SmartArray · Pull Request #33 · DigiByte-Core/digibyte</a></p><p>You see, it was very odd for Jared to be ACK’ing code (Meaning it had been tested), when he’d recently mentioned he had broken his development environment on his Mac. He also confirmed to ycagel when asked shortly thereafter that he never actually reviewed the code that SmartArray had contributed.</p><p>However this really came back to bite him when it turns out this was the code that he had “reviewed”, that confirmed there was actually an infinite supply for DigiByte (not capped at 21bn) and that the supply curve was actually VERY far off what it should have been (emitting 90DGB in 2035, not the near-zero expected).</p><p>Despite asking for where the 21bn supply-cap was in the code, Jared was unable to show this. Even though there were now copious amounts of people stating this was an issue, he blindly denied it, and nobody else who had looked into things could find the supply-cap. Jared attempted to state that there was no hard proof, though SmartArray had already contributed that:</p><p><a href="https://github.com/DigiByte-Core/digibyte/issues/20">Invalid Supply Curve · Issue #20 · DigiByte-Core/digibyte</a></p><p>This GitHub “issue” (which Jared was pointed to, countless times) had both the code where the issue was, charts showing the supply curve, detailed breakdown of the issues and more:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*JZMbKdEkWYBMlUgOWTVZ_Q.png" /><figcaption>Pull Request 33 that Jared ACKd, which had a direct link to all of Yoshis breakdown / charts</figcaption></figure><p>All of which Jared “allegedly” reviewed when he ACK’d Pull Request 33.</p><p>Clearly not.</p><p>You see, Jared had been in such a hurry at the time to be able to say he contributed to 7.17.3, that he hadn’t actually realized what he was doing, and the code that he was acknowledging and approving. He has later since stated “I was simply trying to show gratitude” amongst other changes in his story, none of which are at all related to the industry standard meaning for “ACK” when it comes to reviewing code.</p><p>Unfortunately, despite Yoshi, Barry and Matthew all acknowledging the infinite supply issue, not to mention other developers who had never been involved with DigiByte were able to see the issue very quickly, it was not enough for Jared and he consistently told his Twitter followers the contrary.</p><p>Jared outright denied this was an issue until at the end of July when he finally changed his tune, but instead, implied this was something miners can bypass with a single line change:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*hPP72_ELNhBEeotvOcmiyQ.png" /></figure><p>Which is crazy because the supply-cap + emissions curve IS a consensus level change. This was simply an attempt to discredit the fact that me, a non-developer, had managed to use basic arithmatic to re-add the maximum 12bn supply cap back in, now meaning we only needed to have the supply curve smoothed once more as <a href="https://github.com/DigiByte-Core/digibyte/pull/8">Matthew had done the math for in January</a>.</p><p>Jared unfortunately went through and removed all of his Tweets related to the matter, prior to disabling his own Twitter profile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cxrK9r-Zz2x3qlamZIjjrQ.png" /><figcaption>The release of DigiByte 7.17.3</figcaption></figure><p>Still, despite all of this on the 13th of May, we managed to get DigiByte version 7.17.3 out the door, with help from js555 and ycagel, SmartArray and DigiContributor.</p><h3>Where is DigiByte 8 then?</h3><p>Following the release of DigiByte version 7, nothing at all happened for several weeks.</p><p>GTO90 had setup gitter channels back in the start of May, and Jared finally joined 6 weeks later in the middle of June. It was dead though, no discussion was happening, no progress was being made.</p><p>Jared was still missing from anything coding related, aside from causing drama over his inability to acknowledge the infinite supply issues. Nobody else was commiting any other code.</p><p>A simple one-line update / fix from Jolly-Pirate had gone unacknowledged for weeks, until I specifically mentioned to SmartArray I had checked it on the day it was submitted and it was fine. That was when he also checked it over:</p><p><a href="https://github.com/DigiByte-Core/digibyte/pull/50">Update Qt 5.9 source URL by Jolly-Pirate · Pull Request #50 · DigiByte-Core/digibyte</a></p><p>Nothing was happening, so I figured in July if nobody was going to do anything, again it’d fall to me to push things forward and so I’d ask Barry again if he would finish off version 8.21.</p><p>Barry had already started it, but, had stopped all the way back in January when he was asked by all the non-technical people in the aforementioned groupchat.</p><p>Cue the <a href="https://josiah-digibyte.medium.com/lets-talk-about-digibyte-v8-fundraiser-8960dc00b512">fundraising for version 8</a> on July 7th!</p><p>This however caused further problems when ycagel decided to write a message from the DigiByteCoin twitter page specifically directing people away from the fundraiser, stating that the “official” fundraisers took place in Gitter, as did discussions around development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/335/1*_YFFnVSaCSvUIJXb9tvxRw.png" /><figcaption>DigiByteCoin intentionally stiffling development progress</figcaption></figure><p>Regardless of this intentional stiffling from DigiByteCoin, and from Jared (who was actively re-sharing the “don’t support Barry” message), funds were raised and a few thousand in DigiByte was reached after a week.</p><p>This really seemed to… well, shall we say “motivate” Jared? Given he immediately took the DigiByte code and began, <em>again from scratch</em>, <strong>on his own</strong>.</p><p>At no time, despite knowing fully-well where all the existing code was already (On the DigiByte-Core GitHub no less), despite knowing Barry was on Telegram, regardless of the fact many in the community had just contributed to pay Barry to get a Pull Request for version 8 ready, did Jared ever reach out to Barry about any of the code / work already done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*SvnCuBM6bOIAE-Zpa59mcQ.png" /><figcaption>Jared going to give 2 weeks of 110% focus on DigiByte Core Protocol</figcaption></figure><p>On the 21st of July, Jared announced he would be taking two weeks of full-time work to give “110%” effort towards DigiByte Core. Jared actually gave part of 4days, before he gave up (or at least, has stopped with any commits).</p><p>Barry has done most of 8.21 already, and the work is still further than the current state of Jareds (which is predominantly SmartArray) at this point. I’ve even posted side-by-side screenshot comparisons:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nbUPX3Kq1Y1Ds0ifEpEkKQ.png" /><figcaption>Jareds on the left, fails. Barrys on the right, builds just fine.</figcaption></figure><p>Again despite Barrys code being online at github.com/digibyte-project/ to use / work with / help with, Jared instead decided to work on his own.</p><p>So we now have Jared, doing the very same thing he got mad at Barry for doing: Forking the code, working on it, and trying to get a pull request ready.</p><p>We now have Jared, doing the very thing he got mad at me for doing: Giving people an update on where development was happening, before a pull request had been made back to DigiByte-Core organization.</p><p>We now have Jared doing the very thing he got mad at Barry for doing: Nobody else aside from SmartArray looking over the code prior to the pull request being made.</p><h4>You know what would have been better a better solution from Jared / DigiByteCoin?</h4><p>If they <strong><em>really</em></strong> needed that history in the same branch, given Barry had already done this twice with DigiByte in relation to BTC 0.20 and BTC 0.21, would have been for them to reach out to him (or me even) and say “Hey can we contribute to this fundraiser (<em>for the first time</em>) and ask Barry if he’d be willing to do it as a merge rather than a rebase?”.</p><p>No such luck though.</p><h3>Where does this leave us?</h3><p>Well that’s a really good question. As of now, Jared has created a second codebase that he’s been super lucky somebody else has managed to finish off . After the 26th of July, SmartArray has <strong><em>very clearly done most of the work </em></strong>(And we’re lucky he’s such a kick-ass developer).</p><p>We’d fundraised for Barry who’s put some more time into it and get things finished off with the 8.21 codebase he’d been working on, but it’s pretty clear at this point Jared / GTO aren’t interested in that and are instead hiding behind their new rules that have come in to play <em>since after</em> Barry did most all of the work. Despite this, the version of 8.21 that Barry has been working on has ProgPoW, RandomX, lowered memory requirements, startup optimizations, sync improvements and more, compared with what Jared has done.</p><p>A lot of this stems from the issue that Jared and GTO90 don’t want to change branches to look at commit history. You see we have some fundamental problems with DigiByte Core at the moment that we know of:</p><ul><li>Infinite supply curve (they’ve not merged in my fix yet)</li><li>Supply emissions are skewed</li><li>Users aren’t able to send from older wallets</li><li>Fee guesstimates are not working</li></ul><p>This stems from the fact that over the years we’ve merged and merged and merged and merged, without reviewing the code. Talking with both Barry, SmartArray, GTO90 and DigiContributor, they all agree that the <em>current DigiByte code</em> needs reviewing. We’ve found issues, there’s likely more we don’t yet know about.</p><p>So there’s two ways of going about these upgrades: Rebasing, or merging.</p><p>Here’s the trouble: We have limited developers, limited talent, and limited hours. We all agree on that. What we don’t agree on is what to do with the 7.17.3 codebase.</p><p>We have two competing theories:</p><ol><li>Take Bitcoin Core 0.21 (or v22 now) and rebase off it. This is where it’s the Bitcoin codebase is taken as-is and used as a sound starting point. Then, we bring in ONLY the neccessary changes to make it “DigiByte”, getting rid of a bunch of guff and outstanding issues in the process. This would require a review of JUST the changes, and the parts that make DigiByte “DigiByte”. Developer history would be in a separate branch and require a 5 second change to “look it up” (Even better, if you really need, keep a separate terminal window open with it and just alt-tab).</li><li>Take DigiByte 7.17.3 and merge each patch that’s gone in to Bitcoin 0.18, 0.19, 0.20, 0.21 and then 22, leaving everything in DigiByte still in there, including the developer history (with the benefit of requiring no additional time when referencing). This would mean that all of the code, across the board needs reviewing, every single line in every single file, including all that’s being changed with merging-in Bitcoin to ensure that how it was done did not bring in any inadvertent issues. It would also require reviewing all of the DigiByte code too, both historical and current, which is where the majority of the time would be spent.</li></ol><p>So option #2 will clearly take a LOT longer up-front, there’s literally millions and millions of lines to go through of both DigiByte and Bitcoin codebase, as opposed to only reviewing the “DigiByte” side of things.</p><p>For reasons I cannot grasp, this is the hill that GTO90 and Jared seem to want: to die on: Rather than changing git branches and checking the git history, they would rather spend far more hours doing a merge instead of a rebase, and then countless more reviewing <strong>every single line</strong> (IF it even happens) of code that goes in to DigiByte and that has historically ever been in it.</p><p>When we have other developers who’ve done the work and are fine with that commit-history being elsewhere, it’s clearly not a requirement for contributions from people.</p><p>In the Gitter discussions, DigiContributor seemed to agree with Barry and I that rebasing did make sense. SmartArray has also said that while a rebase isn’t without issues it’s still potentially a good idea.</p><blockquote>So we’ll likely have a completed “version 8” which is still realistically version 7.22 at that point, given there’s no changes aside from bringing in Bitcoin Core updates. There’s none of the RandomX, none of the ProgPoW, none of the updated Odocrypt, none of the aforementioned performance enhancements. Those are still all absent from Jareds repository despite being mostly finished in Barrys.</blockquote><p>But it’s clear at this point to me that it’s Jareds coin, and nobody is willing to speak up against him, which is why I’ve decided that I’m stepping away.</p><p>We tout decentralization of mining, despite it being more and more centralized every day.</p><p>We tout security, despite the fact that SHA256 is a present and immediate risk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/1*jjsO8-vnmN9UxAadgRXfZw.png" /><figcaption>Jared on the suggestion we replace SHA256</figcaption></figure><p>We tout being forward-thinking, but Jared roadblocks everything that he’s not done directly himself. We’ve had just two unique upgrades in the last almost 6 years now: Dandelion &amp; Odocrypt. Everything else like Bech32, SegWit, they’re all merged from Bitcoins existing released codebase.</p><p>So until Jared actually steps away and allows the project to flourish, I’ve decided I’m no longer interested in humoring his facade.</p><p>I don’t know what will happen with the ProgPoW and RandomX work, I’m truly sorry. I don’t know what will come of the beautiful new branding / logo that spiral created for us that would truly help bring some refined branding and a glorious new styling to DigiByte.</p><p>Perhaps Jared can finally get down from his high-horse and talk about the code with Barry like he should have almost a year ago now. But I doubt it.</p><h3>Timelines as promised</h3><p>So here’s a longer timeline of all the work since the DigiSpeed upgrade which I mentioned previously, was the last time prior to Odocrypt we had “new” code in DigiByte:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FCuEC0jmUw0oJ4mDdELP_Q.png" /></figure><p>And a more zoomed in one for the last few months, if anyones wondering why things have been taking so long (Hint: Every time Jared returns and throws out anything that was done without him):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fSubyd9t8FMowU6YXFM3fQ.png" /><figcaption>A more zoomed in timeline</figcaption></figure><p>Barry stopped working on 0.21 when he was asked by js555 in January, pending the development process decision. Even once that had been done in April, Barry started to help with Unit tests but had other day-job commitments that prevented his full-time attention.</p><p>Still, Barrys code remained online, and Jared could have helped with it at any time. He could have pulled it, found the code compiles, and then helped him with the last few fixes which we saw I’d told him needed addressing in the screenshots above. The whole rebase vs merging has only come about in the last couple of months, it was never mentioned back in January.</p><p>Instead, <strong>twice now</strong>, Jared has decided not to play with others, even though myself and SmartArray had already been working with Barry on things.</p><p>So it’s pretty clear this is “Jareds coin”, and until that changes, well I guess that I’m out.</p><p>Nothing has changed in the last 8-odd months, people still pander to Jared. Nobody will call him out. Nobody else questions him. When you do, at point blank, he’ll ignore you, make things up, or go on the attack (and ignore the issue):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*BKTodfyRxYPQzZPnVtROHA.png" /><figcaption>Asking Jared about his own “better” version of 8.21 after the same time as Barry’s, which did compile + work</figcaption></figure><h4>Maybe one day that will change?</h4><p>Maybe one day DigiByte will realize the aspirations of being truly forward-thinking?</p><p>Maybe one day DigiByte will actually sort the gaping security issues?</p><p>Maybe one day DigiByte will genuinely be welcoming of new people, and will actually collaborate with them?</p><p>Maybe one day DigiByte will fix the mining that grows more centralized with every day?</p><p>Maybe one day DigiByte will have more brand recognition, and won’t be confused all the time with Dash as it is currently (probably why DigiByte fell from the Top100 briefly in July ’21 while Dash has remained stable in / near the Top50)?</p><p>At least I can say: <strong>I tried</strong>. I tried really damn hard!</p><p>I’ve been here for the last two years trying to push things forward despite Jareds predominant absence. Jared hasn’t pushed anything forward, nor has he contributed anything aisde from 4-odd interviews in those same two years. He’s stiffled progress at every step that he can.</p><p>One day I hope DigiByte can proceed without him pulling the strings, calling the shots, roadblocking all progress. Until that day, I wish the DigiByte community the best, but I’m out.</p><p><strong>And for the record</strong>: Jared was told about the vulnerability with SHA256 April 5th, 2018. The very vulnerability that permitted the DigiByte blockchain to be doublespent on numerous times in mid-late 2018.</p><p>I came to Jared on July 31st to advise him it looked like DigiByte had been double-spent on earlier in the month (which I noticed while I was reviewing the Orphans chart for a Medium article I was writing). Jared spent the next week trying to claim that it was a Sybil Attack, even sending me back to exchanges to tell them that, because he refused to acknowledge the issue (sound familiar in 2021?):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/487/1*2m5du9sGbiZwk0yIWCcL-A.png" /><figcaption>Nothing is more important than having a secure network, safe from double-spends and 51% attacks 😡</figcaption></figure><p>The reality is there was nothing else going on at that time, and that too was made up by Jared. You can <a href="https://github.com/digibyte/digibyte/commits/6.16.3">go back and look over GitHub</a> even.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*fRWiGavI2ALhyL-toeocrw.png" /><figcaption>Jared even sent me this screenshot confirming he knew it was broken back in April 5th 2018</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/714/1*_AlETJigmwWSY60WMgvZZw.png" /><figcaption>Jared replied, but then, ignored it…</figcaption></figure><p><strong>For the record:</strong> Rebasing would likely have avoided that in the first place, where merging increases the chances of these kinds of issues.</p><h4>This is also why ALL code, existing and new, needs reviewing.</h4><p>You’ll note that despite these messages being in April 2018, work on 6.16.3 didn’t start to happen until August 6th, a whole week after I told Jared there were double-spend issues occurring on the blockchain: <a href="https://github.com/DigiByte-Core/digibyte/commits/archive/6.16.3">https://github.com/DigiByte-Core/digibyte/commits/archive/6.16.3</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/493/1*FA__ikqlwaKkkDwzCeNLmg.png" /><figcaption>Jared on July 31st 2018 trying to say there was no issue still</figcaption></figure><p>Now naturally when I told Jared that SHA256 was a major issue in December 2020, and I’d done the math to prove it, he ignored it and tried to say I was crazy. He still refuses to acknowledge it to this day, and we know how well that went last time, despite me bringing it up regularly:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*35l10PO0w6LhlRz69AiSwA.png" /><figcaption>Jared doesn’t understand how MultiAlgo / MultiShield works</figcaption></figure><p>Just remember, Jared doesn’t actually understand how MultiAlgo nor MultiShield work, we had Matthew correct him earlier this year (Matthew was right, in this video @ 2:14:07):</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FjyFjz_MYSD0%3Fstart%3D8047%26feature%3Doembed%26start%3D8047&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DjyFjz_MYSD0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FjyFjz_MYSD0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/62704dca32b6acdf089f17504d04e217/href">https://medium.com/media/62704dca32b6acdf089f17504d04e217/href</a></iframe><p><em>So good luck with dealing with Jared, because I no longer can.</em></p><p><strong>As such, I don’t think I can be around while he’s participating and carrying on with all the lies and misdirection.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=186e9a499647" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A new design to showcase the importance of DigiByte]]></title>
            <link>https://josiah-digibyte.medium.com/a-new-design-to-showcase-the-importance-of-digibyte-ca948bbc56da?source=rss-714d4d4beb3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca948bbc56da</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[digibyte]]></category>
            <dc:creator><![CDATA[Josiah Spackman]]></dc:creator>
            <pubDate>Wed, 21 Jul 2021 11:20:44 GMT</pubDate>
            <atom:updated>2021-07-21T11:20:44.429Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m thrilled to be able to show you a new design for DigiByte that will help thrust the digibyte project into the future, with a fresh new look, standing out among blockchain projects.</p><p>DigiByte (or rather the suggestion is now “digibyte”) is going to be cemented as a sound project representing immense staying-power with version 8. As such, a number of community members are eager to ensure that we have a brand, logo, and accompanying guidelines so the world will see digibyte as the industry leader we know we can be.</p><p>I present to you, thanks to spiral, the digibyte rebrand:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vk4dAm8e5vKZrCYfKiO-ww.png" /><figcaption>The digibyte brand identity manual</figcaption></figure><p>This design will naturally be subject to the communities feedback and input as part of our contribution guidelines. As mentioned in my last Medium article, Barry has advised he is happy to work on an implementation of this for the digibyte Core wallet, and will include it for consideration by the community.</p><p>As part of this submission, spiral has written a complete guide document for the digibyte community! It includes everything from the logo itself, how to use it, spacing, why the design was done this way, the colors, recommendations and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/1*BBvtF1RZjgALX5OmNxwhkQ.jpeg" /><figcaption>Design suggestion for a digibyte cap</figcaption></figure><p>I am confident you will appreciate the vast amount of effort that has gone into this from spiral in making these concept images, guidelines and more. A big thank you to Damir too for the input, who you will no doubt remember submitted the digibyte mobile wallet designs. I guess we should eventually look at the wallet design again too 😅</p><p>A little bit of history: This design submission has actually been in the works since 2019 when the new design ideas began forming, and I was contacted with an earlier design iteration of this. With the talks about digibyte version 8, both spiral and Damir contacted me again with an updated and more comprehensive suggestion fo the digibyte community to adopt.</p><p>As it will probably be the biggest and most important release that digibyte has ever had, the suggestion was that it makes sense to have a fresh, clean, and vibrant design to accompany version 8. This suggestion does exactly that, simplifying “DigiByte” to “digibyte”, dropping the tagline, and focusing in on the name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TYiGRQyZWxu9r6Y36wKckQ.png" /><figcaption>Just “digibyte”!</figcaption></figure><p>This is a sharp departure from the digibyte of old, and embraces a new harmonious future that will be able to stand out even with the sea of blockchain projects.</p><p>Along with the design we have been provided some mock-up images for how the likes of Twitter could look:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/1*G5sHQrg5jB2RDfBsArdrSw.jpeg" /><figcaption>A mock-up of how the digibyte Twitter page could look</figcaption></figure><p>We have a number of icons too for DigiByte that can be used, which I am including here for a quick look. However, I would encourage you to read the full guideline document that has been created:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/1*K5diK4KaISYnhS2aEKIw_A.jpeg" /><figcaption>Button icons for digibyte</figcaption></figure><p>You can see the whole document for yourself by going to the GitHub repository that has been created: <a href="https://github.com/spiral-ing/digibyte">https://github.com/spiral-ing/digibyte</a></p><p>Direct download: <a href="https://github.com/spiral-ing/digibyte/raw/main/digibyte%20brand%20manual%20guidelines%202021.pdf">https://github.com/spiral-ing/digibyte/raw/main/digibyte%20brand%20manual%20guidelines%202021.pdf</a></p><p>I am sure you will join me in thanking spiral for their time here in creating this for us. As per always, it will go through the contribution guidelines for people to accept / place feedback on when we have a pull request for the Core wallet that includes this design.</p><p>I also want to take this opportunity thank spiral for the time spent. I’ve also included their digibyte address (which is in the document too), and have started the donations with USD$100 worth of digibyte too, as a starting point:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OnITPoqNIkuWAp0rwxG1zQ.png" /><figcaption>DPosQHtKxAVeuiH9DX43XgAUfvrUakZt7e</figcaption></figure><p>I would encourage you to also donate to them and thank them for their time, effort, ideas and input on how we can truly take digibyte to the next level!</p><p>There have been a few initial designs for some merch too and I can’t wait to see stores offering this kind of thing:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/1*7twmwqYbUk7qm51qudQ9sA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*5Hw4yd6RT3p5cjTa1-UDtw.jpeg" /><figcaption>Some digibyte cap ideas</figcaption></figure><p>I’m not much of a cap person myself, but if those were beanies I’d be buying them for sure!</p><p>We’ll also be working on a website for digibyte v8 too, that includes information about digibyte, the changes in version 8, and the website will be built with this new branding in mind. More details will come in due course, more images for you to use and share, more ways for you to get excited about digibyte! I’ve even heard there may be a telegram sticker-pack coming too.</p><p>Let me know what you think, and please again join me in thanking spiral and Damir for their work on this!</p><p>Here’s to a bright future for digibyte, and a slick new logo, theme, and brand for us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca948bbc56da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s talk about DigiByte v8 + fundraiser]]></title>
            <link>https://josiah-digibyte.medium.com/lets-talk-about-digibyte-v8-fundraiser-8960dc00b512?source=rss-714d4d4beb3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8960dc00b512</guid>
            <category><![CDATA[randomx]]></category>
            <category><![CDATA[digibyte]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[progpow]]></category>
            <dc:creator><![CDATA[Josiah Spackman]]></dc:creator>
            <pubDate>Wed, 07 Jul 2021 08:57:44 GMT</pubDate>
            <atom:updated>2021-07-07T08:57:44.738Z</atom:updated>
            <content:encoded><![CDATA[<p>At the start of the year it became clear that DigiByte needed to elevate it’s game and handle development better than had been in the past, with more accountability and transparency. This isn’t to say we believe the previous way was causing any problems, and DigiByte has done well for itself over the previous 7 years, but more importantly this was an opportunity to further improve the decentralization and trustless nature of the blockchain, adopting some industry best-practices, and spearhead DigiByte into the future.</p><p>However, this came at the expense of delaying RandomX, ProgPoW and a number of other things that were already in the works. I want to talk a little about where things are at now that we’ve got this new process in-place and DigiByte v7.17.3 out the door.</p><h3>So, let’s start with RandomX / ProgPoW</h3><p>Late October 2020, I was contacted by Barrystyle via Reddit who noticed we’d been struggling with the RandomX + ProgPoW implementation, and that there was the possibility of a bounty for RandomX. Kristy-Leigh Minehan had graciously volunteered to do the ProgPoW implementation for us but had been having a tough time with finishing it off. Coupled with her catching COVID-19 twice throughout the year, and previous health complications, she advised that she was fine for Barry to do the implementation there for ProgPoW. I’m still personally grateful for the time she’d spent, but more importantly I’m glad that she’s been looking after her health.</p><p>So towards the end of 2020 Barry began implementing RandomX + ProgPoW, originally on the 0.19 codebase that Jared &amp; Gary had been working on back in Jan 2020. Before long, it became clearer it would be better to do it from a fresh base of 0.20 which had come out in the middle of 2020 (June if memory serves me right), as the DigiByte 8.19 was in a very rough state, partly due to the myriad of upstream changes. It was not compiling / building, and hadn’t really been touched much for the better part of 9 months, save for some fixes Yoshi had been slogging away at. As such, Barry advised me he was happy to work on 0.20 for DigiByte as part of the bounties for RandomX &amp; ProgPoW.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*-XyqtGzUU3WfUneGpfedCA.png" /><figcaption>Work on RandomX in the codebase, just, coz picture…</figcaption></figure><p>Work was progressing well towards the end of 2020, with the DigiByte Core compiling + running happily, alongside the incorporation of a number of other major improvements. For example, in Bitcoin 0.18, they removed OpenSSL from their codebase. That has no major impact on Bitcoin, however if you look at the likes of Litecoin and other Scrypt-based projects, the OpenSSL libraries are used as part of the Scrypt hashing algorithm, meaning it’s not as easy to just “remove it”. Barry had rewritten the Scrypt hashing algorithm fully using Bitcoins libsecp256k1, which in and of itself is a brilliant feat, and this was working in the 8.20 code back in November / December! In December 2020, I’d paid out the bounties for RandomX &amp; ProgPoW to him, as the work on the algorithms was all but done, with additional minor fixes needed on a stratum server and the final commit alongside the 0.20 codebase once it was in a happier state.</p><h3>The DigiByte v8 development</h3><p>In January, the 0.21 release of Bitcoin Core came out, and Barry asked me if it was worth us releasing from 0.20 given it was no longer the most recent. A fair question! Couple with the improvements from Schnorr + Taproot that the DigiByte community had been talking about for quite some time now (A year prior I’d given a <a href="https://www.youtube.com/watch?v=eLKG8iMxlAs&amp;list=PL8xahtUlbHa92qQhne1Iu1YFMQBC45RyJ&amp;index=2">presentation on it, in Feb 2020</a>) were being prepared with the 0.21 codebase in-mind. As such, implementing Schnorr + Taproot would be far easier based on 0.21 rather than 0.20. On the 15th of Jan, Barry began to work on 0.21, which included some additional “fun” given the way Bitcoin now rebroadcasts transactions conflicts with Dandelion. Despite this, after just a couple of days in between his other jobs, it was working. He and I had it running on the network, which was when I made <a href="https://twitter.com/dgb_chilling/status/1352849550751408129">several tweets around the time</a> showing it syncing.</p><p>However the other developers rightly raised that we needed to have some better checks in-place to ensure that we wouldn’t inadvertently break DigiByte as we’d done in the past with the likes of 6.16.5 not syncing from scratch. It’s a fair point, DigiByte is a billion-dollar blockchain, so we need to be smart about bringing in such big changes, be it merging / rebasing from Bitcoin, algorithms etc.</p><p>We needed to ensure that DigiByte remained “DigiByte” and that this new client based on the new Bitcoin Core codebase still functioned perfectly in the interim, right up until our first fork-date for v8. It also provided opportunity for us to review the existing code, and address some of the things that have been discussed in <a href="https://gitter.im/DigiByte-Core/protocol">Gitter</a>, including fixing the supply-curve issue I raised last year (Big thanks to Matthew especially for his help with fixing the code there, and Yoshi too for his input) amongst other things.</p><p>This all highlighted we needed to have our Unit Tests fixed and operational, which had been neglected and were in definite need of some loving attention. These were something that Barry was going to be also dealing with for DigiByte. However, after he’d fixed the first few Unit Tests for DigiByte he was unable to wait for the feedback / acceptance of those and got busy with some other jobs of his own. As such, we’re very grateful that Yoshi stepped up and completed the remainder of the Unit Tests (I’d like to also raise from $DGB for Yoshi in the future as well). These Unit Tests now all test correctly, and make sure the code that makes DigiByte “DigiByte” is behaving as expected. Though, any other additional things (Say for example if we show a specific button in the UI) which don’t affect consensus or expected protocol behavior are not tested.</p><p>We then got the release of 7.17.3 completed and out the door (big thanks to Yoshi / Gary and all others involved in those few days of testing / building). This 7.17.3 release contained all of the functional Unit Tests, so we have a solid testing base to now match against with the DigiByte v8 process. This is important because we know that DigiByte is still “DigiByte” up until the fork-date, at which point all nodes will be reorienting anyway, and using the new definition of “DigiByte”.</p><p>Now, no matter what, DigiByte <strong><em>needs to do a hard-fork</em></strong> so that we can resolve the issue with the supply-curve as discussed under <a href="https://github.com/DigiByte-Core/digibyte/issues/20">Issue #20</a>, and again a big thanks to Matthew and Yoshi for helping there with getting to the bottom of this after I raised the problem in late 2019. It makes sense then, if we’re doing one hard-fork, to also have the others (Algorithm replacements) done under the same code-release. If we stagger the forks under the one “v8 release” it will serve two purposes:</p><ol><li>Provide sufficient time in between implementation of RandomX / ProgPoW for MultiShield difficulty to even out and minimize any risks of attack attempts</li><li>Greatly minimize the effort from exchanges / wallets / service-providers who would have to upgrade every single time otherwise, and risk having some of them dropping support for DigiByte if we were to do too many “mandatory” upgrades of the Core wallet.</li></ol><p>Otherwise if we were to try and do a single release each time for each upgrade, there’s the very real possibility of exchanges / services simply deciding they don’t want to accept / support DigiByte, as we have seen happen with a small number in the past.</p><p>This brings us to the important question:</p><h3>Where-to from here?</h3><p>Well, we need to finish off DigiByte v8 based on 0.21, and the sooner we can do this the better it is for addressing the supply-curve. This is because as of right now the block-reward subsidy will drop from 84 DigiByte to 1 DigiByte in 2035. That’s a pretty sharp drop (Worse than any halving event) and after that it will carry on with an infinite supply (also not good). This needs to be done ASAP because the longer we kick the can down the road, the harder the adjustments are going to have to be, and we can avoid that by being prudent with our time.</p><p>Now as mentioned above, Barry has already done a lot of the leg-work so far and it’s largely operational. We as the broader DigiByte community need to simply finalize a few things such as the block-height we want to activate the likes of the supply-curve changes at, ProgPoW, RandomX, Schnorr / Taproot (Schnorr etc can technically just be done at the same time as any one of the other changes). This is also why I’ve mentioned in almost every single video that people should be subscribed to GitHub so they can discuss this. There’s also the <a href="https://gitter.im/DigiByte-Core/protocol">Gitter channels where it can be discussed also</a>.</p><p>However, as we’ve basically gone from it starting with 0.19, then to 0.20, and now 0.21, I wanted to do a bit more of a fundraiser to send funds to Barry for the completion of this, and so that he can dedicate some time away from his other usual projects. I’ve grabbed his DigiByte address which <a href="https://github.com/digibyte-project/info">he’s put on GitHub</a>, and I’d like to see us donate some DigiByte over the next few weeks to him towards the following:</p><ul><li><strong>Finishing 0.21, with the working unit tests, Dandelion changes implemented, and pull request to the DigiByte-Core/DigiByte repository made. This is what most of the donations are for / about.</strong></li><li>Ensure that RandomX is operational and the appropriate stratum modifications available, and documentation / notes around implementation.</li><li>Ensure that ProgPoW is operational and the appropriate stratum modifications available, and documentation / notes around implementation.</li><li>Implementation of the supply-curve fixes.</li><li>Have a date set for Schnorr + Taproot set to the same as the supply-curve changes.</li></ul><p>I also just want to highlight that there’s also a few other things that Barry has already helped with of late too:</p><ul><li>Implementing memory improvements from Yoshi</li><li>Improved sync times (I’ve done a full sync in under half the normal time)</li><li>Significantly improved launch speed (Which is great if you’re testing things regularly)</li><li>The full implementation of Scrypt in libsecp256k1</li><li>Improvements to MultiAlgo block generatetoaddress on testnet</li><li>Added algorithm stats RPC call</li><li>A large amount of the DigiByte-specific codebase has being refactored into a segregated area which will allow for much easier improvements / iterations upon in the future</li></ul><p>In addition to this, Barry has said that he’d be willing to also do some GUI work for us and refine the themes that are currently there but were never fully completed (There’s a lot of contrast issues and places where the themes weren’t quite polished off), as well as fixing up a few of the other issues such as the inability to send from some of the earliest wallets created on DigiByte when the node is sync’d past a certain point.</p><p>So I’m aware that we’ve already sent DigiByte his way last year for the algorithm implementations etc, however, given the regularly moving target this has been through no cause of his own, I want us to arrange for a little more to help get this over the line and as a bit of a thanks to him. This is more specifically for the work around DigiByte v8, both 0.20 / 0.21 and the additional features too. If you’re behind this, I’d encourage you to donate directly to him too: <a href="https://github.com/digibyte-project/info">DGBaZ7bGFn6uifeSYp4wiAY4H4aWRpNCoz</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*2uoWV3L8XWIHi-5CCzYL6A.png" /><figcaption>Donate directly to Barrysty1e</figcaption></figure><p>I’ll be starting off the donations too with <a href="https://digiexplorer.info/tx/616d2425201d67f1c9988f768f216b42fab4ccf52b45d9e0ce4705bec2eab587">~USD$150 of DigiByte</a>.</p><p>I hope you will be joining me and doing likewise, with any amount big or small. I’m eager to see this finished, get it into the GitHub and get v8 ready to roll! There’s so much packed into this already, I’m very excited about the future of DigiByte, and this is a perfect opportunity to have your say and be involved in the production of the 8th major version of DigiByte!</p><h3>How will this be delivered / what will successful completion look like?</h3><p>The primary part here is the completion of an 0.21 based DigiByte v8. This will be something you can compile and test alongside us by going to <a href="http://github.com/digibyte-project/digibyte">github.com/digibyte-project/digibyte</a>, where the branches / improvements being worked on are visible.</p><p>Over the coming weeks as this is finished off, preparation will be made for a pull request against the <a href="http://github.com/digibyte-core/digibyte">existing DigiByte repos</a>. This will include information around the way that ProgPoW &amp; RandomX have been implemented (such as details around the RandomX seed etc, and why it was built the way it was), the moving of the DigiByte-specific parameters into src/digibyte/, some of the testing details, and references to where the upgrade block-heights can be adjusted. For the non-techies, this is basically the same as somebody offering up their code changes and saying “Here’s what I’ve been working on, hope you like it”. All going according to plan, this should be a viable release in and of itself in that state.</p><p>Following this Pull Request, the other DigiByte reviewers will then be able to not only provide feedback, amendments, and other suggestions to the code, but further tweaks / improvements to it as well should there be a desire from them / the community to incorporate or remove anything else from the release of DigiByte v8.</p><p>After the review process, we should be good to go with DigiByte v8! That will naturally mean the fork-heights are finalized and then the community (myself included) will need to reach out to exchanges / wallet providers etc to ensure they’re running this latest release in preparation for the upgrades. This is something I’ll talk more about closer to the time, as a group of us have done this several times over in the past contacting exchanges.</p><p>Should you have any questions about this process, please feel free to reach out to <a href="https://twitter.com/barrysty1e">Barry</a> or <a href="https://twitter.com/dgb_chilling">myself</a> on Twitter, or maybe shoot him a thanks for all that he’s done thus far on the v8 release / algorithms.</p><p>Also, feel free to join in the <a href="https://gitter.im/DigiByte-Core/protocol">Gitter channels</a> to ask any questions about the protocol etc and liven the place up a little. Keep in mind that this is specifically just for development-related purposes, not for general support / questions or any form of speculation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8960dc00b512" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How “green” is DigiByte?]]></title>
            <link>https://josiah-digibyte.medium.com/how-green-is-digibyte-6e2ad24a6308?source=rss-714d4d4beb3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e2ad24a6308</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[proof-of-work]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[digibyte]]></category>
            <category><![CDATA[cryptocurrency-mining]]></category>
            <dc:creator><![CDATA[Josiah Spackman]]></dc:creator>
            <pubDate>Sat, 15 May 2021 23:55:49 GMT</pubDate>
            <atom:updated>2021-05-16T02:57:19.608Z</atom:updated>
            <content:encoded><![CDATA[<p>Thanks to Elon Musk for bringing the conversation to the forefront of peoples minds again. There have been many discussions about Bitcoin mining over the years, along with Proof of Work mining, and how Proof of Stake is supposedly “better for the environment”.</p><p>What we do find is that Bitcoin miners predominantly use renewable energy sources, not just by some small margin but <a href="https://www.jbs.cam.ac.uk/faculty-research/centres/alternative-finance/publications/3rd-global-cryptoasset-benchmarking-study/">by over 75%</a>! Coupled with others suggesting Bitcoin / PoW mining is <a href="https://www.aljazeera.com/economy/2021/4/22/cathie-woods-ark-says-bitcoin-could-help-fight-climate-change">pushing forward innovation and growth in the renewable sector</a>, and it seems the assumption that Elon has put forward may be slightly misrepresented.</p><p>In fact as someone who’s previously run a small GPU farm of 120-odd GTX1060’s back in 2017 / 2018, the entire time I ran it, the energy utilized came from renewable sources thanks to local provider Meridian Energy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yJYQnH9dbUImBe348Pd4rw.png" /><figcaption>Small plug for Meridian in NZ, 100% renewable energy</figcaption></figure><p>However, not everyone has the luxury of simply “going green” with their provider of choice, and sometimes coal-burning power is sufficiently cheaper in their area, that a miner will choose it over the environment.</p><p>But I want to challenge the assertion that Bitcoin, DigiByte, and in-general “Proof of Work” is a bad thing for a number of reasons.</p><p>So let’s start with the obvious question:</p><h3>How much power does DigiByte consume?</h3><p><strong>Fair warning:</strong> Although I’ve done my best with the math, it’s still not going to be 100% accurate.</p><p>It’s actually relatively easy to get a “ballpark” estimate though.</p><p>You see, there are a few variables that we can take a well-educated guess at, based on the blockchain data itself.</p><p>If we take the difficulty for each of the 5x algorithms (Which we know because that’s how we determine the difficulty for the next block), we can use this to get approx numbers of the hashrate on the blockchain at any given point in time depending on how long it’s taking to find a block for each algorithm (5x algorithms, at 1 minute and 15 seconds average each, gives us a 15 second block timing):</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/236714b680a2a7e61b22d6b7b49e2979/href">https://medium.com/media/236714b680a2a7e61b22d6b7b49e2979/href</a></iframe><p>Using this information, coupled with knowledge on each algorithms most efficient miner (hardware):</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/08585c1adee30a2c20db4814791975d6/href">https://medium.com/media/08585c1adee30a2c20db4814791975d6/href</a></iframe><p>We can extrapolate and guess the <strong>rough</strong> power consumption (knowing that not everyone will be using, say, the M30S++ at 110Th/s from 3410w, but some might use the S19 Pro at 110.00 Th/s from 3500w):</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ec0f3b5fdb6dd352ccc82140428591ad/href">https://medium.com/media/ec0f3b5fdb6dd352ccc82140428591ad/href</a></iframe><p>Giving us a grand total of 62,407,560 watts. That’s some serious power!</p><p>What about Bitcoin though? DigiByte has 40x faster blocks, so you’d assume that all other things being equal (Well, it has just one algorithm vs DigiBytes 5) that it’d be able to process 40x the transactions, making the cost-per-transaction only 2.5%? It’s a little more complicated than that…</p><p>Bitcoin, based on a difficulty of 25046487590083, giving us a network hashrate of 163,984.52 Ph/s works out to be around 14.9 million miners, and a power consumption of at least 50,835,199,030w (50.8 TW/h). That is quite a number, approx 814x more than DigiByte!</p><p>Now all things considered, given DigiByte at the time of writing has a Market Cap of USD$1.67 billion, compared to the USD$924 billion of Bitcoin, that’s not too shabby, meaning DigiByte has more watts-per-dollar of marketcap securing the blockchain.</p><h3>So what is the (used) power-per-transaction?</h3><p>With Bitcoin, given most of the blocks are full at present, it’s relatively straight-forward to work out:</p><p>144 blocks per day (86400 / 600), at an <a href="https://ycharts.com/indicators/bitcoin_average_transactions_per_block#:~:text=Basic%20Info,26.80%25%20from%20one%20year%20ago.">average of 1985 transactions per-block</a>, gives us 285840 per-day, comes to approx 4,268 units (kWh) per-transaction.</p><p>On the other hand if DigiByte were to be suddenly “at capacity” (as BTC is), we’d be filling 5760 blocks per-day (86400 / 15). This means if we had the same txn’s per-block as Bitcoin (1985), at present, we’d be around 11,433,600 transactions per-day, at 0.13 units (kWh) per-transaction.</p><p>That is, again presuming that the hashrate and value of DigiByte didn’t increase of course…</p><p>Back in the present world though: DigiByte has done 146,259 txns over the past 10 days to give us an average of 14,625 per-day, or approx 2.5 per-block. Taking 14,625 per-day, at present, gives us 102 units (kWh) per-transaction.</p><h4>Why the massive difference between BTC vs DGB?</h4><p>Well quite simply because Bitcoin has a FAR higher value in the block-rewards, in US dollar-value, compared with DigiByte. There is also the fact that DigiByte has a 40X faster block-timing compared with Bitcoin. Both DigiByte and Bitcoin will hopefully implement Schnorr Signatures &amp; Taproot soon, which will improve the on-chain scalability, but estimates are only ~15–20% and there are no guarantees of future implementations naturally.</p><p>With Bitcoin, there is 6.25 BTC per-block, plus around 1 BTC in block-rewards every 10 minutes. This comes in at a leisurely USD$50 million a day in block reward subsidy at the time of writing (15th May, 2021 here in New Zealand).</p><p>With DigiByte, there is currently 520 DGB reward per-block, and a negligible amount of transaction-fees. This comes to USD$340k per-day in rewards.</p><p>As the price of DigiByte / Bitcoin goes up and down, so-too does the hashrate, coupled with gains in efficiency in the mining hardware etc, and this all affects the power consumed on a daily basis, and subsequently the power used per-transaction.</p><h3>Can’t we just replace an algorithm to be greener?</h3><p>Not specifically.</p><p>You see the block-rewards vs USD price of those block-rewards, are what predominantly determines the amount of hashrate a blockchain can sustain.</p><p>This is why the likes of Litecoin saw a halving of their hashrate at the same time as there was a halving of the block reward subsidy in 2019, because over the following several weeks, miners realized they could not continue to mine while receiving only half as much in USD-value per-block.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yAO_v2Tw_s6Zmw2Xdndb4g.png" /><figcaption>Litecoin hashrate, from July until December ‘19</figcaption></figure><p>The price of Litecoin also plummeted at the time, and so the hashrate of the network actually fell by 75% by the end of the year. This is why Coinbase <a href="https://blog.coinbase.com/announcing-new-confirmation-requirements-4a5504ba8d81">increased the number of confirmations required for Litecoin</a> at the end of 2019.</p><p>You see, Miners have power-bills to pay, and the cost of hardware to recoup. If mining costs them more than their power-bills, they’ve got a total of four options:</p><ol><li>Hope that the price of the coins they’ve mined increases by the time their power-bill is due (In NZ, that’s the 20th of the following month).</li><li>Hope that someone else shuts off their miners with the difficulty adjustment and that they become profitable. At least, in the case with LTC / BTC and their long difficulty adjustments. This is not applicable to DigiByte where the difficulty is adjusted in realtime thanks to the brainchild of MentalCollatz: MultiShield.</li><li>Find a cheaper source of power, such as moving closer to a power-station, changing providers, though usually anybody who’s mining with more than one or two rigs has taken the time to find the cheapest. As such this isn’t usually “an option”.</li><li>Shut off their miners themselves, decreasing the network hashrate.</li></ol><p>Now, as much as I’m a huge proponent of ProgPoW and RandomX both going through our new development process and replacing 2x other algorithms, the fact of the matter is that for the most part it’s not going to change the power consumed per-transaction terribly much, at least not by any largely meaningful factor. ProgPoW and RandomX both utilize largely consumer hardware, so the theory is that a “home” miner is less likely to care about as much direct profitability compared to for-profit semi-professional outfits, though they’re more likely to simply swap to another GPU / CPU mined algorithm instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E6s2aT8hO3O16z2b" /></figure><p>That was what I would do as a small-time miner at least with my GPU’s back in 2017 / 2018 when GPU mining on DigiByte was still a thing. I could sustain slight changes in price profitability, but there would come times when it was significantly more profitable to swap for a day or two to another blockchain before swapping back to mining DigiByte. This equilibrium was caused both by the equation of my hashrate vs network hashrate vs price of DigiByte, and also the hashrate I could attain on another algorithm vs the other network hashrate vs price of the other blockchain.</p><p>So it doesn’t really matter, there’s basically miners who are determining their profit based on the cost they’re getting their power for, and as that profitability drops based on the same hashrate vs network hashrate vs price in fiat, they’ll potentially shut off their miners, OR, look to add more / turn shut-off miners back on.</p><h3>What about HDD mining? What about staking? Aren’t these both “greener” options?</h3><p>These are both interesting ideas!</p><p>There has been a huge boost in HDD mining recently thanks to Chia, which utilizes “plots” on a hard-drive as proof of storage capacity. You take a high-speed SSD with a few hundred gigs on it, it makes the plot over the course of approx 12 hours, and then compresses it down to 100GB for you to store on mass-storage (Such as a hard drive or NAS).</p><p>The plots are different from other projects which allow users to backup + store their data on other peoples computers, as you’re not holding other users data. Rather you’re holding pre-calculated plots of information, which you’ll have to regenerate after about 5 years. This regeneration is also something to consider, especially if you’ve already burned out your low-TBW SSD.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*SmijXnZvgetyEbvYNP8yZw.png" /><figcaption>Chia mining</figcaption></figure><p>It’s something I’ve given a whirl myself, seeing as I have about 10TB on a NAS sitting spare right now, but given it’s still relatively new, I’m still unsure about the whole thing. There’s not enough information about if it’s actually “greener” long-term, though it likely is, but given the amount of hard-drives it’s eating up, critics argue it’s basically just a less-efficient staking, with a “proof of something else”.</p><p>It’s also relatively “new and unproven” at this point in the game, and seeing as security must remain at the forefront (A blockchain without security is… pointless?), it’s probably better to err on the side of caution. But, perhaps this is one to watch?</p><p>Staking on the other hand, most people will know I’m not a huge fan of. In a MultiAlgo situation it could very well have its place eventually replacing one of the 5x algorithms. However at the very least, during this “distribution” phase of DigiByte through the block-reward subsidy, I think that it’s not an ideal method for fairly distributing the DigiByte asset itself.</p><p>This is because with staking, you’ve got to have a lot of money to get more money. There’s a threshold you’ve got to meet (for minimum staking), buying $X worth of DigiByte if we <em>were</em> to do staking, in order to get more rewards. It’s great for keeping nodes online, but that’s where the cost goes to instead of to electricity for PoW: To a VPS provider.</p><p>So sure, there’s no large computation going on with staking, but it’s not without compromises to the security / distribution itself that I don’t believe are worth it (at least at this stage of DigiBytes emissions curve). That may change in the future though!</p><p>The fact of the matter is that at the moment theres around <a href="https://chainz.cryptoid.info/dgb/wallet.dws?478492.htm">12% of the circulating supply sitting on Bittrex</a> (1.8 billion DigiByte), and even Poloniex still have a few hundred million DGB. Both could stake that for themselves if DigiByte were to implement PoS.</p><p>It’s not the get-rich-by-doing-nothing scheme many portray it to be.</p><p>As such even IF DigiByte were to do staking, there’s a very high chance you’d receive very little unless you had 7-figures worth of DigiByte, and it may not be enough to cover the cost of renting a VPS to run the DigiByte node on. Only the rich would get richer and benefit from staking, whereas with Proof of Work anyone can contribute (especially if we have a CPU / GPU mining algorithm, the barrier-to-entry is almost nil, which increases both security while broadening the distribution of the DigiByte asset itself).</p><p>Implementing staking would likely be compromising on security and the decentralization of DigiByte all in one, it just doesn’t make sense, even if it consumes less electricity.</p><h3>That’s why the energy consumed is a good thing!</h3><p>It’s this consumption of energy that provides the network with security.</p><p>If I have a CPU, and I wanted to try and attack the network on, say, SHA256, I’m going to be horribly out-gunned.</p><p>This is because far more efficient hardware exists than I can get my hands on. This is why the block-reward subsidy exists, to ensure that miners have a reason to keep mining when the blocks have very little going on, especially as-is the case with DigiByte right now as the on-chain transaction volume ramps up.</p><p>We’re going to need more transactions occurring on the blockchain as we head into the future and the block-rewards decrease. Miners are going to consume power to continously secure the network. This is OK though, because this is how the network protects against malicious actors who would attempt to double-spend.</p><p>It’s also this power that prevents any central government from being able to simply “issue more” of the asset, as they can with dollars and cents. It’s what prevents any one company, even a wealthy company such as Apple or Tesla, from being able to control the network and make changes.</p><p>And all this power, is 75%+ renewable already, and pushing forward a cleaner / greener future with innovation in the electricity space.</p><p>If you ask me, the Proof of Work employed by Bitcoin / DigiByte, is not only the best way to distribute the blockchains respective assets, and at securing the blockchain, but also pushes forward other industries for a brighter future.</p><p>So yes, it consumes (predominantly renewable) energy, but it still sounds like a winner to me!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e2ad24a6308" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Continuous Integration for DigiByte and the v8 release]]></title>
            <link>https://josiah-digibyte.medium.com/on-continuous-integration-for-digibyte-and-the-v8-release-aa137679f299?source=rss-714d4d4beb3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa137679f299</guid>
            <category><![CDATA[digibyte]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Josiah Spackman]]></dc:creator>
            <pubDate>Sat, 08 May 2021 23:08:24 GMT</pubDate>
            <atom:updated>2021-05-08T23:12:05.235Z</atom:updated>
            <content:encoded><![CDATA[<p>After a HUGE effort with the Unit Tests, Yoshi has taken a lot of the prior work from Marpme_ (Marvin from Vergecurrency) that he did for us and completed the Continuous Integration setup for DigiByte. Thank you also to those who’ve taken time to individually review all of them, as part of our new Gitflow workflow process as well.</p><p>The conclusion of the Continuous Integration means every time a new pull request is made against DigiByte, not only will it do a test compile to make sure it builds, but it will also run the Unit Tests as well to ensure that the changes don’t negatively affect the fundamentals of what makes DigiByte “DigiByte”!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_0R5Ss0YsRDg1zzzvniLZA.png" /><figcaption>Testing the CI with a build “In progress - This check has started…”</figcaption></figure><p>This is a HUGE milestone for the integrity of DigiByte, and we are grateful for all those who’ve been involved with writing / correcting / reviewing the Unit Tests, as well as the Continuous Integration.</p><p>These are major steps forward for us as a project that I’m super excited for.</p><p>The question I’ve been asked lately is:</p><h3>Aren’t we working on DigiByte version 8?</h3><p>Yes. All of this has been done because the DigiByte v8 release is shaping up to be SO massive, that it made sense to ensure we didn’t miss anything inadvertently.</p><p>The earlier MultiAlgo / MultiShield releases of DigiByte may have been the biggest in terms of fundamentals, but v8 will without a doubt be the biggest in terms of lines of code changed, performance enhancements, bug fixes, feature additions, and (what is probably most dear to me) future-proofing of the project to ensure the longevity of the codebase / blockchain.</p><p>So with the Continuous Integration and the Unit Tests, we’re effectively setting a benchmark to compare against for in the future.</p><p>You see, if we inadvertently made a change to DigiByte that allowed for SHA256 blocks to be “mined” from Block 1, then we’re opening ourselves up to a world of pain and potential attack vectors. SHA256 should only valid from the MultiAlgo upgrade. The Unit Tests will ensure “Are we only permitting <em>only</em> Scrypt from Genesis to 145,000th block?”, along with other similar fundamental tests and checks.</p><p>Now that we have these Unit Tests, it means we can <strong>forge ahead with certainty</strong>.</p><h3>So what’s the plan? When do we get DigiByte version 8?</h3><p>First, we’re releasing 7.17.3!</p><p>This will be the same as 7.17.2, but, with unit tests and continuous integration sorted, and that’s basically it. There’s no further fixes / improvements, however this is going to be the foundation we use for version 8. As such, if you’ve got 7.17.2, then there’s no practical reason for upgrading to 7.17.3.</p><p>However, what you’re going to see now on GitHub is more work being done on merging the Bitcoin Core 0.21 code. This will bring in a bunch of stability improvements as well as feature enhancements (Things such as Partially Signed DigiByte Transactions). However there’s also a number of changes to the way that mempool / retransmissions behave, so we’re also re-integrating Dandelion.</p><p>You’ll also see pull requests for algo swaps coming in after this. Barrystyle has almost finished the RandomX + ProgPoW code, we’ve seen demo videos in the past of RandomX etc done against some earlier. However, I want to reiterate that this code will still go through the same rigorous review as everything else, there won’t be any skipping of the process. The code is looking pretty great, however this will provide opportunities for people to provide feedback on:</p><ol><li>Do we implement ProgPoW or RandomX first?</li><li>Do we even implement both? Or do we implement one but not another?</li><li>Do we implement another algorithm altogether?</li><li>Which algo(s) should we replace? SHA256? Or Qubit? Or Skein?</li><li>Are we seeking hard-drive mining?</li><li>Does Odocrypt need to be tweaked / upgraded?</li><li>Or do we not change anything?</li></ol><p>In addition to this we’re also going to see some pull requests for some performance enhancements and feature improvements, I understand we’ve got some of the following things being worked on:</p><ul><li>Caching of block headers / PoW hash for exponentially faster launching (Roughly 500X speed-up)</li><li>Implementing btree to reduce RAM utilization</li><li>Syncing prefers “faster” peers that can feed more blocks, concurrency improvements</li><li>Schnorr Signature implementation + Taproot</li><li>Emissions curve fixes</li><li>Additional RPC calls related to MultiAlgo</li></ul><p>And more. Again though, with each of these, they’ll be going through a peer-review process from other developers, regardless of who commits them, along with discussion around it.</p><p>One thing to be aware of is that just because a pull request is made against DigiByte does <strong>NOT</strong> mean that it’s specifically going to be implemented.</p><p>For example, the caching of block headers / PoW hash will require a little more drive-space usage as a result (Roughly 350MB from early tests, growing as block #s grow). While that’s not much, it’s worth being aware that as part of the review process it’s entirely plausible that other developers might say “Hey what if we made this optional, with a launch flag similar to -txindex rather than being always-on? What if it was enabled by default? What if we disable it by default?” and have these kinds of discussions.</p><p>Once that’s all done we’ll wrap it all up nicely, tie it with a bow, again do some additional tests over and above the Unit Tests (As well as possibly adding some more unit tests along the way) and then get the DigiByte version 8 release out.</p><p>The good news is that a lot of the code has already been done for a number of these items and it’s simply going to require smaller amounts of modification for each to work with this new base. Expect that a lot of these will come pretty quickly now we’ve got an improved foundation to go off.</p><p>So as always I encourage you to go to github.com/DigiByte-Core/digibyte and click the “Watch” up the top-right to stay aware of all these developments as they happen, and have your input in them all!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa137679f299" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is the best mining pool for DigiByte?]]></title>
            <link>https://josiah-digibyte.medium.com/what-is-the-best-mining-pool-for-digibyte-9823138e5a6a?source=rss-714d4d4beb3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/9823138e5a6a</guid>
            <dc:creator><![CDATA[Josiah Spackman]]></dc:creator>
            <pubDate>Thu, 22 Apr 2021 13:28:58 GMT</pubDate>
            <atom:updated>2021-04-22T13:28:58.164Z</atom:updated>
            <content:encoded><![CDATA[<p>We get asked this a lot in the Support / Mining channel, what is the “best” pool?</p><p>What I’m going to do today is teach you why it’s not a clever question, and what you should be asking, to get the most out of your mining!</p><p>You see there is no one answer to this, what is the “best”, because what’s the best for one person likely won’t be for another.</p><p>DigiByte has 5x mining algorithms, these are currently:</p><ul><li>SHA256</li><li>Scrypt</li><li>Odocrypt</li><li>Skein</li><li>Qubit</li></ul><p>If you have a miner that mines SHA256, then there’s little point finding a mining pool that only supports Scrypt mining. Many pools support all 5x algorithms, however some don’t, so look into that. The first thing you MUST know is: What algorithm am I using to mine DigiByte?</p><p>This is going to depend on your hardware. If you’re unsure, a quick Google will help you:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lEeJVbjvtAsOTfUxE15N_A.png" /><figcaption>What you should search for to find out about your mining hardware</figcaption></figure><p>Funnily enough, this search shows a great result, advising “No, the S3 cannot mine using the Scrypt algorithm”, because the Antminer S3 only supports the SHA256 algorithm.</p><p>The same goes for other hardware:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rYD_COQmeoNxtLR8STsiWg.png" /><figcaption>What algorithm does the Innosilicon A6+ support?</figcaption></figure><p>So if you had the Innosilicon A6+, you’ll be mining with Scrypt.</p><p>Perfect, now you know the algorithm you’ll be mining with, it’s time to find a mining pool that supports that algorithm, but which one should you choose?</p><p>You see if you go to <a href="https://www.dgbwiki.com/index.php?title=Pools">DGBWiki under Pools</a>, you’ll see there’s dozens!</p><h3>Which one should you choose?</h3><p>You want to try and mine with the one that’s closest to your physical location, as it likely has the lowest latency:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gPhlTQ2_5k-0nmQaqy0hOQ.png" /><figcaption>Some of the DigiByte mining pools</figcaption></figure><p>If you’re in Austin Texas, then Brutangs Dallas pool is probably a good idea.</p><p>However if you’re in the Netherlands, then it’s going to be a much worse idea. It’ll still work, but you’ll have a lot more rejected “shares”, and should instead be looking at Mining Dutch or similar.</p><h4>But, why?</h4><p>Well, what you’re doing with a mining pool is being divvied up a task, a whole lot of math. You’re working cooperatively with others in the pool to find an answer to a mathematical calculation, while racing against miners in other pools.</p><p>The mining pool will give you a bunch of “work” to do based on roughly how fast your miner is. You complete that work, and give it back to the pool, who then checks that work, and gives you more.</p><p>However, if someone else in your pool found the block during that time, and you’ve just spend the last 5 out of 15 seconds doing “work” that the mining pool has deemed invalid (Because it’s already moved on to the next problem, the next block) then you’ve just wasted ~30% of your hashrate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/981/0*oW3awh9rsAxDeA35" /><figcaption>Rejected shares on Ethereum, image from Reddit</figcaption></figure><p>You want to avoid rejected shares, and the best way to do that is to ensure that your miner can give it’s “work” back to the pool in-time before the pool has moved on to the next job.</p><p>As such, the faster your connection to the mining pool, both in terms of lowest latency and maximum throughput / speed, the better the results you’re going to have. There are ways to measure it, but for simplicity sake, finding a server that is physically near to your location is probably a good starting place.</p><p>This is why there is no one “best” mining pool, and why you shouldn’t be afraid to move around. You’re not finding a life-partner with a mining pool, you pay them (usually a 1–2% fee) so you might as well find one that’s going to give you maximized returns on the hashrate you’re providing, and avoid it going to waste!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9823138e5a6a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A new development era for DigiByte]]></title>
            <link>https://josiah-digibyte.medium.com/a-new-development-era-for-digibyte-fb50a23bdbe8?source=rss-714d4d4beb3e------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb50a23bdbe8</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[gitflow-workflow]]></category>
            <category><![CDATA[digibyte]]></category>
            <dc:creator><![CDATA[Josiah Spackman]]></dc:creator>
            <pubDate>Thu, 08 Apr 2021 03:13:44 GMT</pubDate>
            <atom:updated>2021-04-08T03:13:44.779Z</atom:updated>
            <content:encoded><![CDATA[<p>I can’t tell you how thrilled I am to finally be able to let everyone know about this great next phase in the history of DigiByte, which sets us up to not only live up to our billion-dollar market capitalization, but future-proofs the foundations of the project for growth well into the future!</p><p>This has taken a while to get here, but we’ve been quietly working away in the background, as we evaluated where we are and took a step back, it became important to review and confirm all that is so important to the DigiByte project.</p><p>I would even go so far as to say this is one of the most important changes in DigiBytes history: <strong><em>Changing how development is done.</em></strong></p><p>This was implemented after <strong>significant feedback</strong> and review from a large number of broader stakeholders involved with the DigiByte blockchain, both developers and advocates. We’ve come to a realization that we needed a thorough, professional, reliable, and standardized process for code-review, bugfixes, feature improvements, and especially protocol upgrades. The rigorous checks and balances that this process brings are industry-leading. This high-calibre development environment will enable participation in the DigiByte project with contributions by other experts and new-comers alike, ensuring the utmost excellence and accountability going forward.</p><p>Through this reflection, it has not only reinforced DigiByte from a technological perspective, but also strengthened the relationships of those involved at a broader level. As a by-product it has created a more efficient, effective, and trusted environment for meaningful discussions and idea generation.</p><h3>What inspired these changes?</h3><p>My excitement is underpinned by us now following the<a href="https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow"> Atlassian Gitflow Workflow method</a>, and I want to show you a little bit of an example of this.</p><p>In the past, a number of people could make changes to the README, keeping it updated etc. This was really nice for us from a “low touch” administrative perspective. The users committing to GitHub were basically “trusted” to do the right thing.</p><p>However, there was less accountability, and less reviewing of changes that went into DigiByte. Although this wasn’t abused maliciously, due to the significant growth DigiByte has witnessed, there comes a time where it’s prudent to simply say “This is for the best of the project” and make a change.</p><p><em>As such, we have put that stake in the ground, and made that change!</em></p><p>I appreciate that there were so many participating in these broader improvements, and their involvement has been invaluable. I do want to say a special thanks to GTO90 for spearheading this development process initiative in particular, and for being the driving force behind it. There’s certainly been some bumps along the road but what we have now is basically the “ideal” scenario in every way thanks to his implementation of these methodologies, with Continuous Integration testing coming very soon.</p><h3>What are these improvements?</h3><p>Not only are we taking a leaf out of the Bitcoin Core playbook, we wanted to take it a small step further in terms of tidiness / accountability. This is the difference between<a href="https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md"> Bitcoin Core contributing</a> vs the<a href="https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow"> Gitflow Workflow process</a>.</p><p>Yes, this new process requires slightly more administrative work than even the Bitcoin Core contribution process, BUT it’s for the better!</p><p>The difference with Bitcoin is that some maintainers contribute directly against Master, and other contributors / developers make pull requests against the Master branch. With DigiByte and the Gitflow Workflow, nobody can make commits directly at all, and instead all commit against a Develop branch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UYyeXfPrUgqm0xIw" /><figcaption>Testing changes for DigiByte before they’re accepted</figcaption></figure><p>Previously for DigiByte where a number of people could commit directly to the codebase, that ability is <strong>completely gone</strong>.</p><p>The only way code is now changed is:</p><ul><li>An atomic pull request is made</li><li>Against it’s own feature-branch</li><li>Which is reviewed by <strong>multiple other developers</strong> (You can’t “review” your own work, naturally)</li><li>And then merged into the develop-branch</li><li>That’s merged back in to a release-branch when a release is made</li><li>And it’s all then merged back in to Master after a release has taken place</li></ul><p>The idea being that your Master is always the “current finalized release” with release-branches remaining for historical purposes, and develop-branch is where all the new / fun stuff takes place!</p><p>Now, while this is very similar to Bitcoin Core requirements, what we are doing now for DigiByte with the Gitflow Workflow is slightly more stringent, and I agree with all the developers involved that this is genuinely <strong>the <em>best</em> way to proceed</strong>, and will truly set DigiByte apart from so many other projects, driving the quality of what DigiByte does to the next level like we’ve not seen before!</p><h3>A look at the Gitflow process:</h3><p>We have some examples of this process already taking place that you can see.</p><p>Barry and Yoshi have been hard at work with the DigiByte built-in unit tests, and they’re making HUGE progress on this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*U5Cjf2e576SEswJq" /><figcaption>An example of the recent submissions that have taken place</figcaption></figure><p>The unit tests are baked into Bitcoin Core, that anybody can run as basically a check to go “Yeah, looks good, everything is working as expected”. Some time several years ago, DigiByte deviated sufficiently from the Bitcoin Core codebase (figures, right?) to the point where the unit tests basically broke and never got resolved prior to release. As of DigiByte 7.17.2, they’re still not working. However, this is all changing as we move towards DigiByte version 8.</p><p>Despite prior work being done on DigiByte version 8 by Barry, the developers have basically all agreed that given the absolutely MASSIVE scope of the release, it’s best if we take a step back, rewind a little, and follow this Gitflow Workflow process for DigiByte version 8, beginning by fixing up these long outstanding built-in tests.</p><p>This is why there’s been less DigiByte update videos from me recently on the topic, because the development team are wanting to do their best to do this “the right way” and uphold themselves all to a much higher standard, with all the code reviewed by multiple people, starting by fixing these unit tests.</p><p>As such I would refer you to<a href="https://github.com/DigiByte-Core/digibyte/pull/11"> Pull Request #11 — Fixing blockchain_tests for DigiByte Core</a>.</p><p>Barry has corrected the first part of the unit tests, in particular the original difficulty for DigiByte is lower due to us using Scrypt rather than SHA256. You can see that GTO90 acknowledged the tests but had not himself tested them at the time, with a “utACK” (Un-Tested Acknowledgement). It was then tested by Gary and Yoshi, both with an “ACK” (Acknowledge / approve the changes) and it was then merged into the “develop” branch.</p><p><strong>The importance of this cannot be overstated:</strong> This is how the community can participate in these discussions, allowing any voice to be heard, concerns validated, and opinions listened to.</p><p>We’ve already seen a lot of good come out of this method, with other underlying things being picked up along the way to be sorted and resolved. The end-result being that although this will take slightly longer, DigiByte Core itself will have higher-level organization compared to most blockchains out there in terms of the codebase review.</p><h3>What are the implications for DigiByte 8 release date?</h3><p>I genuinely can’t say, I simply don’t know.</p><p>Once the Unit Tests are all finished, from there we’ll pull in the upstream Bitcoin Core code based on 0.21 most likely.</p><p>After this has been done, we can then review the algorithm replacement proposals to strengthen and enhance the blockchain security. Discussion can take place on the GitHub pull requests at that time too, not just from the developers of course (this is the case, at any point in time) but from the broader DigiByte community.</p><p>It’s the perfect opportunity to voice your thoughts around which algorithms you’d like to see replaced, or even to say that you don’t think X algorithm should be implemented (though you’ll naturally be expected to be able to state your reasoning and articulate your perspective sufficiently). You can even leave your thoughts around which algorithm should be replaced too. This is because although an initial pull request is being made, it can still be edited and further tweaks reviewed prior to acceptance into the codebase.</p><p>After that (or, concurrently alongside it) there will be additional features / improvements / tweaks / bugfixes / performance enhancements which will also all be made as pull requests that I would encourage you to participate in the discussion around.</p><p>I mentioned recently in the Swapzone AMA that there was a number of things that had already been worked on, which have taken a bit of a back-seat while we go through not just setting up this newer / stricter process, but also setting up the ground-work for this next release so it gets to the place where we CAN actually adhere to it and implement (or reject even!) all these fancy new features. This could all take a while to go through but it’s a process we all agree needs to really take place, a “growing up” of DigiByte if you will.</p><p>IF you’re a coder, or even sufficiently skilled at compiling software, I’d encourage you to give these a whirl as well and jump on and test them, help the team out even prior to them being merged into a new release.</p><p>Otherwise, feel free to lurk / watch, or even just react with the emojis when the developers comment that they’ve tested and approved a pull request. The more input we can have going into DigiByte version 8, the better!</p><p>I hope you’re as excited as I am for this new process that we’re following for DigiByte, and if you’ve made it this far then I’m sure you’ll agree that this is for the best for DigiByte as a project and will take the codebase to a whole new level in terms of quality / review. We made do with what we had for a long time, but as we’re attracting more and more incredibly talented developers it makes sense for us to utilize this opportunity to uphold the highest possible standards for DigiByte.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb50a23bdbe8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>