Skip to main content

The Eternal Wall of Grafittis

Hackers have emotion. People says the Bitcoin blockchain is hacker-proof. No hacker has ever managed to hack even a bit of the Bitcoin blockchain since its inception in 2009. The cryptographic process was designed to be very expensive to reverse. So expensive that the total world wealth is not enough to pay for the work to reverse the process. Thus, hackers express their frustration by plaguing the Bitcoin blockchain with grafittis.

They creates fake transactions embedded with grafittis. It is so fake that even miners cannot differentiate. Fake transactions do not compromise on the integrity of the blockchain. However, each of them adds long term memory cost to the miners machines. Fake transactions soothe hackers frustration against so many failed attempts to hack the blockchain.

Graffiti in Transaction

What is a fake transaction? Before we answer that question let us understand what a real transaction is. A real transaction produces new coins to addresses. The new coins may come from another addresses, or from miner rewards. When an owner of an address spend his coins a transaction will be created which states to which addresses the coins will go. A fake transaction is created by a hacker-owner of coins by hijacking the out-to address field and replacing it with an arbitrary data which in turn may actually be an unknown real address that already exists, is yet to exist, or will never exist. The hacker-owner does not care about the address even though he will lose his coins in the process. The arbitrary data can be anything he wanted. It is like a digital graffiti.

Celebrating the act, the hackers invites everybody else beyond the hackers-verse to inscribe arbitrary messages into the blockchain. The inscription is eternal. It is like a noble cause which the purists in the Bitcoin Core team disagree. They called it an act of spamming the blockchain. The purists insist that a transaction can only consists of coin-spending without any attachment what-so-ever, not even a reasonable statement on why a coin was spent, just like cash. However, the purists cannot stop the hackers.

A fake transaction marks a coin as probably forever unspent. Miners monitors all unspent coins waiting for them to be spent. All unspent coins are kept in the memories of miners machines for fast retrieval. On-board memories are expensive compared to external storage. Yet, on-board memories are super fast which is a highly important criteria in the races to win miners rewards, where winner takes all. However, forever-unspent coins bloat the memories. Hence, miners complaints.

The Bitcoin core team came out with a compromise asking hackers not to create fake transactions but to use a new method to embed even longer grafittis on the Bitcoin blockchain. The new method addresses the miners complaints to a certain degree. It is now official that messages can be inscribed into the Bitcoin blockchain. We all know that anything written on the blockchain is eternal. Hence, the eternal wall of grafittis emerges.

Graffiti is a playful word. Eternal data is a new class of asset in information technology. Eternal data rises from the unintentional manifestation of blockchain. It is still a young concept. Information technologists are now rushing to develop new processes and methodologies based on eternal data which is accessible anywhere in the world without any central authority. The hype is blockchain.

Hackers will continue faking transactions though. Miners will have to figure it out themselves on how to work around them. Proof-of-work is just getting more intensive.

P.S. Technical details can be found here. Or, search the Internet for null data or OP_RETURN.


Comments

Popular posts from this blog

Setting Up PyScripter for Quantum GIS

PyScripter is a general purpose Python Integrated Development Environment (IDE). Quantum GIS (QGIS) is a desktop GIS application that can be extended with Python plugins. Both are open source softwares. We intend to use PyScripter as an IDE to build QGIS Python plugin. We are using PyScripter 2.4.1.0 and QGIS 1.6.0 in Windows. PyScripter does not come with Python. On the other hand, QGIS is built in with Python. Thus, we will setup up PyScripter to use the build in Python in QGIS. We assume both PyScripter and QGIS are already installed. Preparing PyScripter batch file We assume that QGIS is installed in C:\OSGeo4W\ folder and PyScripter is installed in C:\Program Files\PyScripter\ . 1. Copy qgis.bat in C:\OSGeo4W\ bin to pyscripter.bat 2. Edit pyscripter.bat to remove the last line that read something like this start "Quantum GIS" /B "%OSGEO4W_ROOT%"\apps\qgis\bin\qgis.exe %* and replace it with this in one line Start "PyScripter" /B "C:\Progr

Sending Emails via SMTP

msmtp  requires a minimal setup for sending emails via SMTP compared to sendmail. Here is a configuration for you to send emails from a web host to an external SMTP server. Prior to doing that, you must check whether there is a clear communication channel between your web host and the SMTP server. You can use Telnet . Set up msmtp You are going to set msmtp as an MTA . Hence, you need to remove all other MTAs such as postfix and sendmail: $ sudo apt-get --purge autoremove postfix sendmail Install msmtp and related utilities: $ sudo apt-get install msmtp msmtp-mta mailutils Configure msmtp: $ sudo nano /etc/msmtprc # Set default values for all following accounts. defaults # Use the mail submission port 587 instead of the SMTP port 25. port 587 # Always use TLS. tls on # Set a list of trusted CAs for TLS. The default is to use system settings, but # you can select your own file. tls_trust_file /etc/ssl/certs/ca-certificates.crt # The SMTP server account mx host mail.mx.example

fatal: Couldn't find remote ref master

If you are using Github then  master is now known as main . Whatever you want to do with a master must now be referred to a main . If you search for this error message on the Internet then you will encounter with a lot of old discussions on how to set up your master properly which is probably not what you are looking for. The master  is your problem. Rename it to main . I wrote Git My Way about two years ago. Today I created another Github repository. I got this  "fatal: Couldn't find remote ref master"  error message when I wanted to sync the new repo for the first time with my notebook using the notes I wrote in the blog. All the discussions around the error message I found on the Internet were perplexing. Then I recalled that Github had renamed master to main  due to the master-slave connotation. We always have a master copy of a code, never a slave copy. Now suddenly a word context has been diminished for good. What is going to happen to the existing vast documen