Expanding Interest-Bearing Stream MVP into a Modular Suite of Integrations

[jmulq]

Hey guys - I'd like to propose a collaboration between the Sablier and BuildersDAO teams to expand the concept of interest-bearing streams into a robust and flexible system of contracts. The goal, to allow users to build and configure streams that can accrue yield through different DeFi protocols, and to support varied stream types (e.g. linear, dynamic, etc.) and payout models (e.g. interest to sender, recipient, or split).

I noticed a discussion around yield bearing streams from 2023, however opted to create a new discussion for this potential collaboration.

We’ve implemented a prototype wrapper contract that:

• Wraps aUSDC from Aave V3
• Mints waUSDC, a 1:1 wrapped token, to stream senders.
• Uses Sablier Lockup to stream waUSDC to recipients.
• On withdrawal, burns the wrapped token and converts aUSDC -> USDC, transferring the principal to the recipient.
• Retains the accrued yield inside the wrapper for later claiming.

This has already been reviewed by @smol-ninja, however the full code and test suite can be viewed here.

---

Proposal

We’d like to start a discussion on whether Sablier sees value in collaborating on a modular, extensible interest-bearing stream system, and what your wishlist or design goals might be for something like this.

Potential directions:

• Support for all Sablier stream types (linear, dynamic, tranched, merged)
• Pluggable yield protocols (e.g., Compound, Aave...)
• Configurable yield routing (e.g., all to sender, all to recipient, 50/50)
• Claimable yield strategies, e.g., auto-claim on cancel, claim mid-stream, etc
• Sablier-native frontend tools to build or interact with interest-bearing streams

We're happy to scope, spec, and propose an architecture — but would love to start the conversation with the Sablier team to:

1. Review the existing prototype.
2. Sanity-check feasibility.
3. Understand if there is an appetite for a generalised interest-bearing stream module within the Sablier ecosystem.
4. Get input on desired extensibility, modularity, or limitations to keep in mind.
5. Discuss any other integrations you had in mind that BuildersDAO can take on.

Looking forward to your thoughts!

@sablier-labs/evm

[PaulRBerg]

hey @jmulq, thank you for posting this. We will aim to respond over the coming weeks, perhaps after EthCC.

Smol, initial feedback: there have been a lot of requests for interest-bearing streams. The devil is in the details, especially in the user interface details. Providing a smooth UI/UX is challenging.