<?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 CodeChain on Medium]]></title>
        <description><![CDATA[Stories by CodeChain on Medium]]></description>
        <link>https://medium.com/@codechain?source=rss-286cacb31d9b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*G1rks2WtNKqa3lhWD-H59A.png</url>
            <title>Stories by CodeChain on Medium</title>
            <link>https://medium.com/@codechain?source=rss-286cacb31d9b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:45:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@codechain/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[Monthly CodeChain TechTalk — January 2020]]></title>
            <link>https://medium.com/codechain/monthly-codechain-techtalk-january-2020-b00a0a020200?source=rss-286cacb31d9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b00a0a020200</guid>
            <category><![CDATA[chaincode]]></category>
            <category><![CDATA[tech-talk]]></category>
            <dc:creator><![CDATA[CodeChain]]></dc:creator>
            <pubDate>Thu, 30 Jan 2020 03:25:04 GMT</pubDate>
            <atom:updated>2020-01-30T03:25:04.959Z</atom:updated>
            <content:encoded><![CDATA[<h3>Monthly CodeChain TechTalk — January 2020</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TfuJDnfQkuosaV91dIcC_w.jpeg" /></figure><p>It’s been great to kick of the year with an awesome tech talk session hosted by CodeChain. We shared the results of our latest implementations with nearly 50 developers from major Korean IT companies who joined the meetup. Again, the talks were followed by great discussions and questions. Here is the recap.</p><h3>Tenderland: randomized leader election in Tendermint</h3><p>Tenderland is a solution to the issue that, in Tendermint, a malicious attacker can attack the network by exactly predicting the next block proposer. It is basically about adding randomness to the leader election process while keeping the stake-proportional leader election property. It also assures that proposals from other validators be verifiable. We combined Tendermint consensus algorithm and Algorand’s sortition algorithm to construct Tenderand.</p><p>During the talk, Seonpyo walked us through all the tests the team had gone to prove our implementation of Tenderand. He concluded that Tenderland proved to have the random quality comparable to “dev/urandom”’s, which means it’s effective in defending against DOS attacks in public blockchains.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FXcpFPDGlo24%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DXcpFPDGlo24&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FXcpFPDGlo24%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/8acd86b3cb250e37c2912060b3b2f598/href">https://medium.com/media/8acd86b3cb250e37c2912060b3b2f598/href</a></iframe><p>For more details, follow the links:</p><ul><li><a href="https://research.codechain.io/t/randomized-leader-election-using-vrf/17">Original research paper</a></li><li><a href="https://medium.com/codechain/tenderand-randomized-leader-election-in-tendermint-a3663d863479">Benchmark tests report</a></li><li><a href="https://docs.google.com/presentation/d/1CgAyXdKTCBhsSTWF8MGa4P86v175juKduRCZeUPZDCM/edit?usp=sharing">Slides</a></li></ul><h3>CodeChain Foundry</h3><p>We announced CodeChain Foundry, a <strong>framework for building blockchain applications</strong>. Its goal is to allow developers to easily create custom blockchains from scratch that can natively interoperate with other blockchains.</p><p>Foundry is characterized by its built-in support for:</p><ul><li>Scalable Consensus (Tendermint)</li><li>Composable Module System</li><li>Inter Blockchain Communication (IBC)</li><li>Light Client</li></ul><p>We are aiming to have an initial version by the end of February, so stay tuned!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FPSORrveZ8qw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DPSORrveZ8qw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FPSORrveZ8qw%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/804408eea3fde0ca294668e99e2df93a/href">https://medium.com/media/804408eea3fde0ca294668e99e2df93a/href</a></iframe><ul><li><a href="https://docs.google.com/presentation/d/105xae0V9CPYIgFRUq5byQ34KJIQ5y2VAYUq18SKwvJk/edit?usp=sharing">Slides</a></li></ul><h3>VeriSync: a fast and verifiable sync method</h3><p>VeriSync is the fruition of the snapshot sync implementation proposed last year. It is a fast and VERIfiable SYNC method for blockchains and its main idea is to split a state tree with verifiable chunks.</p><p>The talk included the design and implementation details as well as benchmark test results. While the time required for the full synchronization is <strong>10h 40m, </strong>our snapshot synchronization took <strong>3m 46s</strong> on the same setting, so we can say we got <strong>169x faster in time/efficiency for the initial setup</strong>. The database constructed with the full block synchronization required <strong>29GB</strong> of space, and the initial database constructed with the snapshot synchronization required <strong>2.8MB</strong> of space. Note that these numbers will get even better as the blockchain’s size grows, so the numbers will be far better than now as time goes on.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FnLsjx3sapDk%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DnLsjx3sapDk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FnLsjx3sapDk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b04b30c6b5323e42f14cecb2513c9c2a/href">https://medium.com/media/b04b30c6b5323e42f14cecb2513c9c2a/href</a></iframe><ul><li><a href="https://docs.google.com/presentation/d/10rf08SSeNed-pka5PLo9O1jHqAtR-CMIkLfExTVgQyw/edit?usp=sharing">Slides</a></li><li><a href="https://research.codechain.io/t/snapshot-sync-proposal/21">Research paper</a></li><li><a href="https://medium.com/codechain/verisync-baf0583ade47">Benchmark tests report</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b00a0a020200" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codechain/monthly-codechain-techtalk-january-2020-b00a0a020200">Monthly CodeChain TechTalk — January 2020</a> was originally published in <a href="https://medium.com/codechain">CodeChain</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monthly CodeChain TechTalk — November 2019]]></title>
            <link>https://medium.com/codechain/monthly-codechain-tecktalk-november-2019-73ad0fa2e7f5?source=rss-286cacb31d9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/73ad0fa2e7f5</guid>
            <category><![CDATA[cosmos]]></category>
            <category><![CDATA[chaincode]]></category>
            <category><![CDATA[interblockchain]]></category>
            <category><![CDATA[ci]]></category>
            <category><![CDATA[ibc]]></category>
            <dc:creator><![CDATA[CodeChain]]></dc:creator>
            <pubDate>Wed, 15 Jan 2020 03:25:35 GMT</pubDate>
            <atom:updated>2020-01-23T05:27:23.104Z</atom:updated>
            <content:encoded><![CDATA[<h3>Monthly CodeChain TechTalk — November 2019</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fMWTQhscl0I7u9gU1PrHoA.jpeg" /></figure><p>Here are some highlights of our second edition of CodeChain Tech Talks. Though the blockchain market is in midst of a slowdown, interests in blockchain technology developments remain still high. Engineers from major IT companies in Korea have joined our second tech talk, discussed our research areas and gave constructive feedback, all of which are of great help to our team’s research activities.</p><h3><strong>CodeChain DEX Protocol</strong></h3><p>Jingyeong explained the key characteristics of the CodeChain DEX protocol that features a decentralized listing process, matching algorithm and techniques to prevent front-running attacks.</p><p>CodeChain DEX listing process does not go under a review process from a decision making body, it is not decided via a voting process and it does not allow anyone to list any token either. It is characterized by its stake tokens; anyone can list by delegating the stake tokens. Delegated stake tokens have the right to earn some portion of the exchange fees, so if a token has low demand in the market, people will undelegate their stake tokens, and the token will be eventually delisted from the exchange if it has insufficient amount of delegated stake tokens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8HpKqvekIFkGUKP1rhz0UA.png" /></figure><p>A second characteristic is that CodeChain DEX has a structure to prevent front-running attacks, a problem that most exchanges have. Our research areas include timed-release encryption, sharmir secret sharing and other cryptographic techniques that prevent front-running attacks even from validators.</p><p>For more details please check out the video, the paper and the slides.</p><ul><li><a href="https://www.youtube.com/watch?v=10IFCzncUhs">Video</a></li><li><a href="https://research.codechain.io/t/codechain-dex-protocol/30">Paper</a></li><li><a href="https://docs.google.com/presentation/d/14atagv2KhDmoIJTZfoQxoF0b_DShDtSir3OdkZtRca8/edit?usp=sharing">Slides</a></li></ul><h3><strong>ICS (InterChain Standard) and CodeChain</strong></h3><p><a href="https://github.com/cosmos/ics">ICS</a> is a standard for inter blockchain communication and the project is led by the Cosmos team. The ICS specification has been under review for a few years and it is currently in its last phase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XpnZw12icGZ0jTbiTs-ezg.jpeg" /></figure><p>The implementation of its specification is not complex and anyone can join the inte blockchain network via this protocol. Cosmos as well as CodeChain have implemented its first demo implementation. During the talk, Juhyung explained the key concepts of the ICS standard, the implications of each component and the areas that we need to consider when implementing the spec. The talk sparked a lot of interest among the audience as inter blockchain communication is a topic that could address interoperability and performance issues. For more details, please check out Juhyung’s talk and slides.</p><ul><li><a href="https://www.youtube.com/watch?v=GbUvNnH4hHQ">Video</a></li><li><a href="https://docs.google.com/presentation/d/13tdTjmdQsrXH-A8mlYqzNbxvFARrjWylqi8Xf2P-6_o/edit?usp=sharing">Slides</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73ad0fa2e7f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codechain/monthly-codechain-tecktalk-november-2019-73ad0fa2e7f5">Monthly CodeChain TechTalk — November 2019</a> was originally published in <a href="https://medium.com/codechain">CodeChain</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monthly CodeChain TechTalk — October 2019]]></title>
            <link>https://medium.com/codechain/monthly-codechain-tecktalk-october-2019-10a471d6d2dc?source=rss-286cacb31d9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/10a471d6d2dc</guid>
            <category><![CDATA[vrf]]></category>
            <category><![CDATA[tendermint]]></category>
            <category><![CDATA[vault]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[chaincode]]></category>
            <dc:creator><![CDATA[CodeChain]]></dc:creator>
            <pubDate>Wed, 23 Oct 2019 07:50:59 GMT</pubDate>
            <atom:updated>2020-01-23T05:27:51.577Z</atom:updated>
            <content:encoded><![CDATA[<h3>Monthly CodeChain TechTalk — October 2019</h3><p>We’re excited to share that we have held our first edition of open CodeChain TechTalks last Wednesday! CodeChain TechTalks are small weekly seminars we are hosting for a small group of engineers interested in blockchain technology. We have been keeping it small as we could not afford hosting bigger seminars every week. However, as we felt that more and more developers were curious to learn and share the latest and coolest technology in the blockchain field, we have decided to open the tech talks to the public and organize monthly meetups to further nurture the Korean blockchain developers community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D9xFSeHM3AHJiFqIuHy10Q.jpeg" /></figure><p>Our first TechTalk was terrific with over 30 developers who got engaged in the discussions and Q&amp;A sessions. Some feedback even helped us revisit few details of our own design. This is the kind of outcome we wanted to see in the meetups — very rare in the Korean blockchain industry where most meetups are held purely for coin marketing (dumping) purposes — and we have indeed succeeded.</p><p>Here is an overview of the topics covered during the tech talk.</p><h3><strong>1. CodeChain Staking System: a tale of two tokens (by Kwang Yul Seo)</strong></h3><p>We have seen a rise of proof of stake (PoS) consensus mechanism. Among these are EOS, Tron, Cosmos, Tezos and many others. At first glance, the attraction of holding these coins looks clear because you can earn 5–15% annually on your holdings by just staking your coins.</p><p>However, with keen eyes on the staking reward mechanism, you will realize that staking rewards are illusory. Staking rewards are created through inflation and staked tokens are rewarded by diluting not-staked tokens. If everybody stakes their coins, there is no net profit at all!</p><p>CodeChain explored the design space in search of a better staking system without these pitfalls. The staking system of CodeChain is different from existing PoS chains in that it has two native tokens: stake tokens (CCS — CodeChain Stake) and fee tokens (CCC — CodeChain Coins). As the names imply, CCS is used for staking and for the network governance.</p><p>The rule is clear and simple. CCS holders earn transaction fees (fee tokens) spent on the network regardless of the staking. Decoupling of fee tokens from staking tokens eliminates the need for staking reward through inflation that causes a lot of confusion. CCS tokens have low liquidity, but in exchange, its owners are guaranteed profits for providing a more secure and stable network.</p><ul><li><a href="https://docs.google.com/presentation/d/1ACYEvIgsy_t1OZa_V-KIwM4E0MKl3lsUlKfEhaYqgUw/edit?usp=sharing">Slides</a></li><li><a href="https://www.youtube.com/watch?v=N9pgnX4yy4w">Video</a></li></ul><h3><strong>2. Vault language (by Joonmo Yang)</strong></h3><p>We all know that Bitcoin’s script and EVM are really difficult to use. Sometimes one has to go through an audit process, which is not even guaranteed, to check whether the program they have written has no flaws. Thus, many organizations and research groups are developing newer and easier-to-use smart contract languages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8TEGnQvkJn3M81tIVKPixg.png" /></figure><p>CodeChain also had its limitations when it came to its script language, and this is the reason why we have developed Vault, a smart contract language for CodeChain. It is inspired by Bitcoin’s miniscript, as we wanted Vault to be as highly composable as miniscript. The compiler basically creates a lock script and an unlock script whenever we input a UTXO condition. One can create complex multi-sigs or HTLC scripts with just one line of code! With Vault, you can express almost all the conditions you can imagine using <em>thresh,</em> which is an expression for m-of-n conditions.</p><ul><li><a href="https://docs.google.com/presentation/d/1y7D8W3irJPR0bp9hWJldz2HhEb8o5j1LfkpI3Egz_cU/edit?usp=sharing">Slides</a></li><li><a href="https://research.codechain.io/t/vault-language-proposal/20">Paper</a></li><li><a href="https://www.youtube.com/watch?v=ypJPQMK2pRw">Video</a></li></ul><h3><strong>3. Snapshot Sync (by Seongchan Lee)</strong></h3><p>The current CodeChain implementation requires new nodes to replay the entire history of the blockchain from the genesis and synchronize with the best chain’s state. This initial sync process uses a large amount of resources. As the blockchain grows constantly, the required resources will grow constantly as well.</p><p>Parity’s Warp sync and Go Ethereum’s fast sync were proposed to address this problem. However, they provide no incremental way to validate the state along the synchronization process. A node may provide an invalid state, allowing attackers to waste network bandwidth.</p><p>Snapshot sync in CodeChain is designed to reduce the resources used during the initial block synchronization process, such as time, CPU, network bandwidth, disk space, and disk I/O. A snapshot consists of multiple chunks with merkle proofs so that a node can easily verify if a downloaded chunk does indeed belong to the state tree.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/439/1*LdvgMk3JLJGEHez2Dw_2ag.png" /></figure><ul><li><a href="https://docs.google.com/presentation/d/1w0MGEBVuMbQKmuOznLFhIpDlj5uD0WtA75FsToO4z3M/edit?usp=sharing">Slides</a></li><li><a href="https://research.codechain.io/t/snapshot-sync-proposal/21">Paper</a></li><li><a href="https://www.youtube.com/watch?v=XlFqSo4kpvE">Video</a></li></ul><h3><strong>4. Randomized leader election in Tendermint using VRF (by Seonpyo Kim)</strong></h3><p>CodeChain is a network that operates under the Tendermint consensus algorithm. It’s simple, and we believe it is, so far, the only consensus algorithm that has been proven in the production level.</p><p>However, Tendermint has its own limitations. It rotates through the validator set, i.e. block proposers, in a weighted round-robin fashion. Leaders can be subject to targeted denial-of-service attacks because attackers can predict exactly who will be the next proposer and direct all their bots to simultaneously attack that proposer. Bitcoin is not susceptible to such attacks because it is impossible to predict the next block proposer before the block is propagated to the network. Only the node that solved the proof-of-work problem knows that it can propose a block and other nodes in the network can confirm that the proposed block is from a valid block proposer by verifying the nonce.</p><p>To prevent such DoS attacks in Tendermint-based networks, validators can change the network structure, but this approach does not fundamentally solve the problem. To mitigate the possible denial-of-service attacks on Tendermint, we need to introduce randomness into its leader election mechanism so that attackers cannot predict the next proposer. In our roadmap, we are planning to adopt a verifiable random function (VRF) to assign leaders to round numbers in a less predictable way. The benefits of introducing VRF for enhancing Tendermint are as follows:</p><p>1. The network gets more secure against seed attacks</p><p>2. It also becomes less vulnerable against sybil attacks as the probability to be elected as leader is proportional to the stake</p><p>3. VRF is going to be used when validating block proposers so it does not affect the safety and liveness of the Tendermint consensus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Md_viFJ3NJNVXmE1G3CVQ.png" /></figure><ul><li><a href="https://docs.google.com/presentation/d/18hW11GyXo0USHFb9BuIJCki_7UGkGudD09CQbMOte6Q/edit?usp=sharing">Slides</a></li><li><a href="https://research.codechain.io/t/randomized-leader-election-using-vrf/17">Paper</a></li><li><a href="https://www.youtube.com/watch?v=paZbHg5AWGA">Video</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10a471d6d2dc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codechain/monthly-codechain-tecktalk-october-2019-10a471d6d2dc">Monthly CodeChain TechTalk — October 2019</a> was originally published in <a href="https://medium.com/codechain">CodeChain</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>