<?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 Peng Zhong on Medium]]></title>
        <description><![CDATA[Stories by Peng Zhong on Medium]]></description>
        <link>https://medium.com/@nylira?source=rss-9f6763f3d5b6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-XXXJLN45ee2Ack6Pxrb1g.jpeg</url>
            <title>Stories by Peng Zhong on Medium</title>
            <link>https://medium.com/@nylira?source=rss-9f6763f3d5b6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:27:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nylira/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[A Light-Year in the Cosmos: Tendermint 2020]]></title>
            <link>https://medium.com/tendermint/a-light-year-in-the-cosmos-tendermint-2020-ca898d31d968?source=rss-9f6763f3d5b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca898d31d968</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cosmos-network]]></category>
            <category><![CDATA[cosmos]]></category>
            <category><![CDATA[tendermint]]></category>
            <category><![CDATA[starport]]></category>
            <dc:creator><![CDATA[Peng Zhong]]></dc:creator>
            <pubDate>Wed, 23 Dec 2020 21:04:00 GMT</pubDate>
            <atom:updated>2020-12-24T01:37:33.435Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NQUribqx-NIqsr6oBcaCzg.png" /></figure><p>It’s been a tumultuous year for all of us due to the COVID-19 pandemic. However, I am incredibly proud of what Tendermint has accomplished for the Cosmos community despite these hardships. In this post, I’ll be going over our highlights for 2020 and also give a preview of what’s coming up next.</p><p>At Tendermint, we’ve faced some additional internal difficulties that resulted in the great re-org of Cosmos engineering in early 2020. We spent the earlier part of the year rebuilding our teams and forging stronger ecosystem relationships. But the vast majority of this year has been spent developing and bringing awareness of the stellar tools that <a href="https://medium.com/tendermint/accelerating-the-internet-of-blockchains-tendermint-in-2020-85cdb2956cdd">accelerate us to the Internet of Blockchains</a>.</p><h3>Highlights of 2020</h3><h4>Engineering</h4><p>A trusted, rock-solid foundation is crucial to the economic growth of Cosmos. Led by Alessio Treglia, our Engineering team has been focused on improving the Cosmos SDK, the foundation for all of our products. Specifically, we’ve focused on improving the client app developer experience, code test coverage, and quality assurance metrics of the SDK. We’ve also broke ground on the Cosmos Cash research project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HlFNVyp1o9qs4CPSG0r2bg.jpeg" /></figure><p>We’re putting app developers first by creating and maintaining <a href="https://blog.cosmos.network/launchpad-a-pre-stargate-stable-version-of-the-cosmos-sdk-e0c58d8c4e24">v0.39 Launchpad</a>, an extended support version of the Cosmos SDK. Launchpad is a stable platform for app developers to build on top of while the core developers iron out final issues around the v0.40 Stargate release of the SDK and IBC 1.0. To assist with transitioning chains to Launchpad, we’ve opened up maintenance PRs against various chain repositories. These include Commerc.io, Band Protocol, Terra, Bluzelle, Ethermint, Akash, and Starname.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uofluyjZkgLME5SUB-Mqlw.jpeg" /></figure><p>We are contributing three significant features for the upcoming <a href="https://stargate.cosmos.network/">Stargate release</a> of the Cosmos SDK: cosmovisor, a more secure keyring implementation, and <a href="https://www.rosetta-api.org/">Rosetta API</a> support. We’ve joined the ADR committee and taken part in critical architectural decisions on the shape of the Cosmos SDK’s future releases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hLHQZysf3YVTL1iN3d_Mpw.jpeg" /></figure><p>We’ve also started working on the <a href="https://github.com/allinbits/cosmos-cash-poc">Cosmos Cash</a> protocol research project this year. Cosmos Cash is a protocol for institutions to issue real fiat tokens on a Cosmos SDK-based blockchain. We’ve completed the first two deliverables for Cosmos Cash: a proof-of-concept and a feasibility study. To learn more, read <a href="https://medium.com/tendermint/unveiling-cosmos-cash-a-regulatory-compliant-finance-protocol-based-on-the-cosmos-sdk-f287785607a4">Alessio’s announcement</a>.</p><h4>Developer Experience</h4><p>Led by Denis Fadeev, the Developer Experience is a team established in the summer of 2020 to improve the experience of building blockchains in the Cosmos ecosystem. <a href="https://github.com/tendermint/starport">Starport CLI</a>, which launched in August, is the easiest way to build a blockchain, full stop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x_2GMsewt9NNXGdSKa_LVQ.jpeg" /></figure><p>Starport CLI features include boilerplate scaffolding, module scaffolding, a single command for building, initializing, running a blockchain node with auto-reload, types within modules, and chain customization through a simple config file. It also includes a frontend scaffold for signing in, sending tokens, creating new transactions, and a friendly welcome screen to guide new developers. Starport has received incredibly positive feedback from the community, both from experienced blockchain developers and those only getting started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*33FtnRvHie1-9Yk3kyrkcw.png" /></figure><p>Since August, we’ve recorded over 120k user interactions with Starport. Usage during our hackathons has peaked at over 6k events and 150 simultaneous users per day. According to Starport’s <a href="https://github.com/tendermint/starport/pulse">GitHub Insights</a>, it receives around 7k git clones and 13k views every month. Starport v0.13, with full support for Stargate, has just launched this week. <a href="https://medium.com/tendermint/starport-v0-13-launch-stargate-chains-in-minutes-cef7cc354a27">Check it out!</a></p><h4>Brand &amp; Design</h4><p>Led by Nass Donald, our design team is one of the most promising in crypto. Designed and launched this year, the <a href="https://five.hackatom.org/">HackAtom V</a> website and the <a href="https://stargate.cosmos.network/">Stargate</a> website have been significant visual design and communication successes. I’m incredibly proud of our design team for the amount of effort they put into every project. The work they have done for Cosmos has been earning accolades from Twitter:</p><blockquote>Have to say I think <a href="https://twitter.com/cosmos">@cosmos</a> might have the best branding and design in crypto? Consistent across all their channels and products</blockquote><p><a href="https://twitter.com/joonian/status/1325962924788240386"><strong>Wong Joon Ian</strong></a> @joonian</p><blockquote>Man,<a href="https://twitter.com/cosmos">@cosmos</a> branding is so good. Just look at this website. Amazing job to whoever designed it. <a href="https://twitter.com/hashtag/Cosmos?src=hashtag_click">#Cosmos</a> <a href="https://twitter.com/search?q=%24ATOM&amp;src=cashtag_click">$ATOM</a></blockquote><p><a href="https://twitter.com/bwhli/status/1330469908652683265?s=20"><strong>brianli.com</strong></a> @bwhli</p><p>The team provided design and front-end development support to a wide array of projects throughout the year, including Starport DevTools and component library; documentation and tutorials websites; online events, workshops, conferences, and hackathons; visual marketing materials for blogs and social media channels; email communications; a few brand design initiatives; and some exciting community-building programs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fB9wowmjBQVt0DnDvBjyPg.jpeg" /><figcaption>A preview of the new Cosmos look and feel</figcaption></figure><p>With iterative improvements to the existing Cosmos website, we’ve seen a steady growth of traffic and engagement throughout the year. Meanwhile, the team has been hard at work behind the scenes in 2020, building an entirely new website and a comprehensive directory of ecosystem projects. You can read about it in the “upcoming releases for 2021” section.</p><h4>Marketing &amp; Community</h4><p>With Chjango and Adriana Mihai’s tireless efforts, the community for Cosmos this year has expanded significantly. We published 320 <a href="https://twitter.com/cosmos">@cosmos</a> tweets to over 10M impressions, increasing our followers from ~30k to 46k. The Cosmos mailing list has grown from 13k to 18k contacts. We’ve also been at the forefront of ecosystem communications, broadcasting major Cosmos events and developments like Game of Zones, Stargate, Ethermint, Cosmos Jobs, Cosmos SDK, Tendermint Core, IBC, Peggy, CosmWasm, and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*msmVW4HV5WV66taTMYiRsg.jpeg" /></figure><p>2020 was a year that saw the rapid growth of virtual events. Our team launched <a href="https://cosmos.network/series/code-with-us">Code with Us</a> this year, a series of live-streamed workshops designed to teach Cosmos concepts to developers. We produced 14 workshops for ~300 live participants — these videos have also received <a href="https://www.youtube.com/watch?v=GfZjnMchKX0&amp;list=PLdQIb0qr3pnBmrPOxVJ7GnfOMP6C5P9BN">over 7k views on YouTube</a>. Other virtual events we ran this year include <a href="https://www.youtube.com/watch?v=W4HAyW7utpo&amp;list=PLdQIb0qr3pnCKDIpPkbyarNhHDFVfXi6H">Cosmos Unchained</a> and <a href="https://youtube.com/playlist?list=PLdQIb0qr3pnC3ao6KMrgVVVaQTxhZS4Ni">Future of the Cosmos Hub</a>. For this year’s end, we hosted Interchain Conversations II in partnership with Dystopia Labs. This highly successful conference had 52 speakers, 46 talks, and 1.6k registrants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u9ETCx8eT4rl8BFmiGLYTw.jpeg" /></figure><p>This year also saw the planning and launch of three successful hackathons. The <a href="https://blog.cosmos.network/spend-the-pandemic-inside-join-our-gitcoin-hackathon-and-win-prizes-6afa8310879c">Gitcoin Cross-Chain Hackathon</a>, which we hosted in partnership with Agoric and Band Protocol, had around 300 registrants and <a href="https://blog.cosmos.network/announcing-the-cross-chain-hackathon-winners-698b6d03bd6">$15k in awards</a>. The <a href="https://blog.cosmos.network/leading-interoperability-protocol-cosmos-network-partners-with-persistence-one-to-launch-hackatom-d06c1a234885">Cosmos India HackAtom</a>, which we hosted in collaboration with Cosmos India and Persistence One, had 1.2k registrants, over 200 workshop attendees, and <a href="https://twitter.com/PersistenceOne/status/1323988451822342145?s=20">$10k in awards</a>. We also delivered <a href="https://blog.cosmos.network/pre-ibc-hackathon-get-your-spacesuits-ready-for-hackatom-v-6aac80ea154d">HackAtom V</a>, the most valuable Cosmos hackathon of the year, to over 320 registrants and <a href="https://blog.cosmos.network/hackatom-v-winners-spotlights-99192e503eac">$50k in awards</a>.</p><p>Finally, as a way to support the growth of the Cosmos ecosystem, we have launched these initiatives this year:</p><ul><li><a href="https://blog.cosmos.network/cosmos-community-contributor-grants-75e24532c261">Cosmos Contributors Grants</a></li><li><a href="https://blog.cosmos.network/announcing-the-cosmos-community-contributor-grants-recipients-of-q2-1b682a05b395">Cosmos Community Contributor Microgrants</a></li><li><a href="https://medium.com/tendermint/introducing-tendermint-fellowships-d6edef6cb62b">Tendermint Fellowship Program</a></li></ul><h4>Operations</h4><p>In Talent &amp; HR, we’ve instituted a transparent and equitable compensation philosophy where <strong>we target the 60% percentile of San Francisco market salaries for all roles, irrespective of location in the world</strong>. We’ve also hired 17 people this year, primarily in engineering and technical roles, which has doubled our company’s size. If you’re interested in building the new decentralized token economy, <a href="https://tendermint.com/careers/">we are hiring worldwide!</a></p><p>In Operations, earlier this year, we formalized and onboarded <a href="https://medium.com/tendermint/the-newly-formed-tendermint-inc-board-of-directors-appoints-peng-zhong-as-ceo-dcc79d8989c1#:~:text=Tendermint%20Inc&#39;s%20newly%20formed%20Board,President%20of%20Tendermint%20Inc%2C%20Claire">a new five-member Board of Directors</a> to improve accountability and decentralize the governance of Tendermint Inc.</p><p>In Corporate Development, we’ve set up processes and templates for investment opportunities and recently signed an investment deal that we should disclose soon. In 2021, we want to support more developers building great projects in the Cosmos ecosystem, and we’re working on publicizing our inbounds for strategic investments.</p><h3>Upcoming releases for 2021</h3><p>We have several great projects coming up for Cosmos in 2021, and here is a high-level overview of what we’re aiming to deliver. We will provide more detailed information and previews of the DEX, Starport 1.0, and Cosmos Website 2.0 early next year.</p><h4>Stargate</h4><p>Our biggest goal for 2021 is to work with the core development community to bring Stargate onto the Cosmos Hub. This upgrade will also enable the interblockchain communication protocol, allowing you to send tokens to and from the Cosmos Hub. Stargate is a massive project that involves more than just the SDK. The API has many breaking changes, and we’re assisting app developers, wallet developers to help migrate their front ends to work flawlessly with Stargate.</p><h4>Liquidity Module</h4><p>We are collaborating with the talented B-Harvest team to develop and build decentralized exchange (DEX) for Cosmos-based blockchains. Work has started on the Liquidity Module in Q4 of 2020, and B-Harvest has already finished Milestone 1. While Engineering manages this product, Design will be coming in to design and develop a well-thought-out web UI for this DEX. We hope to present a prototype of this DEX to the Cosmos community by the end of Q1.</p><h4>Starport 1.0</h4><p>Starport has quickly become the best starting point for any developer who wants to get into the Cosmos ecosystem. While we have made it very easy to build a new Cosmos chain through scaffolding and hot reloads, creating a chain is still only the first step to a production mainnet. Starport’s vision is a vertically integrated tool that supports app developers from their first Hello World-style blockchain to a production mainnet.</p><p>To get us there, we’ve worked on proofs-of-concept for two other components of Starport: Cloud and Network. Starport Cloud is validation-as-a-service for app developers and people who want managed validators. As for Starport Cloud, we hope to have out as an alpha in Q1. We’re also building Starport Network, a marketplace for app developers, chain coordinators, and validators to negotiate token distribution and schedule chain launches. Starport Network is a blockchain, and we hope to have a testnet by Q2.</p><h4>Cosmos Website 2.0</h4><p>We were hoping to get the revamped Cosmos website out to everyone this year, but work has taken a little longer than expected amidst lots of activity in the ecosystem. In Q1 2021, you should see the launch of the brand new Cosmos website. Our company has been working hard on both content and design to make sure it reflects the best of Cosmos and is understandable and usable to newcomers. We’re also kicking off a standalone IBC website, with the goal to court other blockchain frameworks to adopt IBC. Later in the year, we also plan to build a standalone website for Cosmos Hub, providing an entry point for newcomers to learn about the ATOM token and staking.</p><h3>The path to a multi-chain future</h3><p>I’ve never been more bullish on Cosmos. The ecosystem is stronger than ever, and our tools solve scalability problems in cryptocurrency. Tendermint will do everything we can to bring a multitude of sovereign blockchains to market. In fact, I believe there is a viable future for a million interoperable blockchains. If you’re interested in learning more, I gave a presentation a week ago with that exact title — <a href="https://www.youtube.com/watch?v=DWVPTYOrUUo&amp;list=PLdQIb0qr3pnDI69pHyWjBg4hLm6jxywye&amp;index=5&amp;pbjreload=101">A Million Blockchains</a> — at Interchain Conversations II.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nnc2-s8pVD8zdtVEXiwIrg.jpeg" /></figure><p>I want to express my deep gratitude to everyone who has been working so hard to make Cosmos successful this year. I am proud of our growing community, and I appreciate how we’re able to collaborate so well to build out this robust open-source ecosystem. Special thanks to the <a href="https://interchain.io/">Interchain Foundation</a>, which has been tirelessly supporting the majority of ecosystem development efforts. Happy holidays everyone! Enjoy the time off, and I look forward to building something great with you in 2021.</p><p>—</p><p><em>Thanks to Adriana Mihai, Alessio Treglia, Denis Fadeev, Nass Donald, Chris Abejon, Natalia Puntel, and Brent Xu for coming up with the content for this blog post. Thank you to everyone at Tendermint for making this possible.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca898d31d968" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tendermint/a-light-year-in-the-cosmos-tendermint-2020-ca898d31d968">A Light-Year in the Cosmos: Tendermint 2020</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[Accelerating the Internet of Blockchains: Tendermint in 2020]]></title>
            <link>https://medium.com/tendermint/accelerating-the-internet-of-blockchains-tendermint-in-2020-85cdb2956cdd?source=rss-9f6763f3d5b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/85cdb2956cdd</guid>
            <category><![CDATA[cosmos]]></category>
            <category><![CDATA[cosmos-network]]></category>
            <category><![CDATA[tendermint]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[starport]]></category>
            <dc:creator><![CDATA[Peng Zhong]]></dc:creator>
            <pubDate>Tue, 11 Aug 2020 15:01:01 GMT</pubDate>
            <atom:updated>2020-08-11T15:01:01.830Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hQ96ehhbidma-yGqRxCxGA.jpeg" /></figure><p>Our mission at <a href="https://tendermint.com/">Tendermint</a> is to invest in engineering, improve developer experience, and grow the value of the ecosystem. With a newly appointed CEO, what do the next six to twelve months for Tendermint look like? Is Virgo still a thing? How does Starport fit in? In this article, I’ll give clarity on what we’ve been working on recently. I’ll also share our long-term priorities and strategy to accelerate the path to the <a href="https://cosmos.network/">Internet of Blockchains</a>.</p><h3>The end of the Virgo experiment</h3><p>We are winding down the <a href="https://virgo.org/">Virgo</a> project. The Virgo website and other channels will continue to exist, but we are no longer dedicating resources to maintain this presence. We have considered which parts of Virgo have compelling narratives, and we have rolled these projects into our Cosmos-focused teams. This pivot has worked well — we’ve freed up resources and set ourselves up to focus on a singular mission: the Cosmos Network.</p><h3>A renewed focus on Cosmos</h3><p>Tendermint is a ~10% stakeholder of the <a href="https://coincap.io/assets/cosmos">Cosmos Hub</a>. As such, we have skin in the game to ensure the continued growth through the utility of the ATOM. In the short term, we’ll be <a href="https://medium.com/tendermint/tendermint-inc-is-unbonding-all-of-its-atoms-but-theres-no-need-to-panic-e8dfe69f817e">re-delegating ATOM to a more diverse set of Hub validators</a> who actively contribute to building public goods for Cosmos, in the spirit of <a href="https://medium.com/dokia/the-atomic-spread-out-70a22cf3eb8">#TheAtomicSpreadOut</a>. In the long term, we will be leveraging ATOM to accelerate the process of growing into the interconnected network of blockchains that everyone in the community is excitedly awaiting.</p><p>The <a href="https://interchain.io/">Interchain Foundation</a> granted us funding earlier this year, not just for Cosmos ecosystem development, but also for two projects called Dither and Cosmos Cash. One of our priorities for the remainder of this year is to deliver on these projects.</p><p>We’re rethinking what is possible for <a href="https://dither.chat/">Dither</a>. Our current plan is to develop an open-source chat module for the Cosmos SDK that comes with a full-fledged web UI. Think Discord/Slack but designed with first-class cryptocurrency support, built on top of the Cosmos SDK.</p><p>Cosmos Cash is an R&amp;D project that will enable institutions to issue fiat currency (EUR, CHF, etc) as IBC tokens. The primary goal of this project is to connect fiat issuance directly to a zone in the Cosmos Network. We’ll have more news on Cosmos Cash and Dither as we delve further into development.</p><figure><img alt="Our engineers are contributing to the Stargate upgrade for the Cosmos Hub." src="https://cdn-images-1.medium.com/max/1024/1*a8GsFsdubEDJ0tbPCtiRhA.jpeg" /><figcaption>Our engineers are contributing to the Stargate upgrade for the Cosmos Hub.</figcaption></figure><h3>Investing in engineering</h3><p>Earlier this year, due to internal disagreements, many core Cosmos protocol engineers left to form Interchain GmbH, a new engineering-focused team funded by the ICF. We’re in the process of <a href="https://tendermint.com/careers">rebuilding our engineering strength</a> to continue to focus on protocol development, to improve the application developer experience, as well as provide more onramps to the ATOM. Our current engineers are assisting with the <a href="https://stargate.cosmos.network/">Stargate &amp; IBC upgrade</a> for the Cosmos Hub, maintaining <a href="https://blog.cosmos.network/launchpad-a-pre-stargate-stable-version-of-the-cosmos-sdk-e0c58d8c4e24">a stable release</a> of the Cosmos SDK, integrating the <a href="https://rosetta-api.org/">Rosetta API</a> with the Cosmos SDK, as well as leading R&amp;D on a Shared Security module.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qNkGbExcVEr1Bm95wKuxGg.jpeg" /></figure><h3>Increasing Cosmos Hub utility</h3><p>One of the most common questions in the Cosmos ecosystem is regarding how the ATOM will accrue value. ATOM holders have invested a lot of resources into making the Cosmos Hub the most secure proof-of-stake settlement layer in existence. With <a href="https://blog.cosmos.network/preparing-for-ibc-1-0-e6fe75f7b5ef">IBC 1.0 coming soon</a>, how can the Hub leverage this protocol to share its security with other blockchains? There are several teams in the Cosmos ecosystem working on separate, additive approaches to increasing ATOM value.</p><p><a href="https://github.com/ChorusOne/liquid-staking">Liquid staking</a>, alternatively, issuing derivatives of staked tokens, is one approach. Earning rent by securing <a href="https://blog.althea.net/defi-enabled-ethereum-bridge-for-cosmos/">pegged assets</a> is another approach. <a href="https://forum.cosmos.network/t/discussion-thread-for-cross-chain-validation/3180">Shared security,</a> also known as cross-chain validation, is a third approach. One particularly interesting community idea is adding an automated market maker (a la <a href="https://uniswap.org/">Uniswap</a>) DEX directly onto the Hub. We look forward to seeing which of these approaches the ATOM holder community will vote to support.</p><p>We at Tendermint are researching how to introduce decentralized finance (DeFi) protocols into proof-of-stake blockchains in ways that don’t conflict with the staking incentive. We believe the ATOM is the best mechanism in Cosmos to offer premium shared security for future chains. We are actively pursuing R&amp;D on cross-chain validation and we’ll have more to report on this in the near future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mMkH97MzGHLwlrkWd__1UA.jpeg" /></figure><h3>Starport is the solution to SDK usability</h3><p>While attempting to use the Cosmos SDK ourselves to build a production application, we identified several usability issues for first-time app developers. We decided to solve these problems for future developers through intelligent automation and code scaffolding. Over the past couple of months, our Developer Experience team has been building <a href="https://github.com/tendermint/starport">Starport</a>, a friendly interface to the Cosmos SDK. Even though Starport is in early alpha, it’s already capable of helping developers build blockchains in minutes instead of hours. Even more, Starport generates a full web app for every chain, allowing developers to focus on writing business logic.</p><p><a href="https://medium.com/tendermint/starport-the-easiest-way-to-start-building-a-blockchain-8ecc016573d0">We just announced Starport</a> publicly last week, and we’re thrilled at the positive reception that we’ve gotten so far. There are fewer than a thousand Cosmos developers today, but more than 24,000,000 developers worldwide. We believe Starport lowers the barrier to entry to blockchain development and will enable mainstream developers to start solving business problems with IBC and the Cosmos SDK. We have paradigm-altering features in the Starport pipeline that will make Cosmos app development even more accessible and productive — stay tuned for announcements.</p><h3>Starport Cloud is the solution to validator onboarding</h3><p>Over the years, we’ve experienced how much global coordination is required to launch a blockchain with a decentralized validator set. We hope to use our learnings to make this experience easier and more streamlined for future teams who want to start blockchains with a globally distributed validator set. We’re experimenting with novel UX solutions to vastly simplify decentralized network initialization, visualize and debug network state, as well as solve peer discoverability.</p><p>Starport Cloud, which we will fully reveal later in Q3, will be an integrated chain validation and app hosting platform that will make it much easier for developers to deploy and test their blockchain applications. We hope to support developers from early MVP, decentralized launches, incentivized testnets, and all the way to mainnet. We are looking to start discussions with validation providers who are interested in being a part of the Starport Cloud initiative — we plan on simplifying the exchange of validation services for mainnet tokens.</p><h3>Contributor Microgrants are the solution to community funding</h3><p>While Cosmos technical development has been adequately funded, we believe that the community growth of the Cosmos Network could use additional support. We have been identifying small teams building public goods that directly benefit Cosmos Hub through the Cosmos Community Contributor Microgrants. Read about Q1 recipients here:</p><p><a href="https://blog.cosmos.network/cosmos-community-contributor-grants-75e24532c261">Cosmos Community Contributor Grants</a></p><p>We have an upcoming list of Q2 microgrant recipients so stay tuned for news on that. We plan on leveraging ATOM and our Ecosystem Development team’s shared experience to <a href="https://cosmos.network/community">invest in and partner with Cosmos contributors</a> who have emerged as some of the most capable teams in the ecosystem doing cutting edge R&amp;D.</p><p>We’re also looking to work with Hub stakeholders to make the community pool more useful, empowering ATOM holders, validators, and the greater crypto community to participate meaningfully in the growing Cosmos token economy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G5upWVauP5cwjmDf9ICe4A.jpeg" /></figure><h3>Thanks for being a part of the community</h3><p>Our mission is to invest in protocol engineering efforts, improve the Cosmos developer experience, and work with the community on the future of ATOM and the Cosmos Hub. We’ve been leveraging our team’s strengths and hiring over the last couple of months to tackle critical Cosmos adoption problems. Our team is brilliant, highly focused on delivering, and there are many more updates I’d love to share. But I’ll save those for a future post. As always, feel free to reach out to me on Twitter <a href="https://twitter.com/zcpeng">@zcpeng</a>.</p><p>If you want to work with us to build Cosmos and make blockchain development as approachable as possible — <a href="https://tendermint.com/careers">we are hiring!</a></p><p><em>Thanks to Chjango Unchained and Jin Kwon for reviewing and suggesting edits for clarity.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85cdb2956cdd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tendermint/accelerating-the-internet-of-blockchains-tendermint-in-2020-85cdb2956cdd">Accelerating the Internet of Blockchains: Tendermint in 2020</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[Voyager Update: “Onboard with Onboarding”]]></title>
            <link>https://medium.com/cosmos-blockchain/voyager-update-onboard-with-onboarding-3ffe3346b4f9?source=rss-9f6763f3d5b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ffe3346b4f9</guid>
            <category><![CDATA[vue]]></category>
            <category><![CDATA[voyager]]></category>
            <category><![CDATA[cosmos]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Peng Zhong]]></dc:creator>
            <pubDate>Mon, 02 Apr 2018 20:20:30 GMT</pubDate>
            <atom:updated>2018-04-03T01:09:35.209Z</atom:updated>
            <content:encoded><![CDATA[<h4>Brand new series! Find out what the Voyager team achieved during the two week sprint between March 6–20, 2018.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7IExdBulMbSVPWEIzJJDkw.png" /></figure><h3>What is Voyager?</h3><p><a href="https://cosmos.network/voyager">Cosmos Voyager</a> is the GUI, or mission control center to the Cosmos Network. You’ll be able to view visual graphics of the network status in real time, validator status, incoming blocks, and transactions as they happen. You’ll be able to control your Atom balance by sending, receiving, staking, and making block rewards. Most importantly, you’ll be able to influence the future of the network by voting on proposals through the governance interface.</p><p>If you’re a developer interested in building on top of Cosmos, you’re encouraged to <a href="https://github.com/cosmos/voyager">fork Voyager</a> (an Electron and Vue-based app) to quickly and easily create the GUI for your own Cosmos Zone. Our codebase is entirely open-source and we’re working hard to provide comprehensive documentation and guidelines for downstream usage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S0CbC9y3hbEgZNPFWXt_DQ.jpeg" /><figcaption>The computer support systems at the Space Flight Operations Facility within NASA provide real-time control and monitoring of manned space flights. Similarly, the Voyager GUI provides users real-time control and monitoring of interactions made within Cosmos Network.</figcaption></figure><h3>Voyager Update #1</h3><p>Welcome to the first of a regular bi-monthly <a href="https://cosmos.network/voyager">Voyager</a> update! The Voyager team plans out a number of new features and bug fixes to be accomplished over two week sprints. These updates are intended to give you an executive summary of each iterative improvement in the UI.</p><h3>Voyager Additions</h3><ul><li>We welcomed David “NodeGuy” Braun to the Voyager team. David previously worked at Monax with Tendermint CTO, Ethan Buchman.</li><li>The features of the Voyager MVP have been defined.</li><li>The primary users of the Voyager MVP, we’ve identified, are fundraiser contributors, dApp developers, and validators/delegators.</li><li>We were blocked by stability issues with the gaia-2 testnet, so we rebuilt the mock server so that developers and users can test Voyager without a testnet.</li><li>Deterministic builds are highest priority, so we decided to containerize Voyager with Docker.</li><li>We have a new (work in progress) logo for Voyager, shown in the banner at the top of the page.</li></ul><h3>Voyager Bug Fixes</h3><ul><li>We fixed an issue with sorting validators.</li></ul><h3>In Progress</h3><ul><li>We identified the importance of onboarding new users, so we’ve been working on an onboarding wizard for Voyager.</li></ul><h3>Conclusion</h3><p>That’s all for this sprint. For those of you anxious about testing a new Voyager release, please be patient. We will have 0.5.0 releases out soon for Linux, macOS, and Windows. Follow our current progress on <a href="https://github.com/cosmos/voyager">our GitHub page</a>. Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ffe3346b4f9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cosmos-blockchain/voyager-update-onboard-with-onboarding-3ffe3346b4f9">Voyager Update: “Onboard with Onboarding”</a> was originally published in <a href="https://medium.com/cosmos-blockchain">Cosmos Community Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Smart — log_level flag]]></title>
            <link>https://medium.com/cosmos-blockchain/one-of-the-exciting-new-features-in-0-10-0-release-is-smart-log-level-flag-e2506b4ab756?source=rss-9f6763f3d5b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2506b4ab756</guid>
            <category><![CDATA[logging]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[mempool]]></category>
            <category><![CDATA[tendermint]]></category>
            <dc:creator><![CDATA[Peng Zhong]]></dc:creator>
            <pubDate>Tue, 06 Jun 2017 07:00:00 GMT</pubDate>
            <atom:updated>2017-07-11T07:09:45.552Z</atom:updated>
            <content:encoded><![CDATA[<h4>One of the exciting new features in Tendermint 0.10.0 release is smart ` — log_level` flag. By <a href="https://twitter.com/akaliaev">Anton Kaliaev</a></h4><p>One of the exiting new features in Tendermint 0.10.0 release is smart --log_level flag, which now can accept complex queries.</p><p>Before, one only could set logging level to either notice, info, warning, debug or error, and we got rid of the notice and warning levels in the new release.</p><p>Now, you are able to set different log level for modules:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/639e7e39e9bd50ce9c923658e3f40770/href">https://medium.com/media/639e7e39e9bd50ce9c923658e3f40770/href</a></iframe><p>It will work for any module=.... Some of the most important are: consensus, state, p2p, mempool, proxy, node.</p><p>Info level (default) is used for all other modules. To change that you can use * symbol:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/57f82eecc3c6972697c6764156169d5d/href">https://medium.com/media/57f82eecc3c6972697c6764156169d5d/href</a></iframe><p>These are equivalent:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f568c8d49540ef611d587730d905576c/href">https://medium.com/media/f568c8d49540ef611d587730d905576c/href</a></iframe><p>There is a new none level, which can be used to suppress the output for some or all modules.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bb42790fc73da10d2394203f0d938d1b/href">https://medium.com/media/bb42790fc73da10d2394203f0d938d1b/href</a></iframe><p>Have fun playing with them! Hope you like it.</p><p><em>Originally published at </em><a href="https://gist.github.com/e017c1b5f9b978e8c43e4bae8018f1b5"><em>gist.github.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2506b4ab756" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cosmos-blockchain/one-of-the-exciting-new-features-in-0-10-0-release-is-smart-log-level-flag-e2506b4ab756">Smart — log_level flag</a> was originally published in <a href="https://medium.com/cosmos-blockchain">Cosmos Community Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tendermint 0.10.0 Release]]></title>
            <link>https://medium.com/cosmos-blockchain/tendermint-0-10-0-released-major-refactoring-of-the-repositories-config-and-logger-6c9e3dddc7db?source=rss-9f6763f3d5b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c9e3dddc7db</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[consensus]]></category>
            <category><![CDATA[refactoring]]></category>
            <category><![CDATA[tendermint]]></category>
            <category><![CDATA[golang]]></category>
            <dc:creator><![CDATA[Peng Zhong]]></dc:creator>
            <pubDate>Mon, 05 Jun 2017 07:00:00 GMT</pubDate>
            <atom:updated>2017-07-11T07:09:43.975Z</atom:updated>
            <content:encoded><![CDATA[<h4>Tendermint 0.10.0 includes some major refactoring of the repositories, config, and logger. By <a href="https://twitter.com/buchmanster">Ethan Buchman</a></h4><blockquote>Credits to our <a href="https://tendermint.com/about">team</a>, and <a href="http://forum.tendermint.com:3000/">community</a> for the hard work in making this release possible. Especially to <a href="https://twitter.com/akaliaev">Anton Kaliaev (@melekes)</a> for his work on the new logger, and to <a href="https://medium.com/u/330d1b3768ba">Ethan Frey</a> for fixing everything that broke during this massive refactor!</blockquote><p>The main purpose of Tendermint 0.10.0 is to perform some major, long-overdue, cleanup. This includes merging repositories, introducing configuration structs, overhauling our logger, and cleaning up the JSON APIs.</p><p>Get the latest release at <a href="https://tendermint.com/download">our downloads page</a>. See the <a href="https://github.com/tendermint/tendermint/blob/master/CHANGELOG.md#0100-june-2-2017">v0.10.0 release notes</a> for more details.</p><p><strong>Repository Merging</strong></p><p>When we initially introduced the ABCI in late 2015, we took apart the Tendermint codebase by moving many of the pieces into their own repositories. Most notable were the go-p2p, go-rpc, go-crypto, and go-wire, libraries, but there were also many more like go-db, go-common, go-autofile, and so on. Needless to say, it was painful to synchronize changes across all these repositories.</p><p>In v0.10.0, we merged go-p2p and go-rpc back into tendermint, in the p2p and rpc/lib subdirectories, respectively. We also merged most of the other go-XXX repositories into a new repository, called tmlibs. So now go-common is tmlibs/common, go-db is tmlibs/db, and so on.</p><p>The remaining independent libraries are now the following:</p><ul><li>tmlibs</li><li>go-wire</li><li>go-crypto</li><li>abci</li><li>tendermint</li></ul><p>The go-merkle repository is an exception. It contained two kinds of Merkle tree: a simple, static tree (eg. for hashing transactions), and a dynamic tree, the IAVL tree (eg. for storing state). The former has been moved to tmlibs/merkle. The latter can be found in merkleeyes/iavl. Note that <a href="https://github.com/tendermint/merkleeyes">merkleeyes</a> is effectively an ABCI wrapper around the IAVL tree, so its a natural place for the library itself to live. It is also not used by Tendermint core, and is more a part of our application framework (which includes Basecoin) than a part of the core.</p><p><strong>Config Structs</strong></p><p>Until now, configuration of a Tendermint node has been completely flat and somewhat adhoc. The config data was stored in a map and just passed around everywhere. In v0.10.0, we finally provided some structure, by defining an explicit Config struct, consisting of substructs for each important piece of Tendermint that needs to be configured. We also updated many functions, wherever suitable, to only pass in required arguments rather than an entire configuration.</p><p>The new configuration structs and their defaults can all be found in <a href="https://github.com/tendermint/tendermint/blob/master/config/config.go#L11">config/config.go</a>. We hope this makes the configuration options in Tendermint much more obvious, and simplifies configuring a node just the way you like it.</p><p>Some major differences to note are the rpc and p2p sub-configs. For instance, to specify seed nodes to connect with from the command line, you need to use the p2p prefix:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6c89fa632180e76aea064927874a8b12/href">https://medium.com/media/6c89fa632180e76aea064927874a8b12/href</a></iframe><p><strong>New Logger</strong></p><p>Until now, our logging implementation was quite lazy. Each package had its own global logger, and it was very difficult to configure it. This made it difficult to import Tendermint from other projects, and complicated important features like per-package log levels. So we completely overhauled the logger implementation. Loggers must now be explicitly passed where they are needed. We also now support per-package logging that can be specified in the config.toml or from the command line. We are so proud of our new logging implementation that we wrote a blog post just for it - <a href="https://gist.github.com/blog/abstracting-the-logger-interface-in-go">check it out!</a></p><p>Please note that we have compressed what was once six log levels down to only three: error, info, and debug. This probably means you need to change your config.toml files to replace notice with info. Better yet, try out our new default setting, which takes advantage of the per-package log levels: state:info,*:error! It says to use info for the state package, and error for everything else. If you think you need more log levels, <a href="https://dave.cheney.net/2015/11/05/lets-talk-about-logging">take it up with Dave Cheney</a>.</p><p><strong>Cleaner APIs (no more go-wire!)</strong></p><p>Tendermint is a blockchain engine, which means strict determinism and efficient data formatting are paramount to success. For this reason, we defined our own serialization format — a simple binary representation of the basic data types, but with the additional ability to easily deserialize into interface types in Go. To achieve this, each implementation of an interface is given a type-byte and registered with the serialization library. Then when an interface type is being serialized, its simply prepended with the type-byte of the particular underlying implementation. This has been quite useful for things like transactions, keys, protocol messages, events, and so on.</p><p>Of course, as anyone who has used Tendermint probably knows, the problem with this was JSON serialization. For no good reason, we represented interfaces in JSON as an array, where the first element was the type byte and the second was the actual data. This caused no end of suffering for our users, and even ourselves. Well, I’m proud to say that we have eradicated all use of this obtuse JSON format from Tendermint! For instance, a public key that used to look like:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ec5512f2dfaa07ef70dda8f71e5a145a/href">https://medium.com/media/ec5512f2dfaa07ef70dda8f71e5a145a/href</a></iframe><p>Now looks like:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c042fabeb0df01c11a41d887c05ec394/href">https://medium.com/media/c042fabeb0df01c11a41d887c05ec394/href</a></iframe><p>Isn’t that nice?</p><p>Furthermore, we’ve actually removed all type information from the RPC responses. We hope this makes parsing (and hence using) them much easier and more enjoyable!</p><p>If you have other ways you think we can improve our APIs, please <a href="https://github.com/tendermint/tendermint/issues/new">let us know!</a></p><p><strong>Up Next</strong></p><p>Phew! v0.10.0 marks some quite substantial cleanup — we’re thrilled with the result and we hope you are too. Tendermint should be much easier to use now, both for those using the RPC, and for those importing Tendermint as a library.</p><p>Next up for us are some important changes to ABCI to allow apps to decide what to do with validators who are offline or who misbehaved. This is critical for Proof-of-Stake protocols that use the security-deposits and “slashing”, and is the last big change we need to make to Tendermint to prepare for its use in Cosmos.</p><p>Cheers!</p><p><em>Originally published at </em><a href="https://gist.github.com/e6fd3416e9cc51196e242733450325c2"><em>gist.github.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c9e3dddc7db" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cosmos-blockchain/tendermint-0-10-0-released-major-refactoring-of-the-repositories-config-and-logger-6c9e3dddc7db">Tendermint 0.10.0 Release</a> was originally published in <a href="https://medium.com/cosmos-blockchain">Cosmos Community Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Get your cryptocurrency up and running in 10 minutes]]></title>
            <link>https://medium.com/cosmos-blockchain/get-your-cryptocurrency-up-and-running-in-10-minutes-9ae4c703eb1c?source=rss-9f6763f3d5b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ae4c703eb1c</guid>
            <category><![CDATA[tendermint]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[mintnet]]></category>
            <dc:creator><![CDATA[Peng Zhong]]></dc:creator>
            <pubDate>Wed, 31 May 2017 07:00:00 GMT</pubDate>
            <atom:updated>2017-07-11T07:09:41.032Z</atom:updated>
            <content:encoded><![CDATA[<h4>So, your Tendermint application is finally ready and you want to distribute it and run it on several machines. By <a href="https://twitter.com/akaliaev">Anton Kaliaev</a></h4><p>So, your Tendermint application is finally ready and you want to distribute it and run it on several machines, or just run it locally by creating a dozen Docker containers. We have created <a href="https://github.com/tendermint/tools/tree/master/mintnet-kubernetes">mintnet-kubernetes</a> to help you achieve this goal as fast as possible. Note that it should be primarily used for testing purposes or for tightly-defined chains operated by a single stakeholder (see <a href="https://github.com/tendermint/tools/tree/master/mintnet-kubernetes#security">the security precautions</a>). If you want to launch an application with many stakeholders, consider using <a href="https://github.com/tendermint/tools/tree/master/ansible-tendermint">our set of Ansible</a> scripts to deploy Tendermint.</p><p>mintnet-kubernetes is a configuration file for <a href="https://kubernetes.io/">Kubernetes</a>.</p><p><em>Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications.</em></p><p>If you had never heard of it, it won’t hurt to read <a href="https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/">What is Kubernetes?</a> and go through their <a href="https://kubernetes.io/docs/tutorials/kubernetes-basics/">interactive lessons</a>. It won’t take long, I promise.</p><p>There are several ways to install a Kubernetes cluster:</p><ul><li>a local Docker-based solution using <a href="https://github.com/kubernetes/minikube">Minikube</a></li><li>hosted solutions using a Web UI or CLI (e.g. GCE)</li><li>turn-key cloud solutions (e.g. AWS using <a href="https://github.com/kubernetes/kops/blob/master/docs/aws.md">Kubernetes Operations</a>; AWS, Azure, GCE or bare metal using <a href="https://kubernetes.io/docs/getting-started-guides/kargo/">Kargo</a>)</li><li>custom solutions (e.g. Linux machines using <a href="https://kubernetes.io/docs/getting-started-guides/kubeadm/">kubeadm</a>)</li></ul><p>If you just want to play with your application, choose a local installation with Minikube. If you want to run it in the cloud or on bare metal, refer to <a href="https://kubernetes.io/docs/getting-started-guides">Picking the Right Solution</a>, taking into account the cost, safety, reliability, and configuration options of those solutions.</p><p>Further, we will assume that you have a standard 64-bit Linux desktop with <a href="https://www.virtualbox.org/wiki/Downloads">VirtualBox</a> or <a href="http://www.linux-kvm.org/">KVM</a> installed.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a7b4255e1244874d26cb1074f5fecb80/href">https://medium.com/media/a7b4255e1244874d26cb1074f5fecb80/href</a></iframe><p>For Windows or OS X, please check out <a href="https://kubernetes.io/docs/tasks/kubectl/install/">Installing and Setting Up kubectl</a> guide.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c1c002bf1e19d5dfef691ae241c8ed56/href">https://medium.com/media/c1c002bf1e19d5dfef691ae241c8ed56/href</a></iframe><p>For Windows or OS X, please check out <a href="https://github.com/kubernetes/minikube/releases">Releases</a> page.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fb4821d72b29b7bb22e8a9fab7e41c57/href">https://medium.com/media/fb4821d72b29b7bb22e8a9fab7e41c57/href</a></iframe><ol><li>Downloading a configuration template for our future cluster</li></ol><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/39efea5cb0d9411f9c4a7ac4c9358925/href">https://medium.com/media/39efea5cb0d9411f9c4a7ac4c9358925/href</a></iframe><p>Open it in the editor of your choice:</p><pre>$EDITOR app.yaml</pre><p><a href="https://github.com/tendermint/basecoin">https://github.com/tendermint/basecoin</a> will help us create our own currency, extensible with plugins. Writing plugins is out of scope of this article, but you can read about it <a href="https://github.com/tendermint/basecoin/blob/master/docs/guide/basecoin-plugins.md">here</a>.</p><p>Kubernetes DSL (Domain Specific Language) can be difficult for the beginner to grasp. Fortunately, we will need to change only a small piece of code.</p><p>The most important thing is the application’s genesis.json file. It defines the initial distribution of assets. We have 4 nodes by default (replicas: 4in StatefulSet). Generally, it is a good idea to split assets evenly between them and have some large number for everyone.</p><p>Let’s change denom to “MyAwesomeCoin”. You are welcome to pick any other name you like.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b82dea0a56e759cff94b97501032645e/href">https://medium.com/media/b82dea0a56e759cff94b97501032645e/href</a></iframe><p>Now we are ready to launch our cryptocurrency:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/db9a247b4ac4133634e0d4a175292c47/href">https://medium.com/media/db9a247b4ac4133634e0d4a175292c47/href</a></iframe><p>Wait until all of the nodes are running:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c46dbcfbe107f5b9ade556fd8ffb9e9b/href">https://medium.com/media/c46dbcfbe107f5b9ade556fd8ffb9e9b/href</a></iframe><p>Let’s check the first account:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/607ceecff2f855256bf2609dadf01df2/href">https://medium.com/media/607ceecff2f855256bf2609dadf01df2/href</a></iframe><p>Great! Let’s try to send a transaction from the first to the second account:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b690d7dffc6791e64e377a0f07769d00/href">https://medium.com/media/b690d7dffc6791e64e377a0f07769d00/href</a></iframe><p>Checking the first account’s balance we should see 5 coins making their way into the second account:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2d36d93fdca23331a014c3da08ba5bda/href">https://medium.com/media/2d36d93fdca23331a014c3da08ba5bda/href</a></iframe><p>As you can see, it was fairly simple to launch a new cryptocurrency in a Kubernetes cluster. Moreover, with Kubernetes you can add new nodes (pods) with a single command. And using <a href="https://kubernetes.io/docs/concepts/cluster-administration/federation/">federation</a>, you can be sure that your currency will stay alive even after loss of the entire cluster!</p><p>Clean up:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cfa65549c0097a58f511a92c57045979/href">https://medium.com/media/cfa65549c0097a58f511a92c57045979/href</a></iframe><p><em>Originally published at </em><a href="https://gist.github.com/04a4bac8e25043da221ec6a59d77a0bb"><em>gist.github.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ae4c703eb1c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cosmos-blockchain/get-your-cryptocurrency-up-and-running-in-10-minutes-9ae4c703eb1c">Get your cryptocurrency up and running in 10 minutes</a> was originally published in <a href="https://medium.com/cosmos-blockchain">Cosmos Community Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Abstracting the logger interface in Go]]></title>
            <link>https://medium.com/cosmos-blockchain/abstracting-the-logger-interface-in-go-4cf96bf90bb7?source=rss-9f6763f3d5b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/4cf96bf90bb7</guid>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[mempool]]></category>
            <category><![CDATA[consensus]]></category>
            <category><![CDATA[logging]]></category>
            <category><![CDATA[tendermint]]></category>
            <dc:creator><![CDATA[Peng Zhong]]></dc:creator>
            <pubDate>Tue, 30 May 2017 07:00:00 GMT</pubDate>
            <atom:updated>2017-07-11T07:09:39.045Z</atom:updated>
            <content:encoded><![CDATA[<h4>This article describes the evolution of logging in Tendermint. By <a href="https://twitter.com/akaliaev">Anton Kaliaev</a></h4><p>This article describes the evolution of logging in Tendermint. We went from having a static <a href="https://github.com/inconshreveable/log15/">log15</a> logger to a transparent interface and implementation that uses <a href="https://github.com/go-kit/kit/tree/master/log">go-kit’s log</a> package under the hood, but can be easily swapped with any other available package.</p><h3>The old way</h3><p>We were using package level log variables to set the logger for each package. For instance, for the mempool package:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a794049cd4a44ab2291fb35e71ea07a9/href">https://medium.com/media/a794049cd4a44ab2291fb35e71ea07a9/href</a></iframe><p>Here, logger.New returns “something” with a log15.Logger interface.</p><p>Although it was simple and required almost no time to setup, this approach has some downsides:</p><ol><li>Tight coupling between the mempool and logger packages. The mempool package now directly depends on logger at compile time. Also, it’s transitive, which means that any package that consumes mempool is itself dependent on logger at compile time. Read <a href="https://dave.cheney.net/2017/01/23/the-package-level-logger-anti-pattern">Dave Chaney’s post</a> for details.</li><li>Even though log15 is hidden inside the logger package, we are using its interface. When we decided to make changes to the interface, we had to fork the logger repo.</li><li>If somebody wanted to change the log level just for that package, they would need to uncomment the init function. This did not scale very well, as you can imagine.</li><li>There is no way to implement custom coloring when using log15 (for example, if I want different colors depending on whenever key-values contain err key)</li></ol><h3>The new way</h3><h4>Our own interface</h4><p>We started by creating an interface:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2e00ff3d25b1cac64400b128f32d488b/href">https://medium.com/media/2e00ff3d25b1cac64400b128f32d488b/href</a></iframe><p>It is very simple and does not tie us to any existing logging package. Also, we wanted to avoid having many log levels, as many people advocate against it:</p><blockquote><em>Avoid fine-grained log levels — info and debug are probably enough (</em><a href="https://peter.bourgon.org/go-best-practices-2016/#logging-and-instrumentation"><em>Peter Bourgon</em></a><em>)</em></blockquote><blockquote><em>Nobody needs a warning log level. (</em><a href="https://dave.cheney.net/2015/11/05/lets-talk-about-logging"><em>Dave Cheney</em></a><em>)</em></blockquote><p>This fixed the second issue (log15 interface).</p><h4>Writing an adapter for the interface</h4><p>Then we proceeded by picking a logging library and implementing an adapter.</p><p>The requirements for the logging library were as follows:</p><p>a) supports coloring output b) is moderately fast (buffering) c) is somewhat configurable</p><p>In the end, we were choosing between <a href="https://github.com/sirupsen/logrus">logrus</a> and <a href="https://github.com/go-kit/kit/tree/master/log">go-kit/log</a>.</p><p>go-kit/log is flexible and modular, but the default formatter uses <a href="https://brandur.org/logfmt">logfmt format</a>, which is more computer friendly than human friendly.</p><p>logrus is popular and feature rich, but not as flexible.</p><p>Some people say having too many features is bad:</p><blockquote><em>I want to take a contradictory position. I think that all logging libraries are bad because the offer too many features; a bewildering array of choice that dazzles the programmer right at the point they must be thinking clearly about how to communicate with the reader from the future; the one who will be consuming their logs. (</em><a href="https://dave.cheney.net/2015/11/05/lets-talk-about-logging"><em>Dave Cheney</em></a><em>)</em></blockquote><p>So we chose go-kit/log.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b3bb83b08cce20d6e8fce45ab06ce8aa/href">https://medium.com/media/b3bb83b08cce20d6e8fce45ab06ce8aa/href</a></iframe><p>The full code can be found on <a href="https://github.com/tendermint/tmlibs/tree/master/log">Github</a>.</p><p>The code is self explanatory. We implement our interface by proxying to the underlying logger (srcLogger) with level and message keys prepended to keyvals.</p><p>TMFmtFormatter’s format is very similar to <a href="https://brandur.org/logfmt">logfmt</a>, except it gives the level, timestamp and message a special treatment. We inherited this format from <a href="https://github.com/inconshreveable/log15/">log15</a>. It provides a nice balance between readability and computer friendliness.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/20fd6b717da16ac7547544fe50e086c9/href">https://medium.com/media/20fd6b717da16ac7547544fe50e086c9/href</a></iframe><p>The new scheme enabled us to remove all our log.go files, but required us to add log log.Logger fields to the structs that do any logging. This was a worth-while trade-off, since it relieves the tight-coupling (ie. the first issue mentioned earlier).</p><h3>Log levels per package</h3><p>First, we implemented generic filtering based on <a href="https://github.com/go-kit/kit/blob/master/log/level/level.go#L25">go-kit/log filter</a>. Then, we added a few new options:</p><ul><li>AllowDebugWith</li><li>AllowInfoWith</li><li>AllowErrorWith</li><li>AllowNoneWith</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5da7e76e42609811ec9728404bcb773a/href">https://medium.com/media/5da7e76e42609811ec9728404bcb773a/href</a></iframe><p>The API is straightforward and easy to understand. In the example above, we are saying: “use info level if key-values contain “module/crypto” pair; otherwise, use error level”.</p><p>That said, there are some corner cases, which we describe <a href="https://github.com/tendermint/tmlibs/blob/master/log/filter.go#L73">here</a>.</p><h3>Custom coloring</h3><p>Custom coloring is easy with go-kit/log. The only thing you need is to provide the coloring function:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/08e3f8e341a2a4de566f4ed672eaa479/href">https://medium.com/media/08e3f8e341a2a4de566f4ed672eaa479/href</a></iframe><p>There are many other things you can do with such adapters. If you are curious, here is how we <a href="https://github.com/tendermint/tmlibs/blob/master/log/tmfmt_logger.go">implemented our own formatter</a>. Also, it is a nice thing to have a <a href="https://github.com/tendermint/tmlibs/blob/master/log/nop_logger.go">nil logger (or nop logger)</a> to discard the output.</p><h3>Conclusion</h3><p>By replacing the old static logging system with a new abstract interface and adapter, we archived greater flexibility, lower coupling (one could use Tendermint’s package and their own logger, if it conforms to our interface) and avoided vendor lock-in (we now can swap the implementations very easily).</p><p>Thanks to the new implementation we now have consensus tests where each instance has its own color, smart --log_level flag which allows disabling output for one package and allowing some level for others. Stay tuned for more updates!</p><p><em>Originally published at </em><a href="https://gist.github.com/63a0524759e786d40e92d6f964847e25"><em>gist.github.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4cf96bf90bb7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cosmos-blockchain/abstracting-the-logger-interface-in-go-4cf96bf90bb7">Abstracting the logger interface in Go</a> was originally published in <a href="https://medium.com/cosmos-blockchain">Cosmos Community Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Ethermint — Part 1]]></title>
            <link>https://medium.com/cosmos-blockchain/introducing-ethermint-part-1-385ba9a148d3?source=rss-9f6763f3d5b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/385ba9a148d3</guid>
            <category><![CDATA[tendermint]]></category>
            <category><![CDATA[ethermint]]></category>
            <category><![CDATA[consensus]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Peng Zhong]]></dc:creator>
            <pubDate>Fri, 26 May 2017 07:00:00 GMT</pubDate>
            <atom:updated>2017-07-11T07:09:37.525Z</atom:updated>
            <content:encoded><![CDATA[<h4>Running vanilla Ethereum on top of Tendermint consensus. By <a href="https://medium.com/u/a02fdd9c9222">Adrian Brink</a></h4><p>As you might have heard, the <a href="https://tendermint.com/">Tendermint</a> consensus engine can support almost any other crypto-currency, as long as the source code is open-source and some developer is willing to write an ABCI wrapper around it.</p><p>As part of Tendermint’s goal to launch the <a href="https://cosmos.network/">COSMOS hub</a>, we are enabling Ethereum to run on top of Tendermint. This allows developers to have all the nice features of Ethereum, while at the same time benefit from Tendermint’s proof of stake implementation. Tendermint combined with Ethereum results in fast block times, transaction finality while also getting the goodies of smart contracts.</p><h3>Installation</h3><p>Depending on how cutting edge you would like to be, you can choose between the develop branch or the master branch. <strong>Currently you have to choose the </strong><strong>develop branch for </strong><a href="https://ethermint.network/"><strong>Ethermint</strong></a><strong>.</strong></p><h4>Install go1.8</h4><p>To explore the possibilities of Ethermint you need a couple of prerequisites. First, you need to have <a href="https://golang.org/doc/install">go1.8</a> installed and your $GOPATH properly configured. This is necessary since we are currently not shipping binaries for Ethermint.</p><h4>Install Tendermint</h4><p>The second requirement is that you are able to run a Tendermint node, since this engine handles all the blockchain aspects, like P2P and consensus. To install Tendermint just run go get -u github.com/tendermint/tendermint/cmd/tendermint and you should be good to go. If not follow this <a href="https://tendermint.com/docs/guides/install">link</a>. As an alternative you can also download <a href="https://tendermint.com/download">binaries</a>.</p><h4>Install Ethermint</h4><p>Lastly, we need to install ethermint itself. First clone the source code (git clone https://github.com/tendermint/ethermint.git). Afterwards, switch into the source code directory and run make install and voila, Ethermint should be installed.</p><h4>Install geth</h4><p>Geth is an Ethereum tool that allows you to attach to a running Ethereum node over RPC. We will use it later to interact with Ethermint. Please follow this <a href="https://github.com/ethereum/go-ethereum/wiki/Building-Ethereum">guide</a> to install it on your local machine.</p><h3>Running Ethermint</h3><h4>Starting Tendermint</h4><p>First you need to initialise Tendermint by running tendermint --home ~/.ethermint/tendermint init. This initialises the Tendermint node. The next step is to run tendermint --home ~/.ethermint/tendermint node to start the Tendermint node.</p><h4>Starting Ethermint</h4><p>In a second terminal window switch into the folder with the Ethermint source code. Then run ethermint --datadir ~/.ethermint init dev/genesis.json to initialise the Ethermint files. Then in order to have an account with money run cp -r dev/keystore ~/.ethermint/keystore. Afterwards, start the Ethermint node by running ethermint --datadir ~/.ethermint --rpc --rpcaddr=0.0.0.0 --ws --wsaddr=0.0.0.0 --rpcapi eth,net,web3,personal,admin. This tells Ethermint to expose a lot of its functionality over RPC.</p><p>At this stage you should see blocks streaming by in both the Tendermint and the Ethermint windows.</p><h4>Attaching geth to Ethermint</h4><p>In a third terminal window run geth attach http://localhost:8545. Now you should find yourself in a console environment, where you can use the <a href="https://github.com/ethereum/wiki/wiki/JavaScript-API">Web3</a> commands to interact with the Ethermint node.</p><h3>Conclusion</h3><p>In this short introduction I have explained how to setup Ethermint and how to interact with it using geth. From here, you should be able to develop smart contract applications or simply send transaction between different accounts.</p><p>If you have any trouble setting up any of the above systems or are running into issues using them, please find me on <a href="https://tendermint.slack.com/">slack</a> under @adrian, via <a href="https://twitter.com/adrian_brink">twitter</a> or via email <a href="/service/mailto:adrian@tendermint.com">adrian@tendermint.com</a> .</p><h3>Next Up</h3><p><a href="https://blog.cosmos.network/using-ethermint-with-geth-and-mist-d4b7715abbd9">In my next blog post</a> I will explain how to use docker to setup multiple Ethermint instances, so that you can experiment with running networks of Ethermint nodes. Furthermore, I will explain how Ethermint relates to the COSMOS hub.</p><p><em>Originally published at </em><a href="https://gist.github.com/f878a4040a3f92c1094ad742c82cea87"><em>gist.github.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=385ba9a148d3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cosmos-blockchain/introducing-ethermint-part-1-385ba9a148d3">Introducing Ethermint — Part 1</a> was originally published in <a href="https://medium.com/cosmos-blockchain">Cosmos Community Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tendermint 0.9.1 Release]]></title>
            <link>https://medium.com/cosmos-blockchain/tendermint-0-9-1-release-b168cb1383cb?source=rss-9f6763f3d5b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b168cb1383cb</guid>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[merkle-tree]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[tendermint]]></category>
            <category><![CDATA[abci]]></category>
            <dc:creator><![CDATA[Peng Zhong]]></dc:creator>
            <pubDate>Fri, 21 Apr 2017 07:00:00 GMT</pubDate>
            <atom:updated>2017-07-11T07:09:35.389Z</atom:updated>
            <content:encoded><![CDATA[<h4>Tendermint 0.9.1 fixes a few bugs and introduces transaction indexing. By <a href="https://twitter.com/buchmanster">Ethan Buchman</a></h4><blockquote>Credits to our <a href="https://tendermint.com/about">team</a>, and <a href="http://forum.tendermint.com:3000/">community</a> for the hard work in making this release possible.</blockquote><p>The main purpose of Tendermint 0.9.1 is to introduce a long sought feature, transaction indexing. Until now, it has been difficult to track the result of a transaction, or even to know if it was committed, unless you were online and subscribed to events via websockets. Now, we make that easy, with a new rpc endpoint, /tx?hash=X. We also fixed a few bugs in fast sync mode and in the handshake, and upgraded the Command Line Interface to use the phenomenal github.com/spf13/cobra library.</p><p>Get the latest release at <a href="https://tendermint.com/download">our downloads page</a>. See the <a href="https://github.com/tendermint/tendermint/blob/master/CHANGELOG.md#091-april-18-2017">v0.9.1 release notes</a> for more details.</p><p><strong>Tx Indexing</strong></p><p>A blockchain is just a simple list of blocks, where every block contains a list of transactions. For storage, each block is serialized and stored under its height within a LevelDB database. Most blockchain software may actually store blocks under their hash, rather than height, as there may be multiple blocks for a given height. However, since Tendermint never forks, we have a unique block for every height and can use this simpler index.</p><p>Finding a transaction under this kind of storage is difficult, since you have to scan through full blocks. Thus, in the latest release, we index every transaction by its hash, enabling fast queries without having to load any blocks. We also store some other data with the transaction: result of processing it (ie. the Code and Data returned by DeliverTx), the height of the block it was committed in, and the index of the transaction in that block. Note that the transaction is stored on disk twice: once in the block, and once under the transaction index.</p><p><strong>Fast Sync and Handshake Fixes</strong></p><p>A Tendermint node that has fallen behind its peers has a number of ways to catch up. Peers that are many blocks behind can use the fast_sync option (enabled by default) to quickly download and verify blocks, without going through any of the expensive consensus protocol steps. In this mode, peers are polled for their latest height, and the node starts requesting blocks from many peers in parallel. If a peer suddenly goes offline, the node must request any blocks that peer was supposed to provide from new peers. In this release, we fixed a bug that was not properly accounting for these new requests when a peer went offline, causing the downloads to halt all together in some cases.</p><p>Another important syncing mechanism in Tendermint is the ABCI handshake, introduced in 0.8.0, which allows Tendermint to recover from crashing in the middle of processing a block through the ABCI app. During the handshake, Tendermint sends the Info message to the ABCI app, which responds with the latest block it has processed. Tendermint can then replay any blocks it has in its store that the app has not processed yet. There is one particular crash scenario that is more subtle: the app has finished processing a block, but Tendermint crashes before saving its state. In this scenario, Tendermint cannot replay the block (since that would confuse the app), but it needs to get the results from processing it, otherwise it would lose that data, which could contain critical information like validator set changes. This is fixed in the latest release by saving the results of processing a block before calling Commit, reloading those results if necessary upon a crash/restart.</p><p><strong>New CLI</strong></p><p>Until now, Tendermint’s command line interface has been implemented very simply, without using any framework. This made it somewhat annoying to maintain, as we had to keep track of things that can be done for us by many libraries. In this release, we ported the CLI to use the <a href="https://github.com/spf13/cobra">Cobra library</a>, which is quite popular in the Go community and provides many wonderful features. Fortunately, we could make this change without breaking backwards compatibility.</p><p><strong>Up Next</strong></p><p>Next up for us is the grand repo merge! We currently have many little repositories, and even some big ones, and co-ordinating across all of them has become painful. So we will be doing a massive consolidation. All the little libraries will be centralized under github.com/tendermint/tmlibs, including go-common, which will have its new home under tmlibs/common. Our encoding and crypto libraries, go-wire and go-crypto, will remain independent. Our Merkle tree implementations will be moved into other libraries, with the simple Merkle tree going in tmlibs/merkle and the IAVL tree moving under merkleeyes/iavl. Finally, our p2p and rpc libraries, go-p2p and go-rpc, will be merged into Tendermint Core.</p><p>Included in the repo merge are some changes to the way we handle JSON, bringing it inline with standard Go libraries. This will cause breaking changes, for instance to the genesis.json file, so we will be releasing all of this together as version 0.10.0.</p><p>Cheers!</p><p><em>Originally published at </em><a href="https://gist.github.com/3f839abf3e893568dea5f0aeed7c4008"><em>gist.github.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b168cb1383cb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cosmos-blockchain/tendermint-0-9-1-release-b168cb1383cb">Tendermint 0.9.1 Release</a> was originally published in <a href="https://medium.com/cosmos-blockchain">Cosmos Community Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fundraiser Was a Resounding Success]]></title>
            <link>https://medium.com/cosmos-blockchain/fundraiser-was-a-resounding-success-bf378b96fe00?source=rss-9f6763f3d5b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf378b96fe00</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[fundraiser]]></category>
            <dc:creator><![CDATA[Peng Zhong]]></dc:creator>
            <pubDate>Thu, 06 Apr 2017 07:00:00 GMT</pubDate>
            <atom:updated>2017-07-01T02:04:47.379Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By The Cosmonauts</em></p><p>Wow. That was remarkable. Within seconds of opening <a href="https://fundraiser.cosmos.network/">the fundraiser</a> at 6am PDT this morning, well over a million dollars worth of BTC and ETH poured in. Obviously, many of you were very well prepared. Over the following roughly 30 minutes, we raised over 16M USD worth of BTC and ETH, smashing through our hidden cap of 17M.</p><p>Thank you everyone for your amazing support!</p><p><a href="https://fundraiser.cosmos.network/">The fundraiser is now closed.</a> It’s time for us to get back to work on building out the Internet of Blockchains!</p><h3>Proof of the Hidden Cap</h3><p>Our goal for this fundraiser was to raise 10M USD. However, seeing as how quickly certain other fundraisers have hit their cap, we decided to allow more than 10M to be raised within the first 6 hours. That said, we did not want to be in a position where we raised too much money, so we set an additional hard-cap, such that if we hit that, we would halt the fundraiser.</p><p>We decided to keep this hard cap hidden, because we felt doing so would discourage whales from buying too much. Indeed, we got a lot of feed back on slack that many people were discouraged from donating too much because of this hidden cap — exactly the effect we hoped for!</p><p>On March 26, 2017, Jae published a commit to the hidden cap on twitter: <a href="https://twitter.com/jaekwon/status/846055257675218944">https://twitter.com/jaekwon/status/846055257675218944</a>. The commitment is 5faa9a8d3faa019b836f63779c454aa2cefa310ba1e04b251dcbfcd3db5471ec. The pre-image for this is the following text:</p><pre>SALT: 26ed7ab241901f7e0a7d<br>MSG: The cap for the first 6 hours is $17M USD</pre><p>If you save that text in a file, say cap.txt, and run shasum -a 256 cap.txt, you can confirm the commitment.</p><h3>Suggested Atom Allocations</h3><p>For each donation, the Interchain Foundation suggests a certain number of Atoms be allocated to the relevant Cosmos address in the genesis block of the Cosmos Network. The Cosmos Network is expected to launch in Q4 2017, and Atoms will not be accessible until then. That said, the suggested Atom allocations for a given donation can be easily computed.</p><p>First, you need your Cosmos address. If you did not write it down during the fundraiser, no worries. You can use the cosmos-fundraiser tool to figure it out, so long as you wrote down your 12-words. If you lost the 12-words, your Atoms are gone forever.</p><p>To install the tool, you must have node.js installed. Then simply run:</p><pre>npm install -g cosmos-fundraiser-cli@2.11.0</pre><p>Now you can check your Cosmos address by running:</p><pre>cosmos-fundraiser cosmosaddress</pre><p>It will prompt you for your twelve words, and will spit out your address. Please make sure you enter the words correctly.</p><p>If you donated in ETH, your suggested Atom balance is stored directly in the smart contract. To query it, enter your Cosmos address in the record field here: <a href="https://etherscan.io/address/0xcf965cfe7c30323e9c9e41d4e398e2167506f764#readContract">https://etherscan.io/address/0xcf965cfe7c30323e9c9e41d4e398e2167506f764#readContract</a></p><p>If you donated in BTC, your Cosmos address was recorded in an OP_RETURN output. There is no easy way to query for your suggested Atom balance yet, but if you lookup your transaction on blockchain.info, you should see your Cosmos address recorded in the second output, next to OP_RETURN. Note that blockchain.info doesn’t handle OP_RETURN, so it will say “Unable to decode output address” — that is fine and totally expected. To get your suggested Atom balance, just multiply the amount of BTC in the first output by 11635. Also note, your transaction MUST be included between block 460654 and 460661, inclusive. If your transaction is included in a block outside this range, your suggested Atom balance is 0.</p><p>We will put up a service in the next couple days to make it super easy to query for your suggested Atom balance directly, whether you donated in BTC or ETH.</p><p><strong>Update:</strong> The Atom balance viewer is now available on <a href="https://fundraiser.cosmos.network/">the fundraiser page</a>.</p><h3>Issues</h3><p>If you had any issues with the fundraiser, please contact us at <a href="/service/mailto:fundraiser@cosmos.network">fundraiser@cosmos.network</a>.</p><h3>Conclusion</h3><p>Thanks again for making <a href="https://fundraiser.cosmos.network/">this fundraiser</a> an epic success! We look forward to building the Internet of Blockchains with you.</p><p><em>Originally published at </em><a href="https://gist.github.com/ff79c2d17f5bf1a3536193c04f44b060"><em>gist.github.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf378b96fe00" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cosmos-blockchain/fundraiser-was-a-resounding-success-bf378b96fe00">Fundraiser Was a Resounding Success</a> was originally published in <a href="https://medium.com/cosmos-blockchain">Cosmos Community Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>