<?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[Tezos × Cryptoeconomics Lab - Medium]]></title>
        <description><![CDATA[Tezos Integration to Plasma Chamber - Medium]]></description>
        <link>https://medium.com/tezos-cryptoeconomics-lab?source=rss----6778e34e740e---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Tezos × Cryptoeconomics Lab - Medium</title>
            <link>https://medium.com/tezos-cryptoeconomics-lab?source=rss----6778e34e740e---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:29:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/tezos-cryptoeconomics-lab" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Progress Update of Early October]]></title>
            <link>https://medium.com/tezos-cryptoeconomics-lab/progress-update-of-early-october-e3535c17ac0d?source=rss----6778e34e740e---4</link>
            <guid isPermaLink="false">https://medium.com/p/e3535c17ac0d</guid>
            <category><![CDATA[tezos]]></category>
            <dc:creator><![CDATA[Shogo Ochiai]]></dc:creator>
            <pubDate>Wed, 02 Oct 2019 04:42:20 GMT</pubDate>
            <atom:updated>2019-10-02T04:42:20.758Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*hOcvEdHSUjQttQ4MumVz1A.jpeg" /><figcaption><a href="https://www.jalan.net/news/article/104234/">jalan.net/news/article/104234</a></figcaption></figure><h3>What we did</h3><p>Previous OpenSSL issue has been fixed in PR <a href="https://github.com/cryptoeconomicslab/plasma-android-sdk/pull/32">Openssl, pubsub client by tkmct · Pull Request #32 · cryptoeconomicslab/plasma-android-sdk</a></p><p>We could build a Plasma transaction on the mock Android wallet. Precisely, the Android wallet creates a signature and a message, but a Rust server verifies counterfeiting. In production, it as well has to be done on Android by compiling Rust code into WASM.</p><p>We need keccak256 for ocaml-hacl and have to amend the protocol. This proposal would incur some attention to <a href="https://gitlab.com/tezos/tezos/issues/180#note_135573257">this issue</a>, and it simultaneously affects the atomic swap capability. FYI: We know blake2 is three times better performance with the same-level security with keccak256.</p><h3>sg/落合渉悟@ブロックチェーンが国を滅ぼす(仮)執筆中 on Twitter</h3><p>@ArthurB Thanks - And OTOH I understand we still don&#39;t need to abandon having sha3 on Michelson because I&#39;ve read a gitlab issue which is discussing about having sha3 on Michelson for improving interoperability such as atomic swap.</p><p>The serialization of the data format as well is a big discussion part. As our plasma-rust-framework implementation was depending on Ethereum, its De Facto serializer was ABI. We’ve learned that our Rust Plasma client must have an abstract layer for dealing with PACK/UNPACK/Tezos_data_encoding, and <a href="https://github.com/cryptoeconomicslab/plasma-rust-framework/issues/258">we’re building</a> adaptor for data formatting.</p><p>LIGO deposit contract prototype is <a href="https://github.com/cryptoeconomicslab/ovm.tz">cryptoeconomicslab/ovm.tz</a></p><h3>Next Iteration</h3><p>We’re gonna roughly prototype a commitment contract in order to tap the LIGO contract from Plasma. This is a good milestone to finalize the serialization adaptor.</p><p>And we’re gonna integrate these prototype results into <a href="https://gitlab.com/tezos/cortez-android">Cortez</a> to smoke-test every concept are going well or not.</p><p>Once we could confirm it works, we can investigate more complex L2 transaction and exit-game for Tezos.</p><h3>P.S.</h3><p>This week is Devcon5(Ethereum Foundation’s event) in Osaka, and Tezos Foundation is the Serenity(highest) sponsor of this event. Hence I could find many Tezos community people around Osaka and please hit me up at there :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3535c17ac0d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tezos-cryptoeconomics-lab/progress-update-of-early-october-e3535c17ac0d">Progress Update of Early October</a> was originally published in <a href="https://medium.com/tezos-cryptoeconomics-lab">Tezos × Cryptoeconomics Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Progress Update of Early September]]></title>
            <link>https://medium.com/tezos-cryptoeconomics-lab/progress-update-of-early-september-228a62249b8?source=rss----6778e34e740e---4</link>
            <guid isPermaLink="false">https://medium.com/p/228a62249b8</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[tezos]]></category>
            <category><![CDATA[ovm]]></category>
            <category><![CDATA[plasma]]></category>
            <dc:creator><![CDATA[Shogo Ochiai]]></dc:creator>
            <pubDate>Thu, 05 Sep 2019 01:46:52 GMT</pubDate>
            <atom:updated>2019-09-05T01:26:22.895Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d7fwtBhrQZmLaTYVzYAt6Q.jpeg" /><figcaption>Photo credit: <a href="https://visualhunt.co/a3/5d0f68">Billy Wilson Photography</a> on <a href="https://visualhunt.com/re5/fa146bec">Visualhunt.com</a> / <a href="http://creativecommons.org/licenses/by-nc/2.0/">CC BY-NC</a></figcaption></figure><p>Hi guys! We’re gonna share some biweekly update of <strong>OVM(Plasma) on Tezos</strong> project!</p><h3>What we did</h3><p>We could run a transaction from Android to Tezos by using <a href="https://gitlab.com/tezos/cortez-android">cortez-android</a>. And we assured that Java-based module is able to be integrated with Kotlin-based module because <a href="https://github.com/cryptoeconomicslab/plasma-android-sdk">Plasma Android SDK</a> is written in Kotlin.</p><p>We tried to run plasma transaction on Android, but JSON-RPC Rust module requires <a href="https://github.com/cryptoeconomicslab/plasma-android-sdk/pull/32">OpenSSL in Rust side</a>, and now we’re investigating about that.</p><p>We published <a href="https://medium.com/cryptoeconomics-lab/close-up-the-ovm-plasma-edition-934035646942">an article of Plasma-on-OVM spec</a>. It’ll be a good entry point to demystify how can the Plasma and OVM be on Tezos. Gabriel from Marigold as well post some proposal to the <a href="https://forum.tezosagora.org/c/research">Tezos Forum.</a></p><h3>Next iteration</h3><p>Fix OpenSSL issues and make JsonRpc available on Android (many other network layer modules might be a showstopper) and enable creating a Plasma transaction on Android.</p><p>Run LIGO-based smart contract from Android and integrate that contract runner into <a href="https://github.com/cryptoeconomicslab/plasma-android-sdk">Plasma Android SDK</a>.</p><p>Prototype the OVM contract on Tezos.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=228a62249b8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tezos-cryptoeconomics-lab/progress-update-of-early-september-228a62249b8">Progress Update of Early September</a> was originally published in <a href="https://medium.com/tezos-cryptoeconomics-lab">Tezos × Cryptoeconomics Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Tezos Integration to Plasma Chamber]]></title>
            <link>https://medium.com/tezos-cryptoeconomics-lab/announcing-tezos-integration-to-plasma-chamber-374fd18f8b7?source=rss----6778e34e740e---4</link>
            <guid isPermaLink="false">https://medium.com/p/374fd18f8b7</guid>
            <category><![CDATA[scaling-solution]]></category>
            <category><![CDATA[tezos]]></category>
            <category><![CDATA[plasma]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[layer-2]]></category>
            <dc:creator><![CDATA[Daiki Sekiguchi]]></dc:creator>
            <pubDate>Tue, 20 Aug 2019 08:19:29 GMT</pubDate>
            <atom:updated>2019-08-20T08:19:29.485Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wet-uXLUO8VT8LVwBl6UEA.png" /></figure><p>Hi guys! We’re thrilled to announce that we <a href="https://tezos.foundation/news/cryptoeconomics-lab-receives-grant-to-develop-plasma-on-tezos">received a grant from the Tezos Foundation</a> to develop a Plasma layer on Tezos and integrate Tezos to Plasma Chamber!</p><p>This project definitely introduces a new paradigm for L2 development, and we hope many more people will recognize and think about this L2-centered development paradigm going forward!</p><h3>Who we are</h3><p>We’re <a href="https://www.cryptoeconomicslab.com/">Cryptoeconomics Lab</a>, founded in Japan in July 2018. We’ve been contributing to the Plasma community and recently met with Gabriel Alfour of The Marigold Project (<a href="https://medium.com/tezos/marigold-layer-2-scaling-for-tezos-7445b5a3b7be">Marigold</a>, a layer-2 scaling technique for Tezos, and <a href="https://ligolang.org/">LIGO</a>, a statically typed high-level smart-contract language for Tezos). He’s a very talented developer and we are excited to collaborate with his team!</p><h3>What we build</h3><p>We build Plasma with the <a href="https://medium.com/plasma-group/introducing-the-ovm-db253287af50">Optimistic Virtual Machine</a> (OVM) compatible spec. There are so many Plasma variants and zk-S[NT]ARKs applied solutions, and the OVM is a common spec for all of these variants. This OVM specification was introduced by the <a href="https://plasma.group/">Plasma Group</a>, and we’re focusing on building Plasma from their spec. You may be confused why we think such a long explanation is necessary! But this design choice is quite effective for building a strong L2 ecosystem. We will elaborate in the sections below.</p><h3>Why we build</h3><h4>1. Problem of L1 and paradigm shift of L2</h4><p><strong><em>1–1. Problem of L1 and earlier L2 constructions<br>1–1–1. The security and capacity of sidechains</em></strong></p><p>Sidechains usually employ staking for their security models. So, in order to attack a sidechain, an attacker is required to control as much funds as are staked for that sidechain, rather than a Layer-1 (L1) staking (“baking” in Tezos) sum amount. This ease of attack limits the capacity of an ecosystem. It’s okay for gaming usage but it won’t work for international/industrial usage.</p><p><strong><em>1–1–2. TPS limitation of sidechains</em></strong></p><p>As normal sidechains rely on staking, network latency is the main bottleneck for its throughput. Even Hyperledger or a private Ethereum network could only process 300–700 TPS. This is not really enough for international/industrial usage.</p><p><strong><em>1–2. Properties of Plasma<br>1–2–1. Gas-Less</em></strong></p><p>Plasma doesn’t require end-users to pay tx fees in a native token. A Plasma operator pays this when it compresses txs into a Merkle hash. So, non-expert users can handle security tokens or stablecoins more easily. (The operator will take some fee from a chosen token, rather than a native token.)</p><p><strong><em>1–2–2. High Throughput</em></strong></p><p>Plasma is just like PayPal or Alipay with its off-chain design. It uses a blockchain-style specification as a security model, but it doesn’t broadcast blocks or txs to other nodes. This eliminates network latency. We’re assuming a primary performance bottleneck is CPU (Merkle Tree Calculation) and we expect very large room of tuning, yay!</p><p><strong><em>1–2–3. Instant Finality</em></strong></p><p>A state channel on Plasma or NOCUST-ish protocol on Plasma enables instant finality. A normal Plasma tx requires 2~6min to finalize the tx, but we can design ~300ms finality for special use-cases.</p><p><strong><em>1–2–4. Value Centered Contract</em></strong></p><p>Unlike an L1 smart contract (Data Centered Contract), L2 contracts have to use a “Value Centered Contract” paradigm. We call it a <strong><em>Predicate</em></strong>. It can look like the UTXO model of Bitcoin, but we can design several applications which use multisig, state channel, escrow, atomic swap, CDP, and so on.</p><p><strong><em>1–3. “L1 agnostic L2”</em></strong></p><p>We’d like to introduce the “Layer-1 agnostic Layer-2” concept. This is the reason why we could adopt our Plasma implementation to Tezos. And Tezos brings Plasma several improvements!</p><p><strong><em>1–3–1. Smoother dev experience on Tezos</em></strong></p><p>Tezos has a built-in feature-toggle system. When a change to the core protocol is proposed, we first have to implement the proposal, and then only the election-winning proposal can go to the production environment. This election cycle currently occurs once a quarter (approximately every 3 months). Without this feature, we sometimes have to wait extended periods of time for new opcodes and other innovations to be introduced, or we need bypassing temporal implementation. This is very helpful when we deal with new cryptography, etc.</p><p><strong><em>1–3–2. Ease of value exchange between the same spec L2</em></strong></p><p>Interoperability is cumbersome and sometimes insecure. But a cross-chain atomic swap between Plasmas via an HTLC contract would enable much safer interoperability between Tezos and other chains. We could see a DEX with all kinds of tokens from other blockchains.</p><p><strong><em>1–3–3. Open source doesn’t make a Silo, and so L2 first development methodology helps developers a lot!</em></strong></p><p>What if we build Plasmas, State Channels, and zk-S[NT]ARKs solutions on their own, for each blockchain? The learning curve of developers is to be O(N²) and developers will stick to their favorite implementations. It is helpful for all parties to consolidate the spec of L2 implementations and make them easier to switch ecosystems as they require.</p><h4>2. Industrial Adoption and Production Usage</h4><p>Having a chance to adopt Plasma in the real world is very important to get insights of devops and business usage of Plasma. Tezos is gaining adoption and momentum in several industries and so we love that challenge.</p><p><strong><em>2–1. Voting</em></strong></p><p>You know, 500+ people died in an Indonesian presidential election due to a manpower-dependent operation that lasted 48 hours. Building e-voting systems is usually closed source and not developed transparently in order to keep an implementation secret (security of obscurity). But Plasma-based voting systems can be implemented in an OSS way, it’s much cheaper and safer to do so. And this time 180M Indonesians voted in that election. It requires more than 5000 TPS for this type of application. We love high throughput projects.</p><p><strong><em>2–2. Narrow Bank</em></strong></p><p>Plasma can be seen as a narrow bank if we use a stablecoin. Even that narrow bank could be integrated with a DEX of security tokens, other cryptocurrencies, and foreign currencies. Is an operator of Plasma required to obtain a banking license? No, Plasma doesn’t hold customers’ funds at all (non-custodial). So even an electricity giant, a mobile carrier, or e-commerce corps. can easily be a bank!</p><p><strong><em>2–3. Non fossil fuel certificate exchange</em></strong></p><p>A non-fossil fuel certificate can be a token. And it is not regulated as a security in many countries. This area is also very close to real-world adoption!</p><h4>3. Challenge for Seamless User/Dev Experience</h4><p><strong><em>3–1. State Channel integrated Wallet</em></strong></p><p>A state channel and Plasma must share an app in order to avoid redundant source codes.</p><p><strong><em>3–2. Universal Login</em></strong></p><p>This “Sign in” experience enabler can be migrated to Plasma.</p><p>See also: <a href="https://universallogin.io/">https://universallogin.io</a></p><p><strong><em>3–3. Lost Fund Restoration</em></strong></p><p>A Plasma operator can restore funds in a secure way by using exit-game magic.</p><p><strong><em>3–4. Multi runtimes</em></strong></p><p>Plasma has to share several modules between various runtimes such as a mobile app and IoT device. So we chose Rust as our implementation language. WASM enables us to run the same code everywhere.</p><h3>Roadmap</h3><p>Aug~: Android Wallet<br>Oct~: Plasma in OCaml<br>Dec~Feb: Child-chain Integration</p><h3>About Next Iteration</h3><p>We will prototype an Android wallet specifically focusing on Tezos tx creation, Tezos pooling, and Plasma tx creation. A main difficulty is how to run Rust code on Android runtime, and how to abstract Tezos pooling adaptor.</p><p>We’re very happy to introduce the latest spec of Plasma to the Tezos community, and are excited to open a new path to the L1 agnostic abstract implementation of Plasma!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=374fd18f8b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tezos-cryptoeconomics-lab/announcing-tezos-integration-to-plasma-chamber-374fd18f8b7">Announcing Tezos Integration to Plasma Chamber</a> was originally published in <a href="https://medium.com/tezos-cryptoeconomics-lab">Tezos × Cryptoeconomics Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>