<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Story Protocol - Medium]]></title>
        <description><![CDATA[Story Protocol is building open IP infrastructure to grow the creativity of the internet era. - Medium]]></description>
        <link>https://medium.com/story-protocol?source=rss----144390f1ab20---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Story Protocol - Medium</title>
            <link>https://medium.com/story-protocol?source=rss----144390f1ab20---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:26:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/story-protocol" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Story v0.13.0 Upgrade]]></title>
            <link>https://medium.com/story-protocol/story-v0-13-0-upgrade-77a2e548a34c?source=rss----144390f1ab20---4</link>
            <guid isPermaLink="false">https://medium.com/p/77a2e548a34c</guid>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[intellectual-property]]></category>
            <category><![CDATA[story-protocol]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Boris Polania]]></dc:creator>
            <pubDate>Tue, 19 Nov 2024 05:34:09 GMT</pubDate>
            <atom:updated>2024-11-22T20:15:44.477Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6InSGY_x82lQWY1DeYTXjQ.png" /></figure><p>Story v0.13.0 binaries were released today, November 19, 2024 UTC, in preparation for the scheduled upgrade at block height 858,000 estimated to arrive on November 26, UTC. This update addresses issues identified during audits and testing and includes minor improvements to the staking API. All nodes are required to upgrade to this latest stable version at (not before) the upgrade block height to continue running a node on Odyssey testnet.</p><p>You can track the countdown to the block height <a href="https://odyssey.storyscan.xyz/block/countdown/858000">here</a>.</p><p><strong>Node Operator Action Required:</strong></p><p>It is critical to upgrade to client version v0.13.0 before block height 858,000, expected on November 26, UTC. Nodes running older versions will cease functioning and risk falling out of consensus immediately after this block height, and they will be jailed approximately 28,800 blocks later (around block height 886800). <strong><em>To ensure a seamless transition and avoid disruption, we strongly recommend using Cosmovisor, as it minimizes downtime and reduces the potential for errors.</em></strong></p><p>For more details, you can read the <a href="https://github.com/piplabs/story/releases/tag/v0.13.0">Release Notes</a>.</p><p>As the Geth-Story client will also be upgraded to v0.10.1, it must be upgradered before scheduling this Story upgrade using Cosmovisor. For more details about Story v0.10.1, please read the <a href="https://medium.com/story-protocol/story-geth-v0-10-1-upgrade-7fd0b5b40525">official announcement</a>.</p><p><strong>Special notes to validator operators:</strong> Reaching at least 67% voting power from upgraded nodes is essential for the network to continue operating smoothly. Your timely upgrade plays a vital role in maintaining the network’s stability and functionality.</p><p>Follow<a href="https://medium.com/story-protocol/story-v0-10-0-node-upgrade-guide-42e2fbcfcb9a"> this guide</a> for detailed instructions on upgrading your node using Cosmovisor to this new version.</p><p>You can download Story v0.13.0 binaries<a href="https://github.com/piplabs/story/releases/tag/v0.13.0#:~:text=Assets"> here</a></p><p>For any questions or support, contact us on Discord and X (formerly Twitter) [@StoryEngs]. If you haven’t joined our Discord yet, follow this link:<a href="https://discord.gg/StoryProtocol"> https://discord.gg/StoryProtocol</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77a2e548a34c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/story-protocol/story-v0-13-0-upgrade-77a2e548a34c">Story v0.13.0 Upgrade</a> was originally published in <a href="https://medium.com/story-protocol">Story Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Story-Geth v0.10.1 Upgrade]]></title>
            <link>https://medium.com/story-protocol/story-geth-v0-10-1-upgrade-7fd0b5b40525?source=rss----144390f1ab20---4</link>
            <guid isPermaLink="false">https://medium.com/p/7fd0b5b40525</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[story-protocol]]></category>
            <category><![CDATA[intellectual-property]]></category>
            <category><![CDATA[decentralization]]></category>
            <dc:creator><![CDATA[Boris Polania]]></dc:creator>
            <pubDate>Tue, 19 Nov 2024 05:32:54 GMT</pubDate>
            <atom:updated>2024-11-19T22:52:09.069Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6InSGY_x82lQWY1DeYTXjQ.png" /></figure><p>Story-Geth v0.10.1 binaries were released on November 19, UTC. This minor upgrade sets the minimum base gas price to 16 gwei.</p><p>For more details, read the <a href="https://github.com/piplabs/story-geth/releases/tag/v0.10.1">release notes</a>.</p><p>Follow<a href="https://medium.com/story-protocol/upgrading-geth-execution-client-from-0-9-2-to-0-9-3-d2cff671b91e"> this guide</a> for detailed instructions on upgrading your node to this new version.</p><p><strong>Node Operator Action Required:</strong></p><p>Nodes running older versions will remain compatible and continue to operate without interruption. However, upgrading is recommended to keep a consistent minimum base gas price setting.</p><p>As Story client will also be upgraded to v0.13.0, the Story-Geth client must be updated to this version before scheduling the Story upgrade using Cosmovisor. For more details about Story 0.13.0, please read <a href="https://medium.com/story-protocol/story-v0-13-0-upgrade-77a2e548a34c">the official announcement</a>.</p><p>You can download Story-Geth v0.10.1 binaries <a href="https://github.com/piplabs/story-geth/releases/tag/v0.10.1#:~:text=Assets">here</a>.</p><p>For any questions or support, contact us on Discord and X (formerly Twitter) [@StoryEngs]. If you haven’t joined our Discord yet, follow this link:<a href="https://discord.gg/StoryProtocol"> https://discord.gg/StoryProtocol</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fd0b5b40525" width="1" height="1" alt=""><hr><p><a href="https://medium.com/story-protocol/story-geth-v0-10-1-upgrade-7fd0b5b40525">Story-Geth v0.10.1 Upgrade</a> was originally published in <a href="https://medium.com/story-protocol">Story Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[09–29–24 Iliad Network Outage: Incident Report & Analysis]]></title>
            <link>https://medium.com/story-protocol/09-29-24-iliad-network-outage-incident-report-analysis-1d15b07719e7?source=rss----144390f1ab20---4</link>
            <guid isPermaLink="false">https://medium.com/p/1d15b07719e7</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[intellectual-property]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[story-protocol]]></category>
            <dc:creator><![CDATA[Boris Polania]]></dc:creator>
            <pubDate>Tue, 15 Oct 2024 03:53:32 GMT</pubDate>
            <atom:updated>2024-10-15T04:11:10.072Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kB7Hxalve2nBWyEjOYG8pw.png" /></figure><h3>Timeline</h3><p>On Sept 29th at 8:21 AM PST, we observed the iliad network, story’s first public testnet, stopped producing new blocks. Validators nodes stopped with the error:</p><pre>ERRO error in proxyAppConn.FinalizeBlock      module=state err=&quot;send coins from account to module: spendable balance 774789697stake is smaller than 1087941168stake: insufficient funds</pre><p>After identifying the potential root cause, a code change PR was created around 10:00 AM to recover the network.</p><p>Around 01:15 PM, after testing the code change and deployment, the iliad network was recovered and produced new blocks five hours after the outage started.</p><h3>Root Cause Analysis</h3><h4>Context</h4><p><strong>Consensus/Execution separation<br></strong>Story uses the Cosmos SDK and Cometbft as the consensus client (CL) and Ethereum’s geth as the execution client (EL). These two clients communicate with each other through the Engine API interface. Delegators can stake/unstake tokens through the EL’s JSON RPC interfaces, but the staked token balances will be tracked in the CL to determine the validator’s voting power.</p><p><strong>Unbonding<br></strong>When delegators unstake their tokens, they go to an unbonding queue in CL. After a predefined unbonding time, they are unbonded and removed from the queue. The tokens then go to the delegators’ CL account.</p><p><strong>Token withdrawal flow<br></strong>For every block, the CL will check the unbonding queue, see which unstaking requests are mature and will be removed from the queue. It then tells the unbonding queue to pop out all the mature unbonding requests and <strong>assumes that these mature unbonding tokens will all be added to the delegators’ CL balance</strong>. For example, if there are three mature unstaking requests for the current block, with each request to unstake 10 IP tokens, CL will assume these 30 IP tokens to be sent to the delegator’s account. The CL will panic and halt if there are less than 30 IP tokens in the delegator’s account. This is the error we see above for this incident.</p><h4>The Issue</h4><p>The issue here is the assumption CL makes: it assumes that the unbonding queue will pop out all the mature unbonding requests. However, based on the cosmos code, there are many scenarios (<a href="https://github.com/piplabs/story/issues/193">more details here</a>) where mature unbonding requests will not pop out. Hence, the tokens won’t be sent to the delegators’ accounts. Unfortunately, cosmos currently doesn’t log the errors for these scenarios. So, we cannot directly pinpoint the issue from the log.</p><h3>The Mitigation</h3><p>We put in a quick <a href="https://github.com/piplabs/story/releases/tag/v0.10.1">release</a> to mitigate and recover the network after the incident broke out: The CL doesn’t need to throw a panic here. It can send whatever is in the delegator’s CL balance to its EL balance. If the token balance hasn’t been added to the delegator’s CL balance, it must still be in the unbonding queue and may be mature in future blocks. CL won’t miss any payment to the EL for any unstaking requests as long as this property doesn&#39;t break. You can find the commits for the release here: <a href="https://github.com/piplabs/story/commit/89b90f72db3ff6e3c00f47a4769c7d1ce9e03fde">commit1</a>, <a href="https://github.com/piplabs/story/commit/dfdd687bd5274843b63b9e6ad053add4d69034dd">commit2</a>, <a href="https://github.com/piplabs/story/commit/cddfe8b03400546ab9ba7108b0900f8234d5749a">commit3</a>.</p><p>We understand this is a quick mitigation to recover the network, not the fix. The fix will be included in our next testnet release.</p><h3>Next Steps</h3><p>The reason that we had the assumption that the cosmos unbonding queue will unbond all mature unbondings is that cosmos SDK’s function that does the actual unbonding doesn’t return which unbonding requests have been unbonded from the queue. The fix we will put in is to modify the function to return the actual unbonded requests that are unbonded from the queue. In this case, there won’t be a mismatch between what we see and what gets unbonded.</p><p>Additionally, we will add missing error logs in this part of the logic to identify the errors that happen during the unbonding process. This will help us catch any potential payment mismatches and security issues.</p><p>You can track the progress of the fix in this <a href="https://github.com/piplabs/story/issues/197">Github issue</a>.</p><p><em>Story’s Blockchain Lead, Ze Huang, wrote this report. You can follow him on twitter </em><a href="https://x.com/edisonz0718"><em>@edizon0718</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d15b07719e7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/story-protocol/09-29-24-iliad-network-outage-incident-report-analysis-1d15b07719e7">09–29–24 Iliad Network Outage: Incident Report &amp; Analysis</a> was originally published in <a href="https://medium.com/story-protocol">Story Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recovering Story Clients after Missing Block Height]]></title>
            <link>https://medium.com/story-protocol/recovering-story-clients-after-missing-block-height-b34d51b666c8?source=rss----144390f1ab20---4</link>
            <guid isPermaLink="false">https://medium.com/p/b34d51b666c8</guid>
            <category><![CDATA[intellectual-property]]></category>
            <category><![CDATA[story-protocol]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[decentralization]]></category>
            <dc:creator><![CDATA[Boris Polania]]></dc:creator>
            <pubDate>Thu, 03 Oct 2024 20:29:48 GMT</pubDate>
            <atom:updated>2024-10-03T20:27:46.243Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GeVz0GkgW5PTizX3DnUNAA.png" /></figure><p>In the event of a Story-Geth upgrade, if a node is not updated by a specific block height, the Story client may panic because it cannot reach consensus with other nodes that have already upgraded their Geth clients.</p><p>When this happens, you might see some of the following errors in Story-Geth:</p><pre>WARN [10-01|10:48:18.631] Failed to load old bad blocks error=&quot;pebble: not found&quot;</pre><pre>WARN [10-01|10:48:18.641] NewPayloadV1: inserting block failed error=&quot;invalid gas used (remote: 31469 local: 30450)&quot;</pre><p>And Story Client:</p><pre>24-10-01 10:48:20.749 ERRO prevote step: consensus deems this block invalid; prevoting nil module=consensus height=55 round=0 err=&quot;wrong Block.Header.AppHash.</pre><pre>24-10-01 10:48:20.876 ERRO CONSENSUS FAILURE!!! module=consensus err=&quot;precommit step; +2/3 prevoted for an invalid block: wrong Block.Header.AppHash.</pre><h3>Recovering Steps</h3><ol><li>First, ensure the Story Client includes the rollback feature by getting the latest version. You can download it <a href="https://github.com/piplabs/story/releases">here</a>.</li><li>Now, attempt a rollback on the Story Client with the following command:<br>./story rollback — home=${STORY_PATH} — hard<br>Note that ${STORY_PATH} should be the directory including configs and data of Story Client. Default settings can be found <a href="https://docs.story.foundation/docs/node-setup#default-folder">here</a>.</li><li>Now, you should see the message Rolled back state to … confirming that a rollback of one block was successfully performed:<br>24–10–01 12:24:48.335 DEBU Finished loading IAVL tree <br>Rolled back state to height 3099 and hash ...</li><li>Upgrade Geth to the expected version (e.g., v0.9.3) and restart the services in the following order:<br>1. Stop old Story-Geth<br>2. Start new Story-Geth<br>3. Start Story</li><li>Your node should sync successfully to the latest block.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b34d51b666c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/story-protocol/recovering-story-clients-after-missing-block-height-b34d51b666c8">Recovering Story Clients after Missing Block Height</a> was originally published in <a href="https://medium.com/story-protocol">Story Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Upgrading Story-Geth]]></title>
            <link>https://medium.com/story-protocol/upgrading-geth-execution-client-from-0-9-2-to-0-9-3-d2cff671b91e?source=rss----144390f1ab20---4</link>
            <guid isPermaLink="false">https://medium.com/p/d2cff671b91e</guid>
            <category><![CDATA[intellectual-property]]></category>
            <category><![CDATA[geth]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[story-protocol]]></category>
            <dc:creator><![CDATA[Boris Polania]]></dc:creator>
            <pubDate>Wed, 25 Sep 2024 02:05:45 GMT</pubDate>
            <atom:updated>2024-11-19T02:32:36.858Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GeVz0GkgW5PTizX3DnUNAA.png" /></figure><p>To upgrade your Story-Geth node, follow the following steps carefully to ensure everything runs smoothly.</p><p>We assume you’re running a node on the Odyssey network with the following setup:</p><pre>geth --odyssey --syncmode full #execution client<br>story run #consensus client</pre><p>To upgrade Story-Geth to a new version (e.g., on the Odyssey network), follow the below steps:</p><ol><li><strong>Get the Latest Version.</strong> Download or build the newest Story-Geth binary from our <a href="https://github.com/piplabs/story-geth/releases">release page</a> to stay current.</li><li><strong>Graceful Shutdown.</strong> Stop your story consensus client without interrupting any critical processes. A simple Ctrl+C will do the trick if you&#39;re running it manually. For those using systemd, you can use systemctl stop story.</li><li><strong>Pause Your Geth Execution Client.</strong> Apply the same method for your Story-Geth execution client. Note where you stopped to ensure a seamless restart.</li><li><strong>Launch the Updated Version.</strong> Now, it’s time to run the new version. Start your updated Story-Gethclient with geth --odyssey --syncmode full. Remember, if using a custom data directory, include the --datadir /path/to/your/geth/data flag.</li><li><strong>Restart Your Consensus Client.</strong> Restart your storyconsensus client as you did before.</li></ol><p>Your node will pick up where it left off, now with the upgraded execution client fully operational!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2cff671b91e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/story-protocol/upgrading-geth-execution-client-from-0-9-2-to-0-9-3-d2cff671b91e">Upgrading Story-Geth</a> was originally published in <a href="https://medium.com/story-protocol">Story Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Story v0.13.0 Node Upgrade Guide]]></title>
            <link>https://medium.com/story-protocol/story-v0-10-0-node-upgrade-guide-42e2fbcfcb9a?source=rss----144390f1ab20---4</link>
            <guid isPermaLink="false">https://medium.com/p/42e2fbcfcb9a</guid>
            <category><![CDATA[intellectual-property]]></category>
            <category><![CDATA[story-protocol]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Boris Polania]]></dc:creator>
            <pubDate>Sat, 14 Sep 2024 02:03:48 GMT</pubDate>
            <atom:updated>2024-12-10T01:57:03.152Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GeVz0GkgW5PTizX3DnUNAA.png" /></figure><p>This guide provides instructions for upgrading your node to Story v0.13.0.</p><h3>Upgrading Your Node</h3><p>The upgrade process outlined in this guide includes automated and manual approaches to ensure that your node is correctly updated and continues functioning as expected in the upgraded network. The automated upgrade section will cover Cosmovisor, a tool that streamlines the upgrade process by automating various tasks and minimizing node downtime. The manual upgrade section will guide you through the steps to upgrade your node manually, including monitoring the node, stopping and restarting the client, and verifying the upgrade status.</p><h3>Automated Upgrade Procedure with Cosmovisor</h3><p>To simplify the process of upgrading your consensus client, especially during hard forks, it is recommended to use <a href="https://docs.cosmos.network/v0.45/run-node/cosmovisor.html">Cosmovisor</a>. This tool automates the upgrade of client binaries, allowing the node to transition smoothly without requiring manual stops and restarts.</p><p><strong><em>Please note that the installed Cosmovisor version must be at least v1.7.0. Please follow </em></strong><a href="https://docs.cosmos.network/main/build/tooling/cosmovisor"><strong><em>this guide</em></strong></a><strong><em> if you need help setting up or configuring Cosmovisor.</em></strong></p><p><strong>1.Prepare the Story Client Environment<br></strong>To upgrade to Story <a href="https://github.com/piplabs/story/releases/tag/v0.13.0">v0.13.0</a>, the existing story client must first be running version <a href="https://github.com/piplabs/story/releases/tag/v0.12.1">v0.12.1</a>.</p><p>To download the v0.12.1 binaries directly, run the following:</p><ul><li>Linux x86_64</li></ul><pre>wget https://github.com/piplabs/story/releases/download/v0.12.1/story-linux-amd64</pre><ul><li>Linux ARMv8</li></ul><pre>wget https://github.com/piplabs/story/releases/download/v0.12.1/story-linux-arm64 </pre><ul><li>Mac x86_64</li></ul><pre>wget https://github.com/piplabs/story/releases/download/v0.12.1/story-darwin-amd64 </pre><ul><li>Mac 64-bit ARM</li></ul><pre>wget https://github.com/piplabs/story/releases/download/v0.12.1/story-darwin-arm64</pre><p><strong>2. Setup and Configure Cosmovisor</strong></p><p><strong><em>You can skip this step if cosmovisor is already running; in that case, proceed directly to step 5.</em></strong></p><p>As mentioned above, <a href="https://docs.cosmos.network/main/build/tooling/cosmovisor">Cosmovisor must be installed</a> to at least version v1.7.0 to upgrade Story.</p><p>You can verify that Cosmovisor was successfully installed by checking its current version:</p><pre>cosmovisor version</pre><p>Expected sample output:</p><pre>% cosmovisor version<br>cosmovisor version: v1.7.0</pre><p>Once done, define the necessary environment variables needed to configure Cosmovisor:</p><pre>export DAEMON_HOME=${STORY_DATA_ROOT}<br>export DAEMON_NAME=story<br>export DAEMON_DATA_BACKUP_DIR=~/story_backup_folder # Specify your backup directory</pre><p><strong>STORY_DATA_ROOT</strong> refers to the data root folder used by the story client — by default, it is assigned the following values, which you should use unless overriding with your folder:</p><ul><li>Mac OS X: ~/Library/Story/story</li><li>Linux: ~/.story/story</li></ul><p>For <strong>DAEMON_NAME</strong>, ensure it is the same as the name of the story client binary, which should be <em>story</em>.</p><p>The <strong>DAEMON_DATA_BACKUP_DIR</strong> can be set to any custom data backup directory.</p><p><strong>3. Initialize Cosmovisor:</strong></p><p><strong><em>You can skip this step if cosmovisor is already running; in that case, proceed directly to step 5.</em></strong></p><p>Once Cosmovisor is already setup and configured, initialize it with:</p><pre>cosmovisor init ${STORY_CLIENT}</pre><p>Example command:</p><pre>cosmovisor init /usr/local/bin/story</pre><p>Verify that Cosmovisor was successfully installed by checking its current version:</p><pre>cosmovisor version</pre><p>Expected sample output:</p><pre>% cosmovisor version<br>cosmovisor version: v1.7.0</pre><p><strong>4. Run Story as a Managed Process</strong></p><p><strong><em>You can skip this step if cosmovisor is already running; in that case, proceed directly to step 5.</em></strong></p><p>Start <strong>story</strong> under Cosmovisor’s management by running the following command (note that the first <strong>run</strong> is to start Cosmovisor, and the second is the story <strong>run</strong> command):</p><pre>cosmovisor run run</pre><p>To verify that the Story client is running correctly is running correctly, follow our <a href="https://docs.story.foundation/docs/odyssey-node-setup#/">documentation</a> for more information about this step.</p><p><strong>5. Schedule the Client Upgrade</strong></p><p>Start by downloading <a href="https://github.com/piplabs/story/releases/tag/v0.13.0#:~:text=Assets">Story v0.13.0 binaries</a> into a local folder:</p><ul><li>Linux x86_64</li></ul><pre>wget https://github.com/piplabs/story/releases/download/v0.13.0/story-linux-amd64</pre><ul><li>Linux ARMv8</li></ul><pre>wget https://github.com/piplabs/story/releases/download/v0.13.0/story-linux-arm64</pre><ul><li>Mac x86_64</li></ul><pre>wget https://github.com/piplabs/story/releases/download/v0.13.0/story-darwin-amd64</pre><ul><li>Mac 64-bit ARM</li></ul><pre>wget https://github.com/piplabs/story/releases/download/v0.13.0/story-darwin-arm64</pre><p>To schedule an upgrade to a new client version at a specific block height, <em>cosmovisor should already be running</em>. Once confirmed, open a separate terminal and run:</p><pre>cosmovisor add-upgrade ${CLIENT_VERSION} ${NEW_STORY_CLIENT} --force --upgrade-height ${UPGRADE_HEIGHT}</pre><p>Then run the following command to check if the upgrade was successfully scheduled:</p><pre>cat ${PATH_TO_STORY_DATA}/upgrade-info.json</pre><p><strong>Example commands:</strong></p><p>Schedule the upgrade:</p><pre>cosmovisor add-upgrade v0.13.0 story-linux-amd64/story --force --upgrade-height 858000</pre><p>Verify whether it was successfully scheduled:</p><pre>cat /home/ec2-user/story/data/upgrade-info.json</pre><p>Afterward, the console should display the following output:</p><pre>{&quot;name&quot;:&quot;v0.13.0&quot;,&quot;time&quot;:&quot;0001-01-01T00:00:00Z&quot;,&quot;height&quot;:858000}</pre><p>If the output is not as expected, delete the upgrade-info.json file, rerun the cosmovisor add-upgrade command, and verify the result again.</p><p>If successfully scheduled, cosmovisor will automatically replace the current consensus client with the new binary at the specified upgrade height.</p><p>To confirm that the replacement was successful, running the cosmovisor version command should display the path corresponding to the upgraded version, as shown in the following example:</p><pre> % cosmovisor version<br>cosmovisor version: v1.7.0<br>11:27PM INF running app args=[&quot;version&quot;] module=cosmovisor path=/home/ec2-user/story/cosmovisor/upgrades/v0.13.0/bin/story<br>Version       v0.13.0-stable<br>Git Commit    9603826<br>Git Timestamp 2024-19-05T15:43:11Z</pre><h3>Manual Upgrade Procedure for Story Client</h3><ol><li><strong>Wait for the Node to Reach the Upgrade Block Height. </strong>Monitor the node until it reaches the predetermined upgrade block height. The story client should automatically panic at this point, signaling that the node has reached the upgrade height.</li><li><strong>Stop the Existing Story Client. </strong>Once the node reaches the upgrade block height and the story client panics, stop the existing story client to prepare for the upgrade. This can be done by terminating the process running the client.</li><li><strong>Start the New Story Client. </strong>Replace the old story client with the new version. Then, start the new story client to initiate the upgrade process. To verify that the Story client is running correctly, follow our Public Testnet Guide for <a href="https://docs.story.foundation/docs/story-network">more information about this step</a>.</li><li><strong>Verify Node Status Post-Upgrade. </strong>Check the status of the new story client to ensure it either continues to function correctly or enters a waiting state. The network requires upgrading at least two-thirds of the voting power before resuming normal operations. Verify that the node correctly joins the upgraded network and reaches consensus. You can read our <a href="https://docs.story.foundation/docs/story-network">documentation</a> for more information about this step.</li></ol><h3>Unjailing</h3><p>If a node becomes jailed, run the following command on the validator:</p><pre>./story validator unjail --validator-pubkey={validator_public_key} --rpc https://odyssey.storyrpc.io/ --chain-id 1516</pre><p>Replace the validator_public_key value with the validator’s actual public key, and verify that the address has a balance of at least 1 IP.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42e2fbcfcb9a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/story-protocol/story-v0-10-0-node-upgrade-guide-42e2fbcfcb9a">Story v0.13.0 Node Upgrade Guide</a> was originally published in <a href="https://medium.com/story-protocol">Story Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Story v0.10.0 Available for Coming Upgrade]]></title>
            <link>https://medium.com/story-protocol/story-v0-10-0-available-for-coming-upgrade-e2f9cb10443b?source=rss----144390f1ab20---4</link>
            <guid isPermaLink="false">https://medium.com/p/e2f9cb10443b</guid>
            <category><![CDATA[intellectual-property]]></category>
            <category><![CDATA[story-protocol]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[decentralization]]></category>
            <dc:creator><![CDATA[Boris Polania]]></dc:creator>
            <pubDate>Fri, 13 Sep 2024 04:06:57 GMT</pubDate>
            <atom:updated>2024-09-14T05:32:05.239Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GeVz0GkgW5PTizX3DnUNAA.png" /></figure><p>Story v0.10.0 binaries were released today, September 12, 2024, in preparation for the scheduled upgrade at block height 626,575, estimated to arrive on September 17, 2024, at 17:00 UTC. This update brings essential improvements to network performance. All nodes are required to upgrade to this latest stable version at (not before) the upgrade block height to continue running a node on the Iliad network.</p><p><strong>Overview<br></strong>Story v0.10.0 is a major release that optimizes reward distribution sweeping logic to reduce block time further. For more details, read the <a href="https://github.com/piplabs/story/releases/tag/v0.10.0">Release Notes</a>.</p><p>Detailed instructions for the upgrade will be provided soon, along with a more accurate time estimate for when the upgrade will occur. Stay tuned for further updates.</p><p><strong>Node Operator Action Required</strong></p><p>All node operators must upgrade to client version v0.10.0 at 626,575 block height. Nodes running older versions will become incompatible and halted after the block height, estimated to arrive on September 17, 2024, at 17:00 UTC.</p><p>You can download Story v0.10.0 binaries <a href="https://github.com/piplabs/story/releases/tag/v0.10.0#:~:text=public%20Discord.-,Binaries,-Users%20may%20download">here</a>.</p><p><strong>Need Support?</strong></p><p>If you have any questions or need support, contact us on <a href="https://discord.gg/StoryProtocol">Discord</a> and <a href="https://x.com/StoryEngs">X (formerly Twitter)</a>.</p><p><strong><em>Make sure your nodes are ready for the upgrade to stay connected!</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2f9cb10443b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/story-protocol/story-v0-10-0-available-for-coming-upgrade-e2f9cb10443b">Story v0.10.0 Available for Coming Upgrade</a> was originally published in <a href="https://medium.com/story-protocol">Story Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Story Protocol]]></title>
            <link>https://medium.com/story-protocol/introducing-story-protocol-cadddfdb3dac?source=rss----144390f1ab20---4</link>
            <guid isPermaLink="false">https://medium.com/p/cadddfdb3dac</guid>
            <dc:creator><![CDATA[Story Protocol]]></dc:creator>
            <pubDate>Wed, 06 Sep 2023 09:01:13 GMT</pubDate>
            <atom:updated>2023-09-06T09:01:13.577Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OYjLSQhfS775RMqtqtJaew.png" /></figure><h3>Abstract</h3><p><em>The internet is the most powerful creative tool in history. Creative works are connected, remixed, and distributed at zero marginal cost.</em></p><p><em>Despite the abundance of content creation on the internet, creators struggle to grow and capture the value of their intellectual property. The traditional IP model is both opaque and slow. Provenance and attribution need to happen at the speed and scale of the web.</em></p><p><em>By creating an IP framework that embraces the internet’s fundamental principles of openness and collaboration, Story Protocol aims to become the native IP infrastructure of the internet. The protocol will provide a neutral source of provenance to track the lifecycle of an IP as it evolves across mediums and platforms in addition to modules that power frictionless licensing and remixing of IP.</em></p><p><em>Just as Git revolutionized the development of open-source software by underpinning the networked evolution of code, Story Protocol aims to transform the development of creative IP.</em></p><h3>A New Era of Intellectual Property</h3><p>Nearly 600 years after the Gutenberg press accelerated the reproduction of creative works, the internet has evolved into the ultimate idea-propagation machine. And just as the Gutenberg press necessitated the first copyright laws, the digital era demands new IP infrastructure.</p><p>The internet not only amplifies the abilities of the printing press, but also introduces a new paradigm of networked creation. Everyone can remix and distribute content at zero marginal cost. Consider mash-ups on TikTok (Khaby Lame became the most followed account on TikTok through dueting other videos), spinoff stories on fanfiction.net (<em>Fifty Shades of Grey</em> was originally posted there as <em>Twilight</em> fanfiction), sampling on SoundCloud (remixes ignited Kygo, Zedd, and Diplo’s popularity as DJs), and even mod culture in gaming (<em>Defense of the Ancients</em> was a mod of <em>Warcraft III</em> and ultimately inspired hits like <em>League of Legends</em>). People who were previously passive consumers are becoming producers, shaping the culture towards networked development of creative works.</p><p>These networked IPs are becoming the new norm, and artificial intelligence will supercharge this transition, shifting the internet towards ever-lower costs of production. In a culture where replication is instantaneous and remixing is inevitable, we need a new IP regime that respects the rights of creators while acknowledging the fact that creation on the internet is “an endless, recombinant, and fundamentally social <a href="http://www.wired.com/wired/archive/13.07/gibson.html">process</a>.”</p><p>However, our IP system is still deeply wedded to the analog age. Though the architecture of IP today maintains its basic commitments to incentivizing creative work, it overlooks the open nature of value creation on the internet. Our current IP infrastructure is too unwieldy to support remixing, community lore, and co-creation as foundational pillars of creativity. Instead of leaning into the fundamental force of the internet — openness — most IP models emphasize a defensive stance, adding friction to the creative process.</p><p>Before we can unlock the full creative power of the internet, we must upgrade our IP infrastructure so that it works with the web instead of fighting it. This requires embracing the abundance and sociality of the internet while allowing creators to be rewarded for their work. Doing so will enable an explosion of creative works that can evolve at the unprecedented speed and scale of the internet.</p><h3>Requirements for an Internet-Native IP Infrastructure</h3><p>To build this IP infrastructure, there are two fundamental requirements.</p><p><strong>First, the internet needs a standard to track the origin and evolution of IP.</strong> Creation on the internet trends towards zero marginal costs, making the space of content practically infinite. Such abundance of content is one of the superpowers of the internet, but this abundance also makes it extremely difficult for creators to be compensated for the value that they generate. Without a way to trace the lifecycle of IP from the instant of creation to any remixes or derivatives made later, creators lack the ability to ensure that they are compensated for the usage of their work. And as AI makes the production of high fidelity content frictionless, the need for a scalable provenance and attribution solution is only growing more urgent.</p><p><strong>Second, the internet needs a seamless and scalable licensing regime. </strong>We not only need to record the provenance of IP, but also offer the tools to extend that IP in a way that allows creators and contributors to capture the value of their work. The current licensing system is often opaque and complex: every license must be custom negotiated on a one-to-one basis, thwarting collaboration and remixing. This high-friction licensing model is an uphill battle against the recombinant nature of the internet, which requires a more open scheme where IP owners can set the parameters for their licensing rights, resulting in scalable one-to-many licensing. If we can provide primitives for frictionless extension of IP that can be plugged into any software application, the next generation of IP will see not only more value capture for creators but also the largest franchises to date.</p><h3>Introducing Story Protocol</h3><p>The protocol elevates IP into the internet era by providing both an open IP repository and a set of modules to interact with that IP in a frictionless way.</p><p>Our open IP repository enables creative IPs — prose, images, audio, and more — to record their evolutionary journey from inception through the endless combinatorics of digital co-creation. Just as Git enabled the tracking of code through branching and versioning, Story Protocol aims to become the provenance layer for creative IP.</p><p>Beyond tracking the attribution of IP as it grows, our modules power seamless composability, allowing anyone to contribute to an IP and to capture the value of their contribution. Our modules add functionality on top of the IP repository, analogous to how GitHub extended the capabilities of Git by providing forking and pull requests.</p><h4>Nouns and Verbs</h4><p>To realize this vision, our protocol architecture consists of two elements: data structures and modules. The data structures are the “nouns” of the protocol, storing relevant IP metadata into “IP legos.” The modules are the “verbs,” enabling a diverse array of functionality for the IP assets registered on the protocol. Story Protocol’s data structures capture the core components of IP, and its modules represent the operations that can be performed on the data structures.</p><p><strong>The data structures (“nouns”) address the first fundamental requirement of internet-native IP by providing a technical standard for tracking provenance and attribution.</strong> Just as the creation of protocols like HTTP, HTML, and CSS accelerated internet adoption by enabling reliable and structured information sharing, IP on Story Protocol is designed to be similarly streamlined. This standardization makes it simple for any application to leverage our data structures as a global source of provenance.</p><p><strong>Our modules (“verbs”) address the second requirement of internet-native IP by enabling frictionless extension of IP. </strong>Once IP is captured in our IP legos, it can be composed and expanded through our modules. Modules are functions that unlock an array of abilities like licensing, revenue streams from derivative works, and access to global capital. For example, our licensing module enables programmable licenses to be generated with the same flexibility and expressivity as code, like a programmable Getty Images that works for all forms of IP. Instead of relying on one-to-one legal negotiations, creators can set their licensing conditions transparently for others to seamlessly extend their work.</p><h4>Built on Blockchain</h4><p>This entire infrastructure — the data structures and modules — is built on blockchain. As content proliferates on the internet, blockchains offer provenance and authenticity without the need for an intermediate entity. Crucially, the decentralized nature of blockchain empowers builders to create applications on the protocol without fear of interference.</p><h3>A Thriving IP Ecosystem</h3><p>Without these builders, the next era of creative IP cannot be realized. Story Protocol is designed as a base layer for IP applications, but it is only through the efforts of an ecosystem of entrepreneurs and developers building applications on top of the protocol that we can usher in this next era of creativity on the internet. We imagine a robust set of applications — themselves profitable enterprises — that support the entire lifecycle of IP development needs. They represent a new class of services that will exist on top of the protocol in order to support capital formation, co-creation, remixing, and more.</p><p>If these applications — and others yet to be imagined — can be built on Story Protocol, the future of IP may look dramatically different.</p><h4>A New Type of Blockbuster</h4><p>Imagine the next <em>Game of Thrones</em>-level megafranchise emerges on Story Protocol. The creators behind this franchise register a rich, foundational text containing stories, characters, and locations — stored using the data structures on the protocol. Leveraging the licensing module, they can rapidly build a narrative universe and gain economic rewards by licensing rights to translate the work, expand it into new mediums, create spin-offs, produce merchandise, and more. Professional creators and true fans alike can obtain these licenses to grow the narrative. Fans adore these community-driven stories, and the creators leverage the novel ideas and global distribution of their budding community.</p><p>As the initial IP accumulates and expands, so does the value of contributing to the IP. Creators can offer real skin-in-the-game for participants by sharing a portion of their IP rights or revenues using the protocol’s licensing and royalty modules. As the IP grows, there is more incentive for contributors — some amateur, some professional — to join the network with the shared mission of expanding the IP, creating a network effect. Aspiring writers see an opportunity to launch their career by contributing to the canon: a teenage girl from Nigeria contributes a character to the franchise and earns royalties from future earnings, a former Disney writer creates a sequel chapter and makes more than from writing a popular book, a top USC creative writing grad forgoes Hollywood to write full-time on Story Protocol.</p><p>The rising value of the franchise allows the creators to expand into TV and film, with chatter in Hollywood about this being the next big thing. Netflix and HBO are clamoring to sign licensing deals. With proven interest, community, and distribution, the power in the negotiations shifts in the creators’ favor. What’s more, when the IP finally achieves the revenue of a major entertainment franchise, the earliest contributors could receive life-changing rewards.</p><h4>Capturing Value from AI Abundance</h4><p>Generative AI is reshaping creative IP.</p><p>Imagine that a Colombian YouTube star creates a crossover movie between two iconic characters in different franchises by using an advanced version of GPT to create a script and Runway AI to generate the video. It becomes a smash hit, with 200 million views in a matter of weeks. Because the IP for both characters are stored in data structures on Story Protocol, the use of these characters in the AI generated work is tracked automatically. Via the licensing module, any revenue generated by this film instantly flows back to the studios that own each character — much like how profits from YouTube videos with copyrighted music are split with the owner of the copyright itself.</p><p>In this hypothetical, instead of fighting against the inevitable wave of high quality AI generated content, creators and studios actively embrace the abundance of community remixing by storing their IP on Story Protocol. IP is designed not to be siloed but rather as open as possible, becoming the foundation for hundreds of inspired works that grow the value of the underlying property. Popular internet artists begin to allow anyone to generate images in their distinct style, as long as any monetization of the derivative works sends a percentage of revenue back to them. Musicians follow suit. AI has the potential to be part of the value capture problem, but Story Protocol makes AI part of the solution via proper attribution and compensation, allowing creators to leverage the explosion in AI content to capture more value than ever before.</p><h4>IP Liquidity</h4><p>Imagine a future where IP emerges as a liquid asset. Previously notoriously illiquid, IP is now plugged into the broader DeFi ecosystem via the composability of Story Protocol’s global IP repository. Popular IP marketplaces enable a marketplace between creators, fans, and producers. This new ecosystem of “IP finance” generates efficient price discovery for IP, which offers better funding mechanisms for creative works as well as the derivatives that form around them. A whole new world of applications around IP is developed, offering unprecedented expansion opportunities for creators and their communities.</p><h3>Bridging Code and Law</h3><p>By bridging the world of off-chain IP with the programmability of blockchain assets, Story Protocol is uniting code and law: allowing IP to work <em>with</em> the openness and abundance of the internet instead of against it.</p><p>The internet has introduced revolutionary new methods of developing and distributing creative work: endless remixing, participatory franchises, and AI-generated content. However, our current intellectual property infrastructure works against the openness of the internet instead of embracing it. Story Protocol is building an IP infrastructure optimized for the internet era.</p><p><em>Thanks to Sonal Chokshi, Chris Dixon, Simon Seojoon Kim, Scott Kominers, Sriram Krishnan, Eddy Lazzarin, Jon Rogers, Charlie Songhurst, Timshel, Liang Wu, and Joseph Young for suggestions and inspiration.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cadddfdb3dac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/story-protocol/introducing-story-protocol-cadddfdb3dac">Introducing Story Protocol</a> was originally published in <a href="https://medium.com/story-protocol">Story Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>