, 4 tweets, 2 min read Read on Twitter
Examples like this from @veil reveal it’s not so clear where the protocols end & the interfaces begin: link.medium.com/4hFySEn2cU
Lots of smart contract functionality needs to sit below current interfaces to compensate for the shortcomings of the protocols.
The “shortcomings of the protocols” are not necessarily a bad thing, either.

Protocols should remain as thin as possible to provide a useful service to as many interfaces as possible.
Question becomes how many “middleware layers” will we need for application interface builders to leverage the infrastructure of protocols & iterate w/ ease?

And which of those “middleware layers” will be better off as protocols (eg, @zeppelin_os) vs companies (eg, @sendwyre)?
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Chris Burniske
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!