Discussions about changing the dynamic code that runs the Bitcoin blockchain should constantly be happening. Over the course of the past year, the talks of changing the block size have been an overwhelming topic of conversation. There have been some pretty stubborn people when it comes to changing the protocols code, and this is not to say that forking the code is the right step. There has been censorship and subsequently has created a rift between people who want to raise the block size and those that don’t. In time, other discussions may have to occur regarding the underlying hash functions involved with the Bitcoin protocol and to assume things will always stay the same may be naive.
Also read: Stanford University Offers Bitcoin Course to Students
Public key cryptography is used throughout the internet to secure websites, email, and multitudes of various transactions. Currently the two forms of cryptography that commonly secure our web is RSA and the Diffie-Hellman key exchange. These two methods are used in everything from cryptocurrencies financial transactions to the validation of software and legal documentation. This year the National Security Agency (NSA) has shown strong signs of moving in the direction of quantum resistant cryptography, and this is giving the internet a ghoulish scare.
“Customers using layered commercial solutions to protect classified national security information with a long intelligence life should begin implementing a layer of quantum resistant protection.” ~ NSA, August 2015
Within the powerful new toolkits of decryption, the NSA’s quantum materials will supposedly be able to attack nearly all SSL, HTTP, and MySQL connections. Practical quantum computing is often told in theory however it’s not considered a fairytale this day in age and is becoming more of a real threat every day. In August of 2015, the NSA let the world know there was a need for post-quantum cryptography and certain methods should be abandoned in the coming years. Despite this statement, there has been no significant sign of anyone’s ability to crack the certain encryption they see as vulnerable. The elliptic curve P-384, RSA-3072, AES-256, SHA-384, and DH mod p 3072 all are under question as the NSA says they are safe for now but not for long.
Bitcoin is partially quantum-safe and it’s ECDSA function could be changed over time and in theory so could it’s SHA-256. Theoretically ECDSA could be swapped with minor blows to the network with various temporary techniques like throw-away addresses. However, the implementation of changing out the SHA-256 algorithm could be catastrophic as it is the mining architecture of the entire ecosystem. It would take a lot of effort for a switch to say SHA-512 as the industry is dependent on the hardware specifically designed for the 256 algorithms. If there were a backdoor to SHA-256 our friend RIPEMD160 would allow developers time to try and do this swap but it’s timing would be critical.
Discussing how the block size increase may or may not speed up the amount of transaction processing time is a discussion that must be had. Vulnerabilities in ECC could definitely be a threat in the future and figuring out the best possible scenario should probably be a wise researched decision before it’s too late. Dynamic software is made to change all the time and conforming to no change at all can be dangerous to the evolution for certain technologies. The block size discussion is happening today. Tomorrow we may be discussing the security of the underlying cryptography itself. Or should we now?
What do you think about changing the code? Let us know in the comments below.
Images courtesy of Shutterstock, Pixbay, and Redmemes