Source: Pixabay Motivation and Background I think there is a benefit to separate out some of the concepts that are currently coupled with upvotes and downvotes (aka flags) on Steem platforms. The first

I think it is time for BitShares to learn from its younger sibling Steem and adopt some crucial security features: time-locked savings and recovery accounts. These are features that I have quickly come

I reviewed code changes for hardfork 13 and assisted the core devs in finding issues and iterating on the design of the new mining algorithm included in v0.13.0. I provided a suggestion for how to fix

On Monday, August 8, 2016, a set of accounts that all started with the name supercomputing dominated the mining queue. People were speculating how this was done. Some thought @supercomputing built a GPU

I continued work on the will contract / recovery feature that I started the week prior. I finished the design and made a post about it on Friday, Aug. 5, 2016 as an official proposal which you can read

This proposal discusses a new set of features and operations for the Steem blockchain which allows a user to either eventually regain control of their account even if they lose their password or to

It seems this is a fairly popular topic on Steem, and I have seen a few misunderstandings regarding how the economics of Steem really work. So this is my attempt to explain the economics behind Steem,

I originally starting writing this post as a comment to the recent blog post by Steemit called "Steemit to Update Password Policy". But it ended up being so long that I thought it was a little

Clickbaity title, I know. But this is an important message, so I have to grab people's attention. I hope you read it fully. Are you familiar with that situation when the (centralized) website you use gets

Repeatedly pressing F5 with the mouse cursor over the upvote button

Steemit has released version v0.8.4. That release is identical to v0.8.3 (which does not have retroactive changes to curation rewards) except that it has some politically-neutral bug fixes. I think it

I ran some simulations of the July 4th payouts using the v0.8.2 steemd and v0.8.3 steemd. As a reminder, v0.8.2 uses @theoretical's new rule for calculating curation rewards retroactively going back to

I felt like sharing my opinions on the hardfork or no-hardfork debate happening in the Ethereum community now as a result of the hack on The DAO. I think the particular choice to make should depend on

It has been a week since the last snapshot, so it is time for a new one. This is a snapshot as of block 2199289 (2016-06-09T23:08:03 UTC) estimating the July 4th rewards. It assumes the weekly median price

I have computed a snapshot estimating the July 4th content reward payouts for all top-level posts. This is just the Steem Dollar (SMD) portion of the content rewards for top-level posts only. An equivalent

@dan posted a teaser of the top 8 on the reward leaderboard, but what about the rest? After playing around with some scripts, I have more or less recreated the list that @dan posted except I have the full

Now with faster mining! I recently made a change that fixed the hash rate slowdown bug for the MinGW cross-compiled Windows build of steemd. (Note: this does not fix the slowdown for MSVC compiled versions.)

This is a proposal for a new standard that allows front-end clients to adjust how comments are displayed in the UI (e.g. allowing auto-hiding) based on the moderation of accounts optionally selected by

This is a step-by-step guide on how to cross-compile Steem for Windows on a Linux host. Guide to build Steem for a 64-bit Windows target on an Ubuntu Linux host I have spent a lot of time making changes

One problem I immediately see is that the tag gets cut off at a hyphen, which means I cannot use the tag #steemit-issues Another issue is that sometimes I want to use the hashtag without referring to a