<?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[Stories by Denis Fadeev on Medium]]></title>
        <description><![CDATA[Stories by Denis Fadeev on Medium]]></description>
        <link>https://medium.com/@dfadeev?source=rss-2ef88d6ad83b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fFn1qbF3s_ZerE6FeKAzEQ.jpeg</url>
            <title>Stories by Denis Fadeev on Medium</title>
            <link>https://medium.com/@dfadeev?source=rss-2ef88d6ad83b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:11:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dfadeev/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ZetaChain’s New Revert Handling for Cross-Chain]]></title>
            <link>https://medium.com/zetachain-tech-blog/zetachains-new-revert-handling-for-cross-chain-313629c92e63?source=rss-2ef88d6ad83b------2</link>
            <guid isPermaLink="false">https://medium.com/p/313629c92e63</guid>
            <category><![CDATA[zetachain]]></category>
            <category><![CDATA[interoperability]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[solidity]]></category>
            <dc:creator><![CDATA[Denis Fadeev]]></dc:creator>
            <pubDate>Wed, 19 Feb 2025 08:30:42 GMT</pubDate>
            <atom:updated>2025-02-19T08:30:42.146Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ee_TZHYUpiYoQdW5BCujKQ.png" /></figure><p><strong>ZetaChain’s new </strong><strong>onAbort mechanism prevents stuck assets in cross-chain transactions. With </strong><strong>onRevert for rollbacks and </strong><strong>onAbort as a failsafe, every transaction is either executed or accounted for — ensuring seamless failure recovery without manual intervention. Learn more here.</strong></p><h3>Why Reverts Matter in Cross-Chain Transactions</h3><p>If you’ve ever interacted with a smart contract and seen your transaction fail, you’ve likely encountered a “revert.” A revert occurs when a contract refuses to execute a transaction, undoing any changes and returning an error.</p><p>While it’s not an ideal scenario, reverts are a built-in safety feature that ensures only valid transactions are processed. They effectively roll back all changes made to the state during the transaction, helping prevent unintended effects or harmful actions.</p><p>But handling reverts in cross-chain applications is far more complex than on a single chain. If a failure occurs on one blockchain, it can cause ripple effects that impact other parts of the application. Without proper handling, assets can get stranded, smart contract logic can break, and users can be left in a frustrating state of uncertainty.</p><h3>The Challenge: Why Cross-Chain Reverts Are Hard</h3><p>In a single-chain smart contract, revert handling is straightforward: the transaction fails, and all state changes are rolled back automatically. In a cross-chain environment, however, things are not as simple:</p><ol><li>What happens if a transaction fails after crossing chains?</li><li>How do we ensure assets aren’t stuck if a cross-chain transaction doesn’t complete?</li><li>Who pays for the gas needed to execute a revert?</li></ol><p>Many existing cross-chain solutions do not handle reverts natively, leaving developers to build their own rollback logic or rely on manual intervention.</p><h3>How ZetaChain Handles Cross-Chain Reverts</h3><p>ZetaChain provides a built-in framework for managing cross-chain failures automatically, preventing a single failure from leaving an application in a broken or inconsistent state.</p><h3>Types of Transactions: Incoming vs. Outgoing</h3><p>To understand ZetaChain’s approach, let’s define two types of cross-chain transactions:</p><ul><li>An <strong>incoming</strong> transaction goes from a connected chain (for example, Ethereum) to ZetaChain.</li><li>An <strong>outgoing</strong> transaction goes from ZetaChain to a connected chain.</li></ul><p>ZetaChain provides a structured approach to handling failures in both scenarios, including the new onAbort functionality that mitigates scenarios where a traditional revert process cannot fully complete.</p><h3>Handling Incoming Transactions: A Smarter Revert Process</h3><p>Consider a scenario where a transaction originates on Ethereum and calls a function on ZetaChain using depositAndCall:</p><pre>function depositAndCall(<br>    address receiver,<br>    bytes calldata payload,<br>    RevertOptions calldata revertOptions<br>)</pre><pre>struct RevertOptions {<br>    address revertAddress;<br>    bool callOnRevert;<br>    address abortAddress;<br>    bytes revertMessage;<br>    uint256 onRevertGasLimit;<br>}</pre><p>depositAndCall triggers an exection of the onCall function of a universal contract call on ZetaChain. If the execution succeeds, the transaction completes normally.. However, if onCall fails, ZetaChain attempts a revert.</p><h3>Ensuring There’s Enough Gas for a Revert</h3><p>For ZetaChain to execute a revert transaction back to Ethereum, the original deposit must include enough tokens to cover cross-chain execution fees.</p><p>If the transaction amount is sufficient for a revert, ZetaChain will:</p><ol><li>Use deposited funds to cover the gas costs of the revert. If the deposited amount is in gas tokens, the gas fee will be deducted from the amount. If the deposited amount is in non-gas fungible tokens (for example, supported ERC-20), ZetaChain will swap the amount required for a gas fee on the liquidity pools on ZetaChain (currently, a Uniswap v2 instance is used).</li><li>ZetaChain creates a cross-chain transaction from ZetaChain to Ethereum.</li><li>Call onRevert on the original Ethereum contract:</li></ol><p>The protocol first checks whether the amount of tokens supplied in the original transaction is sufficient to cover the costs of calling back to the source chain. If, for example, making a call from ZetaChain back to Ethereum costs 0.001 ETH, the original deposit must exceed that amount. If the deposited token is not the gas token (e.g., USDC), ZetaChain will use its liquidity pools to swap for enough gas to cover the return call, provided the deposit is sufficient.</p><p>If the amount covers the return call costs, the protocol initiates a cross-chain transaction that returns execution back to the connected chain. On that chain, the contract specified in RevertOptions.revertAddress has its onRevert function called:</p><pre>function onRevert(<br>    RevertContext calldata revertContext<br>) external onlyGateway {<br>    emit RevertEvent(&quot;Revert on EVM&quot;, revertContext);<br>}</pre><pre>struct RevertContext {<br>    address sender;<br>    address asset;<br>    uint256 amount;<br>    bytes revertMessage;<br>}</pre><p>Under normal circumstances, the flow is: Ethereum -&gt; ZetaChain onCall → Ethereum onRevert.</p><h3>Introducing onAbort: Preventing Stuck Transactions</h3><p>But what happens if there aren’t enough funds to pay for the revert? In many cross-chain systems, this would result in an aborted state, leaving assets stranded on the destination chain.</p><p>ZetaChain introduces onAbort, a new mechanism that executes locally on ZetaChain when a traditional revert cannot be completed: Ethereum → ZetaChain onCall fails → Insufficient gas → ZetaChain onAbort executes.</p><p>The onAbort function provides a final failsafe, ensuring assets are never trapped and allowing contracts to recover gracefully.</p><pre>function onAbort(AbortContext calldata abortContext) external {<br>    emit AbortEvent(&quot;Abort on ZetaChain&quot;, abortContext);<br>}</pre><pre>  struct AbortContext {<br>    bytes sender;<br>    address asset;<br>    uint256 amount;<br>    bool outgoing;<br>    uint256 chainID;<br>    bytes revertMessage;<br>}</pre><p>This is particularly critical for non-asset transfer transactions (gatewayEVM.call). Without onAbort, these transactions would have no way to recover.</p><p>The abort context provides the information you need to handle the recovery. sender is the original sender from the connected chain, asset and amount represent the deposited ZRC-20 tokens, chainID is the connected chain&#39;s ID and revertMessage has the same value passed to the original Gateway call. outgoing is false when a call was made from a connected chain and reverted on ZetaChain and true when the call was made from ZetaChain.</p><h3>Handling Outgoing Transactions: When Reverts Happen on Another Chain</h3><p>When a transaction is sent from ZetaChain to a connected chain, the flow is slightly different.</p><p>If the onCall function on the connected chain reverts, a cross-chain transaction automatically calls back into the universal contract on ZetaChain. Because ZetaChain features free cross-chain calls from connected chains, the revert mechanism doesn’t depend on having deposited tokens; the system will still call onRevert on ZetaChain, allowing the contract to handle cleanup or error logic.</p><p>In this scenario, the flow is: ZetaChain → Connected chain onCall reverts → ZetaChain onRevert</p><p>However, if onRevert itself fails on ZetaChain, the onAbort function is triggered to provide a final fallback: ZetaChain → Connected chain onCall reverts → ZetaChain onRevert reverts → ZetaChain onAbort</p><p>While most revert-related logic should be handled gracefully in onRevert, it’s reassuring to have an additional failsafe should something go wrong there as well.</p><h3>Why This Matters: The Future of Cross-Chain Reliability</h3><p>The introduction of onAbort makes ZetaChain’s failure handling far more robust than traditional cross-chain protocols:</p><ul><li>No stranded assets — Every transaction is either fully executed or accounted for.</li><li>Automated failure recovery — Developers no longer need manual fallback solutions.</li><li>Gas-aware reverts — The protocol ensures transactions have the resources they need to fail gracefully.</li><li>Safer cross-chain applications — App logic remains consistent, even in failure scenarios.</li></ul><p>This feature will be available in the next ZetaChain testnet release, and developers can already start integrating it with the <a href="https://github.com/zeta-chain/localnet">latest Localnet version</a>.</p><h3>About ZetaChain</h3><p>ZetaChain is the first Universal Blockchain with native access to Bitcoin, Ethereum, Solana, and more, offering seamless user experience and unified liquidity to the next billions of users. With its Universal EVM, ZetaChain empowers developers to build Universal Apps that operate natively across any blockchain, creating a fluid crypto ecosystem from a single platform.</p><p>Follow ZetaChain on Twitter <a href="https://twitter.com/zetablockchain">@zetablockchain</a> and join the conversation on <a href="https://discord.gg/zetachain">Discord</a> and <a href="https://t.me/zetachainofficial">Telegram</a>. Reach out to <a href="/service/mailto:partnerships@zetachain.com">partnerships@zetachain.com</a> if you’re building on top of ZetaChain.</p><p><strong><em>Any projects mentioned are 3rd party, not ZetaChain.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=313629c92e63" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zetachain-tech-blog/zetachains-new-revert-handling-for-cross-chain-313629c92e63">ZetaChain’s New Revert Handling for Cross-Chain</a> was originally published in <a href="https://medium.com/zetachain-tech-blog">ZetaChain Dev Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to Universal Apps on ZetaChain]]></title>
            <link>https://medium.com/zetachain-tech-blog/introduction-to-universal-apps-on-zetachain-15c1a608caea?source=rss-2ef88d6ad83b------2</link>
            <guid isPermaLink="false">https://medium.com/p/15c1a608caea</guid>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[zetachain]]></category>
            <category><![CDATA[interoperability]]></category>
            <category><![CDATA[evm]]></category>
            <dc:creator><![CDATA[Denis Fadeev]]></dc:creator>
            <pubDate>Tue, 28 Jan 2025 14:25:16 GMT</pubDate>
            <atom:updated>2025-03-12T14:43:52.434Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6pYrhDE9To1cFob2iPvj2w.png" /></figure><p><a href="https://www.zetachain.com/docs/">ZetaChain</a> is an EVM-compatible blockchain with built-in cross-chain interoperability.</p><p>A smart contract deployed on ZetaChain can handle <em>incoming contract calls</em> from any connected blockchain like Ethereum, Base, Polygon, BNB, Solana and Bitcoin. Contracts on ZetaChain can also make <em>outgoing contract calls</em> to contracts on connected chains. Contract calls can contain a payload of arbitrary data as well as gas and supported ERC-20 tokens.</p><p>Gas and ERC-20 tokens transferred to contracts on ZetaChain from connected chains are represented as <a href="https://www.zetachain.com/docs/developers/tokens/zrc20/"><strong>ZRC-20</strong></a> (an ERC-20-like token) on ZetaChain. For example, when you make a call with ETH, a contract on ZetaChain receives ZRC-20 ETH. Under the hood ETH is locked in ZetaChain’s custody on Ethereum and the same amount of ZRC-20 ETH tokens is minted to a contract on ZetaChain. Anyone can permissionlessly withdraw ZRC-20 back into native assets.</p><p>The mechanism that facilitates these incoming (to ZetaChain) and outgoing (from ZetaChain) is called <a href="https://www.zetachain.com/docs/developers/evm/gateway/"><strong>Gateway</strong></a>. Each connected chain has a Gateway that acts as a single entry-point for interacting with contracts on ZetaChain. There are Gateway contracts on <a href="https://www.zetachain.com/docs/developers/chains/evm/">connected EVM chains</a> like Ethereum and Polygon, Gateway program on <a href="https://www.zetachain.com/docs/developers/chains/solana/">Solana</a> and Gateway address on Bitcoin. <a href="https://www.zetachain.com/docs/developers/chains/zetachain/">ZetaChain</a> also has a Gateway contract, which is used to trigger outgoing calls.</p><p>For example, <a href="https://www.zetachain.com/docs/developers/tutorials/swap/">you can write a contract</a> that handles an incoming tokens from one chain, swaps them for target tokens and withdraws them to the destination chain. To perform a cross-chain swap using this contract a user would call a Gateway, for example, on Ethereum with an amount of USDC, which ZetaChain contract to call and data payload containing target token address. ZetaChain validators observing Gateways notice the transaction and make a cross-chain transaction to a swap contract on ZetaChain. A swap contract receives USDC and the payload, executes the swap, and withdraws the target token to the destination chain, for example, Bitcoin. In a single transaction an Ethereum user has initiated a cross-chain contract call to a contract ZetaChain, which swapped ZRC-20 ETH for ZRC-20 BTC and withdrawn native BTC to the recipient on Bitcoin.</p><p>A user was able to make a cross-chain swap between blockchains by making a single transaction on their chain of choice. They didn’t have to worry about gas, bridging assets, or switching wallets. Of course, swapping is just one example. NFT marketplaces, lending platforms, multi-chain governance mechanisms, yield aggregators, and more can be built on ZetaChain.</p><p>We call contracts like these <a href="https://www.zetachain.com/docs/developers/apps/intro/"><strong>universal apps</strong></a>, because they can orchestrate complex cross-chain transactions universally across all connected blockchains. Writing cross-chain apps as universal apps is easy, because most of the logic is encapsulated in a single contract on ZetaChain that can handle incoming calls and make outgoing calls to contracts on other chains.</p><p>Here’s a simple “<a href="https://www.zetachain.com/docs/developers/tutorials/hello/">Hello, World!</a>” universal app:</p><pre>// SPDX-License-Identifier: MIT<br>pragma solidity 0.8.26;<br> <br>import &quot;@zetachain/protocol-contracts/contracts/zevm/GatewayZEVM.sol&quot;;<br> <br>contract Universal is UniversalContract {<br>    event HelloEvent(string, string);<br> <br>    function onCall(<br>        MessageContext calldata context,<br>        address zrc20,<br>        uint256 amount,<br>        bytes calldata message<br>    ) external override {<br>        string memory name = abi.decode(message, (string));<br>        emit HelloEvent(&quot;Hello: &quot;, name);<br>    }<br>}</pre><p>onCall is a special function that gets executed whenever a Gateway on a connected chain is called. Gateways on Ethereum, Solana and Bitcoin all trigger the same onCall function. You can, of course, execute different logic based on the context.chainID or any other parameter.</p><p>It’s easy to <a href="https://www.zetachain.com/docs/developers/tutorials/call/">make outgoing cross-chain calls</a> from universal apps:</p><pre>// SPDX-License-Identifier: MIT<br>pragma solidity 0.8.26;<br><br>import &quot;@zetachain/protocol-contracts/contracts/zevm/GatewayZEVM.sol&quot;;<br><br>contract Universal is UniversalContract {<br>    GatewayZEVM public immutable gateway;<br>    event HelloEvent(string, string);<br>    error TransferFailed();<br><br>    constructor(address payable gatewayAddress) {<br>        gateway = GatewayZEVM(gatewayAddress);<br>    }<br><br>    function call(<br>        bytes memory receiver,<br>        address zrc20,<br>        bytes calldata message,<br>        CallOptions memory callOptions,<br>        RevertOptions memory revertOptions<br>    ) external {<br>        (, uint256 gasFee) = IZRC20(zrc20).withdrawGasFeeWithGasLimit(<br>            callOptions.gasLimit<br>        );<br>        if (!IZRC20(zrc20).transferFrom(msg.sender, address(this), gasFee)) {<br>            revert TransferFailed();<br>        }<br>        IZRC20(zrc20).approve(address(gateway), gasFee);<br>        gateway.call(receiver, zrc20, message, callOptions, revertOptions);<br>    }<br><br>    function onCall(<br>        MessageContext calldata context,<br>        address zrc20,<br>        uint256 amount,<br>        bytes calldata message<br>    ) external override {<br>        string memory name = abi.decode(message, (string));<br>        emit HelloEvent(&quot;Hello on ZetaChain&quot;, name);<br>    }<br>}</pre><p>To make a call:</p><ul><li>Query the gas fee in destination chain’s gas token ZRC-20</li><li>Approve the ZetaChain Gateway to use gasFee ZRC-20</li><li>Execute gateway.call</li></ul><p>zrc20 determines which chain a cross-chain call is made to (use ZRC-20 ETH address to call Ethereum), receiver is the contract being called on the destination chain and message is an arbitrary payload. By default an onCall function on the receiver contract on the destination chain is called, but it is possible to call any other function.</p><p>ZetaChain’s Gateway offers powerful features for developers to handle even the most sophisticated cross-chain scenarios:</p><ul><li>Deposit native gas or supported ERC-20 tokens</li><li>No-asset incoming contract call</li><li>Deposit and call</li><li>Withdraw ZRC-20</li><li>No-asset outgoing contract call</li><li>Withdraw and call</li><li>Outgoing calls to arbitrary functions (not just onCall)</li><li>Revert handling (Ethereum → ZetaChain onCall → Ethereum onRevert)</li><li>Coming soon: Abort handling (Ethereum → ZetaChain onCall → ZetaChain onAbort)</li></ul><p>ZetaChain and its universal apps make cross-chain interactions easier than ever. With ZetaChain, users can interact with your app from any blockchain without worrying about bridging, swapping tokens, or managing gas on multiple chains — it all just works. This opens up endless possibilities for developers to build cool, interconnected features like multi-chain DeFi platforms, NFT marketplaces, games, and much more. If you’ve been wanting to create apps that truly span multiple blockchains while keeping things simple for users, ZetaChain is the perfect place to start. The future of cross-chain innovation is here — time to build!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15c1a608caea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zetachain-tech-blog/introduction-to-universal-apps-on-zetachain-15c1a608caea">Introduction to Universal Apps on ZetaChain</a> was originally published in <a href="https://medium.com/zetachain-tech-blog">ZetaChain Dev Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starport v0.18: Cosmos SDK Updates and Scaffolding Enhancements]]></title>
            <link>https://medium.com/tendermint/starport-v0-18-cosmos-sdk-updates-and-scaffolding-enhancements-5ea5654bcd0c?source=rss-2ef88d6ad83b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ea5654bcd0c</guid>
            <category><![CDATA[starport]]></category>
            <category><![CDATA[cosmos-network]]></category>
            <category><![CDATA[cosmos-sdk]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Denis Fadeev]]></dc:creator>
            <pubDate>Wed, 29 Sep 2021 14:14:35 GMT</pubDate>
            <atom:updated>2021-12-16T17:11:36.471Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4adNB8eFXaOf5CPqQRbfhA.png" /></figure><p><a href="https://github.com/tendermint/starport">Starport</a> has always been committed to providing the latest features for blockchain developers. Over a year ago, Starport started with Cosmos SDK v0.39, then added early support for Stargate, maintained two versions of the Cosmos SDK to smooth the transition, and finally embraced IBC earlier this year. In Starport v0.18, we’ve switched the default blockchain template to the latest Cosmos SDK v0.44. Due to the changes introduced in Cosmos SDK v0.44, this default template switch is a breaking change for Starport, so make sure to read the following section for details.</p><p>Starport v0.18 is also featured-packed with new scaffolding capabilities: using previously scaffolded types as fields for new types, setting a custom transaction signer name, and specifying a custom list of indices for map scaffolding. All of these features make chain development much more streamlined and allow you to prototype your blockchain with just a few commands.</p><h3>Cosmos SDK v0.44 and Breaking Changes</h3><p>Cosmos SDK v0.44 introduced many changes, including new <a href="https://github.com/cosmos/cosmos-sdk/tree/v0.44.0/x/authz">authz</a> and <a href="https://github.com/cosmos/cosmos-sdk/tree/v0.44.0/x/feegrant">feegrant</a> modules, moving <a href="https://github.com/cosmos/ibc">IBC</a> modules into a separate repository, and introducing API changes related to marshallers and codecs. While all of these features are incredibly useful and bring more functionality, the new Cosmos SDK v0.44 version includes changes that break compatibility with chains that were scaffolded for the previous version of Cosmos SDK.</p><p>Starport v0.18 supports Cosmos SDK v0.44 and thus its scaffolding capabilities are incompatible with chains scaffolded with previous versions of Starport. If you have an existing chain using Cosmos v0.42.9 or lower versions, for the best experience we recommend that you upgrade the chain to the latest Cosmos SDK v0.44. See the <a href="https://docs.starport.network/migration/">Upgrading a Blockchain to use Starport v0.18</a> migration document for steps to guide you through the upgrade path from a chain scaffolded with Starport v0.17.x to a chain that is compatible with Starport v0.18.</p><h3>Scaffolding Improvements</h3><p>Scaffolding code is one of the core features of Starport. Starport v0.18 significantly expands the scaffolding functionality of the CLI.</p><h3>Custom Field Types</h3><p>A new type is created when creating a list, map of types, a single type, or using the new starport scaffold type command. In the following example, a Product type is created with two fields: name and quantity.</p><pre>starport scaffold list product name:string quantity:int --no-message</pre><p>You can then use the product type as a field type when creating messages, maps, lists, and singles.</p><pre>starport scaffold message release-product product:Product available:bool</pre><p>This type creation allows for more advanced data modeling when scaffolding functionality for your blockchain.</p><p>When using the blockchain’s CLI, custom types are accepted as JSON:</p><pre>appd tx app release-product &#39;{&quot;name&quot;: &quot;foo&quot;, quantity: 5}&#39; true --from alice</pre><h3>Custom Signer Name</h3><p>By default, the field that contains the address of the signer of the transaction is called creator. This field name works for most cases, but if you would like to use a different name for the field, you can now use the --signer field.</p><pre>starport scaffold list post title body --signer author</pre><h3>Custom Map Index</h3><p>By default, a field is used to index the elements in the store when a map is scaffolded. The field is called index. This field is sufficient for many simple use-cases, but sometimes you might want to customize the name or even provide a list of indices. You can now use the new --index flag for the map command to customize how elements are indexed.</p><pre>starport scaffold map product name price --index date,sku:int</pre><p>In this example, using --index date,sku:int lets a product in the map be indexed by a date (when it was created, for example) and a unique SKU identifier.</p><h3>Cosmos Chain Client</h3><p>To simplify writing Go clients for Cosmos SDK chains, we’ve created the cosmosclient package that provides a streamlined API for broadcasting transactions and querying data from a blockchain.</p><p>To showcase how easy it can be to interact with your chain from a standalone Go program, we’ve written a tutorial that will guide you through this process.</p><h3>Shell Completions</h3><p>With Starport v0.18 we wanted to provide a convenient way for users to navigate the growing number of Starport CLI commands.</p><pre>starport tools completions zsh</pre><p>This example command generates completions for the zsh shell. Use the output of the command and redirect it to your shell config file. To learn more installing command completions, run starport tools completions --help.</p><h3>Other Improvements</h3><ul><li>Starport now checks the version number and suggests upgrading if a newer version is available.</li><li>Standard templates have been extended with genesis validation tests and tests for ValidateBasic methods</li><li>starport version now prints detailed information about OS, Go version, and more</li></ul><h3>Get Started with Starport</h3><p>Are you ready to get started with Starport v0.18?</p><ul><li>Install <a href="https://github.com/tendermint/starport/">Starport CLI</a> with a single command:</li></ul><pre>curl https://get.starport.network/starport! | bash</pre><ul><li>Learn more about building chains: https://docs.starport.network/guide</li></ul><p>Got questions? Join our channel on Discord: <a href="https://discord.gg/vcExX9T">https://discord.gg/vcExX9T</a> where you’ll find an active community of Starport users and developers. They can help you with any doubts and make launching your own Cosmos blockchain and connecting to our ecosystem even easier.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ea5654bcd0c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tendermint/starport-v0-18-cosmos-sdk-updates-and-scaffolding-enhancements-5ea5654bcd0c">Starport v0.18: Cosmos SDK Updates and Scaffolding Enhancements</a> was originally published in <a href="https://medium.com/tendermint">Tendermint Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starport v0.17: Streamlined CLI, Improvements to Scaffolding]]></title>
            <link>https://medium.com/tendermint/starport-v0-17-streamlined-cli-improvements-to-scaffolding-a5332e5fb4ed?source=rss-2ef88d6ad83b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5332e5fb4ed</guid>
            <category><![CDATA[scaffolding]]></category>
            <category><![CDATA[cosmos-network]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cosmos-sdk]]></category>
            <dc:creator><![CDATA[Denis Fadeev]]></dc:creator>
            <pubDate>Fri, 16 Jul 2021 11:53:10 GMT</pubDate>
            <atom:updated>2021-07-16T11:53:10.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rpSYwZ3FZEa9xzlJMlKEUg.jpeg" /></figure><p>In <a href="https://github.com/tendermint/starport">Starport</a> v0.17, we’ve streamlined the command line interface and added these powerful new features:</p><ul><li>A GitHub action that lets you install a chain’s binary with a single command</li><li>Printing of filenames that were modified and created during scaffolding</li><li>New flags and functionality for chain and module scaffolding commands</li><li>New generate commands for generating source code</li><li>Simplified the cmd package</li><li>Support for scaffolding BandChain oracle queries</li><li>Exposed the protoc command for advanced users</li></ul><h3>Streamlined Command Interface</h3><p>We’ve improved the Starport command-line interface by restructuring the top level of the CLI in a more intuitive way to make it easier to navigate between the various features offered by Starport. The commands were reorganized in several top-level groups that correspond to functional areas: scaffold, chain, generate, network, relayer, and tools. We’ve added command aliases so you can type less and scaffold more.</p><h3>Build Me a Blog-Chain</h3><p>How are the commands different? They make more sense! Here’s a quick look at the Starport v0.17 commands that you use in the canonical blog example:</p><pre>starport scaffold chain github.com/cosmonaut/blog</pre><pre>cd blog</pre><pre>starport scaffold list post title body</pre><pre>starport chain serve</pre><h3>Scaffold Commands</h3><p>The scaffold namespace offers commands for scaffolding source code and wiring this code into the blockchain. The purpose of code scaffolding is to save developers&#39; time by automatically creating and modifying files with boilerplate code. Scaffolding also allows a developer to quickly add code to the project that implements create, read, update, and delete (CRUD) logic for a particular data structure.</p><ul><li>chain: a new Cosmos SDK chain</li><li>module: a new Cosmos SDK module in the x directory</li><li>list: CRUD for a type stored as an array, like a list of products</li><li>map: CRUD for a type stored as key-value pairs, like a map of account balances</li><li>single: CRUD for a type stored in a single place in the state, singleton</li><li>message: a Cosmos SDK message for triggering a state transition</li><li>query: a Cosmos SDK query for fetching data from a blockchain</li><li>packet: a Cosmos SDK message with an IBC packet for an IBC module</li><li>band: a BandChain oracle query for an IBC module</li><li>vue: a Vue 3 web app template</li></ul><p>Every command accepts flags that customize its behavior and let you get the most out of Starport. The following examples highlight a few options of what Starport can scaffold.</p><p>A new Cosmos SDK chain without a default module:</p><pre>starport scaffold chain github.com/cosmonaut/mars --no-module</pre><p>To make typing commands faster, scaffold has an alias s.</p><p>A new IBC-enabled Cosmos SDK module that uses a bank keeper:</p><pre>starport s module spaceport --ibc --dep bank</pre><p>All the logic necessary to implement CRUD for a new spaceship type stored as key-value pairs in a particular module (spaceport), but without messages:</p><pre>starport s map spaceship power:int desc --module spaceport --no-message</pre><p>A Cosmos SDK message for assembling spaceships:</p><pre>starport s message assemble-spaceship size:int color --module spaceport</pre><p>A message with an IBC packet for launching spaceships to Earth:</p><pre>starport s packet launch-spaceship spaceshipID destination --module spaceport</pre><h3>Chain Commands</h3><p>The chain namespace contains commands for building, initializing, and starting a blockchain node in development.</p><ul><li>build: build proto files, install dependencies, and compile and install node&#39;s binary</li><li>init: build the binary and initialize a node</li><li>serve: init and start a node in development with hot-reloading enabled</li></ul><h3>Generate Commands</h3><p>The generate namespace is for commands that generate code from existing source code. The code generated with these commands is fully developed and is not meant to be modified by hand.</p><ul><li>proto-go: generate Go source code from protocol buffer files that are required during the build process; the starport c build command generates Go automatically</li><li>vuex: TypeScript/Vuex client code for interacting with the blockchain API using a web browser</li><li>openapi: OpenAPI spec for the blockchain&#39;s API, exposed by default on localhost:1317</li></ul><h3>Other Command Namespaces</h3><ul><li>network: access Starport Network (currently in proof of concept phase)</li><li>relayer: configure a relayer and connect to other chains with IBC</li><li>tools: additional commands for advanced users</li><li>docs: Starport documentation</li></ul><h3>Integration with the BandChain Oracle</h3><p>BandChain is a Cosmos SDK-based cross-chain data oracle platform that lets developers query real-world data from the modules they build. Normally, blockchains cannot access data from external sources, because it is a non-deterministic operation. However, with IBC, your blockchain’s module can make a query an oracle-blockchain (such as BandChain) that already has the data you need and return it back to your chain.</p><p>Starport now offers an easy way to add oracle-querying capability to your IBC-enabled module.</p><p>First, scaffold an IBC-enabled module (if you don’t have one already) inside a chain. Let’s call the module consuming:</p><pre>starport s module consuming --ibc</pre><p>Next, scaffold an oracle query inside the module. Let&#39;s call the query coinRates:</p><pre>starport s band coinRates --module consuming</pre><p>This command creates all the necessary code to query BandChain from your consuming module. Follow <a href="https://docs.starport.network/scaffold/oracle.html">instructions</a> in the Starport documentation to start your blockchain&#39;s node, connect it to BandChain&#39;s testnet with starport relayer, and query BandChain for token prices.</p><p>Querying for external data is an extremely useful feature that lets developers build more advanced blockchain applications that work with stock market data, real-world events, random numbers, weather, and much more.</p><h3>Install Chain&#39;s Binary</h3><p>The Starport chain template now includes a GitHub action that builds the chain&#39;s binary. The chain binary is built upon git push to the default branch and when a release is created on GitHub. The action essentially runs starport build that produces a binary of the node. You can then use the following curl command to install the binary without having to clone and build the project. This GitHub action feature is incredibly handy for validators of your network. Validators can skip the clone-and-build step and just download the binary directly.</p><pre>curl &lt;https://get.starport.network/USER/REPO@latest&gt;! | bash</pre><p>This command fetches and runs the script that installs the binary of your blockchain into /usr/local/bin. Learn more about the <a href="https://github.com/allinbits/starport-installer">starport-installer script</a> to know how you can use it to install a specific version of the binary.</p><h3>Scaffolding Improvements and New CLI Features</h3><p>Scaffold commands now print a list of modified and created files to make it easier to see how the command has affected the project.</p><pre>starport s list post title body</pre><pre>modify proto/mars/genesis.proto<br>create proto/mars/post.proto<br>create x/mars/client/cli/query_post.go<br>...<br>modify x/mars/handler.go<br>create x/mars/keeper/grpc_query_post.go<br>create x/mars/keeper/grpc_query_post_test.g</pre><p>Since Starport v0.16, Starport is bundled with protoc, a protocol buffer compiler, and all the required proto files. In v0.17 we&#39;ve exposed protoc, so it can be used, for example, to generate client-side code for other languages.</p><pre>starport tools protoc</pre><p>When scaffolding a chain, pass the --no-module flag to skip scaffolding of the default module that matches with the name of the project. The following command creates a chain without the x/mars module.</p><pre>starport scaffold chain github.com/cosmonaut/mars --no-module</pre><p>Module scaffolding now accepts --dep flag that lets you specify inter-module dependencies. This dependency feature is useful for using keeper methods from other modules, such as bank, in your custom module.</p><pre>starport scaffold module foo --dep bank</pre><p>The cmd package of the template has been simplified to reduce the amount of boilerplate code.</p><p>Read the full changelog in the <a href="https://github.com/tendermint/starport/blob/develop/changelog.md">changelog.md</a> file.</p><h3>Get Started with Starport</h3><p>Are you ready to get started with Starport v0.17?</p><ul><li>Install <a href="https://github.com/tendermint/starport/">Starport CLI</a> with a single command:</li></ul><pre>curl https://get.starport.network/starport! | bash</pre><ul><li>Learn more about building blockchains: <a href="https://tutorials.cosmos.network/">https://tutorials.cosmos.network</a></li><li>Read Starport documentation: <a href="https://docs.starport.network/">https://docs.starport.network</a></li></ul><p>Do you have questions? Join our channel on Discord: <a href="https://discord.gg/vcExX9T">https://discord.gg/vcExX9T</a> where you’ll find an active community of Starport users and developers. Community members can help answer your questions and make launching your own Cosmos blockchain and connecting to our ecosystem even easier.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5332e5fb4ed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tendermint/starport-v0-17-streamlined-cli-improvements-to-scaffolding-a5332e5fb4ed">Starport v0.17: Streamlined CLI, Improvements to Scaffolding</a> was originally published in <a href="https://medium.com/tendermint">Tendermint Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starport v0.16 Brings Keplr, Better IBC support, and a Whole Lot More]]></title>
            <link>https://medium.com/tendermint/starport-v0-16-brings-keplr-better-ibc-support-and-a-whole-lot-more-b38cb414c144?source=rss-2ef88d6ad83b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b38cb414c144</guid>
            <category><![CDATA[starport]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cosmos-network]]></category>
            <category><![CDATA[tendermint]]></category>
            <dc:creator><![CDATA[Denis Fadeev]]></dc:creator>
            <pubDate>Tue, 25 May 2021 18:35:11 GMT</pubDate>
            <atom:updated>2021-05-25T18:35:11.561Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Knk05V35UKNh8FNjYwlXTQ.jpeg" /></figure><p><a href="https://github.com/tendermint/starport/">Starport v0.16</a> has landed and it makes building your own blockchain easier than ever before. If you’re considering highly scalable, interoperable, and energy-efficient Cosmos technology for your blockchain project, read on to find out more about this significant upgrade — and how to easily deploy your own blockchain in minutes.</p><h3>Starport v0.16</h3><p>With more and more people using <a href="https://github.com/tendermint/starport/">Starport</a> to build their blockchains and experiment with the bleeding-edge technology that Cosmos offers, we decided to make it even easier to use. With Starport v0.16, you can now install Starport with a single click, benefit from improved scaffolding capabilities, and connect to other chains using our groundbreaking <a href="https://ibcprotocol.org/">Inter-Blockchain Communication</a> protocol (IBC).</p><p>One of the major advantages of Starport v0.16 is that it bundles all its dependencies with the binary. This means that, after you install Starport with a single command, you can start building immediately. We’ve also expanded the set of scaffolding commands, made scaffolding more reliable by intelligently detecting placeholders, and even added the ability to scaffold modules in projects that were not created with Starport, providing you maximum flexibility.</p><p>The standard Vue frontend now features Keplr wallet integration, allowing you to connect more easily to your end-users through an intuitive UI. A dedicated relayer section lets you connect your chain to the Cosmos Hub or other IBC-enabled chains and plug into a growing ecosystem of interconnected blockchains. New network functionality provides more control over the process of launching a chain, and you even can pass a custom initial genesis file and manually send &quot;create validator&quot; transactions.</p><h3>Scaffold Tests, Queries, and Modules</h3><p>One of the core features that make Starport so appealing to blockchain developers is the ability to scaffold code to bootstrap the development process. In v0.16, we, therefore, made scaffolding even more reliable and added new components that you can scaffold.</p><p>CRUD scaffolding with type command now generates a full set of tests to promote best development practices and help you better understand how to write tests for Cosmos SDK blockchains. All unit and integration tests are generated automatically. To check out this functionality, simply scaffold some types and run go test ./....</p><p>CRUD is incredibly useful because it allows you to add functionality to your blockchain with a single command. With the ability to run tests, it’s even easier to manage the generated code. One consideration to keep in mind here is that, in some cases, types are updated from the logic within handlers and don’t require messages. This means that, with the new --no-message flag, you can skip scaffolding the messages so that only the code you need is scaffolded. The --no-message flag works for type and packet scaffolding.</p><p>To make scaffolding even more flexible, we’ve also added the starport query command to scaffold a single query. For example:</p><pre>starport query sellOrderBook orderID --response amountDenom,priceDenom</pre><p>Simply pass request fields as arguments and pass comma-separated list responses with a --response (-r) flag. CLI query description can be passed using the optional --desc flag to provide more information about a command to end-users. Often queries require pagination that can be enabled using the optional --paginated flag.</p><p>To make all scaffolding commands even more reliable, we&#39;ve added advanced placeholder tracking that prevents scaffolding code if the required placeholders are not present. This ensures that Starport generates code that can be successfully compiled and prevents scaffolding-related errors.</p><p>Another great addition is the ability to scaffold a Cosmos SDK module even the chain wasn&#39;t scaffolded with Starport. So, for example, a chain like Gaia can be extended with a custom module, and types, messages, and queries can be easily scaffolded.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-AuExRijtrA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-AuExRijtrA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-AuExRijtrA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f527409a3cc548480fa9461d1929f978/href">https://medium.com/media/f527409a3cc548480fa9461d1929f978/href</a></iframe><h3>OpenAPI</h3><p>Starport now automatically generates OpenAPI documentation for your blockchain’s API for standard, imported, and custom Cosmos SDK modules. By default, an OpenAPI document is generated in the docs directory. This document is ready to be published on the web and is embedded in the node&#39;s binary. To make it easier to see available API endpoints and make HTTP requests, a simple Swagger UI is made available when you run starport serve. As with all features in v0.16, we&#39;ve considered ease of use and optimization at every stage.</p><h3>IBC Relayer</h3><p>Relayers play a key role in the network of interconnected blockchains. In the previous Starport release, we included Go relayer functionality to streamline the development of IBC-enabled modules and allow you to quickly and easily connect to other chains both local and remote.</p><p>In v0.16, we’ve switched our CLI commands to use the more robust TypeScript relayer. The interface of high-level starport relayer configure and connect commands hasn&#39;t changed, but now connecting to mainnet chains like Cosmos Hub happens more reliably.</p><p>With the TypeScript relayer, we’ve also been able to add the relayer functionality to the Vue frontend. This means that you now can connect chains from the browser from an intuitive graphical UI.</p><h3>Keplr Integration</h3><p>Keplr is the most popular wallet extension in the Cosmos ecosystem. Keplr is easy to install, convenient to use, and even offers IBC functionality. Naturally, most developers want their chain UI to be integrated with this wallet to give end-users the ability to see their token balances and sign transactions directly from the extension.</p><p>The Starport Vue frontend now seamlessly integrates with Keplr, bridging the gap between your end-users and your blockchain. To check out Keplr support, you can scaffold a new chain or use <a href="https://github.com/tendermint/vue/tree/develop/packages/template">the standalone Vue template</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BO1--re1yihjQdS8y4Lo6w.png" /></figure><h3>Launch a Chain with Custom Genesis</h3><p>In Starport v0.16, we expanded the set of network commands to facilitate launching chains with a custom genesis file. You can simply use the --genesis flag to pass a URL to a file that will act as an initial genesis file.</p><pre>starport network chain create [chainID] --genesis &lt;https://example.org/genesis.json&gt;</pre><p>The join command now features new optional flags: --gentx for passing a &quot;create validator&quot; transaction file (gentx.json) and --peer to pass a peer address of the server on which the validator node will run.</p><pre>starport network chain join [chainID] --gentx gentx.json --peer 9c32599f243182c0a2af240711ad9ee7257f9bb9@1.2.3.4:26656</pre><p>The show command can now output the genesis file with --genesis flag or a list of peers with the --peers flag.</p><p>All starport network commands have the --nightly flag that&#39;s meant to be used with the Starport CLI that&#39;s built from the develop branch. By default, requests from Starport go to the <a href="https://rpc.alpha.starport.network/">https://rpc.alpha.starport.network</a> testnet. The --nightly requests are sent to the <a href="https://rpc.nightly.starport.network/">https://rpc.nightly.starport.network</a> testnet.</p><p>All these additions make it possible for you to easily launch your own testnet and experiment with onboarding your validators in a safe environment. The upcoming launch of Starport Network is another step by us aimed at making validator onboarding easier and more accessible for all.</p><p>Starport Network is under active development. So be sure to stay tuned as more information is released later this year. The current version of starport network commands aims to provide a sneak peek at the features that we&#39;re working on.</p><h3>Other Changes</h3><ul><li>We removed support for Cosmos SDK v0.39 Launchpad</li><li>starport serve no longer starts the web app in the vue directory. Use npm to manually start the web app</li><li>Default scaffold no longer includes legacy REST API endpoints (thanks <a href="https://github.com/bensooraj">@bensooraj</a>!)</li><li>We fixed the error that prevented scaffolding a chain when an underscore was in the repo name (thanks again, <a href="https://github.com/bensooraj">@bensooraj</a>!)</li></ul><h3>Get Started with Starport</h3><p>Are you ready to get started with Starport v0.16?</p><ul><li>Install <a href="https://github.com/tendermint/starport/">Starport CLI</a> with a single command:</li></ul><pre>curl &lt;https://get.starport.network/starport&gt;! | bash</pre><ul><li>Learn more about building blockchains: <a href="https://tutorials.cosmos.network/">https://tutorials.cosmos.network</a></li><li>Read Starport documentation: <a href="https://docs.starport.network/">https://docs.starport.network</a></li></ul><p>Got questions? Join our channel on Discord: <a href="https://discord.gg/vcExX9T">https://discord.gg/vcExX9T</a> where you’ll find an active community of Starport users and developers. They can help you with any doubts and make launching your own Cosmos blockchain and connecting to our ecosystem even easier.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b38cb414c144" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tendermint/starport-v0-16-brings-keplr-better-ibc-support-and-a-whole-lot-more-b38cb414c144">Starport v0.16 Brings Keplr, Better IBC support, and a Whole Lot More</a> was originally published in <a href="https://medium.com/tendermint">Tendermint Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starport v0.15: Supercharged IBC and Frontend Code Generation]]></title>
            <link>https://medium.com/tendermint/starport-v0-15-supercharged-ibc-and-frontend-code-generation-44735df556e6?source=rss-2ef88d6ad83b------2</link>
            <guid isPermaLink="false">https://medium.com/p/44735df556e6</guid>
            <category><![CDATA[internet-of-blockchains]]></category>
            <category><![CDATA[starport]]></category>
            <category><![CDATA[scaffolding]]></category>
            <category><![CDATA[cosmos-sdk]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Denis Fadeev]]></dc:creator>
            <pubDate>Tue, 16 Mar 2021 18:57:19 GMT</pubDate>
            <atom:updated>2021-03-16T18:57:19.310Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WZMMqTygTr4Iyrv8s_u24g.jpeg" /></figure><p><a href="https://github.com/tendermint/starport">Starport</a> has supported Cosmos SDK Stargate even before Starport was released in September 2020. We have improved and simplified the scaffold, introduced better tools to manage proto files, and switched to the latest version of SDK by default. Starport v0.15 focuses on one of the most important features of Stargate — the inter-blockchain communication protocol (IBC). This release includes incredibly useful commands for scaffolding IBC modules, packets, messages, and indexed types. To provide an even better developer experience, a built-in relayer accelerates the development of IBC interconnected blockchains.</p><p>Starport has always bundled a frontend application with every scaffolded chain. In this release, frontend support is re-engineered to include separate packages for Vue components and common Vuex stores. The foundation under all our frontend efforts is the new client code generation capability. Starport automatically generates JavaScript, TypeScript, and Vuex clients for standard Cosmos SDK modules as well as, of course, the custom modules you are building.</p><h3>IBC scaffolding</h3><p>The first action after you come up with a great interchain idea is to scaffold an IBC-enabled module. Starport now has a command just for that purpose:</p><pre>starport module create dex --ibc</pre><p>An IBC module is similar to a regular Cosmos SDK module, but also includes logic for dealing with channels, packets, and acknowledgments.</p><p>After you’ve scaffolded a module and a few types, you start thinking about all the packets that the module handles. Scaffolding code for the packets is just as easy:</p><pre>starport packet sellOrder amountDenom amount:int price:int --module dex</pre><p>The starport packet command creates all the packet types and handling logic, as well as the CLI commands to send packets. With an optional --ack flag you can also specify custom acknowledgment types for the packet.</p><p>After scaffolding all the IBC-specific bits, you might also need custom messages:</p><pre>starport message cancelSellOrder amountDenom orderID:int --module dex</pre><p>Just like that, with only a few commands, a substantial part of your IBC-enabled module is written in minutes. Starport takes care of code generation, so you can focus on the creative aspects of blockchain development.</p><h3>Starting a blockchain</h3><p>To try out the newly created IBC module, you might want to launch two blockchains and send packets between them. The Starport serve command uses a config.yml in the project directory to start a second chain in parallel. Just copy the contents of the config.yml file into mars.yml and tweak some settings (chain ID, home directory, and ports).</p><p>Starport v0.15 introduces the host config property that lets you configure the ports that the blockchain node to run on.</p><pre>host:<br>  rpc: &quot;:26659&quot;<br>  p2p: &quot;:26658&quot;</pre><p>After you have two config files, run starport serve -c config.yml to launch the first blockchain and starport serve -c mars.yml to start the other one.</p><h3>Starport relayer</h3><p>After the two blockchains are running, you can use Starport relayer commands to configure and connect these chains using the IBC protocol.</p><pre>starport relayer configure</pre><p>The configure command guides you through the process of connecting blockchains together. The relayer also attempts to fetch tokens from faucets if the faucets are available (by default, faucets are enabled in Starport chains). If you&#39;re building a custom module, you can use --advanced mode to configure ports and versions for your IBC module.</p><p>With Starport relayer, you are not limited to a single path between two blockchains. You can configure connections between multiple blockchains.</p><pre>starport relayer connect</pre><p>This connect command connects configured blockchains and enters the &quot;watch&quot; mode that relays pending packets. To send a packet, use the scaffolded CLI command:</p><pre>appd tx dex send-sellOrder &quot;photon&quot; 200 12 --from alice --chain-id mars --home ~/.mars</pre><p>The combination of incredibly useful scaffolding commands, simple configuration syntax, and a user-friendly relayer make Starport the best tool for IBC development. To use the Starport v0.15 features to build interchain apps, try the <a href="https://tutorials.cosmos.network/hello-world/tutorial/">IBC “Hello, World!” tutorial</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FNmytpuD33lY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DNmytpuD33lY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FNmytpuD33lY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4ba9626e69c55aaf8d04c0f5c90905b5/href">https://medium.com/media/4ba9626e69c55aaf8d04c0f5c90905b5/href</a></iframe><h3>Frontend code generation</h3><p>One of the major features of Starport v0.15 is an automatic generation of client-side code. Starport now analyzes the source code of your blockchain and creates clients in JavaScript, TypeScript, and Vuex. These clients support querying the blockchain by making requests to gRPC HTTP gateway and broadcasting transactions with messages encoded using protobuf. The clients use the exact version of Cosmos SDK that is imported by your blockchain.</p><p>This client-side code generation means that every blockchain that uses Starport in development always gets automatic generation of up-to-date clients.</p><p>To enable client code generation add the following to config.yml:</p><pre>client:<br>  vuex:<br>    path: &quot;js&quot;</pre><p>If you’ve scaffolded a blockchain with a previous version of Starport, run the following command to regenerate the clients for standard Cosmos SDK modules:</p><pre>starport serve -r --rebuild-proto-once</pre><p>Browser-based client code generation is a crucially important feature of Starport that lets you focus on building custom logic for your frontend applications and saves you weeks of development time.</p><p>New libraries improve the developer experience:</p><ul><li>@starport/vuex contains Vuex modules common for all Cosmos SDK blockchains.</li><li>@starport/vue contains visual components that implement Starport Interface.</li></ul><p>To update <a href="https://github.com/tendermint/starport">Starport</a> to v0.15 with the latest features, get the latest binary with:</p><pre>curl <a href="https://get.starport.network/starport!">https://get.starport.network/starport!</a> | bash</pre><p>Learn more about how to <a href="https://github.com/tendermint/starport/blob/develop/docs/1%20Introduction/2%20Install.md">install it locally</a> or try it out in the <a href="https://gitpod.io/#https://github.com/tendermint/starport/tree/master">web IDE</a>.</p><p>Do you have any Starport questions? Find us on the Cosmos discord channel, under the Cosmos SDK category 👉 <a href="https://discord.gg/dkubTXerEW">https://discord.gg/dkubTXerEW</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44735df556e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tendermint/starport-v0-15-supercharged-ibc-and-frontend-code-generation-44735df556e6">Starport v0.15: Supercharged IBC and Frontend Code Generation</a> was originally published in <a href="https://medium.com/tendermint">Tendermint Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starport v0.14: state persistence and improved support for proto files]]></title>
            <link>https://medium.com/tendermint/starport-v0-14-state-persistence-and-improved-support-for-proto-files-cd58e8d9dd06?source=rss-2ef88d6ad83b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd58e8d9dd06</guid>
            <category><![CDATA[cosmos]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[starport]]></category>
            <category><![CDATA[tendermint]]></category>
            <category><![CDATA[cosmos-sdk]]></category>
            <dc:creator><![CDATA[Denis Fadeev]]></dc:creator>
            <pubDate>Thu, 04 Feb 2021 17:02:17 GMT</pubDate>
            <atom:updated>2021-02-04T17:02:17.412Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aUJjAAusoDouljOeudx93g.jpeg" /></figure><p>For the first release of 2021, we’ve decided to focus on improving the core features of <a href="https://github.com/tendermint/starport">Starport</a>: scaffolding, configuring, and running blockchains in a development environment. Starport now offers even more streamlined Stargate support with commonly used protocol buffer files bundled with the CLI, a simpler scaffold, and automatic code generation. Configuration now supports setting a custom binary name, the path to the home directory, and enabling a built-in faucet. Finally, the blockchain state now persists between restarts.</p><h3>Introducing state persistence</h3><p>Since the very first version, Starport has featured automatic chain restarts. On every file change, the chain would stop, recompile the binary, reinitialize the node, and start fresh. This is incredibly convenient because it reduces the feedback loop to a minimum and allows developers to see changes live almost instantly. The only drawback was that the state had to be reset to make sure that it’s compatible with the changes to the source code.</p><p>With state persistence starport serve now keeps the state between restarts by default. When a file change is detected, Starport exports the blockchain state, rebuilds the binary, imports the state, and starts the node. Accounts, balances and all data remain on chain, which makes running blockchains in development even more convenient. Since state persistence depends on the export and import functions of modules, it becomes easier to test these functions by populating the store with data and restarting the chain.</p><p>When the state becomes incompatible with the source code, using the --reset-once flag will reset the state before running the node as usual.</p><p>If significant changes to the data model are expected, --force-reset will run Starport in &quot;reset state on every file change&quot; mode.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fs-r3vptpN1w%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Ds-r3vptpN1w&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fs-r3vptpN1w%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/31d255d4529fd2c8a1f1370ff742552b/href">https://medium.com/media/31d255d4529fd2c8a1f1370ff742552b/href</a></iframe><h3>Improved proto support</h3><p>With Stargate, Protocol Buffers has become an integral part of Cosmos SDK, making it possible to define your module’s data model in a declarative, language-agnostic way. With this version, Starport has improved support for protobuf by integrating the protoc compiler and bundling commonly used proto files with the CLI. This simplifies the scaffold, allowing developers to focus on proto files of their custom modules. As with other files in the project, Starport intelligently detects file changes and generates .pb files automatically.</p><p>While the necessary proto files are included in Starport, developers can still easily add other third-party files to the proto_vendor directory or customize this behavior with the build.proto property in config.yml.</p><h3>Integrated token faucet</h3><p>Starport now includes a staple of blockchain development: a token faucet. Incredibly convenient for client-side development, a faucet can be enabled and customized in just a few lines in config.yml:</p><pre>accounts:<br>  - name: bob<br>    coins: [&quot;20000foo&quot;]<br>faucet:<br>  name: bob<br>  coins: [&quot;100foo&quot;]</pre><p>Within the faucet section, coins specify amount and denomination of coins that are sent from a faucet per request (which can be in multiple denoms). coins_max lets you limit the total amount for a single address, and port configures the port of the HTTP endpoint.</p><p>The faucet can be used through a web UI, programmatically by sending HTTP POST requests, or by running starport faucet command on the CLI.</p><h3>New configuration options</h3><p>To further improve the developer experience of building with Cosmos SDK, we continue to introduce new functionality to the Starport configuration file.</p><pre>build:<br>  binary: mychain</pre><p>The build.binary property lets you customize the name of the node’s binary. On change, Starport will automatically recompile the binary and use it to initialize and start the node.</p><pre>init:<br>  home: &quot;~/mychaindir&quot;</pre><p>With init.home, it&#39;s easier than ever to set a custom path for the directory that the blockchain will use to keep the genesis file, internal configuration files and keys.</p><p>Lastly, items in the accounts list now optionally accept an address property that will prevent Starport from generating a new keypair for the account, but instead create an account with an existing address. This feature is very useful for adding accounts to the genesis for existing wallets stored elsewhere (for example, in the browser).</p><p>To update <a href="https://github.com/tendermint/starport">Starport</a> to v0.14 with the latest features, get the latest binary with:</p><pre>curl https://get.starport.network/starport! | bash</pre><p>Learn more about how to <a href="https://github.com/tendermint/starport/blob/develop/docs/1%20Introduction/2%20Install.md">install it locally</a> or try it out in the <a href="https://gitpod.io/#https://github.com/tendermint/starport/tree/master">web IDE</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd58e8d9dd06" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tendermint/starport-v0-14-state-persistence-and-improved-support-for-proto-files-cd58e8d9dd06">Starport v0.14: state persistence and improved support for proto files</a> was originally published in <a href="https://medium.com/tendermint">Tendermint Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developer Experience in 2020]]></title>
            <link>https://medium.com/@dfadeev/developer-experience-in-2020-70530dafb101?source=rss-2ef88d6ad83b------2</link>
            <guid isPermaLink="false">https://medium.com/p/70530dafb101</guid>
            <category><![CDATA[tendermint]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[starport]]></category>
            <category><![CDATA[cosmos]]></category>
            <category><![CDATA[developer-experience]]></category>
            <dc:creator><![CDATA[Denis Fadeev]]></dc:creator>
            <pubDate>Thu, 31 Dec 2020 22:49:27 GMT</pubDate>
            <atom:updated>2020-12-31T22:49:27.033Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CIO8sG5ATuW6-MqdWA4NXA.jpeg" /></figure><p>I’ve been leading the Developer Experience team at <a href="https://tendermint.com/">Tendermint</a> since mid-2020 with the mission to improve the experience of building blockchains in the Cosmos ecosystem. The is just a short retro on what has been accomplished in the past six months.</p><p>In August we released <a href="https://github.com/tendermint/starport">Starport</a>, a CLI tool for building blockchains with Cosmos SDK with a particular focus on making the process of development easy and user friendly. The features include scaffolding the source code, single command for building, initializing, and running a blockchain node with auto-reload, scaffolding modules, and types within modules, customization through a simple config file, web scaffold for sign in, sending tokens, and creating types and a friendly welcome screen for guiding new users. Upon <a href="https://www.youtube.com/watch?v=rmbPjCGDXek">release</a>, Starport has received very positive feedback from the community both from experienced blockchain developers as well as those only getting started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nLr-jSUfc3K7tWil5f_y9g.png" /></figure><p>In five months we’ve released four versions of Starport with fixes, improvements, and exciting new features. Each release was accompanied by a blog post and a video illustrating new features of Starport. <a href="https://www.youtube.com/watch?v=HkBR4L9bi8c">In September</a> we introduced genesis and account customization, better logging, and significantly improved automatic code reloading.</p><p>In early October <a href="https://www.youtube.com/watch?v=Guz1Opfzvyw">we’ve updated</a> the web scaffold and configured Starport to run in a browser-based IDE that allowed users to get a working development environment in seconds and start building blockchains even without installing Starport. We also introduced initial support for the Cosmos SDK Stargate.</p><p>In late October <a href="https://www.youtube.com/watch?v=eQYf0Z2pJD0">we’ve added</a> a block explorer, commands for scaffolding custom modules, building the chain, and support for interchain token transfers allowing users to send tokens between newly scaffolded chains.</p><p>In December <a href="https://www.youtube.com/watch?v=DhciTJHxvAY">we’ve updated</a> Starport commands and templates to use Cosmos SDK Stargate by default and introduced an alpha release of a major new feature for decentralized launches of Cosmos SDK blockchains. With just a few commands a coordinator can initialize the launch, validators can propose themselves to become part of the genesis file, and once proposals are approved by the coordinator, validators can launch their nodes and a blockchain network goes online. Launching blockchains has never been easier!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDhciTJHxvAY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDhciTJHxvAY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDhciTJHxvAY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0c489185fc5aa22a47487369da8894e6/href">https://medium.com/media/0c489185fc5aa22a47487369da8894e6/href</a></iframe><p>The decentralized launch feature is powered by the <a href="http://github.com/tendermint/spn">Starport Network</a> blockchain (SPN) that the Developer Experience team has been building since early November.</p><p>Since its introduction, Starport has been used more than 120k times on some days receiving over 6k events with 150 simultaneous users. According to Github Starport’s repo receives 7k git clones per month on average and over 13k views.</p><p>To improve the experience of new developers the team has created two tutorials: a beginner-friendly tutorial on building a simple voting module with web-based UI and a detailed tutorial on building a blog module by hand. The voting module tutorial has become very popular in terms of page views and offers a great starting point for developers new to Cosmos SDK.</p><p>The team actively participates in events with presentations and workshops: <a href="https://www.youtube.com/watch?v=GkuH7VqzgFA">Cosmos Russia meetup</a>, <a href="https://www.youtube.com/watch?v=h6Ur_40LB9k">Code with Us</a>, <a href="https://www.youtube.com/watch?v=qQHfQxOH0Sk">HackAtom India</a>, <a href="https://www.youtube.com/watch?v=kRJAbS-xgBQ">HackAtom V</a>, <a href="https://www.crowdcast.io/e/liquidity2020summit/52">Liquidity 2020</a>, <a href="https://www.youtube.com/watch?v=DWVPTYOrUUo">Interchain Conversations II</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SrLZhDbtufOrhDpeA_HyNA.jpeg" /></figure><p>Starport has been embraced by the community and has been extensively used by developers to create <a href="https://github.com/Sifchain/sifnode">blockchain</a> <a href="https://github.com/allinbits/cosmos-cash-poc">modules</a>, by participants of events like HackAtom, and has become the recommended way for developers to get started building with Cosmos SDK.</p><p>We’ve done quite a bit this year and we have so much more to accomplish in 2021.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70530dafb101" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starport v0.13: Launch Stargate chains in minutes]]></title>
            <link>https://medium.com/tendermint/starport-v0-13-launch-stargate-chains-in-minutes-cef7cc354a27?source=rss-2ef88d6ad83b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cef7cc354a27</guid>
            <category><![CDATA[tendermint]]></category>
            <category><![CDATA[starport]]></category>
            <category><![CDATA[cosmos-network]]></category>
            <category><![CDATA[cosmos-sdk]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Denis Fadeev]]></dc:creator>
            <pubDate>Mon, 21 Dec 2020 19:19:42 GMT</pubDate>
            <atom:updated>2020-12-21T19:19:42.869Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QO94tbYwABeQvChLV19xSQ.jpeg" /></figure><p>We’re thrilled to announce the release of <a href="https://github.com/tendermint/starport">Starport</a> v0.13. With this release, we’re bringing exciting new features to Starport that will allow developers to launch Stargate chains in a decentralized way in minutes.</p><p>We’ve also significantly improved support for Stargate. Since late September, Starport has supported two versions of the Cosmos SDK: “Launchpad” and “Stargate.” In October, we released an IBC update for “Stargate,” which featured <a href="https://www.youtube.com/watch?v=eQYf0Z2pJD0">interchain token transfers</a>. With Starport v0.13, we’ve switched to using Stargate by default for new chains, deprecating support for “Launchpad” and giving our full attention to “Stargate.”</p><h3>Launching a chain</h3><p>Launching a Cosmos SDK chain in a decentralized way has always been a challenge. Manually setting up a node, creating PRs on Github with gentxs, finalizing a genesis file, sending it back to validators, specifying peers, and finally launching a node, hoping that no one made a mistake. We saw an opportunity to improve this process and make it as simple as possible.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDhciTJHxvAY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDhciTJHxvAY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDhciTJHxvAY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0c489185fc5aa22a47487369da8894e6/href">https://medium.com/media/0c489185fc5aa22a47487369da8894e6/href</a></iframe><p>A launch starts from a coordinator (someone who wants to launch a chain) running the following command:</p><pre>starport network chain create [chainID] [sourceURL]</pre><p>Chain ID is a name that uniquely identifies the chain. To check if a name is available, run starport network chain list (there is a --search flag). Source URL points to a repository with a Stargate chain. Validators propose their candidacy by running:</p><pre>starport network chain join [chainID]</pre><p>This sets up a validator node and sends proposals to the coordinator. A coordinator can view a table of all proposals:</p><pre>starport network proposal list [chainID]</pre><p>And approve the right ones (numbers match proposal IDs from the table):</p><pre>starport network proposal accept [chainID] 2,3,4,5</pre><p>Once proposals are accepted, validators can start their nodes:</p><pre>starport network chain start [chainID]</pre><p>As soon as enough validators go online, the chain will launch and start generating blocks.</p><p>Watch <a href="https://www.youtube.com/watch?v=DWVPTYOrUUo&amp;list=PLdQIb0qr3pnDI69pHyWjBg4hLm6jxywye&amp;index=5">“A Million Blockchains”</a> presentation with a demo of launching a chain live with 13 validators!</p><p>Disclaimer: functionality for launching chains is under active development. Information about blockchain launches persists between updates to the source code (roughly once a week).</p><h3>Bringing CRUD to Stargate</h3><p>Starport has always supported scaffolding data types that allow developers to start building custom modules quickly. With this update, we’ve brought create, read, update, and delete (CRUD) operations to Stargate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PryirK2NwZEp1V_k" /></figure><p>Starport automatically generates proto files necessary for Stargate for each scaffolded module and datatype.</p><p>By default, Starport `app` now scaffolds a Stargate blockchain and the Launchpad version is available with the --sdk-version launchpad flag.</p><h3>More config options</h3><p>With the new init top-level property in config.yml it has become easier to configure parameters in app.toml and config.toml inside a blockchain’s data directory. By default, Starport’s serve command deletes the data directory on file change, and with init it’s easy to set specific values.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6AvVaDrPSMuPbFJL" /></figure><p>For example, changing a moniker of a node or setting a halt height for testing purposes.</p><h3>Starport &amp; HackAtom V</h3><p>HackAtom V, the premiere Cosmos hackathon of the year, ended in early November. We’ve been elated to watch hackers make use of Starport during this event. We want to thank the participants of HackAtom V for testing out this new tool — which was only released in July! As maintainers of this project, we’ve received a lot of actionable feedback, and we’ve been working on making the developer experience even better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cef7cc354a27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tendermint/starport-v0-13-launch-stargate-chains-in-minutes-cef7cc354a27">Starport v0.13: Launch Stargate chains in minutes</a> was originally published in <a href="https://medium.com/tendermint">Tendermint Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Launch a new token and send it across the Cosmos — Starport v0.12 is here!]]></title>
            <link>https://medium.com/tendermint/launch-a-new-token-and-send-it-across-the-cosmos-starport-v0-12-is-here-d1578012ba09?source=rss-2ef88d6ad83b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1578012ba09</guid>
            <category><![CDATA[starport]]></category>
            <category><![CDATA[tendermint]]></category>
            <category><![CDATA[cosmos-network]]></category>
            <category><![CDATA[cosmos-sdk]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Denis Fadeev]]></dc:creator>
            <pubDate>Tue, 20 Oct 2020 14:23:02 GMT</pubDate>
            <atom:updated>2020-10-20T14:23:02.101Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Launch a new token and send it across the Cosmos — Starport v0.12 is here!</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pQRGEYHfZSqXvMrg-R4zZw.jpeg" /></figure><p>We’re excited to announce Starport v0.12, which grants developers the ability to create tokens on one chain and transfer it to an infinite number of other blockchains. Based on the <a href="https://blog.cosmos.network/how-seven-teams-collaborated-to-deliver-the-biggest-software-upgrade-in-the-cosmos-universe-2288f4f9afe8">multi-organizational effort</a> to launch Stargate &amp; IBC, you can now create a new blockchain with a new token and send that token to any other IBC-enabled blockchain. The vision of Cosmos — the internet of blockchains — has finally arrived!</p><p>Alongside interchain token transfers, we’ve also designed and built a beautiful developer UI that lets you inspect blocks, transactions, and messages on your chain. We’ve also added new CLI commands to help you build your chain and scaffold multiple custom modules.</p><h3>Interchain token transfers</h3><p>With Starport, you can now scaffold Stargate-compatible chains, connect them with IBC, and send tokens between them in just a few simple commands. Starport’s online dev environment now includes an IBC relayer that we’ve automatically configured for your chain.</p><p>Watch this video to learn how to make interchain token transfers:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FeQYf0Z2pJD0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DeQYf0Z2pJD0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FeQYf0Z2pJD0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b561d5f28850091e9335a374019aa5e9/href">https://medium.com/media/b561d5f28850091e9335a374019aa5e9/href</a></iframe><p>In summary, to start building with IBC, you’ll want to <a href="https://gitpod.io/#https://github.com/tendermint/starport/">open up two editors</a>, create chains with</p><pre>starport app github.com/yourname/yourchain --sdk-version stargate</pre><p>and connect them with starport chain add {{insert relayer info here}}. After the chain is restarted and an inter-blockchain connection is established, you can send tokens and start prototyping with IBC. Read <a href="https://github.com/tendermint/starport/blob/develop/docs/1%20Introduction/6%20Starport%20IBC.md">the guide</a> on interchain transfers with Starport.</p><h3>Developer UI</h3><p>In this release, we’ve also redesigned the welcome screen from scratch. With a brand new visual design, it now provides a better overview of your chain’s running processes and lists the growing number of Starport tutorials and guides.</p><p>The other addition to the Starport toolset is a block explorer built for chain developers. Beautifully designed and lightweight, it focuses on displaying the information SDK developers need, including formatted messages from custom SDK modules, errors, and the necessary meta information.</p><p>This initial release is the first step at bringing better user-friendly developer tooling to the Cosmos ecosystem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AA9qMK-fydG-WUhBgQz0SQ.png" /><figcaption>Starport block explorer</figcaption></figure><h3>New CLI commands</h3><p>In v0.12, we’re introducing two new highly requested commands for building your chain and scaffolding custom modules.</p><p>starport build will build and install the CLI of your blockchain without running it. After building, you can use the binaries to launch nodes or API servers manually.</p><p>starport module create foo will scaffold an empty custom module in `x/foo`. Cosmos SDK was originally built as a flexible system extensible through modules and this Starport command helps you build your chain in a more modular way.</p><p>When scaffolding new data types, you can now select a module to create these in.</p><pre>starport type post title body --module blog</pre><p>This command will create a post datatype in the x/blog module.</p><h3>Starport &amp; HackAtom V</h3><p><a href="https://five.hackatom.org/">HackAtom V</a> is a two-week hackathon that started last Friday (the 16th) and runs until October 30th. Hackers can win up to $50,000 USD in ATOM tokens. If you didn’t know about this event — no worries, you can still join! Because Starport enables you to generate new blockchains in minutes, there’s little disadvantage to joining late.</p><p>We look forward to seeing what the community builds with Starport v0.12. With support for interchain token transfers, Cosmos’s future has expanded into an entirely new dimension: space.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1578012ba09" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tendermint/launch-a-new-token-and-send-it-across-the-cosmos-starport-v0-12-is-here-d1578012ba09">Launch a new token and send it across the Cosmos — Starport v0.12 is here!</a> was originally published in <a href="https://medium.com/tendermint">Tendermint Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>