We have been very busy working to make EOS.IO the best smart contract platform on the market. Our team has been pushing the boundaries of blockchain design to provide the best possible balance between

Charles Hoskinson took some time to respond my post on Cardano's consensus algorithm Ouroboros. In his response he sets out a process that one must follow: Start out with a Definition of Security, which

I recently had an opportunity to review Cardano’s Ouroboros consensus algorithm as presented in a youtube presentation. The original paper can be found here. The marketing behind Cardano and Ouroboros

A community’s ability to self-govern can be judged by the safety of its members. When you can leave your doors unlocked and not worry about breaking and entering, then you know you live in a solid community.

As a society we seem to have double standards when it comes to privacy. We would like to know everything about everyone else while simultaneously ensuring nobody knows anything about us. We want the right

Merkle trees are used to enable proofs of user actions to light weight clients. Light weight clients are the foundation of inter-blockchain communication where one blockchain acts as a light-client to

Every so often someone decides to write an article attacking Delegated Proof of Stake (DPOS) on some basis. The most resent example is @anonymint's article claiming DPOS can't internet-scale. Before I

The block.one team has been working around the clock to make eos.io the most advanced blockchain software possible. While advancing the core software, we have also been working with a number of major players

I recently reviewed the latest Casper Research Paper in light of an ongoing discussion with Vitalik Buterin over consensus mechinisms. It is my intent to be as objective and practical as possible while

I just recently learned of these remarks from Vitalik on reddit. In these remark's Vitalik brings up the issue of Fees and Voting, both of which I feel deserve to be addressed. Client Side Validation Lack

Vitalik Buterin recently took a question about EOS at the Ethereum Shenzhen Keynote. Today I would like to provide some factual corrections to his claims about EOS. I will do this by addressing each of

Although the official test network is still in preparation, anyone can create their own test environment on a local node. Please understand things are likely to change; however, not drastically so. We

This week I have been focused on the API that smart contract developers will use to write contracts. To help facilitate the design of this API I have given myself an example contract to write. This time

Today I would like to take a moment to explain the current structure of an EOS.IO transaction so that developers can better understand the concurrency model. Below is a JSON representation of a transaction

This week we made great strides toward refining the architecture of EOS and defining the developer API. In particular we have identified a programming model that should enable parallelism while maximizing

Today I met with the team to discuss the challenges of making smart contracts both easy to develop and easy to execute in parallel. If you are familiar with the challenges associated with parallel execution

This week block.one’s blockchain c++ development team has picked up 4 new members and has been interviewing a few more. The new recruits have already begun making contributions to the code. Removing Registered

A recent post has identified the rise of identity theft on steemit. Some savvy individuals have taken it upon themselves to create introduce yourself posts that are nothing but lies. Now that we know these

A couple days ago, Charles Bovaird published an article on CoinDesk. In this article there were numerous quotes which I feel should be addressed because they demonstrate the clear cognitive dissonance