flipside

    Try Quests to earn cryptoTry Quests to earn crypto
    Share

    StreamSwap Launch

    This dashboard provides an overview of the StreamSwap protocol launch for the FLIX/OSMO pool, including data on deposit and claiming phases, liquidity pool volumes, token swapping behaviors, and more. Key insights include a significant rise in deposit actions and depositors over time, a high number of claim actions in the first hour of the claiming phase, and the popularity of $OSMO as the most exchanged token among swappers.

    ✨Introduction

    Introducing the StreamSwap Protocol, a new DeFi protocol that enables time-based token swaps. Unlike instant token swaps in an AMM pool, StreamSwap allows for token swaps to occur over a fixed period of time. This presents a new opportunity for the Cosmos ecosystem and DeFi in general. The protocol involves two types of stakeholders - Streamers and Subscribers. Streamers create streams by locking a fixed number of tokens to be exchanged for an accepted token over a predetermined time period, while Subscribers can deposit or withdraw their tokens during the bootstrapping and streaming phases. Token swaps occur linearly over the entire stream duration, and price discovery happens at the end of the Streaming Phase based on the total tokens received by the Streamer. The Stream's Average Price and Current Price are key metrics that help subscribers optimize their average purchase price, and subscribers can redeem their tokens based on their accumulation throughout the Streaming Phase. Read more...

    🛠 Methodology

    On 4/18, StreamSwap launched on Osmosis, and the first streamer to join was OmniFlix Network. With the help of StreamSwap, OmniFlix Network launched its native token, $FLIX, and users could participate in the $FLIX launch by depositing $OSMO tokens in the $OSMO/$FLIX stream pool. As an analyst, I wanted to track the $FLIX launch process and user activity in the first stream of StreamSwap.

    To do this, I used the osmosis.core.fact_msg_attributes table and set the ATTRIBUTE_KEY = 'stream_id' and ATTRIBUTE_VALUE to '1'. This helped me track all transactions related to StreamSwap's first stream. Additionally, I used ATTRIBUTE_VALUE = 'action' and ATTRIBUTE_VALUE = 'subscribe_pending' to find $OSMO depositing actions and ATTRIBUTE_VALUE = 'exit_stream' for $FLIX claiming actions.

    To track swaps and transfers activity, I used the $FLIX token's contract (ibc/CEE970BB3D26F4B907097B6B660489F13F3B0DA765B83CC7D9A0BC0CE220FA6F) on osmosis.core.fact_swaps and osmosis.core.fact_transfers tables.

    Overall, this methodology allowed me to analyze the first few days of the StreamSwap launch and gain insights into user behavior and the $FLIX token launch process.