<?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 ICX_Station on Medium]]></title>
        <description><![CDATA[Stories by ICX_Station on Medium]]></description>
        <link>https://medium.com/@icxstation?source=rss-37cf51ed2615------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZQvXUoFFFDTARypKtn8RjQ.png</url>
            <title>Stories by ICX_Station on Medium</title>
            <link>https://medium.com/@icxstation?source=rss-37cf51ed2615------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:22:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@icxstation/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[ICX Station Announces the Revamp of ICON Vote]]></title>
            <link>https://medium.com/helloiconworld/icx-station-announces-the-revamp-of-icon-vote-a9c68d27ff52?source=rss-37cf51ed2615------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9c68d27ff52</guid>
            <category><![CDATA[ecosystem]]></category>
            <category><![CDATA[icx-station]]></category>
            <dc:creator><![CDATA[ICX_Station]]></dc:creator>
            <pubDate>Fri, 13 Nov 2020 22:56:45 GMT</pubDate>
            <atom:updated>2020-11-13T22:56:45.674Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*32C0GdEsgvL7evfN" /><figcaption>ICON Vote Revamp</figcaption></figure><p><a href="https://icxstation.com/">ICX Station</a> is proud to announce that <a href="https://icon.vote/">ICON Vote</a> revamp has been completed with the support of the <a href="https://parrot9.com/">Parrot 9 team</a> and a <a href="https://forum.icon.community/t/grant-application-icon-vote-revamp-proposal/656">community developer</a>. We are extremely excited that ICON Vote went through the beta testing phase, collected feedback from community members, and is ready to be utilized by P-reps and community members of the ICON Ecosystem for more active governance.</p><p>Here are a few major updates since the beta release:</p><ol><li>P-reps can create a proposal that is specific to community members who voted for a specific P-rep or general community members who voted for any P-rep with their staked ICX</li><li>New <a href="https://icon.vote/about">About</a> Page</li><li>Enhanced user experience/design</li></ol><p>As a reminder, ICON Vote has the following major benefits:</p><ol><li>Utilize <a href="https://executive.mit.edu/blog/will-collective-intelligence-change-the-way-we-work">collective intelligence</a> from the community: we believe the community is the biggest asset to the ICON ecosystem and it would be a waste to not utilize the community’s feedback.</li><li>Silent majority can voice their opinion now through votes: social media can sometimes be skewed towards a specific direction based on vocal minorities and many do not like to participate in such discussions. ICON Vote can give them an outlet to voice their opinion.</li><li>Great efficiency and productivity: Discussion needs to end sometimes and voting can help move conversations forward. Healthy discussions are always good, but some discussions never end, and there is no progress. As a mature community, we need to sometimes agree to disagree and put it to a vote so that we can move on to work on greater things.</li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FUrkEUU3Zz_0%3Fstart%3D118%26feature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DUrkEUU3Zz_0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FUrkEUU3Zz_0%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/91d4a770f1dd3b050fde46f581e1fdf2/href">https://medium.com/media/91d4a770f1dd3b050fde46f581e1fdf2/href</a></iframe><p>We believe in <a href="https://en.wikipedia.org/wiki/Eating_your_own_dog_food">dogfooding</a>, so we will actively start utilizing the revamped ICON Vote for the upcoming <a href="https://docs.google.com/document/d/1g1idSDN7D64gHaBjOyhNw2dAD2YqEQcon_kB1WLJhas/edit?usp=sharing">Contribution Proposal System</a> (CPS). CPS, which has been one of the most significant innovations by the ICON Project, is expected to launch soon and P-reps are supposed to evaluate projects that are submitted through CPS. ICX Station will actively monitor projects that are submitted, but we believe in the importance of hearing the voices of the community as well, so we would like to take our community’s feedback on ICON Vote as we consider projects on CPS.</p><p>We also would like to encourage more P-reps to consider using ICON Vote to communicate with their community members for CPS and other interesting purposes. Community is the biggest asset to the ICON ecosystem and we believe it is essential to provide tools for community members to proactively participate in the future of the network, which will strengthen our community and ecosystem in return. It may not be the ultimate tool to solve the existing voter apathy problem, but we hope ICON Vote becomes a useful tool for ICX enthusiasts so that they can voice their opinion more proactively. Go Vote!</p><p>Your Partner in Blockchain,</p><p>ICX Station</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9c68d27ff52" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helloiconworld/icx-station-announces-the-revamp-of-icon-vote-a9c68d27ff52">ICX Station Announces the Revamp of ICON Vote</a> was originally published in <a href="https://medium.com/helloiconworld">Hello ICON World</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bridge: Connecting blockchain-based applications to the masses]]></title>
            <link>https://medium.com/helloiconworld/bridge-connecting-blockchain-based-applications-to-the-masses-1152798d7afe?source=rss-37cf51ed2615------2</link>
            <guid isPermaLink="false">https://medium.com/p/1152798d7afe</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[magic]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[icon-foundation]]></category>
            <dc:creator><![CDATA[ICX_Station]]></dc:creator>
            <pubDate>Mon, 17 Aug 2020 16:47:57 GMT</pubDate>
            <atom:updated>2020-08-17T16:47:57.549Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ypTAfeKMeLtjXVbr" /></figure><p>ICX Station is proud to announce Bridge, our latest incubator project focused on growing the addressable market for blockchain-based applications. With Block42 and PARROT9 assisting with development, we will utilize SDKs from both <a href="https://magic.link/">Magic</a> (formerly Fortmatic) and a banking partner to create a seamless user experience when non-crypto users interact with ICON applications. Bridge will offer an SDK to ICON developers for simple integration of the Bridge widget into their application.</p><p>The mission of Bridge is simple: remove all friction when using blockchain apps. When consumers are using applications built on ICON, Bridge will hide everything and anything associated with blockchain technology. To the end user, all they will know is that they created an account using an email address and deposited some money into their account.</p><p>Unbeknownst to the user, Bridge will create a Magic wallet linked to their email address. When a user deposits fiat currency, our banking partner will take custody of their currency and Bridge will then mint fiat-backed stablecoins for the user. To the end user, all they have done is log-in with their email and deposit money into their Bridge account.</p><p>Equipped with fiat-backed stablecoins and an ICON wallet, users are now free to interact with any application using ICON’s technology without ever having to understand what a blockchain is. Bridge brings together several different existing blockchain services (fiat-backed stablecoins, fiat on-ramp, fiat off-ramp, and private key management) into one seamless user experience.</p><p>ICX Station hopes to see Bridge open up the door to a different kind of application built on ICON. Some apps will always require a knowledge of blockchain and awareness of ICX (<a href="http://balanced.network/">Balanced</a>, for example), however, future ICON applications using Bridge could instead allow users to buy/sell goods and services while still under the impression they are using fiat currency.</p><p>At ICX Station, we realize that the current target market of DApps is small. There are only so many people in the word that know about cryptocurrency, let alone how to purchase and use it. Instead of competing for market share in this relatively small market, Bridge allows ICON developers to expand their target market far beyond existing cryptocurrency holders and traders. This is an effort to grow the pie, rather than fighting for slices of the existing one.</p><p>We are excited for the launch of Bridge with current expectations of a Q3 2020 launch. If you have any ideas to launch a project built around Bridge, please reach out to us on <a href="https://t.me/icxstation">Telegram</a> or <a href="https://twitter.com/IcxStation">Twitter</a>.</p><p>Your Partner in Blockchain,</p><p>ICX Station</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1152798d7afe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helloiconworld/bridge-connecting-blockchain-based-applications-to-the-masses-1152798d7afe">Bridge: Connecting blockchain-based applications to the masses</a> was originally published in <a href="https://medium.com/helloiconworld">Hello ICON World</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ICON Economics Overview]]></title>
            <link>https://medium.com/helloiconworld/icon-economics-overview-8f5ed8db0c63?source=rss-37cf51ed2615------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f5ed8db0c63</guid>
            <category><![CDATA[icx-station]]></category>
            <category><![CDATA[ecosystem]]></category>
            <dc:creator><![CDATA[ICX_Station]]></dc:creator>
            <pubDate>Tue, 14 Jul 2020 05:46:28 GMT</pubDate>
            <atom:updated>2020-07-14T05:46:28.200Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello from ICX Station,</p><p>We have noticed more questions being asked about ICON’s economic policy and have realized that the only form of documentation is the yellow paper. With that said, we will keep this document as short, simple, direct, and up-to-date as possible. It will cover ICON’s current economic policy and will be updated as things change over time.</p><p>ICON’s current economics can be broken into two categories: block producers (P-Reps) and voters (ICX holders). The network directly rewards voters and nodes separately, so there is no need for nodes to take a commission fee and disperse the rest to their voters, this is already built into the network. Read more about this structure <a href="https://medium.com/helloiconworld/path-to-sustainable-economics-450be4137724">here</a>.</p><h3>Block Producers (P-Reps)</h3><p>The top 100 P-Reps, with ranking based on votes received (1 ICX = 1 vote), earn rewards, and the top 22 are block producers with governance rights. The amount of rewards earned is based on a variable called i_rep.</p><p>I_rep is a number that determines the monthly reward for P-Reps. P-Reps submit what they think i_rep should be, then the network takes an average. The effect i_rep has on rewards is illustrated below assuming an i_rep of 14,000:</p><p><strong>Rewards for receiving votes:</strong> Half of i_rep is used to reward P-Reps based on how many votes the P-Rep has received. Take 14,000 / 2 = 7,000. P-Reps will earn 7,000 ICX per month per 1% of the vote they receive. If a P-Rep has 3% of all votes, they will earn 21,000 ICX per month (7,000 x 3).</p><p><strong>Rewards for being in the top 22:</strong> Half of i_rep is used to reward P-Reps in the top 22. Take 14,000 / 2 = 7,000. Each P-Rep in the top 22 earns an extra 7,000 ICX per month just for being in the top 22.</p><p>Applying what was explained above, a P-Rep in the top 22 with 3% of the vote will earn 28,000 ICX per month (3 x 7,000 + 7,000).</p><p>As for penalties, there are currently no burn/slashing penalties to block producers. If you miss too many blocks, you are taken out of rotation. If you miss so many blocks that your productivity drops below 85%, your node will be disqualified and removed.</p><h3>Voters</h3><p>Most importantly, <strong>you must stake and vote in order to get rewards. </strong>There<strong> </strong>is no reward for only staking.</p><p>Voters receive the same reward no matter which P-Rep they vote for. The reward rate is <strong>lower when more people are voting</strong> and <strong>higher when less people are voting</strong>, with a maximum annual reward rate of 36% and a minimum annual reward rate of 6%. The current reward rate can be found <a href="https://tracker.icon.foundation/governance">here</a>.</p><p>When an ICX holder chooses to unstake, there is a variable unstaking period from 5–20 days based on how many people are currently staking. If <strong>more people are staking the period is shorter</strong>, and if <strong>less people are staking the period is longer</strong>. The current unstaking period can be found <a href="https://icon.community/">here</a> (scroll all the way down to the bottom and look on the right side).</p><p>As for penalties, there are no penalties for voters. If you vote for a P-Rep that ends up getting disqualified, your tokens will be un-voted and you will simply need to vote again to resume receiving rewards.</p><p>We hope this helps your understanding of ICON’s economics. Thanks for reading and please let us know if you would like something added or clarified.</p><p>Your Partner in Blockchain,<br>ICX Station</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f5ed8db0c63" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helloiconworld/icon-economics-overview-8f5ed8db0c63">ICON Economics Overview</a> was originally published in <a href="https://medium.com/helloiconworld">Hello ICON World</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ICX Station Transparency Report]]></title>
            <link>https://medium.com/@icxstation/icx-station-transparency-report-f4da0349254e?source=rss-37cf51ed2615------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4da0349254e</guid>
            <category><![CDATA[icx]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[icon-project]]></category>
            <category><![CDATA[transparency]]></category>
            <dc:creator><![CDATA[ICX_Station]]></dc:creator>
            <pubDate>Wed, 06 May 2020 20:53:08 GMT</pubDate>
            <atom:updated>2020-05-06T20:53:08.310Z</atom:updated>
            <content:encoded><![CDATA[<p>ICX Station is excited to provide a transparency report for the community. Along with this report, we are sharing a publicly viewable <a href="https://docs.google.com/spreadsheets/d/1qSL-hmA9cLNZkDSbFh0hpKUWBAgg_QZDP_yn8JlGYOw/edit?usp=sharing">google sheet</a> that tracks all of our income and expenses with notes explaining each item. The sheet will be updated regularly as we earn and spend ICX. If you have any questions, feel free to reach out to us in our <a href="https://t.me/icxstation">telegram room</a></p><h3>Reporting Period: November 2019 — April 2020</h3><p>We include our total earnings and costs along with the earnings and costs for this specific period. Given this is the first report, we only include total earnings and costs. Everything we don’t spend is used for staking and delegating toward teams contributing to the ICON Project.</p><p><strong>Total Earnings: 1,343,361.33 ICX</strong></p><p><strong>Total Costs: 143,350 ICX</strong></p><p>Costs as of this reporting period include support for ICONbet, support for ICON.vote, reimbursements to team members for pre-decentralization costs, and server costs. More detail can be found in the <a href="https://docs.google.com/spreadsheets/d/1qSL-hmA9cLNZkDSbFh0hpKUWBAgg_QZDP_yn8JlGYOw/edit?usp=sharing">google sheet</a>.</p><h3>Future Outlook</h3><p>This section of the report outlines our future plans with rough estimates of costs.</p><p><strong>Balanced — DeFi Protocol</strong></p><ul><li>Security Audit: 15,000 USD</li></ul><p><strong>Bridge (Unannounced) — Seamless UX for non-crypto users</strong></p><ul><li>Development: 22,000 USD</li><li>Security Audit: 5,000 USD</li></ul><p><strong>ICONbet — DAO gaming platform</strong></p><ul><li>Texas Holdem Grant: 45,000 USD</li></ul><p>We hope this report provides the transparency that voters have been asking for. We look forward to seeing this report evolve over time as we make progress with our various projects.</p><p>Your Partner in Blockchain,</p><p>ICX Station</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4da0349254e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ICON, deconstructed]]></title>
            <link>https://medium.com/helloiconworld/icon-deconstructed-8e70e9888298?source=rss-37cf51ed2615------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e70e9888298</guid>
            <category><![CDATA[ecosystem]]></category>
            <category><![CDATA[icx-station]]></category>
            <dc:creator><![CDATA[ICX_Station]]></dc:creator>
            <pubDate>Fri, 03 Apr 2020 01:41:34 GMT</pubDate>
            <atom:updated>2020-04-03T01:41:34.437Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nwf2f-v5E2DtogChywCVDA.png" /></figure><p>Part IV: Governance</p><p>In the first three parts of our series, 1) we introduced the ICON network at a high level, 2) took a look at the differences between ICON and some of the other leading blockchain technologies, 3) discussed the differences in the blockchain layers and the framework of ICON’s technology and 4) dove into some of the technical details of ICON, including scalability and our smart contract functionality. In Part IV, we’ll spend most of the time focusing on ICON’s unique on-chain governance design.</p><p><em>ICYMI: Here are the first three parts of the ICON, deconstructed series</em></p><p><strong>Part I:</strong> <a href="https://medium.com/helloiconworld/icon-deconstructed-81a944bd835b">What is ICON?</a></p><p><strong>Part II:</strong> <a href="https://medium.com/helloiconworld/icon-deconstructed-9cf743b8aa79">Blockchain Layers and Architecture Behind ICON</a></p><p><strong>Part III:</strong> <a href="https://medium.com/helloiconworld/icon-deconstructed-5eb7f99eeeb1">Scalability and SCORE</a></p><h3>Governance</h3><p>Blockchain governance refers to the mechanisms by which decentralized networks adapt and change over time. At a high level, governance is typically split into two categories: on-chain and off-chain. On-chain governance typically refers to protocol upgrades and changes to parameters that occur autonomously, pending the outcome of an on-chain vote. On-chain governance is unique, mainly because it provides a sense of accountability, transparency, and consistency not reflected in other more traditional governance mechanisms. Off-chain governance requires added social coordination of stakeholders, including miners, developers, and token holders sometimes leading to less democratic outcomes often determined by a smaller subset of stakeholders. There are pros/cons to both, but we won’t go into detail here.</p><p>The ICON design uses an on-chain approach with built-in incentive mechanisms (ICON Incentive Scoring System or “IISS”) to align incentives for stakeholders. Importantly, ICON’s DAO-friendly environment and the project’s philosophy of incentivizing community engagement to drive value set it apart from other projects.</p><p>Blockchains are dynamic and evolving ecosystems consisting of many anonymous market participants. To grow and flourish, clear and defined governance mechanisms are needed to promote collaboration in the ecosystem. And we’re happy to say that <strong>ICON is one of the few blockchains in the entire space to provide such an approach.</strong></p><p>We’ll go into more detail below, but before that, let’s review the elected nodes known as Public Representatives or P-Reps who will participate in governance on our network.</p><h4>What is a Public Representative (P-Rep)?</h4><ul><li>A Public Representative (P-Rep) is a block validator on the ICON Network that participates in consensus and governance</li><li>P-Reps consist of the top 22 Main P-Reps and 78 Sub P-Reps and are elected by ICONists (ICX token holders)</li><li>1 ICX token is worth one vote</li><li>Main P-Reps vote on text and network proposals: needing 15 of 22 and 67% of the total delegations to approve</li></ul><p>P-Reps earn rewards based on delegation and block production and have the following responsibilities within the ICON Ecosystem:</p><ul><li><em>Managing the network:</em> Producing and validating blocks</li><li><em>Governing the network:</em> Monetary policy, network upgrades and governance changes</li><li><em>Protecting the network</em>: Maintaining security standards and preventing malicious attacks</li><li><em>Growing the network</em>: Impacting the growth of the network through on-chain and off-chain activities</li></ul><p>In the current IISS design, Public Representatives receive representative rewards according to the votes they receive. Meaning all 100 Nodes on the network receive rewards. However, the main P-Rep Representatives (the top 22 by delegation percentage) also receive a block validation reward. <em>See image below:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QAOBHHJiZh8P-uhz" /></figure><p>Total rewards are decided by the stake weighted average of the i_rep submitted by the main P-Reps. You can see the current P-Rep submissions <a href="https://tracker.icon.foundation/governance">here</a>.</p><ul><li>i_rep variable is a governance variable that determines the size of the reward fund to be kept in the Public Treasury as determined by IISS</li><li>All P-Reps submit the governance variable (i_rep) based on the number of rewards they deem necessary to fulfill representative responsibilities (i.e. managing, governing, growing and protecting the network)</li><li>Only the submissions of the top 22 P-Reps are factored into the final calculation for i_rep. As noted above, the result is calculated by taking a stake-weighted average of each of the top 22 P-Reps’ submissions</li><li>P-Reps control the ICX issuance rate (or inflation rate of the network) and the size of the reward fund through the use of i_rep</li></ul><p>ICX is a governance and utility token, and as an ICONist, you participate in governance by voting for P-Reps that closely align with you’re respective interests and viewpoints. ICONists receive rewards for their participation.</p><p><em>Note: There is currently a proposal to update IISS which you can view </em><a href="https://forum.icon.community/t/iiss-3-0-proposal/518/63"><em>here</em></a><em>.</em></p><h3>On-chain governance breakdown</h3><p>Currently, P-Reps are the only parties that can vote on governance issues for the ICON network. And more specifically, only the top 22 P-Rep can vote on the outcome. As the network matures, we expect this number to grow.</p><p>Recall, the purpose of on-chain governance is to maintain and upgrade the protocol and adjust parameters. In the ICON design, text proposals, for example, are used for agreeing on protocol/parameter changes before spending time on development. Since these are all saved on-chain, there is an immutable history of decision making among Representatives.</p><p>Network Proposals are more advanced text proposals that do not require additional development and can update the network autonomously pending the outcome of a vote.</p><p>Below is an example of a network proposal submitted by the ICON Foundation to stabilize the network. As you can see it was approved by P-Reps and implemented at a specific block height.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wsSJ9CUx2yAapcer" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hLUW2zHWXx_0SD38" /></figure><p>Text proposals, however, are non-binding and rely on good-faith execution. For example, if a non-binding text proposal is submitted and approved by P-Reps, developers will work on the proposed changes.</p><p>Once the changes are developed and completed, a revision proposal will be submitted for a re-vote. At this point, it would be considered a network proposal and binding pending the outcome of the vote. Therefore, autonomously implemented at a specific block height (similar to the above example).</p><ul><li><em>Note, the Foundation is exploring the feasibility of making text proposals referendum style and available to all ICONists (both voting and proposing) — not just the Top 22 P-Reps.</em></li></ul><p>Now that we’ve covered governance at a high level, we’ll move on to our native token ICX, its token economics, and how it’s used in our ecosystem. Stay tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e70e9888298" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helloiconworld/icon-deconstructed-8e70e9888298">ICON, deconstructed</a> was originally published in <a href="https://medium.com/helloiconworld">Hello ICON World</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ICX Station Partners with ICON Hyperconnect to launch ICX Station Seoul Launchpad]]></title>
            <link>https://medium.com/helloiconworld/icx-station-partners-with-icon-hyperconnect-to-launch-icx-station-seoul-launchpad-a5a453f81069?source=rss-37cf51ed2615------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5a453f81069</guid>
            <category><![CDATA[accelerator]]></category>
            <category><![CDATA[ecosystem]]></category>
            <category><![CDATA[icon-foundation]]></category>
            <dc:creator><![CDATA[ICX_Station]]></dc:creator>
            <pubDate>Tue, 31 Mar 2020 01:38:44 GMT</pubDate>
            <atom:updated>2020-03-31T01:47:01.237Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JPntnLob9m6eezBR1LxxOQ.png" /></figure><p>Hello from ICX Station,</p><p>We are proud to announce that ICX Station is partnering with <a href="https://www.twitter.com/Markusjayvc">ICON Hyperconnect</a>, P-Rep and ICON accelerator, to launch and manage the Seoul Launchpad of ICX Station.</p><p>ICON Hyperconnect will become an official accelerator partner of the ICON Foundation and ICX Station. Launchpads are hubs for ICX Station, each committed to accelerating the growth of the ICON Ecosystem. This partnership marks an integral expansion of ICX Station’s efforts to increase ICON’s presence and growth of ICON in Korea, the birthplace of ICON and one of the most important countries in the blockchain industry.</p><p>ICON Hyperconnect is led by <a href="https://twitter.com/markusjayvc">Markus Jun</a>, former Head of Research at Deblock, ICON’s former venture capital firm and accelerator partner. Along with his background in computer science at Seoul National University, he has extensive experience working closely with the ICON Foundation and ICX Station members and has overseen <a href="https://medium.com/markusjay/reflections-on-the-past-6-months-with-deblock-icon-and-the-future-b647b9105ecc">research, investment and acceleration</a> on several projects that looked to build on ICON.</p><p>He has also heavily promoted and represented ICON and Deblock, including a <a href="https://medium.com/markusjay/talk-at-samsung-electronics-on-icon-deblock-and-blockchain-crypto-in-korea-ffa2d8f5f5af">talk on ICON at Samsung Global Strategy Group</a>, and several <a href="https://www.youtube.com/watch?v=paFYyt1hVWc&amp;t=18s">interviews</a> and <a href="https://theicon.ist/2018/09/03/deblock-accelerating-koreas-crypto-future/">articles</a> with top blockchain thought leaders and publications. For further insight on ICON Hyperconnect’s vision, read their <a href="https://medium.com/markusjay/launch-of-our-p-rep-icon-hyperconnect-bd8076e0c3b">proposal</a> and follow their progress <a href="https://twitter.com/Markusjayvc">here</a>.</p><p>We look forward to meaningful collaborations and further expansion of ICX Station as we add launchpads around the globe. For more information on ICX Station please visit our <a href="http://icxstation.com/">website</a>.</p><p>Your Partner in Blockchain,</p><p>ICX Station</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5a453f81069" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helloiconworld/icx-station-partners-with-icon-hyperconnect-to-launch-icx-station-seoul-launchpad-a5a453f81069">ICX Station Partners with ICON Hyperconnect to launch ICX Station Seoul Launchpad</a> was originally published in <a href="https://medium.com/helloiconworld">Hello ICON World</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ICON Ecosystem Map: Lessons Learned and Missing Pieces]]></title>
            <link>https://medium.com/helloiconworld/icon-ecosystem-map-lessons-learned-and-missing-pieces-8f97b7506a3b?source=rss-37cf51ed2615------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f97b7506a3b</guid>
            <category><![CDATA[icon-foundation]]></category>
            <category><![CDATA[ecosystem]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[ecosystem-map]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[ICX_Station]]></dc:creator>
            <pubDate>Tue, 24 Mar 2020 20:55:42 GMT</pubDate>
            <atom:updated>2020-03-24T20:55:42.808Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*V69F8tZXVUH6KK2V5eWIPg.png" /></figure><p>It has been 5 months since the ICON network went through decentralization. The ICON ecosystem gathered 100+ validators across 30+ countries. As validators join the ICON ecosystem, many have asked how they can add value to the ecosystem as they try to align themselves with DPoC (Delegated Proof of Contribution), so we created an ICON Ecosystem Map hoping that it can be a guide for P-reps interested in adding value to the ICON ecosystem.</p><p>As mentioned in the past few P-rep governance calls, the current focus of the ICON ecosystem is to bring in more ICONists (# of users) and create uses cases (# of transactions). In order to drive these KPIs, we believe the best way to add value to the ecosystem is by 1) <strong>creating a developer friendly environment</strong> and 2) <strong>creating meaningful blockchain use cases on the ICON network</strong>. In the ICON Ecosystem Map, we compared the ICON ecosystem to the Ethereum ecosystem, the most robust ecosystem within the blockchain world, and tried to identify what is already built and what is currently missing.</p><p>Working on this ecosystem map taught us the following three lessons: 1) The ICON ecosystem is getting more mature and more robust everyday, 2) The ICON ecosystem has some unique use cases, however 3) we still have many things that need to be built to make the ICON ecosystem more attractive.</p><p>1) As seen from the ICON Ecosystem Map, many infrastructure projects are being built by communities (<a href="https://iconation.github.io/iconswap/">ICONSwap</a>, <a href="https://medium.com/metanyx/iconpay-for-woocommerce-7788241d8037">ICONPay</a>, <a href="https://github.com/insight-infrastructure/terraform-aws-icon-prep-basic">Insight</a>, <a href="https://balanced.network/">Balanced</a>, <a href="https://www.myiconwallet.com/">MyICONWallet</a>) and many are also being built by ICON’s partners as well (<a href="https://medium.com/helloiconworld/morpheus-labs-and-icon-collaborate-to-grow-the-developer-community-ae9a889b2b1b">Morpheus Labs</a>, <a href="https://medium.com/helloiconworld/icon-plans-integration-with-leading-oracle-solution-chainlink-c4b746384096">Chainlink</a>, <a href="https://twitter.com/IcxStation/status/1228500221660811264">Formatic</a>). Many are currently in the early stage of development, but we hope to see many of them live soon to make the ecosystem more developer friendly. Additionally, we start to see some good use cases on the Ethereum ecosystem being built on the ICON network by communities (<a href="https://twitter.com/FutureIcx">FutureICX</a>, <a href="https://medium.com/posbakerz/introducing-the-icon-icx-risk-free-lottery-44d6ffa5c37a">Risk free lottery</a>, <a href="https://www.devblockchain.tech/">Devblockchain.tech</a>) as well.</p><p>2) Despite being in the early stage of development, the ICON ecosystem starts to show impressive accomplishments. ICONbet is a unique DAO based iGaming platform, which has <a href="https://www.dapp.com/article/dapp-com-list-icon">ranked №1 in terms of 30 days transactions among hundreds of blockchain-based iGaming platforms</a>. It has shown valuable and unique community behavior in which community members are running for a P-rep to support the platform and community developers are building additional games for the platform. We may be seeing a real DAO happening, which has <a href="https://www.coindesk.com/understanding-dao-hack-journalists">previously failed in the Ethereum ecosystem</a>. We have also seen unique enterprise focused use cases such as <a href="https://www.broof.io/">Broof</a> and <a href="https://www.visitme.app/">VisitMe</a> as well as the unique Kpop (culture) focused use cases such as <a href="https://stayge.net/">Stayge</a> and <a href="https://somesing.io/index">Somesing</a>.</p><p>3) That being said, we are still in the early stage of development of the ecosystem, and we need many more things to be built. In terms of infrastructure projects, we realized that several of the missing projects, such as a chain analysis project, could be done through partnerships as seen in previous examples (<a href="https://medium.com/helloiconworld/icon-plans-integration-with-leading-oracle-solution-chainlink-c4b746384096">Chainlink</a>, <a href="https://medium.com/helloiconworld/morpheus-labs-and-icon-collaborate-to-grow-the-developer-community-ae9a889b2b1b">Morpheus Labs</a>, etc.). However, we do need more robust developer tools, which can’t be done through partnerships, and are hoping that<strong> our community developers can create an equivalent of </strong><a href="https://www.trufflesuite.com/"><strong>Truffle</strong></a><strong> for the ICON ecosystem.</strong></p><p>Use cases tend to be trickier as there are not many use cases that support multiple chains at the moment, so it is best for our ecosystem to come up with unique blockchain use cases ourselves. We have noticed that ICON doesn’t have a use case with NFT although <a href="https://github.com/icon-project/IIPs/blob/master/IIPS/iip-3.md">standard documentation</a> is ready to be leveraged. <strong>We believe NFTs have many blockchain specific use cases such as </strong><a href="https://godsunchained.com/"><strong>card games</strong></a><strong>, </strong><a href="https://www.mycryptoheroes.net/"><strong>RPG games</strong></a><strong>, </strong><a href="https://opensea.io/"><strong>marketplaces</strong></a><strong>, etc, and hope that our community developers can come up with interesting NFT use cases. Finally, as we see stable coins introduced to the ICON ecosystem, a lending platform would be a helpful addition to the ICON ecosystem.</strong></p><p>This ICON Ecosystem Map is just version 1 and we plan to update the ecosystem map as our ecosystem matures. Projects that are currently being developed have their logos shown semi-transparently. Please reach out to Daeki Lee (@Dkong5) on Telegram or leave comments here if you have inquiries about the ICON Ecosystem Map.</p><p>Your Partner in Blockchain,</p><p>ICX Station</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f97b7506a3b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helloiconworld/icon-ecosystem-map-lessons-learned-and-missing-pieces-8f97b7506a3b">ICON Ecosystem Map: Lessons Learned and Missing Pieces</a> was originally published in <a href="https://medium.com/helloiconworld">Hello ICON World</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ICON, deconstructed]]></title>
            <link>https://medium.com/helloiconworld/icon-deconstructed-5eb7f99eeeb1?source=rss-37cf51ed2615------2</link>
            <guid isPermaLink="false">https://medium.com/p/5eb7f99eeeb1</guid>
            <category><![CDATA[ecosystem]]></category>
            <category><![CDATA[icx-station]]></category>
            <dc:creator><![CDATA[ICX_Station]]></dc:creator>
            <pubDate>Sat, 14 Mar 2020 00:10:56 GMT</pubDate>
            <atom:updated>2020-03-14T00:10:56.683Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o_ooaHe-hvc5EqlHVQ5i2Q.png" /></figure><p>Part III: Scalability and SCORE</p><p>In the last two parts of our series, 1) we introduced the ICON network at a high level, 2) took a look at the differences between ICON and some of the other leading blockchain technologies, and 3) discussed the differences in the blockchain layers and the framework of ICON’s technology. In Part III, we’ll provide an overview of ICON’s scalability solutions and smart contract functionality.</p><p><strong><em>Reminder:</em></strong><em> the goal for this series is two-fold. First, we want to write this series in a way that’s easy to understand for beginners exploring our project for the first time. But, additionally, we also want to provide enough depth that it can be enjoyed by more advanced blockchain enthusiasts. We’ll be releasing each part in smaller segments, so please let us know if you have feedback as we can make adjustments to the releases as we go. We hope you enjoy!</em></p><p>Let’s unpack these concepts now.</p><h3>DPoC Throughput</h3><p>Blockchain performance is often measured by transaction throughout. This measurement is typically expressed as a number of <strong>transactions</strong> per second the system can handle (TPS). As we all know, one of the biggest pushbacks on blockchain technology is its limited throughput capacity compared to legacy platforms and the perceived lack of scalability to handle mass adoption.</p><p>One of the greatest weaknesses of Bitcoin and Ethereum is an innately low transaction speed, which is why these protocols require second-layer solutions like the Lightning Network to increase their throughput. That said, we believe DPoC provides an effective solution to one of blockchain’s most salient issues — scalability.</p><p>Ethereum supports a throughput velocity of 20 transactions per second (TPS), which is significantly smaller than payment systems like PayPal (~190 TPS) and Visa (~1700 TPS). ICON, on the other hand, offers a more competitive transaction speed of ~500 TPS. Before taking a look at what enables ICON to do that, let’s explore 3 common Ethereum approaches to improving scalability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*XIaYJcuhq92aJ20v" /></figure><h3>Raiden Network: State Channel / Off-chain</h3><p>The Raiden Network is <em>“an off-chain transfer network … that aims to scale Ethereum by using state channel technology.”</em> This means that an off-chain payment channel is opened between parties, allowing to group and process multiple micro-transactions and saving time and transaction fees. The channels are governed by multi-sig smart contracts and require updating the blockchain on creation/deletion to lock/unlock the asset.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/0*43K-AD36Kf7Oz1Ck" /></figure><h3>Plasma: Side-chain</h3><p>Plasma is a framework that allows the creation of “children” blockchains that rely on the main Ethereum chain for trust and arbitration. Plasma enables users to move their assets onto a “child” blockchain configured specifically to match the demand of their use case for more efficient processing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BcOCamoEEc8ijRn-" /></figure><h3>Sharding</h3><p>Sharding refers to splitting the state into “shards” (hence the name). Currently, each node in Ethereum processes stores the entire state of the blockchain. Scaling via sharding allows dividing the validation process among many nodes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CgxrEVdFrI8Ln7xh" /></figure><h3>ICON blockchain architecture</h3><p>The ICON blockchain architecture derives from these predecessor scalability solutions. ICON leverages multi-channel technology (i.e. sharding into many channels) to provide interoperability functions, which we will explore later. The state of SCOREs, smart contracts in the ICON ecosystem, is likewise sharded, so that SCORE states are independent of one another. The 500 TPS speed provided by DPoC is scaled out to each channel, improving overall performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9POP_pWUN55NiIjl" /></figure><h3>Smart Contract on Reliable Environment (SCORE)</h3><p>Since we touched on SCOREs several times already, let’s explore these enhanced smart contracts in greater detail. SCOREs offer the following advantages over smart contracts running on protocols like Ethereum:</p><ul><li>SCORE (Smart Contract on Reliable Environment) is a smart contract running on the ICON network. Recall, a smart contract is a collection of codes (functions) and data (states) that resides at a specific address on the blockchain. SCORE can be regarded as a state transition machine that a user could implement a service logic such as token transfers. The state transition is triggered by sending transactions to an address that the SCORE resides. Any service logic that can be modeled by a state transition machine can be implemented in the SCORE code.</li><li>SCOREs have a versioning capability, which means that updating them is extremely easy and fast. This is conducive to iterative development, which is the process of designing, developing, and testing code in repeated cycles.</li><li>Within a node, the ledger and smart contracts exist in separate domains, which increases work efficiency.</li></ul><p>The last of the advantages ties into our discussion of how Cosmos separates the application and protocol layers. Since applications built on ICON are based on smart contracts, separating blockchain processes (e.g. adding blocks) from smart contract processes (e.g. versioning) makes sense on a node level. Let’s now look at how this separation affects developers.</p><p><strong>Building applications on ICON</strong></p><p>Separating the protocol and application layers is also useful for developers looking to build on ICON. Before delving deeper into developing applications, we need to learn about remote procedure calls — the technology that enables developers to “talk” to nodes.</p><p><strong>Remote procedure call (RPC)</strong></p><p>Communicating with an ICON node requires making a remote procedure call (RPC) to the node. An RPC is nothing more than a request asking a remote server to do something for you that does not require a response from the server; in this analogy, the server is an ICON citizen node. The type of RPC protocol used in ICON nodes is known as JSON-RPC.</p><p><strong>ICON SDK</strong></p><p>The ICON SDK enables building DApps on ICON by providing a framework for developers. Beyond allowing developers to define the state of their applications, the SDK comes equipped with functionalities to create wallets, transfer ICX, and deploy IRC2 tokens built on ICON.</p><p>The ICON SDK/RPC structure allows DApps to technically be programmed in any language. However, the ICON SDK currently supports four programming languages: Java, Python, JavaScript, and Swift.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/774/0*vgtAg998lQOvhmYD" /></figure><p>The diagram above depicts the separation between the protocol and application layers in ICON. Applications developed with an ICON SDK use the JSON-RPC protocol to make requests to Citizen nodes. Citizen nodes propagate requests between each other and the validator nodes using the gossip protocol. Validators receive the request and reach consensus on a block that encompasses the request.</p><p>The way ICON separates the protocol layer (LFT) from the application layer (SDK and RPC) provides developers with a lot of flexibility to build DApps. It’s important to note that while ICON DApps can be programmed in any of the four officially supported languages, SCOREs have to be written in Python.</p><p>However, smart contract development with Python is still a better developer experience than building on Ethereum, which requires programmers to learn Solidity. In contrast, Python is one of the most simplistic of the most popular programming languages and enables easy idea prototyping. It is also the preferred language for domains like machine learning and data analytics, both of which have strong synergies with the future of blockchain technology.</p><p>At this point, we’ve covered decentralization, as well as the architecture of the ICON blockchain and how it differs from other chains. We still have to explore blockchain interoperability, but before that, we’ll discuss governance on the ICON network in next week’s ICON, deconstructed Part IV.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5eb7f99eeeb1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helloiconworld/icon-deconstructed-5eb7f99eeeb1">ICON, deconstructed</a> was originally published in <a href="https://medium.com/helloiconworld">Hello ICON World</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ICON, deconstructed]]></title>
            <link>https://medium.com/helloiconworld/icon-deconstructed-9cf743b8aa79?source=rss-37cf51ed2615------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cf743b8aa79</guid>
            <category><![CDATA[icx-station]]></category>
            <category><![CDATA[ecosys]]></category>
            <dc:creator><![CDATA[ICX_Station]]></dc:creator>
            <pubDate>Wed, 26 Feb 2020 20:22:42 GMT</pubDate>
            <atom:updated>2020-03-06T16:24:50.456Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SVkld3Uc72Ak_kBZDCnJvg.png" /></figure><p>Part II: Blockchain Layers and the Architecture Behind ICON</p><p><em>This is the second part of a 30+ page series designed to provide an overview of ICON’s technology. Remember, the goal for this series is two-fold. First, we want to write this series in a way that’s easy to understand for beginners exploring our project for the first time. But, additionally, we also want to provide enough depth that it can be enjoyed by more advanced blockchain enthusiasts. Part II has been updated to reflect LFT 2.0, ICON’s next-generation consensus mechanism.</em></p><h3>Introduction</h3><p>In <a href="https://medium.com/helloiconworld/icon-deconstructed-81a944bd835b">Part I of ICON, deconstructed</a> we outlined some of the basics of ICON Network. This included an introduction to nodes and a brief look into the blockchain layers. In Part II of this series, we’re going to take a deeper dive into those layers and provide an overview of ICON’s architecture. Also, stay tuned for the next part of our series on DPoC throughput, scalability and SCORE.</p><h3>Blockchain Layers</h3><p>In Part I of ICON, deconstructed we broke down the blockchain protocol layers into smaller components. To recap: we said there’s no conventional standard for this decomposition, but one way to think about the protocol layer is by dividing it into <strong>consensus, propagation, and Sybil resistance layers</strong>. Here’s a quick recap on each layer:</p><ul><li><strong>Sybil resistance layer</strong>: protects from a Sybil attack — an attempt by a single malicious entity to prevent finality on the network by gaining an overwhelmingly large influence. Finality is the guarantee that all well-formed blocks are irreversible once added to the ledger. A lack of finality can lead to transaction reversals and double-spending.</li><li><strong>Propagation layer</strong>: defines how the state (blocks and transactions) are communicated between nodes in the network.</li><li><strong>Consensus layer</strong>: ensures that nodes can agree on the state of the network, which means that the local view of the ledger for each node is the same. This layer also defines the rules for adding new blocks to the ledger. To compare one blockchain project with another, it helps to decompose its blockchain into separate layers. The most basic distinction can be drawn between the protocol and application layers of a blockchain.</li></ul><p>We also noted that layers are best understood by looking at the Internet, where the protocol layer consists of protocols like HTTP and TCP/IP, while the application layer represents user-facing platforms like Google, Facebook, and Netflix. The application layer can also be viewed from a more general perspective (e.g. search engines, social media, video streaming).</p><p>Lastly, we noted that each of these layers has a specific function, but there’s a great amount of interplay between them.</p><p>In the next section, we’re going to use the framework above to compare layers across several different blockchains. We’ll start with Bitcoin and move our way through Ethereum, Cosmos and lastly through ICON. Let’s dive in.</p><h3>Bitcoin protocol layers</h3><p><strong>1. Sybil resistance layer</strong></p><p><strong>Proof-of-Work (PoW)</strong> is a protocol that requires nodes to compete for each block by performing computational work to solve a complex puzzle. The difficulty of producing a block (mining) is stored in the block header, which means that any node can compare the difficulty between two blocks. Naturally, it takes a lot of computational work (and thus resources) to produce a block with a high difficulty.</p><p>By extension, producing the block with the highest difficulty would require an enormous amount of computational work. The Bitcoin network is massive and constantly growing, which makes it highly improbable that a malicious entity could gain control of enough computational power to execute an attack due to the sheer cost of doing so.</p><p><strong>2. Propagation layer</strong></p><p>Bitcoin uses the <strong>gossip protocol</strong>, a peer-to-peer protocol to ensure that every mining node broadcasts a mined block to other nodes. To see how it works, consider the following example: a node, N1, mines a block and randomly chooses a peer, N2, to share the block information with. Then, N1 and N2 each randomly pick another peer (N3 and N4) to pass along the same information. This continues until all nodes in the network receive the same information.</p><p>Note that all types of nodes can participate in the communication process. The biggest advantage of light clients — the ability to propagate the true ledger across a greater distance at a lower cost than full nodes — comes directly from the gossip protocol.</p><p><strong>3. Consensus layer</strong></p><p>Fundamentally, <strong>Nakamoto Consensus</strong> is the agreement that Bitcoin nodes will choose the chain of blocks with the highest total difficulty and add it to their local view of the ledger. Nakamoto Consensus inherently relies on the <strong>Proof-of-Work (PoW)</strong> protocol, and nodes can check which block has the highest difficulty. Nakamoto Consensus is the origin of the “longest chain” rule — the longest chain is recognized as the one with the highest total block difficulty.</p><p>A malicious party could hypothetically broadcast blocks from its local view, but there’s no chance they would be added to other nodes’ local views since their difficulty would be much lower than that of blocks produced by large mining pools. Note that Nakamoto Consensus is a static rule, and does not require any communication between nodes.</p><h3>Ethereum protocol layers</h3><p><strong>1. Sybil resistance layer</strong></p><p>Ethereum also currently uses the PoW protocol to prevent Sybil attacks, although the network is in the process of transitioning to Proof-of-Stake (PoS), another Sybil resistant scheme.</p><p><strong>2. Propagation layer</strong></p><p>Ethereum uses the same gossip protocol as Bitcoin to communicate block and transaction information between nodes.</p><p><strong>3. Consensus layer</strong></p><p>Ethereum uses another PoW-based consensus algorithm called Ethash. This protocol functions similarly to Nakamoto Consensus and also makes use of the longest chain rule.</p><p>Ethash modifies Nakamoto Consensus by making computational performance a function of how fast a mining machine can move data across different memory locations (as opposed to a machine’s computation speed). The goal is to prevent large mining pools from obtaining significant influence over the network.</p><h3>Cosmos protocol layers</h3><p><strong>1. Sybil resistance layer</strong></p><p>Cosmos uses Delegated Proof-of-Stake (DPoS) as its Sybil resistance scheme. On a basic level, DPoS replaces external resources (mining machines and energy) with an internal resource (the blockchain’s native cryptocurrency). Nodes have to stake (lock-up) cryptocurrency or receive delegation (votes) for a chance to become block producers and validators. Validators vote on a block, and voting power is determined by the size of the stake.</p><p>Thus, acquiring a disproportionately large voting weight and producing many blocks for a Sybil attack is very expensive. The cost of purchasing additional tokens will likely increase, as the market price increases with each purchase. Even if a malicious entity acquires a significant amount of tokens, there’s little incentive for it to undermine a network that it is heavily invested in.</p><p><strong>2. Propagation layer</strong></p><p>As mentioned before, validator nodes on the Cosmos network vote to approve blocks. That requires all the nodes to communicate block information to each other, to make sure everyone in the network has the same local view. Cosmos uses the same gossip protocol as Ethereum and Bitcoin to accomplish that.</p><p><strong>3. Consensus layer</strong></p><p>Cosmos uses the <strong>Tendermint</strong> consensus algorithm to ensure that nodes agree on every block in a round-based system. Each round consists of 4 steps: <strong>propose</strong>, <strong>prevote</strong>, <strong>precommit</strong>, and <strong>commit</strong>. The last step is contingent on the success of the first three.</p><p>Once a block is <strong>proposed</strong>, ⅔ of the voting power (based on stake size) needs to do <strong>prevote</strong> the block for it to proceed to the <strong>precommit</strong> step. Then, another ⅔ of the voting power is needed to move the block to the next<strong> </strong>step, where it is <strong>committed</strong> to the blockchain. Both the prevote and precommit steps require each validator to broadcast their vote to the other nodes. It may take more than a single round for a block to get committed.</p><h3>Comparing application layers</h3><p>Now that we’ve acquired some understanding of protocol layers in different blockchains, let’s look at their respective application layers.</p><p><strong>Bitcoin application layer</strong></p><p>Bitcoin’s primary application is P2P (peer-to-peer) transactions, which are enabled by <strong>Scrypt</strong>, a simple programming language. Bitcoin’s application layer is inseparable from its protocol layer — Bitcoin transactions are impossible without Nakamoto consensus or PoW.</p><p><strong>Ethereum application layer</strong></p><p>The core features of the Ethereum application layer are the <strong>EVM (Ethereum Virtual Machine)</strong> and <strong>Solidity</strong>, a specialized language for smart contracts. The EVM runs on every node in the network and compiles high-level Solidity contract code into machine code. The EVM can be thought of as a decentralized computer containing millions of executable programs, each with its own permanent data storage.</p><p>Smart contracts allow for <strong>Decentralized Applications (DApps)</strong> to exist on the Ethereum blockchain. Another element of the Ethereum application layer are ERC20 cryptocurrencies (like DAI and USD Coin) which can have issuance and economic structures different from Ethereum’s. However, just like with Bitcoin, you can’t separate Ethereum DApps or ERC20 cryptocurrencies from the underlying Ethash consensus.</p><p><strong>Cosmos application layer</strong></p><p>Cosmos takes a different approach — it decouples the application layer from the protocol layer. One of the key value propositions of Cosmos is blockchain interoperability, which is why this separation makes sense — a network of blockchains needs to accommodate independent blockchains with different functionalities, requirements, and governance structures. Since interoperability is also one of the core principles of ICON, the separation between the protocol and application layers is likewise present in the network.</p><p>The need for interoperability arises from the fact that there is no single all-encompassing blockchain protocol for all blockchain applications. To see what this means, let’s consider building a DApp using the blockchain protocols we’ve discussed above.</p><p>Bitcoin’s Scrypt is great for enabling simple P2P transactions, but any application that requires a higher degree of logical sophistication would be tough to build. Bitcoin, just like Ethereum, has a slow transaction speed, which means that an application requiring a high volume of transactions would not function well.</p><p>Ethereum has been shown to be somewhat vulnerable to errors and security attacks because of the external nature of the EVM. For an application requiring a high degree of security, that would be unacceptable. Furthermore, updating deployed smart contracts in Ethereum is difficult, which makes iterative development harder to accommodate.</p><p>However, Cosmos lacks network-wide incentives and governance mechanisms that stimulate the growth and adoption in the broader ecosystem. Recently, one of the validators on the Cosmos Hub <a href="https://figment.network/wp-content/uploads/2019/12/Figment-Networks-Cosmos-GWG-proposal.pdf">proposed changes</a> to address these issues.</p><p>Governance is a core principle of ICON, and the network has multiple incentive mechanisms to stimulate development and accelerate growth. Nonetheless, ICON has many shortcomings of its own that we’ll discuss later. Before that, let’s take a closer look at the blockchain layers in ICON.</p><h3>The blockchain architecture behind ICON</h3><p>Public and private blockchains on the ICON network use a proprietary consensus algorithm called <strong>Loop Fault Tolerance (LFT)</strong>. LFT was developed for the loopchain engine, which powers both the ICON public chain and ICONLOOP private chains. The fact that LFT has been used to provide high-performance solutions to enterprise clients in Korea speaks volumes about the algorithm’s efficiency, scalability, and reliability.</p><p>LFT is Byzantine Fault-Tolerant and uses Delegated-Proof-of-Contribution (DPoC) for Sybil resistance. Let’s unpack what these terms mean.</p><p><strong>Byzantine fault tolerance (BFT)</strong></p><p>In distributed computing systems, Byzantine fault tolerance (BFT) refers to the network’s ability to tolerate machines (validator nodes) failing in unpredictable ways. Two conventional assumptions that follow from this concept are that (1) the failure is due to nodes being malicious and (2) no more than ⅔ of the nodes are malicious at any given time.</p><p>You remember from our discussion of the Cosmos consensus layer that Tendermint requires ⅔ of the total voting power on the network to commit a block. Tendermint and LFT are both BFT consensus algorithms, which is why the ⅔ majority is important in both protocols.</p><p><strong>Delegated-Proof-of-Contribution (DPoC)</strong></p><p>Delegated-Proof-of-Contribution, a modified version of Proof-of-Stake, offers two key advantages over PoS:</p><ol><li>It also relies on staking for Sybil resistance, but token holders stake to elect delegates who validate blocks on their behalf, instead of voting on the validity of the blocks themselves.</li><li>It provides unique incentives for early adopters and token holders who actively engage with the community and contribute to the growth of the ICON ecosystem.</li></ol><p>We’ll return to DPoC later when we delve into ICON’s governance structure. For now, let’s go back to LFT consensus and see how it works in detail.</p><h3>How LFT consensus works</h3><p>As a refresher, recall that the primary function of a consensus algorithm is to ensure state invariance across nodes in a network after a transaction is completed. LFT defines how nodes on the ICON network agree on the next block to be added to the blockchain. Let’s refresh a few topics first.</p><p><strong>P-Reps</strong></p><p>We learned earlier that the full nodes that produce blocks and verify transactions are called P-Reps (Public Representatives) on the ICON Network. Initially, we have 100 P-Reps, and each of them receives a reward proportional to the number of votes they receive. 1 vote is equal to 1 ICX, the native cryptocurrency of ICON.</p><p>The top 22 P-Reps (Main P-Reps) serve as validators, receiving block rewards as an incentive to continue securing the network. The other P-Reps (Sub P-Reps) function as non-validator full nodes, storing a copy of the ledger and stepping up to replace the Main P-Rep if necessary. LFT aggregates votes from the Main P-Reps to determine the next correct block.</p><p><strong>Sybil Resistance</strong></p><p>DPoC is an extension of PoS, and it utilizes a similar Sybil resistance logic to its predecessor. For a malicious entity to gain sufficient control of the network to cause harm, it would need to (1) obtain a very large amount of ICX, (2) get enough votes to be elected as a P-Rep, and (3) stake their ICX.</p><p>Attacking the ICON network would almost invariably crash the value of ICX, thus destroying the entity’s initial investment. So it is assumed that no rational actor would be willing to face such a loss, thus the probability of a Sybil attack is very low.</p><p><strong>Consensus LFT 1.0</strong></p><p>There are two types of nodes in most BFT consensus algorithms: a “leader” that creates and broadcasts a block, and a “validator” that votes on the block and verifies other nodes’ votes. Like Tendermint, LFT consensus runs on a round-based system.</p><p><em>Before we go into more detail on LFT consensus, let’s talk about the concept </em><strong><em>height</em></strong><em> — a non-unique block identifier.</em></p><p>If you visualize the blockchain as a vertical stack with blocks layered on top of each other, each block will be at a different distance, or height, from the genesis block at the foundation (the genesis block has a height of zero).</p><p>Height is a non-unique identifier — while each block will have a specific and invariant height, a certain block height does not always identify a single block. Two blocks competing for the same spot in the stack (a scenario that could lead to a blockchain fork) would have the same height until one of the blocks is rejected via a consensus algorithm.</p><p>LFT resembles Tendermint with its two-vote broadcast steps (prevote and precommit) but reduces the block data verification to a single vote broadcast. Each round consists of 3 steps: <strong>propose</strong>, <strong>vote</strong>, and <strong>commit</strong>.</p><ol><li>Before the consensus process begins, the validator nodes communicate transactions to the leader node.</li><li>The leader node creates a block from collected transactions and embeds its digital signature in it. In the <strong>propose </strong>step, the leader broadcasts the created block to all validators.</li><li>In the <strong>vote</strong> step, validators verify the block by looking at three things: (1) the leader’s digital signature is correct, (2) the height of the block and the hash of the previous block are correct, and (3) the transaction data itself is valid. If all three criteria are met, validators propagate their consensus vote data to all other nodes in the network.</li><li>A new leader node replaces the previous leader.</li><li>Once the new leader receives vote data from more than ⅔ of the voting weight (remember, total voting power is not distributed evenly across validators), it <strong>commits</strong> the block by adding it to its local view of the blockchain and creating a new block with the consensus vote data embedded in it. Validators confirm the block by updating their local view and incrementing block height when they vote to verify the new block.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3aT2nGseTcXIgHb3" /></figure><p>Since the previous block is committed at the same time as the new block is proposed, LFT can be seen as having 2.5 steps instead of 3. Combining the propose and commit steps eliminates the need to transmit data after counting the consensus votes to allow validators to verify that a ⅔ majority was attained.</p><p>It might take more than a single round to add a block to the blockchain for a given height. This scenario could result from:</p><ul><li>The leader node misses the window to propose a block, or a significant number of validators are offline and the ⅔ consensus is not reached. ICON has a built-in penalty system that punishes such negligent behavior by stripping validators off their block production rights for some time or burning a fraction of their delegated ICX.</li><li>The block broadcast by the leader node is invalid and more than ⅓ of the validators propagate a null vote on the block.</li></ul><p><strong>LFT 2.0</strong></p><p>Our next-generation consensus mechanism, LFT 2.0, also resembles Tendermint with its two-vote broadcast steps (prevote and precommit), and still reduces the block data verification to a single vote broadcast. Each round consists of 2 steps: <strong>propose</strong> and <strong>vote</strong>. LFT 2.0 uses something called a pipelined consensus where each block is committed when a connected block vote is completed.</p><p>Below is an infographic describing the process by which one block is committed in LFT 2.0. It’s a bit technical but we’ll try to break it down into simpler terms.</p><ul><li>B: Block ID</li><li>V(N, B’, B): Vote(Node Number, Candidate Block ID, Target Block ID)</li><li>C(N, B’, B): Candidate(Node Number, Previous Candidate Block ID, Candidate Block ID)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GqTxfH6soBJ2K2C6" /></figure><p>The stages can be differentiated by Round or the block height. Here is a summary of the events that take place for each stage:</p><p><strong>Propose</strong></p><ul><li>As a new Round gets started, theProposeTimer is reset and starts running. The Leader gets replaced by the next node in line that will create a new block.</li><li>The new Leader generates a block of new height which contains the information of transactions and the votes of Candidate Block.</li><li>The Leader sends the new block and its digital signature to other Validators.</li></ul><p><strong>Vote</strong></p><ul><li>Validators receive the new block generated by the Leader.</li><li>Validators check whether the delivered block is generated by a valid Leader.</li><li>Validators check whether the block height and the hash of the previous block written in the delivered block are valid.</li><li>Validators check whether the delivered block is connected to Candidate Block.</li><li>Validators make a vote message according to the results of the tests above and send it to Node Set.</li></ul><p><strong>Candidate</strong></p><ul><li>A Node Set gets vote messages from Node Set except itself.</li><li>When Node Set gets more than enough votes to meet a quorum but consensus is not reached, VoteTimer starts running and it follows VoteTimer.</li><li>Candidate Block information is not included in the next block and only each node knows it.</li></ul><p><strong>Commit</strong></p><ul><li>When Node Set gets the same V(N, B’, B) votes enough to form a quorum, it Commits the block B’.</li><li>It enters the Propose stage in the next Round</li></ul><p>That’s a brief overview of LFT 2.0. In the coming weeks, we’ll have even more information about LFT 2.0 and its advantages.</p><p><strong>ICON propagation layer</strong></p><p>LFT consensus relies on round-based block and vote broadcasts between validators. ICON uses the gossip protocol to get all the nodes up to speed. It’s important to note that light clients and non-validator full nodes can also participate in the propagation process.</p><p>We’ve seen how LFT differs from Tendermint because it has a reduced number of steps required to achieve consensus. Let’s look at some of the other differences between the two protocols.</p><p><strong>Finality</strong></p><p>While LFT and Tendermint vary in some regards, both of them are BFT consensus algorithms, and thus they differ significantly from PoW-based Nakamoto Consensus and Ethash. One key difference is each class of protocols interprets the meaning of “finality.” Remember that finality is the guarantee that blocks are irreversible once added to the blockchain, and a lack of finality can lead to transaction reversals and double-spending.</p><p>One issue with PoW-based consensus algorithms is that the gossip protocol is not instantaneous and thus there exists the possibility that disparate geographic regions of the network may receive competing blocks of the same height that claim to have solved the current puzzle. This would cause a temporary fork as different regions choose to build upon different chains of blocks; eventually, one branch will grow longer than the other.</p><p>Thus, blocks within PoW-based chains have a chance of being reverted, and the Bitcoin whitepaper suggests waiting for 6 blocks to ensure that a transaction will not be discarded. On the other hand, in BFT-based chains, blocks are guaranteed to be irreversible as soon as validators successfully vote to commit the block. ICON and Cosmos are thus said to be “deterministic” blockchains, while Bitcoin and Ethereum are called “probabilistic.”</p><p>Now that we have a good understanding of how consensus works on the ICON network and how it differs from other protocols, let’s take a look at the application layer.</p><h3>ICON application layer</h3><p>The ICON application layer is heavily tied in with one of the network’s core principles — governance. Earlier, we defined governance as the structure that determines how participants in a network can interact with each other. That is a rather broad definition, so let’s examine some concrete initiatives that ICON is building towards.</p><p>As one might infer from its name, the Delegated-Proof-of-Contribution protocol emphasizes distributing rewards based on relative contribution. The measurement of contributions and distribution of rewards on the ICON network is regulated by a system called <strong>IISS (The ICON Incentives Scoring System)</strong>.</p><p>IISS is much more than a measurement mechanism; it serves as an ICON-funded incubator that provides “grants” to entities looking to build on or expand the ICON network. These grants are funded through a decentralized funding design called the contribution proposal system.</p><p>All of these activities require a high transaction throughput and a solid technical framework behind the scenes. So in the next part of our series, we’ll take a look at some of these technical advantages that the ICON network confers.</p><p>Your Partner in Blockchain,</p><p>ICX Station</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cf743b8aa79" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helloiconworld/icon-deconstructed-9cf743b8aa79">ICON, deconstructed</a> was originally published in <a href="https://medium.com/helloiconworld">Hello ICON World</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ICON, deconstructed]]></title>
            <link>https://medium.com/helloiconworld/icon-deconstructed-81a944bd835b?source=rss-37cf51ed2615------2</link>
            <guid isPermaLink="false">https://medium.com/p/81a944bd835b</guid>
            <category><![CDATA[icx-station]]></category>
            <category><![CDATA[ecosyste]]></category>
            <dc:creator><![CDATA[ICX_Station]]></dc:creator>
            <pubDate>Wed, 19 Feb 2020 21:28:05 GMT</pubDate>
            <atom:updated>2020-02-19T21:28:05.292Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jTNBSM30Vce2WxbI0sTNTw.png" /></figure><p>Part I: What is ICON?</p><p><em>This is the first part of a 30+ page series designed to provide an overview of ICON’s technology. The goal for this series is two-fold. First, we want to write this series in a way that’s easy to understand for beginners exploring our project for the first time. But, additionally, we also want to provide enough depth that it can be enjoyed by more advanced blockchain enthusiasts. We’ll be releasing each part in smaller segments, so please let us know if you have feedback as we can make adjustments to the releases as we go. We hope you enjoy!</em></p><h3>Introduction</h3><p>The crypto industry, young as it may be, has already gone through several generations of evolution. The first generation was ushered in by the Bitcoin launch in 2009, followed by the rise of simple altcoins. At that point, the main focus of crypto seemed to be on creating a frictionless network of P2P payments.</p><p>The next great advance in the industry was Ethereum, arriving in 2015. Ethereum introduced the smart contract — a tool that automates transactions based on validated triggers. Smart contracts allow for far greater complexity to exist on the blockchain.</p><p>The current generation of blockchains is comprised of a diverse set of projects that offer performance enhancements over the previous generation. <em>Scalability</em> and <em>interoperability</em> have been some of the defining buzzwords of this new wave, and a significant reason why the ICON<strong> </strong>project garnered so much attention when it launched in late 2017.</p><p>ICON has a vision of building a digital nation known as the ICON Republic, where heterogeneous communities with differing economic, social and governance ideals can interact seamlessly over the ICON network utilizing the Blockchain Transmission Protocol (“BTP”). Bridging communities allows for value and information to be shared seamlessly across the network, thus empowering the next evolution of digital transformation.</p><p>We’re now almost 2.5 years on from the 2017 ICO, and while a lot of material has been published since then on the business aspects of ICON, the technical side of the project hasn’t quite received the level of attention it deserves.</p><p>For that reason, let’s deconstruct ICON and take a closer look at how it compares to other projects across the blockchain space.</p><h3>What is ICON?</h3><p>Here’s how ICON defines itself:</p><p><strong><em>The ICON Project aims to build a decentralized network that allows independent blockchains with different governances to transact with one another without intermediaries.</em></strong></p><p>This definition allows us to identify the three main principles that underlie the ICON network: <strong>decentralization</strong>, <strong>interoperability</strong>, and <strong>governance</strong>.</p><ul><li><strong>Decentralization</strong> is defined as the transfer of authority from a single entity to a network of participants. Decentralization allows for autonomous governance of the ICON network, which is essential if this network comprises multiple “independent blockchains.”</li><li><strong>Interoperability</strong> refers to how the network allows these independent blockchains to communicate with each other. ICON’s capacity for interoperability makes it an <em>interchain.</em></li><li><strong>Governance</strong> is the structure that regulates how participants in a network can interact with each other. Without a sound governance system, ICON’s competencies of decentralization and interoperability would be rendered useless as the network would fail to sustain itself and expand.</li></ul><p>While these principles of decentralization, interoperability, and governance, are important and valid on their own, it is their convergence that makes ICON stand out. Let’s take a closer look at each of them.</p><h3>Decentralization</h3><p>The endgame for the ICON project is a decentralized network of independent blockchains. To better understand what that means, let’s start by revisiting some blockchains basics.</p><h4>Blockchain revisited</h4><p>You’ve probably encountered a definition that goes like this: <em>“a blockchain is a distributed, decentralized, public ledger.”</em> This definition is a little confusing, and also depends on how exactly one defines terms like “distributed” and “public ledger.”</p><p>Instead, let’s consider another way to describe blockchain. Blockchain is <em>a distributed database that is replicated among the peers (nodes) of a network.</em> A fundamental conclusion that flows from this definition is that every node on a blockchain network stores the same exact data or state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ySI8LXCL9wvtMpPw" /></figure><p>A <strong>consensus algorithm</strong> is what allows nodes to agree on the state of the blockchain. Different blockchains use different consensus algorithms, each with their own strengths and weaknesses.</p><p>Bitcoin and Ethereum are both blockchains — networks of nodes that reach consensus, leading to the creation of blocks. ICON, like Cosmos and Polkadot, is an interchain. ICON calls itself the “Network of Blockchains” while Cosmos goes with the “Internet of Blockchains,” but the idea is the same. Both are large networks comprised of smaller networks, each with their own nodes and governance.</p><h4>Decentralized Blockchains</h4><p>We’ve covered the difference between blockchains and interchains, but we haven’t touched decentralization yet. What exactly does it mean for blockchain to be decentralized?</p><p>As it turns out, this question has no easy answer since the definition of “decentralization” itself is quite fluid, as Vitalik Buterin remarks in<a href="https://medium.com/@VitalikButerin/the-meaning-of-decentralization-a0c92b76a274"> his article on the subject</a>. One way to “measure” the extent to which a blockchain is decentralized is to look at who controls the nodes.</p><p>Remember, nodes are essentially computers on the blockchain network that participate in a consensus algorithm to enable the creation of a new block. Thus, if there was a single entity in control of a significantly higher number of nodes than anyone else, it would be hard to call that blockchain decentralized. The number of nodes on the network is likewise a valid indicator of decentralization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/0*33mcPnuaHy3zBnr8" /><figcaption><em>This figure illustrates a Sybil attack — a network disruption caused by a malicious entity controlling the majority of the nodes. Centralized networks with a small number of nodes are typically more vulnerable to Sybil attacks.</em></figcaption></figure><p>NEO and Ripple are two examples of blockchains that are mostly centralized. On the other hand, Bitcoin, Ethereum, and Cosmos are all decentralized blockchains, with many independent entities controlling the nodes.</p><p>ICON is a decentralized network consisting of 22 Main P-Reps and 78 Sub P-Reps. Main P-Reps are responsible for producing blocks and verifying transactions. Every person who holds ICX can delegate their vote to P-Reps to help secure the network.</p><p>Before delving deeper into governance on the ICON Network, let’s discuss the types of nodes in greater detail.</p><h3>Nodes on the ICON Network</h3><p>At a fundamental level, there are two types of nodes on a blockchain network: full nodes (in the ICON network, we call them peer nodes) and light clients. Full nodes store the full state of the blockchain. But what exactly does that mean?</p><p><strong>Full Nodes</strong></p><p>Remember that we defined blockchain as a distributed database that is replicated among the peers (nodes) of a network. This database itself is a chain of blocks, where each block contains a block header and all the transactions stored in it.</p><p>The architecture of the distributed ledger is a rather complicated subject on its own, and you can explore it further <a href="https://mlsdev.com/blog/156-how-to-build-your-own-blockchain-architecture">here</a>. The important thing to know is that block headers contain a hash, or encryption, of the previous block’s header and a Merkle Root, which is a fingerprint of all the transaction data stored in that block. If a tiny bit of transaction data changes, the Merkle Root will change as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/637/0*uakJqtopDc6kVKQW" /></figure><p>Full nodes store all state, including block headers and transactions. Most nodes don’t need to store the entire state of the blockchain, which is why the role of full nodes is usually reserved for validators — P-Reps on the ICON network.</p><p>Main P-Reps are full nodes that verify blocks and participate in consensus, thus serving as validators in the ecosystem. Sub P-Reps also function as non-validator full nodes, adding to the security of the network and stepping up to replace a Main P-Rep if needed.</p><p><strong>Light Clients</strong></p><p>Light clients only store the block headers from the genesis block to the most recent one. They do not participate in consensus or store transaction data. Light clients use the Merkle Roots in block headers to verify the authenticity of transaction data.</p><p>Since they don’t store the full state of the blockchain, light clients require significantly less storage and than full nodes — in fact, light clients can sometimes run on mobile devices. Light clients will be really important once we get into interoperability on the ICON network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*5OYP3wContkLPVER" /></figure><p><strong>Citizen nodes</strong></p><p>Another type of node on the ICON network is the citizen node. Citizen nodes don’t participate in block generation, but synchronize block data and relay transaction requests to the full nodes. Citizen nodes are typically used by DApps and exchanges on ICON Network allowing full nodes to focus on consensus, producing and validating blocks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XE02OL46lkDz075K" /></figure><p>Now, let’s explore ICON’s <strong>blockchain layer structure </strong>and how it differs from other blockchains.</p><h3>A primer on blockchain layers</h3><p>So far, we’ve taken a look at the role of nodes on a blockchain network and discussed the structure of the distributed ledger. All public blockchains have validator nodes, and they generally utilize the ledger structure described in the previous section (with minor adjustments).</p><p>To compare one blockchain project with another, it helps to decompose its blockchain into separate layers. The most basic distinction can be drawn between the protocol and application layers of a blockchain.</p><p>This distinction is best understood by looking at the Internet, where the protocol layer consists of protocols like HTTP and TCP/IP, while the application layer represents user-facing platforms like Google, Facebook, and Netflix. The application layer can also be viewed from a more general perspective (e.g. search engines, social media, video streaming).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l1LBDFQQTMMCkQXB" /></figure><p>The protocol layer for blockchains represents the underlying frameworks and mechanisms that enable communication between nodes and guarantee consensus. The application layer is different for each blockchain. The diagram below shows the application layer for Bitcoin, which is a network for peer-to-peer (P2P) transactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TxyI7LGwNVBVRygL" /></figure><p>The protocol layer in Internet technologies can be further decomposed into a set of specialized protocols — the Internet Protocol (IP) underlies the Transmission Control Protocol (TCP), which sits below the HyperText Transfer Protocol (HTTP).</p><p>Similarly, the blockchain protocol layer can be broken down into smaller components. There’s no conventional standard for this decomposition, but one way to think about the protocol layer is by dividing it into consensus, propagation, and Sybil resistance layers.</p><ul><li><strong>Sybil resistance layer</strong>: provides protection from a Sybil attack — an attempt by a single malicious entity to prevent finality on the network by gaining an overwhelmingly large influence. Finality is the guarantee that all well-formed blocks are irreversible once added to the ledger. A lack of finality can lead to transaction reversals and double-spending.</li><li><strong>Propagation layer</strong>: defines how the state (blocks and transactions) are communicated between nodes in the network.</li><li><strong>Consensus layer</strong>: ensures that nodes can agree on the state of the network, which means that the local view of the ledger for each node is the same. This layer also defines the rules for adding new blocks to the ledger.</li></ul><p>Each of these layers has a specific function, but there’s a great amount of interplay between them.</p><p>In the next part of our series, we’ll apply this protocol layer decomposition to Bitcoin, Ethereum, and Cosmos. And also discuss ICON’s composition in greater detail.</p><p>Your Partner in Blockchain,</p><p>ICX Station</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81a944bd835b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helloiconworld/icon-deconstructed-81a944bd835b">ICON, deconstructed</a> was originally published in <a href="https://medium.com/helloiconworld">Hello ICON World</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>