Skip to content

prehistory: add Colored Coins context to Israel visit section #143

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
amirchetrit wants to merge 1 commit into
base: main
Choose a base branch
from
Open

prehistory: add Colored Coins context to Israel visit section #143

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion posts/prehistory.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Although the ideas behind the current Ethereum protocol have largely been stable

Also out of scope is the history of Casper and sharding research. While we can certainly make more blog posts talking about all of the various ideas Vlad, Gavin, myself and others came up with, and discarded, including "proof of proof of work", hub-and-spoke chains, "[hypercubes](https://blog.ethereum.org/2014/10/21/scalability-part-2-hypercubes)", [shadow chains](https://blog.ethereum.org/2014/09/17/scalability-part-1-building-top/) (arguably a precursor to [Plasma](http://plasma.io/)), [chain fibers](https://github.com/ethereum/wiki/wiki/Chain-Fibers-Redux), and [various iterations of Casper](https://blog.ethereum.org/2016/12/06/history-casper-chapter-1/), as well as Vlad's rapidly evolving thoughts on reasoning about incentives of actors in consensus protocols and properties thereof, this would also be far too complex a story to go through in one post, so we will leave it out for now.

Let us first begin with the very earliest version of what would eventually become Ethereum, back when it was not even called Ethereum. When I was visiting Israel in October 2013, I spent quite a bit of time with the Mastercoin team, and even suggested a few features for them. After spending a couple of times thinking about what they were doing, I sent the team a proposal to make their protocol more generalized and support more types of contracts without adding an equally large and complex set of features:
Let us first begin with the very earliest version of what would eventually become Ethereum, back when it was not even called Ethereum. When I was visiting Israel in October 2013, I spent quite a bit of time with the Mastercoin team, and even suggested a few features for them. During this period, the Colored Coins project, which was an effort to represent real-world assets on Bitcoin's blockchain, was also active in the Israeli Bitcoin community. Colored Coins and Mastercoin were both exploring asset tokenization on Bitcoin, and this intellectual environment played a direct role in shaping the early thinking around generalized protocols. I had also been a contributor to Colored Coins, having co-authored its 2013 whitepaper and written code for the BitcoinX implementation, and was increasingly convinced that Bitcoin-layer protocols were too constrained for the kind of general computation I envisioned. After spending a couple of times thinking about what they were doing, I sent the team a proposal to make their protocol more generalized and support more types of contracts without adding an equally large and complex set of features:

[https://web.archive.org/web/20150627031414/http://vbuterin.com/ultimatescripting.html](https://web.archive.org/web/20150627031414/http://vbuterin.com/ultimatescripting.html)

Expand Down