EOS will render Steem anything over my dead body.
The explicit bandwidth costs, the multiple ops to settle contracts... get ready to be dissapointed by EOS.
Dan selfishly and secretively wrote ops into Steemd as STEEMIT_OP .. well, they’re properly written as STEEM_OPs now as I always meant them to be - orchestrated for platform use - not single website use.
Now the way is clear for Steem as a platform: bolstered by SMTs and Communities.
RE: Can EOS disrupt Steem?