Code your own blockchain in less than 200 lines of Go!
If this isn’t your first time reading this post, check out Part 2: Networking here!
The data examples in this tutorial will be based on your resting heartbeat. We are a healthcare company after all :-) For fun, count your pulse for a minute (beats per minute) and keep that number in mind throughout the tutorial.
Almost every developer in the world has heard of the blockchain but most still don’t know how it works. They might only know about it because of Bitcoin and because they’ve heard of things like smart contracts. This post is an attempt to demystify the blockchain by helping you write your own simple blockchain in Go, with less than 200 lines of code! By the end of this tutorial, you’ll be able to run and write to a blockchain locally and view it in a web browser.
What better way to learn about the blockchain than to create your own?
What you will be able to do
- Create your own blockchain
- Understand how hashing works in maintaining integrity of the blockchain
- See how new blocks get added
- See how tiebreakers get resolved when multiple nodes generate blocks
- View your blockchain in a web browser
- Write new blocks
- Get a foundational understanding of the blockchain so you can decide where your journey takes you from here!
What you won’t be able to do
To keep this post simple, we won’t be dealing with more advanced consensus concepts like proof of work vs. proof of stake. Network interactions will be simulated so you can view your blockchain and see blocks added, but network broadcasting will be reserved for a future post.
Let’s get started!
Since we’re going to write our code in Go, we assume you have had some experience with Go. After installing and configuring Go, we’ll also want to grab the following packages:
go get github.com/davecgh/go-spew/spew
Spew allows us to view
slices cleanly formatted in our console. This is nice to have.
go get github.com/gorilla/mux
Gorilla/mux is a popular package for writing web handlers. We’ll need this.
go get github.com/joho/godotenv
Gotdotenv lets us read from a
.env file that we keep in the root of our directory so we don’t have to hardcode things like our http ports. We’ll need this too.
Let’s also create a
.env file in the root of our directory defining the port that will serve http requests. Just add one line to this file:
main.go file. Everything from now on will be written to this file and will be less than 200 lines of code. Let’s get coding!
Here are the imports we’ll need, along with our package declaration. Let’s write these to
Let’s define the
struct of each of our blocks that will make up the blockchain. Don’t worry, we’ll explain what all of these fields mean in a minute.
Block contains data that will be written to the blockchain, and represents each case when you took your pulse rate (remember you did that at the beginning of the article?).
Indexis the position of the data record in the blockchain
Timestampis automatically determined and is the time the data is written
BPMor beats per minute, is your pulse rate
Hashis a SHA256 identifier representing this data record
PrevHashis the SHA256 identifier of the previous record in the chain
Let’s also model out the blockchain itself, which is simply a
So how does hashing fit into blocks and the blockchain? We use hashes to identify and keep the blocks in the right order. By ensuring the
PrevHash in each
Block is identical to
Hash in the previous
Block we know the proper order of the blocks that make up the chain.
Hashing and Generating New Blocks
So why do we need hashing? We hash data for 2 main reasons:
- To save space. Hashes are derived from all the data that is on the block. In our case, we only have a few data points but imagine we have data from hundreds, thousands or millions of previous blocks. It’s much more efficient to hash that data into a single SHA256 string or hash the hashes than to copy all the data in preceding blocks over and over again.
- Preserve integrity of the blockchain. By storing previous hashes like we do in the diagram above, we’re able to ensure the blocks in the blockchain are in the right order. If a malicious party were to come in and try to manipulate the data (for example, to change our heart rate to fix life insurance prices), the hashes would change quickly and the chain would “break”, and everyone would know to not trust that malicious chain.
Let’s write a function that takes our
Block data and creates a SHA256 hash of it.
calculateHash function concatenates
PrevHash of the
Block we provide as an argument and returns the SHA256 hash as a string. Now we can generate a new
Block with all the elements we need with a new
generateBlock function. We’ll need to supply it the previous block so we can get its hash and our pulse rate in BPM. Don’t worry about the
BPM int argument that’s passed in. We’ll address that later.
Notice that the current time is automatically written in the block with
time.Now(). Also notice that our prior
calculateHash function was called.
PrevHash is copied over from the hash of the previous block.
Index is incremented from the Index of the previous block.
Now we need to write some functions to make sure the blocks haven’t been tampered with. We do this by checking
Index to make sure they’ve incremented as expected. We also check to make sure our
PrevHash is indeed the same as the
Hash of the previous block. Lastly, we want to double check the hash of the current block by running the
calculateHash function again on the current block. Let’s write a
isBlockValid function that does all these things and returns a
bool. It’ll return
true if it passes all our checks:
What if we run into an issue where two nodes of our blockchain ecosystem both added blocks to their chains and we received them both. Which one do we pick as the source of truth? We choose the longest chain. This is a classic blockchain issue and has nothing to do with nefarious actors.
Two well meaning nodes may simply have different chain lengths, so naturally the longer one will be the most up to date and have the latest blocks. So let’s make sure the new chain we’re taking in is longer than the current chain we have. If it is, we can overwrite our chain with the new one that has the new block(s).
We simply compare the length of the slices of the chains to accomplish this:
If you’ve made it this far, pat yourself on the back! We’ve basically written up the guts of our blockchain with all the various functions we need.
Now we want a convenient way to view our blockchain and write to it, ideally in a web browser so we can show our friends!
We assume you’re already familiar with how web servers work and have a bit of experience wiring them up in Go. We’ll walk you through the process now.
We’ll be using the Gorilla/mux package that you downloaded earlier to do the heavy lifting for us.
Let’s create our server in a
run function that we’ll call later.
Note that port we choose comes from our
.env file that we created earlier. We give ourselves a quick console message with
log.Println to let us know the server is up and running. We configure the server a bit and then
ListenAndServe. Pretty standard Go stuff.
Now we need to write the
makeMuxRouter function that will define all our handlers. To view and write to our blockchain in a browser, we only need 2 routes and we’ll keep them simple. If we send a
GET request to
localhost we’ll view our blockchain. If we send a
POST request to it, we can write to it.
We simply write back the full blockchain, in JSON format, that we can view in any browser by visiting
localhost:8080. We have our
ADDR variable set as 8080 in our `.env` file so if you change it, make sure to visit your correct port.
POST request is a little bit more complicated, but not by much. To start, we’ll need a new
struct. We’ll explain in a second why we need it.
Here’s the code for the handler that writes new blocks. We’ll walk you through it after you’ve read it.
The reason we used a separate
Message struct is to take in the request body of the JSON POST request we’ll use to write new blocks. This allows us to simply send a POST request with the following body and our handler will fill in the rest of the block for us:
50 is an example pulse rate in beats per minute. Use your own by changing that integer to your own pulse rate.
After we’re done decoding the request body into our
var m Message struct, we create a new block by passing in the previous block and our new pulse rate into the
generateBlock function we wrote earlier . This is everything the function needs to create a new block. We do a quick check to make sure the new block is kosher using the
isBlockValid function we created earlier.
A couple notes
spew.Dumpis a convenient function that pretty prints our structs into the console. It’s useful for debugging.
- for testing POST requests, we like to use Postman.
curlworks well too, if you just can’t get away from the terminal.
When our POST requests are successful or unsuccessful, we want to be alerted accordingly. We use a little wrapper function
respondWithJSON to let us know what happened. Remember, in Go, never ignore errors. Handle them gracefully.
Let’s wire all these different blockchain functions, web handlers and the web server in a short, clean
So what’s going on here?
godotenv.Load()allows us to read in variables like our port number from the
.envfile we placed at the root of our directory so we don’t have to hardcode them (gross!) throughout our app.
genesisBlockis the most important part of the
mainfunction. We need to supply our blockchain with an initial block, or else a new block will not be able to compare its previous hash to anything, since a previous hash doesn’t exist.
- We isolate the genesis block into its own go routine so we can have a separation of concerns from our blockchain logic and our web server logic. This will work without the go routine but it’s just cleaner this way.
Tada! We’re done!
Here’s the full code:
blockchain-tutorial - Write and publish your own blockchain in less than 200 lines of Gogithub.com
Now for the fun stuff. Let’s try it out :-)
Fire up your application from terminal using
go run main.go
In terminal, we see that the web server is up and running and we get a printout of our genesis block.
localhost with your port number, which for us is 8080. As expected, we see the same genesis block.
Now, let’s send some POST requests to add blocks. Using Postman, we’re going to add a some new blocks with various BPMs.
Let’s refresh our browser. Lo and behold, we now see all our new blocks in our chain with the
PrevHash of our new ones matching the
Hash of the old ones, just as we expected!
Congrats!! You just wrote up your own blockchain with proper hashing and block validation. You should now be able to control your own blockchain journey and explore more complicated topics like Proof of Work, Proof of Stake, Smart Contracts, Dapps, Side Chains and more.
What this tutorial doesn’t address is how new blocks get mined using Proof of Work. This would be a separate tutorial but plenty of blockchains exist without Proof of Work mechanisms. In addition, the network broadcasting is currently simulated by writing and viewing the blockchain in a web server. There is no P2P component in this tutorial.
If you’d like us to add things like Proof of Work and Networking, make sure to tell us in our Telegram chat and follow us on Twitter! That’s the best way to communicate with us. Ask us questions, give feedback, and suggest new tutorials. We’d love to hear from you!
By popular demand we’ve added Part 2: Networking to this tutorial! Check it out!
To learn more about Coral Health and how we’re using the blockchain to advance personalized medicine research, visit our website.