Everyone has heard of bitcoin and some of you have probably made transactions using it, maybe as a payment method or a speculative investment.
About a year ago, I was talking with a friend and trying to explain why I felt reasonably confident having myself invested in it. I understood the basic principles of how it operated as a digital currency, but as I tried explaining even the basics of encryption and the mining process all that was coming out was the bitcoin equivalent of Ruby Magic.
This talk will compile the bits and pieces I've learned since then to answer the above, as well as go into a bit more detail on how bitcoin relates to subjects we've covered in class such as cs data structures and authentication/cryptology.
By the end of this, developers should:
- Understand the basic principles of bitcoin.
- See some parallels between bitcoin mining networks and cs data structures that we've seen in class
- Know where to find starter code for integrating bitcoin payments into projects
- Be able to mine sample bitcoins via the command line in a sandbox p2p environment.
- Hopefully not be on an NSA watchlist or have inadvertently committed any cyber crimes.
Bitcoin was invented by a person with the pseudonym Satoshi Nakamoto as a way to mitigate fraud in online transactions. They postulated that the current system of relying on financial institutions as third parties to process transactions is risky because it introduces a significant need for trust between parties. Bitcoin instead allows two parties to interact directly with each other based on cryptographic proof and records transactions in a public ledger called the 'block chain' which we'll cover momentarily.
Their vision has only been partially achieved. Bitcoin's proponents will note that its value has increased from pennies in 2012 to ~450 USD today and currently averages ~250k transactions/day in one of the larger Bitcoin wallets, Blockchain.
However, the same fasciliation of near total anonymity and authentication standards that made Bitcoin successful have made it a target for crime. The most well-known cases are probably its fascilitation of a wide variety of illegal transactions on Silk Road and the disappearance of hundreds of millions of dollars worth of Bitcoin from the servers of an exchange called Mt Gox run by this super trustworthy looking guy:
This video gives a glimpse into the mindset of Bitcoin's more enthusiastic fanboys who were less than dissuaded by the scandal.
In short, Bitcoin has a short but wildly varied history. Further exploring the merits of bitcoin and predicting its future are fascinating but lengthy discussions. For our purposes, let's go under the hood to explore what a bitcoin actually is and check out the software mechanisms that produce them.
Have a look at the running transaction log on blockchain.info and click on a transaction (this is just a popular wallet, not to be confused with the block chain data structure). Perhaps surprisingly, you can not only see all the transactions occuring but you can see details for each one including wallet addresses and hash keys such as these which originated from Barcelona:
address 1Ath6yhq2uoMUMXTpBot2rNRsdRYS39L2m
hash 6c7fd28c807427b387d5813702aa901ee7319bce
Bitcoin wallet services provide users with a free alphanumeric address that, like an ip address, gives them a unique location on the Bitcoin network. The above hash is just the public portion of a randomly generated token similar to those we've used in generating user credentials for our projects. If you like, later on you can create your own and send/receive BTC using this sandbox wallet.
To complete a transaction, the payer of the Bitcoin being transferred must provide their own private key to ensure validation:
At it's essence, bitcoin is a digital file that is structured with key value pairs (names and amounts) that are updated when a transaction occurs.
However, such a transaction isn't local to one user or machine. We can see all transaction addresses/hashes because 'Power users' who provide bitcoin mining services all maintain a copy of this file, and they are all updated accordingly when BTC changes holders. Who are these power users? To answer that, we need to delve into Bitcoin nodes and the block chain.
Nodes in this context are simply a network of machines running bitcoin software (such as bitcoin core which we will use to create a test network) that broadcast transaction updates to other nodes. To help visualize that process, check out this gif of a node connecting to the bitcoin network in real time (the origin node is the first green sphere):
Another cool visualization of nodes in real time
Each individual node records transactions, adds them to the machine's local record, and then broadcasts any changes to peer nodes across the network. These changes are then published in a public database, which brings us to...
The block chain is a public ledger/database which is operated on by the aforementioned nodes. Remember when you almost had your university credentials rescinded for torrenting Wings of Liberty without a vpn on the school network? Bitcoin works in a similar capacity, albeit by providing tangible financial rewards (bitcoins) for providing peer-to-peer mining services.
In contrast to the tree structure we've seen in class, the block chain relies on a structure called the merkle/hash tree which recursively hashes nodes together until they are consolidated into one.
Miners/power users operate server banks which perform this operation repeatedly to consolidate transactions and verify their authenticity. Again, this is where the peer-to-peer nature of the Bitcoin network comes in. Every time a hash is created and miners provide validation for the transactions they recieve, they also get 25 bitcoins. The block chain is then globally updated and the process starts over.
To be accepted by the network, blocks must contain an arbitray number (nonce) that is determined by a brute force algorithm even more advanced than my tic tac toe game logic. Each block header contains the following when completed:
And we can see an actual bit of python code that incorporates those fields to calculate the hash of a block created in 2011:
>>> import hashlib
>>> header_hex = ("01000000" +
"81cd02ab7e569e8bcd9317e2fe99f2de44d49ab2b8851ba4a308000000000000" +
"e320b6c2fffc8d750423db8b1eb942ae710e951ed797f7affc8892b0f1fc122b" +
"c7f5d74d" +
"f2b9441a" +
"42a14695")
>>> header_bin = header_hex.decode('hex')
>>> hash = hashlib.sha256(hashlib.sha256(header_bin).digest()).digest()
>>> hash.encode('hex_codec')
'1dbd981fe6985776b644b173a4d0385ddc1aa2a829688d1e0000000000000000'
>>> hash[::-1].encode('hex_codec')
'00000000000000001e8d6829a8a21adc5d38d0a473b144b6765798e61f98bd1d'
Since we're all python bosses now who would like to walk me through this code? Jk :)
Blocks being built in real time
Thanks to testing environments, we can replicate this system on a smaller scale to see what kind of operations real Bitcoin farming software carries out on a constant basis.
- Follow along to configure bitcoind
- Run
bitcoind -regtest -daemonwhich should yield 'bitcoin server starting' - Set bitcoind to testing mode with
bitcoin-cli -regtest setgenerate true 101 - Verify balance with
bitcoin-cli -regtest getbalance- you should have 50 bitcoin available. - Again follow along on screen to connect to my test node
If you want to enable bitcoin payments in your web app, stripe provides useful tools for doing so. First, create a checkout handler/event such as-
let handler = StripeCheckout.configure({
key: 'pk_test_La0sDwdMY4vZwGyewISFrpm4',
image: '/img.png',
locale: 'auto',
token: function(token) {
}
});
$('#checkoutBtn').on('click', function(e) {
handler.open({
name: 'Site name',
description: 'Buy Stuff',
amount:
bitcoin: true
});
e.preventDefault();
});
You must also create a reciever object that can accept bitcoin payments when an order is created. An example post request to do so would be:
curl https://api.stripe.com/v1/bitcoin/receivers \
-u sk_test_uDTLkYo56xbc6pDAl6Y3oPZT: \
-d amount=100 \
-d currency=usd \
-d description="Receiver for John Doe" \
-d email="test@example.com"
Yielding a massive json object, the highlights of which are:
"bitcoin_amount": 1757908,
"bitcoin_amount_received": 0,
"bitcoin_uri": "bitcoin:test_7i9Fo4b5wXcUAuoVBFrc7nc9HDxD1?amount=0.01757908",
Amount being the number of bitcoins that the user must send denominated in 10^8 BTC. Additional documentation can be found here
Hooray bitcoin!
- If you're still fuzzy on how everything is related, this flow chart nicely sums up what we've covered http://core0.staticworld.net/images/article/2013/04/bitcoinhow-100032615-orig.jpg
- Original bitcoin whitepaper- https://bitcoin.org/bitcoin.pdf
- Fascinating vice video on a Chinese bitcoin mine http://motherboard.vice.com/read/chinas-biggest-secret-bitcoin-mine
- Stripe docs for bitcoin payment integration https://stripe.com/docs/bitcoin
- Test wallet https://sandbox.coinbase.com/
- Create a test mining environment on your machine https://github.com/bitcoin/bitcoin (beware, this download is enormous)
- Merkle trees http://chimera.labs.oreilly.com/books/1234000001802/ch07.html#merkle_trees
Source code distributed under the MIT license. Text and other assets copyright General Assembly, Inc., all rights reserved.