$STREAM is a gem!

Reviewed Streamflow’s token vesting and streaming infrastructure for Solana projects. The contract architecture for immutable linear vesting is solid, but here is a critical UX and operational friction point during real multi-sig management:

1. Cancellation & Clawback Transparency: When a project sets up a revocable vesting stream for an employee or contributor via Squads multi-sig, if the stream is prematurely cancelled, the unvested balance is automatically returned to the sender. However, the transaction receipt on Solscan doesn't clearly delineate between accrued-unclaimed tokens vs. returned clawback tokens in the event logs without manual parsing. Adding an explicit on-chain event log showing "claimed_to_recipient" vs "clawed_back_to_treasury" would drastically simplify accounting for corporate treasuries.

2. Cliff Period Partial Unlocks: Currently, if a stream has a 6-month cliff, the recipient cannot interact with the stream at all. It would be valuable to allow users to delegate voting power (SPL governance) during the cliff period without unlocking token liquidity. Has the team considered integrating SPL Governance voter weight plugins natively into Streamflow lock contracts?