<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Stee</title>
        <link>https://paragraph.com/@stxph</link>
        <description>DeFi builder and protocol architect. I design token economies, build smart contracts, and make magic internet money do useful things.</description>
        <lastBuildDate>Sun, 14 Jun 2026 15:31:16 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>Stee</title>
            <url>https://storage.googleapis.com/papyrus_images/756f17e9009c88c770fdf8024b7ea6972973d51746b82bef0d6dd14d5b825df4.png</url>
            <link>https://paragraph.com/@stxph</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Project Flywheel: From Symmetric to Revolv]]></title>
            <link>https://paragraph.com/@stxph/project-flywheel-from-symmetric-to-revolv</link>
            <guid>ehTiI7HyaICrCTURcFGA</guid>
            <pubDate>Thu, 03 Jul 2025 14:16:10 GMT</pubDate>
            <description><![CDATA[Having helped build Symmetric for over two years now, I’ve seen it go from a fresh Balancer fork on Telos to a fully-featured DEX and index protocol with custom pools, vote-escrow governance, and a small but supportive community. We shipped a lot and tried to make it easy for people to launch and manage liquidity. But over time, a few things became clear. The token model didn’t really reward participation. Protocol fees weren’t being used effectively. Governance slowed down. The system worked...]]></description>
            <content:encoded><![CDATA[<p>Having helped build Symmetric for over two years now, I’ve seen it go from a fresh Balancer fork on Telos to a fully-featured DEX and index protocol with custom pools, vote-escrow governance, and a small but supportive community. We shipped a lot and tried to make it easy for people to launch and manage liquidity.</p><p>But over time, a few things became clear. The token model didn’t really reward participation. Protocol fees weren’t being used effectively. Governance slowed down. The system worked, but wasn’t doing enough to support growth or activity.</p><p>So the team and I started exploring a possible relaunch. We’ve been calling it <strong>Revolv</strong>, a fresh start with a new name and new token, <strong>RVLV</strong>, along with a governance model based on vote-locked RVLV, or <strong>veRVLV</strong>. It’s not live, and nothing is finalised yet, but we’ve got a few ideas we’re excited about.</p><h3 id="h-a-bribe-marketplace" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><strong>A Bribe Marketplace</strong></h3><p>One of the first features we’re planning is a permissionless bribe marketplace.</p><p>Anyone, whether a project or an individual user, will be able to offer bribes to voters in exchange for support. If a project wants more rewards directed to their pool, they can post a bribe. If you&apos;re a voter, you can choose where to vote based on which pools are offering the best incentives.</p><p>We think this creates a more open and competitive system. It also gives newer or smaller pools a chance to attract attention without needing to directly pay liquidity providers.</p><h3 id="h-yield-accelerated-pools" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><strong>Yield Accelerated Pools</strong></h3><p>Another feature we want to introduce is Yield Accelerated Pools.</p><p>These pools automatically deposit the underlying assets into external strategies that generate yield. The yield earned is used to boost RVLV rewards for liquidity providers. So LPs don’t just earn liquidity rewards, they get a share of that extra yield too.</p><p>Our first integration will be with Meridian Lend, the main lending protocol on Telos. We’ll likely add more options as we go.</p><h3 id="h-putting-protocol-fees-to-work" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><strong>Putting Protocol Fees to Work</strong></h3><p>In Symmetric, fees mostly just left the system. They didn’t really benefit token holders or support long-term growth. With Revolv, we want to change that.</p><p>All protocol fees, which include those from swaps, bribes, flash loans, and yield, would be used to buy RVLV from the open market. Instead of burning those tokens or storing them in a treasury, we would use them to fund bribes in the marketplace and provide additional rewards to liquidity providers.</p><p>Here’s how it works. If a pool is generating activity and earning fees, the protocol buys RVLV and uses it to fund bribes targeting voters who supported that pool. This means that active pools naturally attract more votes, which directs more emissions their way. It creates a feedback loop that encourages participation and rewards the people keeping the protocol active.</p><h3 id="h-a-simpler-approach-to-ve-governance" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><strong>A Simpler Approach to ve-Governance</strong></h3><p>One thing we’d like to change in a relaunch is the governance model. In Symmetric, veSYMM required users to lock an 80/20 LP token. 80% tSYMM and 20% wTLOS. The idea was to combine governance and liquidity.</p><p>It made sense at first, but it had a serious downside. When tSYMM came under sell pressure, veSYMM holders ended up being the exit liquidity. Their LP tokens were locked, and they couldn’t adjust their positions or protect themselves.</p><p>For veRVLV, we’d take a much simpler approach. Governance would be based on locking plain RVLV, without any LP exposure. This gives users more control and removes the risks that came with being tied to an illiquid or volatile pair.</p><h3 id="h-fixing-the-token-supply-model" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><strong>Fixing the Token Supply Model</strong></h3><p>Another issue with Symmetric was how the token supply was handled. tSYMM followed a fixed supply schedule with a hard cap of 20 million tokens. Emissions were set to halve every four years, which might sound reasonable at first, but it caused a few problems in practice.</p><p>Most of the emissions happened early on, which led to a lot of tSYMM being farmed and dumped when the protocol was still getting off the ground. Governance had no control over the rate of emissions, and there was no flexibility to slow things down or redirect incentives when market conditions changed.</p><p>For RVLV, we want to take a different approach.</p><p>Rather than having ongoing emissions, the full supply will be minted from day one. There won’t be any future minting, so the supply will be capped from the start. Of that supply, around 5.5 million RVLV tokens (the same amount of tSYMM that was still sitting in the Symmetric treasury) will be set aside specifically for liquidity rewards.</p><p>veRVLV holders will vote on how quickly these rewards are distributed. That could be on a bi-monthly or quarterly schedule, depending on what governance decides. This gives the community much more control over emissions and avoids the kind of runaway dilution we saw before.</p><p>The goal is to reward participation, but in a way that’s coordinated and responsive, rather than locked into a schedule that can’t adapt.</p><h3 id="h-what-happens-to-existing-holders" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><strong>What Happens to Existing Holders</strong></h3><p>If we move ahead with Revolv, the plan is to make sure existing Symmetric users are fairly included.</p><p>Anyone holding at least 10 tSYMM will receive veRVLV on a 1-to-1 basis. These tokens will be locked for one year. This airdrop also covers the tSYMM portion for liquidity providers who were in the 80/20 tSYMM-wTLOS pool.</p><p>On top of that, LPs will be reimbursed for the wTLOS they had in the pool before the compromise. So between the veRVLV airdrop and the wTLOS reimbursement, both parts of their original position are being accounted for.</p><p>I know the one-year lock might seem a bit restrictive, but I believe it gives the protocol the stability it needs in the early stages. It also creates a stronger foundation for value to build. With buybacks from protocol fees and swap fees being directed to veRVLV holders through the bribe system, I think the return on those locked tokens will be meaningful over time.</p><p>This is about setting things up properly, not just for launch, but for the long run.</p><h3 id="h-looking-ahead" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><strong>Looking Ahead</strong></h3><p>Revolv isn’t live. It’s just something the team and I have been working through based on what we’ve learned so far. The structure feels better. It’s simpler, easier to maintain, and more aligned with the people actually using the protocol.</p><p>We’re still shaping the details, but this is the direction we’re excited about. Just wanted to share where we’re at.</p><p>– Stee</p>]]></content:encoded>
            <author>stxph@newsletter.paragraph.com (Stee)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/8446ce37e24ab60c834787d4ac3277923ef6cf5404f8bc71928da0ac5139528a.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>