BitCoin reading

I’ve known about BitCoin since at least some point in 2011 (based on searching my email archive)…I even played around with mining a bit back then (only ever earned a fraction of a bitcoin through that though).

Since that time, I’ve been nothing more than an interested observer sitting on the sidelines learning, watching, and occasionally sharing my (still emerging) opinion as it’s had it’s ups and downs - it’s fans and foes.

But it wasn’t until recently that I took the plunge and bought my first full BitCoin (I bought at $355 and since it’s dropped to $317 – which is *typical* if you know my track record)…and it wasn’t until recently that I started to get the bug to try and actually build something that takes advantage of the BlockChain (and BitCoin).

I haven’t come up with a specific hack or idea just yet…but I have been spending more of my free time poking around the space and getting a feel for what’s out there, who’s doing what, what (obvious) holes are still out there, and what it currently takes to actually build something useful in this space.

In the course of all that poking around - I’ve come across a couple of really good reading lists that I would encourage anyone else interested in digging into this space to check out:

1. A BitCoin related reading list from ZapChain Magaize

2. A list of BitCoin white papers (aggregated by William Mougayar)

Hopefully you’ll find them both as useful and interesting as I have.

This post has received 4 loves.


SUBSCRIBE WITH YOUR EMAIL

ARCHIVE OF POSTS



This is the personal blog of Kevin Marshall (a.k.a Falicon) where he often digs into side projects he's working on for digdownlabs.com and other random thoughts he's got on his mind.

Kevin also talks in more depth about many of the these things around twice a month via his drip campaign and has a day job as CTO of Veritonic. You can also check out some of his open source code on GitHub or connect with him on Twitter @falicon or via email at kevin at falicon.com.

If you have comments, thoughts, or want to respond to something you see here I would encourage you to respond via a post on your own blog (and then let me know about the link via one of the routes mentioned above).