<?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>dish</title>
        <link>https://paragraph.com/@dish</link>
        <description>undefined</description>
        <lastBuildDate>Tue, 18 Aug 2026 13:00:24 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>dish</title>
            <url>https://storage.googleapis.com/papyrus_images/1d08e174458f12ccbf234cc041f2e9a7.jpg</url>
            <link>https://paragraph.com/@dish</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Introducing Clanker v4]]></title>
            <link>https://paragraph.com/@dish/introducing-clanker-v4</link>
            <guid>COrIGV7FeZCnvgJdv4zd</guid>
            <pubDate>Tue, 17 Jun 2025 00:33:35 GMT</pubDate>
            <description><![CDATA[Clanker v4 marks a significant step forward, transitioning from Uniswap v3 to Uniswap v4 and adopting a modular contract system. This upgrade not only boosts overall user configurability and accelerates future feature integrations, but also introduces dynamic fee mechanisms—designed to attract external liquidity providers and sustain creators' liquidity rewards over the long term. Additionally, creators can now utilize multiple LP positions to optimize reward generation, alongside improved vi...]]></description>
            <content:encoded><![CDATA[<p>Clanker v4 marks a significant step forward, transitioning from Uniswap v3 to Uniswap v4 and adopting a modular contract system. This upgrade not only boosts overall user configurability and accelerates future feature integrations, but also introduces dynamic fee mechanisms—designed to attract external liquidity providers and sustain creators' liquidity rewards over the long term. Additionally, creators can now utilize multiple LP positions to optimize reward generation, alongside improved visibility into unclaimed fees. These enhancements position Clanker to deliver a more flexible, transparent, and creator-friendly experience, setting the stage for us as we expand our value proposition and strengthen alignment across our ecosystem.</p><p>The Clanker v4 contracts are audited by <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://0xmacro.com/">Macro</a> &amp; <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://cantina.xyz/">Cantina</a> and integrations with aggregators / routers are actively being completed. Soon, we'll be publishing the technical specifications, updated SDK, and a comprehensive implementation guide.</p><h2 id="h-key-features" class="text-3xl font-header">Key Features</h2><p><strong>Customizable Fee Structures:</strong> Configure fee tiers, collect fees in only a specified token, or set dynamic fees based on trading activity</p><p><strong>Custom Liquidity Distributions:</strong> Create your own liquidity distribution curve by placing up to 7 LP positions to make more or fewer tokens available for purchase at specified prices. Available via SDK or direct contract interaction</p><p><strong>Multiple Reward Recipients:</strong> Set up to 7 rewards recipients at launch, each modifiable by a paired “admin” address</p><p><strong>Streamlined Rewards:</strong> Create multiple tokens paired with WETH and claim all the WETH rewards in one transaction, as rewards are claimed on a per-token basis</p><p><strong>MEV Modules:</strong> Modify the initial pool’s behavior at the time of deployment with various MEV modules. Our initial module, which delays trading of deployed pools by two blocks, is the first installment of our sniper-aware technology</p><p><strong>Clanker Extensions:</strong> Vaulting and Creator Buy / Dev Buy functionality are now grouped under Clanker Extensions. Extensions are contracts that can be used to add new functionality to the token deployment process. Up to 90% of the token supply may be allocated to extensions in total</p><ul><li><p><strong>Vaulting:</strong> Now vault up to 90% of the token supply with a reduced minimum lock of 7 days</p></li><li><p><strong>Creator Buy / Dev Buy:</strong> Any amount of ETH may be used to execute a Dev Buy upon creating a token (remains the same). For non-WETH paired tokens, the paired token must have a WETH &lt;&gt; Paired Token Uniswap v4 pool in order to complete a Dev Buy (updated)</p></li><li><p><strong>Airdrops (coming soon):</strong> Set airdrop allocations upon token creation with vesting parameters. Tokens are then allocated to recipients and claimable after a minimum of one day. Contract support is live, frontend and SDK support soon to follow.</p></li></ul><h3 id="h-fee-mechanisms" class="text-2xl font-header">Fee Mechanisms</h3><p>Fees can be configured to be either static or dynamic.</p><p><strong>Static Fees</strong></p><p>Static fees can be configured on a per-token basis, meaning token creators can decide how much of each input token on the swap is collected as a fee. Full customizability is available via deployments through the SDK.</p><div data-type="callout" type="info"><link rel="preload" as="image" href="https://paragraph.com/editor/callout/information-icon.png"><div class="callout-base callout-info" data-node-view-wrapper="" style="white-space:normal"><img src="https://paragraph.com/editor/callout/information-icon.png" class="callout-button"><div class="callout-content"><div><p>E.g., Clanker token fee = 1%, paired token fee = 2%</p><ul><li><p>Swapping the Clanker token in exchange for the paired token incurs a 1% fee</p></li><li><p>Swapping the paired token in exchange for the Clanker token incurs a 2% fee</p></li></ul></div></div></div></div><p><strong>Dynamic Fees</strong></p><p>Dynamic fees are collected in both the Clanker token and paired token. A base fee is set, which is a static fee collected on each swap. A variable fee is added on top of the base fee, based on the price impact of the current swap and the accumulated volatility from previous swaps. Generally, the more a token’s price is moving over a short period of time, the higher the effective fee is that will be collected. Full customizability is available via deployments through the SDK. Additional information on the dynamic fee mechanism will be provided in the technical specifications.</p><p><strong>Clanker Protocol Fee</strong></p><p>The Clanker fee is now collected at the pool level, meaning it applies to other LPs that participate in the initial pool. This fee is 20% of the effective fee, which is collected in addition to the static / dynamic fee.</p><h3 id="h-liquidity-distribution" class="text-2xl font-header">Liquidity Distribution</h3><p>Up to 7 LP positions may be added during the token creation process to enable various liquidity distributions in the pool. Previously, all tokens were placed in a single LP position from the starting price to infinity. Now, Clanker token liquidity is able to be more / less concentrated in specific ranges, depending on the liquidity profile that the token creator wishes to set. This is available via deployments through the SDK. Additional detail on placing multiple LP positions to come in the updated SDK documentation.</p><h3 id="h-reward-recipients" class="text-2xl font-header">Reward Recipients</h3><p>Token creators accrue rewards from trading activity that occurs against the tokens that are initially placed in the trading pool during token creation.</p><p>At least one <code>rewardAdmin</code> + <code>rewardRecipients</code> pair is required to be set. Up to a maximum of 7 of these pairs may be included.</p><p>For each pair, you must set the % of trading fees the <code>rewardRecipients</code> will receive using <code>rewardBps</code>. <code>rewardBps</code> is denominated in basis points (1 basis point = 0.01%) and the sum of <code>rewardBps</code> across all pairs of recipients must be 10,000 (100%).</p><p><strong>Can Be Changed</strong></p><ul><li><p>Any given <code>rewardAdmin</code> may change its paired <code>rewardRecipients</code><em>(e.g. rewardAdmin #1 can change rewardRecipients #1)</em></p></li></ul><p><strong>Cannot Be Changed</strong></p><ul><li><p>Any given <code>rewardAdmin</code> cannot change a <code>rewardRecipients</code> that it is not paired with <em>(e.g. rewardAdmin #1 cannot change rewardRecipients #2)</em></p></li><li><p><code>rewardBps</code> cannot be changed post token deployment</p></li></ul><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/0b86058eb104bc32a0476e56d928b98f.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAYCAIAAAAUMWhjAAAACXBIWXMAAAsTAAALEwEAmpwYAAAFpUlEQVR4nK2Vb0wTZxzH74XL9mZL9kIXo7hhZMIcZKB2o0hhVEbREsSBUyy2wMjQRBNHVGL2JzFLjJtDxQb/lE2lzEpNW6ilpa1Xj7Nnq6UFKtACRWIptoX27qTXCtfELtcDJC7ZC+Wb58Vdft97vvnc8zy/B4gtiCTJWCwWQPG+QdfAyPjY00mCCM+ECAzDY28hQNOlBQBgzbpEAABKvi1tlnYBCanAqqTSg/VnLwgLi0qaRM109hsGEAQhk8klt9pkMrnNZhsen2i6IRVeu3XX+MjhHIZgo9PlIsnomwcsfSHJ6P/MRcarr42lhrm52Ug4HAmH5+ZmybheD3gbvYiEselnEQKLEFgID0TCeAifxgN+YOzppEjS0dgsOSdqPX2x+ZyotbFZ0nYH9Pp8QRQNoqjHM+n1+bw+n9qAnBfdpG2NzZLzV8Rnr7aaewcJIhREMa97XKm91yCi5jkvutkg+sdgtAS8E8AdEPmccwAAPgKAFQClVe8kfZXPr1MoVddbxBcuXqw9dPiXX09dF7dyK48usa0AgA+B9xN/+uNyX28vBBthCNxRcQh4NyFeBYD31h08eSaETwPTQbRDa5DIVWJp+402uUSukshVd6EHKIpiGD4TCtEcQRS19A20tCnE0vZmsVQsVYilihtt8mHXE4KgtvLUM4/J/Egi7xRL2/9ulba0KXrtQ1jAB3h9fj0Ile3lfVO4c1tuXtle3o/H6mHEtEAgXCRQKFV7efx8DvfLLFY+h1u8e4+gphYxmeH7CGIy3zOASqVKUFObnctOZ2TyBNXwfYRaAwzDTRYrCMEavUGp1mr0Bo3eYOsfIEmSIAg0LgzDSZJ0OF36e90avUGhVGv0BhCClWqde8ITi70kSRIPBh4/fgx2I4sG5+joPIFGb9hVti+Ps5OZk7erbN+RuhM0QdPlq0LhpdpDh+tP/iz665pCqdq9Z3/udg4ji5W7nVNYVMwTVFN/HzZCMAzq9fIOJf/7H5g5eakZjO94AgiGXxHAiImG0IMQCMF99kG6eRBxCIIgYrGYw+kCIZi2LT54fX56mxLP8SHHENiN6EGI/g2usSevCLglpdtyt2cwmIVFJUfqTkCISSqTNQqbGs418itr6o7XN12+Ku9QcktKmTl56YxMZk5ePofLE1RTSSCVp1appDJZOb+KkZX96Wdp5fwqCDbOE1isNrOlBzE9hGAjYnpIE5D/kdPlQkwPaUM38sBs6dHoDYtrEMIDTqfjgXl+HhCCXWNj8wSdOrCAW8zIYqVmMAq4xTUHD0OI6bZMcbbhwpnf/+RVVB45Wie8dEUqay8sKmZkZW9K38LIymaxC0r2lNMEehDSabtkMnlZ+YEvtmYmJiVzS0ohGKYCZkKhPvugxWpbHLZ+e7zBUXoxO0vERZLkuNtNG8yWHtpmsli9Pn80Gl0gcFqs/Rar7VGP1dZvd094qJPs9fmksnZmDjslbfPHG5KZOeyy/XylWndbpmgUNp367XSFoKru2HHhpSvXWm6y2JyUtM1r1yelpG3OYDDZHC614BQBqNN2SW61cYp2JyalrFydwGJzVGrdPMGQc7TPbl8Yg332wUUCMr6RaAL3hGeJjXJarLYFgige8I+OjMQ/p6q2/oF5AveEp1Uqy2TlbUxNX/PJhi1MVjm/ulMHLhLwKirrjtfTBMwc9sbU9NUJ65NTMzalb92xq3SBAFKrVC3iVjanaO36pA9Wrv66YOc8AUmSwfhZpTsPhuFBFAui6JJrgFIsFqOrtMHvn8Iw3O+fIojwwjlAcQwNhyPxizZELx5FsFz3AfEcHRl2OhyOfrt9YGAQho0ej4ciWK6AEI52qlRVNbU7iooFVTXJm9K0Wl0IDyxbQJSMRMnI9JTfO+me8nufjrsiYeJFJAzQ/XK5NDc3G4u9jITD0WgUx7CZUOhfZIPfBS8XcusAAAAASUVORK5CYII=" nextheight="1308" nextwidth="1775" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><h3 id="h-reward-claiming" class="text-2xl font-header">Reward Claiming</h3><p>Behind the scenes, Clanker contracts now automatically collect the fees earned on the LP position(s) and send them to a separate fee locker for claim. The rewards claiming process is now on a per-token basis rather than a per-token <em>pair</em> basis (recipients may claim WETH for multiple tokens they created in one transaction, rather than collecting WETH + token #1 in one transaction then WETH + token #2 in another). Claiming rewards for a given token / recipient is still a publicly callable function.</p><h3 id="h-mev-modules" class="text-2xl font-header">MEV Modules</h3><p>Modify the initial pool’s behavior at the time of deployment with various MEV modules. The initial module adds a 2 block delay between token / pool deployment and when it is enabled for trading. This is to prevent snipers from sniping in the same block of deployment. Future MEV module upgrades will explore auctioning off the first swaps on pools for the benefit of creators. For more information, see Lily's (head of protocol) article: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://hackmd.io/@lobstermindset/rkwlyMpkgl"><strong>Minimal Viable Auction for New Assets on Priority Ordered L2s</strong></a></p><p>Additional information on MEV modules will be provided in the technical specifications.</p><h2 id="h-extensions" class="text-3xl font-header">Extensions</h2><h3 id="h-vaulting" class="text-2xl font-header">Vaulting</h3><p>Vaulting, a Clanker extension, allows for token creators to set aside tokens before they are placed in the initial liquidity position(s). Up to 90% of the token supply may be vaulted and allocated to extensions in total.</p><p><code>lockupDuration</code> refers to the time (in seconds) since token creation before vesting begins. The minimum enforced <code>lockupDuration</code> is 7 days.</p><p><code>vestingDuration</code> refers to the time (in seconds) during which vesting occurs. Vesting occurs linearly and begins once <code>lockupDuration</code> ends. Note that the lockup period does not constitute a traditional vesting cliff where vesting starts at the beginning but tokens are locked until the cliff - no tokens are vested until <code>lockupDuration</code> ends.</p><p><code>admin</code> can claim tokens anytime once the <code>lockupDuration</code> ends. The amount will vary depending on both the amount of time that has passed since the <code>lockupDuration</code> ended and whether some of the tokens have already been claimed. The claim is a <strong>public function</strong> (anyone can call the claim function) and can be triggered multiple times, and however many tokens are vested + unclaimed at that time will be available. Upon triggering a claim, vested + unclaimed tokens are sent to the <code>admin</code> address.</p><p><strong>Can Be Changed</strong></p><ul><li><p>The <code>admin</code> of the vaulted tokens may designate a new admin address, thus relinquishing their control <em>(e.g. </em><code>admin</code><em> at deployment is Team EOA #1, who can then change the </em><code>admin</code><em> address to Team Multisig #1)</em></p></li></ul><p><strong>Cannot Be Changed</strong></p><ul><li><p>Neither <code>lockupDuration</code> nor <code>vestingDuration</code> can be changed post-deployment</p></li></ul><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/b7a57f227303a8afdfd108479587be25.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAaCAIAAABZ+cloAAAACXBIWXMAAAsTAAALEwEAmpwYAAAFsElEQVR4nLWVbUxTVxjHr8ZsmsUpZsBggoIS0anoxE1YFrcsmdvihyUzxizbXNToNlQoL5UJlCIgtlBUvC0tUNAWrZRAEUtdWykFymhU6kuZVKFQW1oLFbjF3tuXSzlLuQ6BCfjB/fPk9nlOe8/vPuffcy4E/jd5PB4AAIQgSE+fMS8vPzePfqdD82ZnR1HUB8ijM7ZEf7IqPOLAwcMAAARBUBT1TMjldqP/yuPxoNPlcrs9s4jA+AAoik4C36A8UztweXBRXb1UJpPK5Hc6NFKZXKFQaDR3W1QqhUKhbGnxjTQpW1VtLSqVXH5T3CBRqdrEDZI5lnQaQCy58f3efeTUNFLyCRo9/6f9B+ITk3h8Po2en06hUk+dOpaQlJBEPhJ3PCHpRHbu6bh4Ujol69CR31IzMucHvM4SuTDMhTlcGIZ7nC7MgeMeIp9IHNionQgX5kBHESJsVgsAAPd6XwAmXZ0h7/g4hqGDZqNjdNRhRwatT4VXr5LJZIFAUFDAyMykMpnMQgajmMViMlnZ2TnNSiXucTrsyLMB6zTAHB24nU77kHWiAwfucT7S6RJIpLijx06eTEtOScmgZGZQMpNTyHFHj5FIiQ87O3GPE8NQZHhoJsA7Pg4AUD7Q0AR8uLaaXV+HuZwAgDEcbxMLhSxaTVmhmAdLBWxFNVcu4CiqyyauXKIk8usVRTVlhb7g0N0uH+MlgGii9EaD38fbF65afZhxpn9wEADgsCMyAXNXTNS2dSG7YqJiN63dHB4UumLx+pDAjWFB0ZGhG0IDwwPfDV2x+JvYrV/FbN4UFrw9cnXcvt1W433P2NhMAE3AfydmBxQWFv3zjyOoAwCAYejlQkoJ9Sg3O4F3hrzni4/W+C+M3RAaGbT00/WhOzeFbQnzjwxa+uXWtZ9tDP3h6x28M2RuTuL5E4d6/1ZN64BY8UFkpO3B/UZ1u/6p2eV2E4MDZoNBpzX1dJl6uqyGbpvZ0CSTWJ/02Mx9xHUysT7pIX7WrX2xRV5h8sDg4K2OjolB/L+eE1Y1NrdM4l93H3jHx4mbzRYLsUUnAWM4PjUAAG1qNTHFjK8mw4lhs240o9FUW1c/x6M97Oq6yONf5PG12s75OyDqdvUtrbZTo7mr1XYqmpQX4OLHuse6Cen1vUajyWyxEKVW2ylukMTFk8ipabWia3p9LzGu0+m6e/QGg1Gv7+039Ws0d194QHzAMJPFKSmCYYFA2K6+1apqb1W1NbeqJFIpLf/sLwd/zaMzroslraq2VlWbWn27RfXXvfsP1Orbza2qyZDKG7NP0zOzcgrPXRBW18xq8lTZbDapTAbDTD6/EkGQOVwFAPQZ+iqvXM45ncdiF5stlpkeTPXZ91+yDV/gi/iixpIqCcyvEzWqS6okArECAGDoszAK+Bx2TQW3nltWV8qpLeXUEiUMC1mwkH+pQVzfMqvJBOOeru/96F0Q5A8FRkABa6GANVBAxN7jVN9x0tQRFLITglZCUDAEhUBQyIIFayaS9/wCt0GQ/zL/bcmJZ+cBPNSb/KM+h5YEQ0s+WBS8Dlq+CoL8vztIBgAoFHf27iF/u/t3CFq2PCBqqd+HCxeFQ5Df8oCot96OWLk6dv9+CiWdNc/7wNBvPcerY1aKmZVibo28iH+NUVHDE90EAPR0m05RS1iwsKxEVMqphc8LWLCwlFPLZlaXlYgquPW0vItXLv85DTDjbe52OgdswyazhVtezuaUsjkccuofSqXSPDCEIMizZ4hU3piSmkpKSuGWl8cnJqZnUKhZWTR6fk5ublpGRhEMP3rUN08How50yP7chePXbsgLiti67l7c6zU+tQEAhofs3Y8Nl/hVJ9Ozmazy80VsJqv87PliQVVtAQPOpNIqKgQm08BLwCv13OEYGkaGRxDc6/Ud2qhzeMRXoiiKIHa73XfQzia3040gdmKefwC8lduTS9M0VwAAAABJRU5ErkJggg==" nextheight="1494" nextwidth="1808" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><h3 id="h-creator-buy-dev-buy" class="text-2xl font-header">Creator Buy / Dev Buy</h3><p>Any amount of ETH may be used to execute a Dev Buy upon creating a token (remains the same). For non-WETH paired tokens, the paired token must have a WETH &lt;&gt; Paired Token Uniswap v4 pool in order to complete a Dev Buy (updated).</p><h3 id="h-airdrops-coming-soon" class="text-2xl font-header">Airdrops (coming soon)</h3><p>Set airdrop allocations upon token creation with vesting parameters. Tokens are then allocated to recipients and claimable after a minimum of one day (<code>lockupDuration</code> minimum is one day). Once available for claim, anyone can initiate the claim process for a given airdrop recipient and the given airdrop recipient will receive the tokens. Lockups / vesting work the same way as they do when vaulting tokens.</p><h2 id="h-beyond-v4" class="text-3xl font-header">Beyond v4</h2><p>While our primary focus remains on ensuring a seamless v4 integration and comprehensive post-launch support, we've also begun actively exploring new strategic opportunities for the Clanker token and our role in the ecosystem as a whole. This includes evaluating fresh approaches to tokenomics, incentive structures, and partnerships aimed at deepening our ecosystem's value and sustainability.</p>]]></content:encoded>
            <author>dish@newsletter.paragraph.com (Jack Dishman)</author>
            <category>clanker</category>
            <enclosure url="https://storage.googleapis.com/papyrus_images/0fbda938f1ced33a65e803e48ddead77.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Post-Clank Clarity]]></title>
            <link>https://paragraph.com/@dish/post-clank-clarity</link>
            <guid>sb3HzlEbIDPmndJReucn</guid>
            <pubDate>Sat, 01 Feb 2025 19:24:37 GMT</pubDate>
            <description><![CDATA["You eat what you kill"Attending college in the Bay Area for Computer Science was meant to launch me into a FAANG career at one of the companies everyone knows about with the stacked snack drawers and ID badges. That was the norm and traditionally marked success after graduation. I worked at a large consulting company for a year and while I learned a lot, I wanted to have more impact with my work since it'd take up so much of my life. I've always know I wanted to take the higher-risk path of ...]]></description>
            <content:encoded><![CDATA[<div class="relative header-and-anchor"><h2 id="h-you-eat-what-you-kill">"You eat what you kill"</h2></div><p>Attending college in the Bay Area for Computer Science was meant to launch me into a FAANG career at one of the companies everyone knows about with the stacked snack drawers and ID badges. That was the norm and traditionally marked success after graduation. I worked at a large consulting company for a year and while I learned a lot, I wanted to have more impact with my work since it'd take up so much of my life. I've always know I wanted to take the higher-risk path of startup land, even knowing nine out of ten fail. </p><p>I was really close to giving up on doing my own thing and taking a cushy job at a large company with clear expectations and comfortable "rest and vest" equity and 401k packages. After each startup I worked at failed by running out of money or pivoting to whatever's hyped in the market, it sounded even more appealing. But I knew deep down that it wasn't the type of career I wanted. It runs in the family; my dad’s mantra has always been “you eat what you kill” as he runs his own practice and built up what he has today, similarly to my grandfather who was a residential home builder. It makes the stakes more real to me, knowing the ceiling isn't capped by a manager's yearly review. A stable salary with linear promotions might work for some, but I craved the risk of doing things my own way. </p><p>In a startup, you pour long hours, late nights, weekends, and 80-hour work weeks into an idea you believe in, only to realize it might not be the one. The key is maintaining your work ethic and staying adaptable. Looking back, I probably overworked myself and lost touch with the world around me. </p><p>Read this for more insights into where I was at right before clanker:</p><div data-type="embedly" src="https://paragraph.xyz/@dish/five-year-career-reflections" data="{&quot;provider_url&quot;:&quot;https://paragraph.xyz&quot;,&quot;description&quot;:&quot;I'm writing this article as an extension of my reflections for recalibrating my five-year plan now that time has expired for my previous ...&quot;,&quot;title&quot;:&quot;Reflection of My First Five Years in Startup Land&quot;,&quot;thumbnail_width&quot;:307,&quot;url&quot;:&quot;https://paragraph.xyz/@dish/five-year-career-reflections&quot;,&quot;thumbnail_url&quot;:&quot;https://storage.googleapis.com/papyrus_images/5d0b70cea2fa9a13571d98d13f83233d.jpg&quot;,&quot;version&quot;:&quot;1.0&quot;,&quot;provider_name&quot;:&quot;Paragraph&quot;,&quot;type&quot;:&quot;link&quot;,&quot;thumbnail_height&quot;:307,&quot;image&quot;:{&quot;base64&quot;:&quot;data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAIAAAD8GO2jAAAACXBIWXMAAAsTAAALEwEAmpwYAAAFjUlEQVR4nO2Ue0xTdxTH7+2914KAUh9DGEMlig+GJqBGxxKHQ6c4gYi8aqEVaGmht9x7+6AFWqDyUMBkjoqLjdaIE9Egj2KlVLBCFQRhOhnocJr5SLb9YTZnYnR/nKUw8IVKjPGvff+8j8/nnnvO+SHI//k/HyoogqAjwTAWC0U/iBJ9TxrUGZYLjs+Y7u7vOycsJGi+jxeGYe8HjSAIgeMLfL1XBQasCw6KDQ8lYyMUvKi48NDPly3y9HB7Ry6GYf/RCdx71syAuT5B/n5rly2NWbeKjo/YrxEf0Ii+pVM1/K3LF859RweKIh7uU0MWL1jmP2/F4gVbw9aok6IN8jQDk1adT5nys3RCbkFqgl7M9ff2Gnll0vSRIUHdXImkiPBs3jbh+i94a1cVpcV/k7WjNCW2ND3uqJ46opdXl2iN+ar9uYwgcgOCIJPqytggOh9d+LEXnRBt21PUZyjvLNX1G/RXq4rvVBuumMotlYXHirIN2dI8kaCYSs8TJc3mcN7uGKWPC5b4+aj4ibdrq8FqAZsZbE3Qdwmu9UFvh91QXihMyk9JHKjad/vgQW1q0mfLlyIIguP4ZAVTCHyOpyfNjfuz8dRTc/3t6kN3amvh+hAMD0Lfxb/M9cZc9R8na+DGz9BqV0RHL/HzHa1g4uVAX4kLm81xd/s6dPVQjQmGB6CzAxzd0H8Z7DbotkPvhYcWM3R1wA/90NhCR0ROd3NHEeeSv3b7XhJMwXE2xgoPCe6oNEBnO5xvA2sT2M9C32Xo74KL7f+0WqDLAYNDUNcYGbp6mrv7+FkygePVCggMc8HQuV5e1/dUQovF+eF2K1zpg/v34Po1cLQ9tp6Glia4aL932Lhh9QrvmbNe4ryJjqIoG8Nccdx3xkfQYIYOB9jbwXEWhn+E3+4629DtgDbro6aTcLoObA2laQLv2bPG13NSAoKFT8EJjpu7QZr1tKkOTh2DM6dg+BrcvwXDP8HVXjjf/tTaDJY66GgcMu4NCVg4tkDIpAQYymLjBBvDgub73zywD46cAHOzk/vLEAz2P7nkeNBme9RqgfZmsNXcMhkYfsqX4ZtXBq/hcDgo+qLjVTprREBgOIERnh4etTl5UFMHfRegp/1Jb/fj7q67tjN/d1idV6z1HRVlYn56YrwgIV4QG8vb+FXk6Bo9G9kJK2CN/SUCI8KCg68Yqx5aGh71OH532H+1mG/U1w7W1fSaDhcz2XFx/LgY3rat3KgtCdFRCZs2Rvl9Mg9FWc8crxNgGEbgBIHjri6uuzMzH5yz37S29pw4Xl1RUZFXoCRVsXECLle4I1nCTxYJ+GJ+sjiRmxK7jbd5U0xg4HIvLx8CJ17fg7GwCYJgYSsDP80nyd0qVVluvkRE8/mkSEhLJSqJiJGIFOlCRixSSERMWgopSJZuTxBu56YkxPDWrV0/zWPaxIJxBz4SNpuNE/iiRUvTUsjMDLWcKmBkBbRMJ5PmkRlqmVSTIVZlStRkhjpdqMySagpzS7TqQlqq2JGU9hYBhmEEQWAYNnWqW0wMn5ZpKUorlWpk0rzs7GIlU8RQ+kyJmpblZZE6WqYlM3LUdKH5aNOu/N1SURYtVbxdgI+ckaGhYSpViYzUMpSelOWJUhlhqoKS6eS0nnKWoqXpnXJaL6f11d/VDHT2d7U4jHuNx03HkDegx+kzODOTeBK1uoR24gooqoAktWKRUpiqyMjQMNROitLRdKFc4azpbP25C61d1jrrQGe/tbZ5UoKAgECVsoiR61WqEpreSVN6GamTZuSIxRqxSC1XFNG0nqb0SqZYyRQXaPdkq3ZVlht7rF0N39e/IHge/XwPNoRvyckpVzLFGnWZSlWiZIppylkKKdVJxBpGrteoy0bpo7doSi+ni6r2mg7tN/0LZcRSGhadujwAAAAASUVORK5CYII=&quot;,&quot;img&quot;:{&quot;width&quot;:307,&quot;height&quot;:307,&quot;src&quot;:&quot;https://storage.googleapis.com/papyrus_images/5d0b70cea2fa9a13571d98d13f83233d.jpg&quot;}}}" format="small"><link rel="preload" as="image" href="https://storage.googleapis.com/papyrus_images/5d0b70cea2fa9a13571d98d13f83233d.jpg"><div class="react-component embed my-5" data-drag-handle="true" data-node-view-wrapper="" style="white-space:normal"><a class="link-embed-link" href="https://paragraph.xyz/@dish/five-year-career-reflections" target="_blank" rel="noreferrer"><div class="link-embed"><div class="flex-1"><div><h2>Reflection of My First Five Years in Startup Land</h2><p>I'm writing this article as an extension of my reflections for recalibrating my five-year plan now that time has expired for my previous ...</p></div><span><svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-link h-3 w-3 my-auto inline mr-1"><path d="M10 13a5 5 0 0 0 7.54.54l3-3a5 5 0 0 0-7.07-7.07l-1.72 1.71"></path><path d="M14 11a5 5 0 0 0-7.54-.54l-3 3a5 5 0 0 0 7.07 7.07l1.71-1.71"></path></svg>https://paragraph.xyz</span></div><img src="https://storage.googleapis.com/papyrus_images/5d0b70cea2fa9a13571d98d13f83233d.jpg"></div></a></div></div><div class="relative header-and-anchor"><h2 id="h-clanker">Clanker</h2></div><p>This ties into Clanker. Alex and I were local, in the right place at the right time. Luck and the post-election buzz played their part. In a bear market, we focused on learning skills and building networks. We click because our shared values and ethics make it easy to align, challenge, pivot, and gain perspective. I’m the techie, Alex is the relationship guy who understands what people want.</p><p>Before Clanker, we built “pump.linkedin” for about a month. The idea was simple: map endorsements for a coin, and once it hit a threshold of around three advocates (FIDs), the coin would launch. Some of that logic still lives in the Clanker codebase. Caught up in the hype around Aethernet and Askgina, Alex proposed a rogue bot that would launch random coins. I built the core functionality, taking a name, symbol, and image from a cast to create a coin, and soon we realized we’d created a half-decent token launcher with an in-feed UI.</p><p>Growth was insane. I remember rushing to add pagination as tokens deployed rapidly, then tackling the challenge of directing LP fees to the requestor’s address tied to their FID. We were building the ladder as we climbed it.</p><p>We knew immediately after launch that we were onto something. I was interviewing at Base, my dream job at the time, and Alex had referred me. As tempting as a stable, prestigious role was, I realized that fully committing to this partnership and project was a once-in-a-lifetime opportunity.</p><p>Big things happen when you least expect them. When you take the pressure off reaching a goal, everything falls into place over time with consistency.</p><p>I forget who casted this but someone said there's now two eras: Before Clanker (BC) and After Deployment (AD) which I have a feeling will define milestones in my career</p><p></p><p>Thanks for reading, more to come, just wanted to get these thoughts down!</p><p>-jd</p><p></p>]]></content:encoded>
            <author>dish@newsletter.paragraph.com (Jack Dishman)</author>
        </item>
        <item>
            <title><![CDATA[Fostering Engagement: Key Traits that Define Successful Farcaster Channels]]></title>
            <link>https://paragraph.com/@dish/fc-channel-frames-takes</link>
            <guid>BLCUN774tJM1oYva8zI4</guid>
            <pubDate>Mon, 23 Sep 2024 01:42:56 GMT</pubDate>
            <description><![CDATA[I've outlined some of the traits of the most influential Farcaster channels. By breaking down their unique characteristics and use cases, I hope to abstract models that channel owners can leverage to brainstorm new ideas for their communities. Often, channel growth and rankings are gauged by follower count, but I believe metrics of engagement and contributors ("replyooors"), as well as the quality of "interesting content," should be better indicators of success. These metrics reflect the impa...]]></description>
            <content:encoded><![CDATA[<p>I've outlined some of the traits of the most influential Farcaster channels. By breaking down their unique characteristics and use cases, I hope to abstract models that channel owners can leverage to brainstorm new ideas for their communities.</p><p>Often, channel growth and rankings are gauged by follower count, but I believe metrics of engagement and contributors ("replyooors"), as well as the quality of "interesting content," should be better indicators of success. These metrics reflect the impact a channel has within the Farcaster ecosystem—and eventually, beyond it.</p><p>1. <strong>Marketplaces</strong> – Channels like <strong>/bounties</strong> create value by serving both the supply and demand sides of a task or job market. The automated daily summaries delivered via direct messages help keep followers engaged. Channels offering this functionality become daily check-in spots for users seeking opportunities while fulfilling the needs of both sides&nbsp;</p><p>2. <strong>Idea Incubators</strong> – Channels like <strong>/someone-build</strong> provide space for brainstorming and collaboration, allowing users to pitch ideas and receive feedback. This format allows people to share ideas while builders can browse recent casts to identify new side projects, gauge market demand, or receive recommendations for alternative solutions. Channels like <strong>/founders</strong> can act as soundboards for people in the founder’s circle, offering value even to passive participants who simply read the casts</p><p>3. <strong>Recurring Challenges of Showcasing Accountability</strong> – Channels such as <strong>/the-arena</strong> and <strong>/firstdraft</strong> use weekly tasks to maintain standings and streaks. Some include gamified elements like eliminations and awards. These channels succeed by promoting competitive yet collaborative environments, while allowing founders and curators to showcase their work and invite feedback.&nbsp;</p><p>4. <strong>Personal Channels</strong> –  Personal channels act as repositories for themes or philosophies, like <strong>/six</strong>, where users share personal insights. I use mine similarly to a Facebook wall. However, I feel that current channels lack the customization needed to truly express their subject matter.</p><p>5. <strong>Project Showcases</strong> – Channels like <strong>/thegarage</strong> excel at highlighting DIY projects, offering a space for knowledge sharing and inspiration. Developer-focused versions, like <strong>/devfc</strong>, allow developers to share knowledge, seek advice, and showcase weekend projects in channels like <strong>/base-builds</strong>. Often, these projects are eligible for rewards like grants or retroactive funding. Such channels let users celebrate their work while learning from others.</p><p>6. <strong>Exclusive Community</strong> – Channels such as <strong>/firstdraft</strong> stand out by offering exclusive access to private group chats and events, fostering a tight-knit community and enhancing the prestige of membership. I see exclusive community-building directly tied to content curation and revenue generation. The next wave of publishers could collectively curate interesting pieces and sell them to niche consumers, while channels might eventually form their own stores, charge fees, or sell advertising spots—think <em>Variety Magazine</em>, <em>The Boston Globe</em>, or <em>TMZ.</em></p><p>The beauty and excitement in all this channel talk lies in the organic evolution that’s happening. As new use cases and tools emerge, channels will continue to evolve and grow in impactful and unique ways.</p>]]></content:encoded>
            <author>dish@newsletter.paragraph.com (Jack Dishman)</author>
            <category>farcaster</category>
        </item>
        <item>
            <title><![CDATA[What can we learn from sports betting that applies to on-chain Fundraising and Social Capital Coordination Going]]></title>
            <link>https://paragraph.com/@dish/what-can-we-learn-from-sports-betting-that-applies-to-on-chain-fundraising-and-social-capital-coordination-going</link>
            <guid>1WaL7PkXpXZvlWmZGKL7</guid>
            <pubDate>Sat, 14 Sep 2024 00:00:00 GMT</pubDate>
            <description><![CDATA[Unlock the Future of On-Chain Fundraising: Explore how social capital, transparency, and investor engagement are transforming startup fundraising. Learn how sweat equity, milestone-based rounds, and strategic alignment with product progress can fuel your next venture’s success in the evolving world of blockchain fundraising.]]></description>
            <content:encoded><![CDATA[<p>Through the people in my daily life, I see many using various methods to make a few extra bucks via apps. The most popular, by far, are sports betting apps. It doesn’t really matter which one—FanDuel, DraftKings, BetMGM—they often create new accounts to take advantage of new member incentives, like "bonus bets," where you place a bet, and if you lose, you’re refunded up to the advertised amount.</p><p>Sports betting isn’t new; in the past, you’d have to go to a casino or a bookie. The only difference now is that you can place bets from your couch. I guess you could also do it over the phone before, but the point remains.</p><p>My point here is that people aged 21-29 are used to juicy onboarding incentives and quick, simple returns. The only "gamification" is your account balance and watching the games.</p><p>Online lottery apps make playing scratch tickets, the Powerball, KENO, and other instant-win games super easy with direct deposits through a connected bank account. It’s surprising to see this vertical gain traction, especially since it’s government-sponsored. But with the Massachusetts State Lottery bringing in over six billion dollars last year, I guess it’s no shock they’re going digital.</p><p>Sports betting, in particular, has social aspects similar to crypto-native projects, gaining traction through word-of-mouth and shared bets. There's a research phase before betting, where you can see stats on how many people are picking a side and how much money represents confidence levels. In crypto, it’s the same, except the two sides are buyers vs. sellers, pitting bettors against each other.</p><p>Now, you might ask, Jack, how does this relate to on-chain fundraising?</p><p>It’s all about social capital coordination, something we see actively in sports betting and shared fantasy team ownership. The outcome isn’t left to pure chance, like a coin toss or card draw; there’s thought involved, though the final result is out of the bettor’s hands.</p><p>Similarly, when investing in a company or industry, there’s a process of researching the team, track record, and progress. Bettors follow a similar process when making picks.</p><p>With on-chain fundraising, I believe social capital coordination goes beyond financial pooling. Investors become early adopters, advocates, marketers, and, in a way, the product’s executive board.</p><p>Here’s how I see the startup fundraising model being flipped:</p><ul><li><p><strong>Proof of Commitment:</strong> Demonstrating sweat equity through a functioning MVP signals to investors that the founder is serious and capable. It reduces perceived risk because there's already a foundation to build on.</p></li><li><p><strong>Value-Progress Correlation:</strong> The amount raised should align with the product's maturity. This allows investors to see clear potential returns based on progress, not just promises. Early investment should cover essential hires, like designers and marketing, to ensure the product can scale.</p></li><li><p><strong>Investor Trust:</strong> Investors trust founders more when they’ve already invested significant effort and resources. Only raise funds for tasks outside the core contributor’s skill set to accelerate growth.</p></li><li><p><strong>Transparent, Phased Funding Rounds:</strong> Break fundraising into smaller, milestone-based rounds so only immediate needs and tasks are funded. Investors will know exactly where their money is going. You could even break it down further into sponsoring bounties for specific tasks. Start with funding immediate needs and plan subsequent rounds based on progress.</p></li></ul><p>In the same way sports bettors and crypto participants rally around their chosen outcomes, startup founders should leverage social capital to fuel their product’s growth. By showing real progress, aligning fundraising with product maturity, and involving investors as more than just check writers, the traditional fundraising model is turned on its head. Investors become true stakeholders, not only contributing financially but actively advocating for the product. The future of on-chain fundraising lies in this blend of transparency, trust, and strategic social coordination—because at the end of the day, it’s not just about raising money, it’s about creating momentum.</p>]]></content:encoded>
            <author>dish@newsletter.paragraph.com (Jack Dishman)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/af442c1ebf31350471d974e3a3829390.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Welcome to Paragraph!]]></title>
            <link>https://paragraph.com/@dish/welcome-to-paragraph</link>
            <guid>0IA8sj8RTyTjwyf1dYXB</guid>
            <pubDate>Mon, 29 Jan 2024 23:10:41 GMT</pubDate>
            <description><![CDATA[This post teaches you everything you need to know about getting started with Paragraph.]]></description>
            <content:encoded><![CDATA[<p>Paragraph lets you create and share beautifully crafted posts - just like this one. </p><p>Write anything - from your smallest paragraph to your grandest masterpiece - and publish it online or send it as email newsletters directly to your readers.</p><p>Your Paragraph publication is blazing-fast, SEO optimized, and combines the best parts of both web2 and web3 to help you create content and grow your community better than ever. </p><h2>Getting started</h2><p>What you&apos;re looking at right now is the Paragraph editor. We support markdown, callouts, code, and rich media embeds like Twitter and YouTube.</p><div data-type="twitter" tweetid="1560419350976221185">   <div class="twitter-embed embed">    <div class="twitter-header">        <div style="display:flex">          <a target="_blank" href="https://twitter.com/paragraph_xyz">              <img alt="User Avatar" class="twitter-avatar" src="https://pbs.twimg.com/profile_images/1521582712527548416/VaZi_24t_normal.jpg">            </a>            <div style="margin-left:4px;margin-right:auto;line-height:1.2;">              <a target="_blank" href="https://twitter.com/paragraph_xyz" class="twitter-displayname">paragraph.xyz</a>              <p><a target="_blank" href="https://twitter.com/paragraph_xyz" class="twitter-username">@paragraph_xyz</a></p>                </div>            <a href="https://twitter.com/paragraph_xyz/status/1560419350976221185" target="_blank">              <img alt="Twitter Logo" class="twitter-logo" src="https://paragraph.xyz/editor/twitter/logo.png">            </a>          </div>        </div>          <div class="twitter-body">      On <a class="twitter-content-link" href="https://t.co/BbYULfPfbU" target="_blank">paragraph.xyz</a>, all posts are stored on <a class="twitter-content-link" href="https://twitter.com/ArweaveTeam" target="_blank">@ArweaveTeam</a>. This means they&apos;re immutable, uncensorable, permanent, and composable <img class="twitter-emoji" draggable="false" alt="✨" src="https://twemoji.maxcdn.com/v/14.0.2/72x72/2728.png">                    <a class="twitter-card-link" href="https://t.co/BbYULfPfbU" target="_blank">          <div class="twitter-media twitter-summary-large-image">            <img src="https://pbs.twimg.com/card_img/1747066277238108161/waMOL0FA?format=jpg&name=800x320_1">            <div class="twitter-summary-card-text">              <span>paragraph.xyz</span>              <h2>Paragraph | all-in-one publishing &amp; newsletter platform</h2>              <p>Create, publish and share web3-native blogs &amp; newsletters.</p>            </div>          </div>        </a>           </div>         <div class="twitter-footer">          <a target="_blank" href="https://twitter.com/paragraph_xyz/status/1560419350976221185" style="margin-right:16px; display:flex;">            <img alt="Like Icon" class="twitter-heart" src="https://paragraph.xyz/editor/twitter/heart.png">            16          </a>          <a target="_blank" href="https://twitter.com/paragraph_xyz/status/1560419350976221185"><p>7:12 PM • Aug 18, 2022</p></a>        </div>      </div>   </div><p>When you publish a post, you&apos;ll have the option of sending it as a newsletter or storing it in the permanent &amp; uncensorable Arweave. </p><h2>Helpful links</h2><p>Here&apos;s a few helpful pointers to customize your publication &amp; get the most out of Paragraph:</p><ul><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/settings/publication/theme">Theming &amp; customization</a>. Change your publication&apos;s font &amp; colors; truly make this space your own.</p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/settings/publication/emails">Set up a welcome email</a>. This is the email your readers receive when they subscribe to your newsletter. </p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/settings/publication/blog">Configure your publication&apos;s settings</a>. Add links to your homepage, set up a custom domain, configure Google Analytics &amp; more. </p></li></ul><h2>Need help or have feedback?</h2><p>We&apos;ve put together some documentation <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://docs.paragraph.xyz">here</a>, but if you still have questions you&apos;d like answered we’d love to hear from you. </p><p>You can reach us via email at <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="mailto:hello@paragraph.xyz">hello@paragraph.xyz</a> or subscribe to our newsletter <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/@blog">here</a>. We&apos;re also pretty active on <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out " href="https://paragraph.xyz/discord">Discord</a>. </p>]]></content:encoded>
            <author>dish@newsletter.paragraph.com (Jack Dishman)</author>
            <category>tutorial</category>
            <enclosure url="https://paragraph.xyz/covers/welcome_to_paragraph_modern.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>