Contents

1. Overview

2. DAO domain overview

3. Protocol overview and comparison

4. What’s needed?

5. Conclusions

1. Overview

Drips v0.1 was primarily architected around the supporter model, and focused on solving gas efficiency for a single recipient collecting large numbers of streams. Since its release, a market for streaming has been rapidly emerging in the DAO tooling space.

This document aims to provide an overview of the streaming protocol landscape through the lens of DAO tooling, and zooms in on the specific challenges that end-users and product builders are having that Drips can help to address.

The final sections attempt to synthesise this analysis into some conclusions about how we can better serve the users and builders in the DAO tooling space.

2. DAO domain overview

This is an overview of DAOs and DAO tooling from the perspective of Drips and streaming.

Drips aims to empower developers to create products that serve end-users.

<aside> 💦 Drips → products → end-users

</aside>

Our relationship to product builders and end-users are related but fundamentally different, and so this section is split into two sub-sections to reflect that.

End-users

These are the people who actually use the products built on top of drips. They are driving the use-cases that drips ultimately needs to be able to serve.

Known workflows