Maintaining the security of DigiByte

How does a merge differ from a rebase?

So why is merging bad then?

DigiSpeed code removed

Double spends on DigiByte

Jared sent me this screenshot, he was the green, and the person reporting the security issue was in white on the left.
DigiByte Orphan chart from 2018 when the double spends were happening

Code can easily be slipped through when merging

GitHub won’t show you the file by default, the merge was too big to even show on your PC

Inability to import older wallets

Couldn’t import the older private keys

Broke fresh blockchain syncing

Release of 6.16.5.1 fixed the new client sync issue

So why do Jared and GTO90 insist on a merge?

Will a rebase really solve these issues though?

Sounds scary, how the heck would that work?

So what’s the way forward?

--

--

--

I write interesting things about cryptocurrency, especially DigiByte

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

SubQuery Network: Aiming for Success in 2022

Potentials of using Blockchain in Education system in 2022

Crypto/NFT: How to set up your own Smart Contract

Challenges Beget Change: Issues with Arbitration, Attribution, and Trust Spur Blockchain Innovation

What is Tesla Energy? An Introductory Guide

“Sustainable” GameFi

Democratizing the Wealth Generated by the Data Market.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Josiah Spackman

Josiah Spackman

I write interesting things about cryptocurrency, especially DigiByte

More from Medium

Things Everyone Knows About Hottest Wives of NFL Players

Things Everyone Knows About Hottest Wives of NFL Players

CS371p Fall 2021: Ziyi Zhao : Final Entry

Ushering of “Internet of Things”

Understanding the Role Propaganda Played in Allowing the Holocaust to Happen