<?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 Yuan Han Li on Medium]]></title>
        <description><![CDATA[Stories by Yuan Han Li on Medium]]></description>
        <link>https://medium.com/@yuan-han-li?source=rss-7c0f39cb0fa2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OvXYseqUId34DHNj91tY5g.jpeg</url>
            <title>Stories by Yuan Han Li on Medium</title>
            <link>https://medium.com/@yuan-han-li?source=rss-7c0f39cb0fa2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:43:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yuan-han-li/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[WTF is Data Availability?]]></title>
            <link>https://medium.com/blockchain-capital-blog/wtf-is-data-availability-80c2c95ded0f?source=rss-7c0f39cb0fa2------2</link>
            <guid isPermaLink="false">https://medium.com/p/80c2c95ded0f</guid>
            <category><![CDATA[rollup]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Yuan Han Li]]></dc:creator>
            <pubDate>Tue, 11 Jan 2022 17:41:49 GMT</pubDate>
            <atom:updated>2022-01-16T18:52:39.978Z</atom:updated>
            <content:encoded><![CDATA[<h4>and why solving the “data availability problem” is crucial if we want blockchains to scale</h4><p>You’ve probably heard that Ethereum’s roadmap for sharding has <a href="https://ethereum-magicians.org/t/a-rollup-centric-ethereum-roadmap/4698">essentially scrapped execution sharding and is now exclusively focused on data sharding</a> to <a href="https://notes.ethereum.org/@vbuterin/data_sharding_roadmap">maximize Ethereum’s data space throughput</a>.</p><p>You might also have seen the recent discussion about <a href="https://polynya.medium.com/rollups-data-availability-layers-modular-blockchains-introductory-meta-post-5a1e7a60119d">modular blockchains</a>, dove into rollups and learnt about v<a href="https://polynya.medium.com/volitions-best-of-all-worlds-cfd313aec9a8">olitions/validiums, then heard about “data availability solutions.”</a></p><p>But maybe you found yourself a little confused at one point, scratched your head, and asked yourself WTF is data availability?</p><p>Before we dive in, it might be helpful to have a little refresher on the basics of how most blockchains work.</p><h4><strong>Transactions, Nodes, and the Infamous Blockchain Trilemma:</strong></h4><p>When you come across a new OHM fork with an APY that could make your grandparents have a heart attack, your next course of action is to smash that “stake” button, naturally. But what happens when you actually submit that transaction from Metamask?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/0*dEUo_lVd9b34yE3a" /></figure><p>In simple terms, your transaction goes into the mempool, and assuming your bribe to miners/validators was high enough, your transaction gets included in the next block and is added to the blockchain for posterity. This block containing your transaction then gets broadcasted to the network of the blockchain’s nodes. Full nodes would download this new block, execute/compute every transaction included within this block (including yours), and make sure they are all valid. For instance, in the case of your transaction, these full nodes might verify you are not stealing funds from anyone else and that you actually had enough ETH to pay for gas amongst other things. Full nodes therefore perform the important task of enforcing the blockchain’s rules on miners/validators.</p><p>It is because of this mechanism that traditional blockchains run into scaling issues. Since full nodes check every transaction to verify they follow the rules of the blockchain, blockchains cannot process more transactions per second without increasing the hardware requirements of running a full node (better hardware = more powerful full nodes = full nodes can check more transactions = bigger blocks containing more transactions are allowed). But if the hardware requirements of running full nodes increased, there would be fewer full nodes and decentralization would suffer — it would be dangerous if there are fewer people checking the work of miners/validators to keep them honest (as trust assumptions would increase)!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/0*9LmQwjHRMfHZZPd_" /><figcaption>The need to make data available is one of the main reasons why we can’t have all 3 😡</figcaption></figure><p>This mechanism also describes the importance of guaranteeing data availability in traditional monolithic blockchains: block producers (miners/validators) must broadcast and make available transaction data from blocks they produce so that full nodes can check their work<strong>.</strong> If block producers do not make transaction data from blocks they produce available, we would be in a situation where full nodes can’t check their work and keep miners/validators honest by enforcing the blockchain’s ruleset!</p><p>Now that you understand why data availability is important in traditional monolithic blockchains, let’s move on to how they come into play with everybody’s favorite scalability solution — rollups.</p><h4><strong>The Importance of Data Availability in the Context of Rollups:</strong></h4><p>Let’s first revisit how rollups help solve the scalability problem: Instead of raising the hardware requirements of running a full node, why don’t we just reduce the number of transactions that full nodes have to check are valid instead? We can do this by shifting transaction computation and execution away from full nodes to a much more powerful computer called a sequencer.</p><p>But doesn’t this mean we have to trust the sequencer? If full node hardware requirements are to be kept low, they definitely will lag behind the sequencer’s when trying to check its work. So how can we ensure new blocks proposed by this sequencer are valid then (i.e., that the sequencer is not stealing everyone’s funds)? Given it has been harped to death already, I’m sure you already know the answer to this question, but just bear with me here (if you need a refresher, <a href="https://www.mechanism.capital/rollups-introduction/">see Benjamin Simon for an ELI5</a>, or <a href="https://vitalik.ca/general/2021/01/05/rollup.html">Vitalik’s piece to go deeper</a>):</p><p>For Optimistic Rollups, we rely on something called fraud proofs to keep the sequencer honest (we assume the sequencer is behaving unless someone submits a fraud proof that shows the sequencer had included an invalid/malicious transaction). But if we want others to be able to compute fraud proofs, they will need the transaction data from the transactions the sequencer executes to be able to submit fraud proofs. In other words, the sequencer must make transaction <strong>data available</strong>, as otherwise, no one would be able to keep the optimistic rollup’s sequencer(s) honest!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*wg-6jtubV-peaUeG.jpg" /></figure><p>With ZK Rollups, keeping the sequencer(s) honest is much simpler — the sequencer must submit validity proofs (a ZK-SNARK/STARK) when it executes a batch of transactions, and this validity proof guarantees that none of the transactions were invalid/malicious. Moreover, anyone (even a smart contract) can easily verify the proof that was submitted. But <strong>making</strong> <strong>data available</strong> is still extremely important for the ZK-Rollup’s sequencer. This is because as a user of said rollup, we need to know what our account balances on the rollup are if we want to ape into shitcoins. If transaction data is not made available, we can’t know our account balances, and will be unable to interact with the rollup anymore.</p><p>Notice that the above lets us see exactly why people keep shilling rollups. Given full nodes don’t have to be able to keep up with the sequencer, why not just make it a very powerful computer? This would let the sequencer execute a ridiculous amount of transactions per second, making gas fees low and keeping everyone happy. But remember how the sequencer needs to make transaction data available? This means that even if the sequencer were an actual supercomputer, the number of transactions per second it can actually compute will still be limited by the data throughput of the underlying data availability solution/layer it uses.</p><p>Put simply, if the data availability solution/layer used by a rollup is unable to keep up with the amount of data the rollup’s sequencer wants to dump on it, then the sequencer (and the rollup) can’t process more transactions even if it wanted to, leading to higher gas fees like we see in Ethereum today.</p><p><strong>This is exactly why data availability is extremely important — guaranteeing data availability allows us to ensure rollup sequencers behave, and maximizing the data space throughput of a data availability solution/layer is crucial if rollups are to maximize their transaction throughput.</strong></p><p>But you, the observant reader, might realize that we haven’t actually fully solved our problem of ensuring sequencers behave. If full nodes of the “parent” blockchain on which the rollup settles do not need to keep up with the sequencer, the sequencer can choose to withhold a large portion of transaction data. How can nodes of the parent blockchain enforce that sequencers actually dump the data on the data availability layer — if nodes can’t enforce this, we haven’t actually made any progress with scalability at all because we would then be forced to trust sequencers or to all buy supercomputers ourselves!</p><p>This problem is known as “The Data Availability Problem.”</p><h4><strong>Solutions to “The Data Availability Problem”:</strong></h4><p>The obvious solution to the data availability problem would just be to force the full nodes to download all the data dumped by the sequencer onto the data availability layer/solution — but we know this gets us nowhere since it would require the full nodes to keep up with the sequencer’s rate of transaction computation, thereby raising the hardware requirements of running a full node and worsening decentralization.</p><p>It is therefore clear we need a better solution to this problem, and we do have one!</p><h4>Enter Data Availability Proofs:</h4><p>Every time the sequencer dumps a new block of transaction data, nodes can “sample” that the data was indeed made available by the sequencer using something called a data availability proof.</p><p>How these data availability proofs actually work is very math-y and jargon-y, but I’ll try my best to explain anyway (<a href="https://zeroknowledge.fm/151-2/">h/t John Adler</a>).</p><p>We can first require that the block of transaction data dumped by the sequencer be erasure-coded. This basically means that what would have been the original data is doubled in size, and then the new/extra data is encoded with redundant pieces (this part is what we call the erasure code). By erasure coding the data, we can recover the entirety of the original data with any arbitrary 50% of the erasure-coded data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*IQJvNd8s9LPEPu41" /><figcaption>Erasure-codes are the same technology that allows you to continue abusing your annoying cousin and his friends in Fortnite even after that time you startled the cat</figcaption></figure><p>Notice, though, that by erasure coding the block of transaction data, this would require a misbehaving sequencer to withhold more than 50% of the block’s data. If the block had not been erasure-coded, the sequencer could have misbehaved by just withholding 1% of the data — so by erasure coding the data, we already have a big improvement in the confidence levels full nodes can have that the sequencer is indeed making data available.</p><p>Obviously, though, we want as much of a guarantee that the sequencer is making all the data available as possible. Ideally, we want to be as confident as we would be if we had downloaded the entire block of transaction data directly — and indeed, this is possible: full nodes can randomly choose to download some piece of data from the block. If the sequencer was misbehaving, the full node would have a &lt;50% chance of getting fooled, i.e. of randomly downloading a piece of data that is indeed there when the sequencer is trying to withhold data. This is because if the sequencer was trying to misbehave and withhold data, remember that they would have had to withhold &gt;50% of the erasure-coded data.</p><p>Notice, that this means that by doing the above again, full nodes can drastically reduce the likelihood of getting fooled. By randomly choosing another chunk of data to download a second time, the chance of getting fooled would be &lt;25%. In fact, by the seventh time a full node tries to randomly download a chunk of data, the chance of it failing to detect that the sequencer is withholding data would become &lt;1%.</p><p>This process is called sampling with data availability proofs, or, just data availability sampling. It is incredibly efficient because it means that a node can download just a small portion of the full block of data published by the sequencer on the parent blockchain and have guarantees that are essentially identical to downloading and checking the entirety of the block (the node can use merkle roots on the parent blockchain to find what/where to sample). Just to make sure I am really hammering this point home here: imagine if going for a 10 minute stroll around the neighborhood burns as many calories as going for a 6 mi/10 km run. That’s how groundbreaking data availability sampling is!</p><p>By giving full nodes of the parent blockchain the ability to do data availability sampling, we have now solved our earlier dilemma of how we can ensure that rollup sequencers do not misbehave. We can now all be happy because we can be confident that rollups are indeed able to scale our favorite blockchains — but wait, before you close this tab and find better uses of your time than watching me struggle to translate nerd-speak into plain English, remember how we still need to find a way to scale data availability itself? If we want blockchains to onboard the world’s population so our bags can be pumped (pls ser, mi famiglia), we need rollups; and if we want rollups to scale blockchains, we need to not only neuter the ability of sequencers to do evil, we must also scale data space throughput so that sequencers have a cheap place to dump their transaction data.</p><h4>Data Availability Proofs are also the key to scaling data space throughput:</h4><p>Currently, the most notable L1 with a roadmap focusing on scaling data space throughput is Ethereum. Ethereum hopes to do this through data sharding, which essentially means that not every validator will continue to download the same transaction data as nodes do currently (validators also have to run nodes). Instead, Ethereum will essentially split its network of validators into different partitions called “shards.” Let’s say Ethereum has 1000 validators that currently store the same transaction data, if you split them into 4 groups of 250 validators each that will now store different data, you will then have suddenly 4xed the amount of space available for rollups to dump data! Seems simple enough, right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1h4G5q72_gbKtoDY.jpg" /><figcaption>Ethereum is shooting for 64 data shards in its “near-term” data sharding roadmap</figcaption></figure><p>The problem, however, is that validators within a shard will only download and store the transaction data that is dumped to their shard. But this means validators within one shard won’t have guarantees that the entirety of the data dumped by a sequencer was indeed made available — they would only have guarantees that the data dumped to their shard was made available, but not that the rest of the data was made available to other shards.</p><p>This means we run into a situation where validators in one shard cannot be sure that the sequencer was not misbehaving because they do not know what is happening in other shards — this is where our friend data availability sampling comes in handy again. If you are a validator in one shard, you can simply sample for data availability using data availability proofs in every other shard! This will give you essentially the same guarantees as if you were a validator for every shard, and thereby allowing Ethereum to safely pursue data sharding.</p><p>There are also other blockchains that are hoping to scale to massive amounts of data space throughputs, namely Celestia and Polygon Avail. Unlike most other blockchains, both Celestia and Polygon Avail seek to do only 2 things: order blocks/transactions, and to be a data availability layer. This means that to keep Celestia/Polygon Avail’s validators honest, all that is important would be to have a decentralized network of nodes that ensure that their validators are indeed storing and ordering transaction data correctly. But since this data does not need to be interpreted (i.e. executed/or computed), you don’t need to be a full node to have guarantees that the validators are behaving! Instead, a light node that performs data availability sampling would have essentially the same guarantees as a full node has, and having many light nodes sampling with data availability proofs would be sufficient to hold validators accountable in guaranteeing data availability. This means that so long as there are enough nodes that are sampling for data availability using data availability proofs (and this is easy <a href="https://twitter.com/musalbas/status/1480901457633239048?s=21">given data availability proofs can be computed even by phones</a>), you can make block sizes bigger and increase the hardware requirements of validators, thereby increasing data space throughput.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*3oOq9fYJu0jyCsIccjloNg.jpeg" /></figure><p>Now, to recap: the data availability problem is perhaps the crux of the blockchain trilemma, impacting all of our scaling efforts. Luckily, we are able to solve the data availability problem through the core technology of data availability proofs. This allows us to scale data space throughput massively, giving rollups a cheap place to dump enough transaction data to process enough transactions to onboard the global population. Moreover, data availability proofs mean we don’t have to trust rollup sequencers, and that we can keep them honest and verify they are behaving instead. This hopefully now helps you understand exactly why data availability is so crucial for rollups to reach their full potential.</p><p><strong>Want to go deeper? I’d suggest the following rabbit hole:</strong><br><a href="https://arxiv.org/abs/1809.09044">The original paper which proposes a fraud and data availability proof system to increase light client security and to scale blockchains (by Mustafa Al-Bassam, Alberto Sonnino, and Vitalik Buterin)</a></p><p><a href="https://github.com/ethereum/research/wiki/A-note-on-data-availability-and-erasure-coding">More accessible and shorter version of the above</a></p><p><a href="https://ethereum-magicians.org/t/a-rollup-centric-ethereum-roadmap/4698">A rollup centric roadmap for Ethereum</a></p><p><a href="https://www.youtube.com/watch?v=r0jtV9mxdI0">Scaling ETH in 2020 and beyond — a talk by Vitalik</a></p><p><a href="https://zeroknowledge.fm/151-2/">Podcast with John Adler on the Data Availability Problem</a></p><p><a href="https://zeroknowledge.fm/208-2/">Podcast with Ismail Khoffi on Celestia</a></p><p><a href="https://soundcloud.com/daniel-goldman-84321635/data-sharding-roadmap-a-rollups-perspective">Recording of a Twitter Space with zkSync’s Angela Lu, Arbitrum’s Daniel Goldman, and Fuel Labs’ John Adler giving us a Rollup’s Perspective on Ethereum’s Data Sharding Roadmap</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80c2c95ded0f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blockchain-capital-blog/wtf-is-data-availability-80c2c95ded0f">WTF is Data Availability?</a> was originally published in <a href="https://medium.com/blockchain-capital-blog">Blockchain Capital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Right-Click Utilize]]></title>
            <link>https://medium.com/blockchain-capital-blog/right-click-utilize-b5c5a8530511?source=rss-7c0f39cb0fa2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5c5a8530511</guid>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Yuan Han Li]]></dc:creator>
            <pubDate>Thu, 06 Jan 2022 20:53:12 GMT</pubDate>
            <atom:updated>2022-01-06T20:53:12.696Z</atom:updated>
            <content:encoded><![CDATA[<h4>Building on NFTs with Unicly</h4><h4>The Rise of Virtual Assets</h4><p>Society is becoming increasingly digitally native.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z5QgiybNOE0N0BP53eQCqg.jpeg" /></figure><p>As we spend more of our lives — for both work and play — online, it naturally follows that we will increasingly look to express ourselves in the digital spaces we spend time in using different virtual goods.</p><h3>Rex Woodbury on Twitter: &quot;A virtual Gucci bag in Roblox sold for 350,000 Robux, or about $4,100. The &quot;real world&quot; version of the purse costs $3,400. / Twitter&quot;</h3><p>A virtual Gucci bag in Roblox sold for 350,000 Robux, or about $4,100. The &quot;real world&quot; version of the purse costs $3,400.</p><p>Just as the vast majority of offline physical goods are non-fungible, the same will be true for digital assets — and due to the benefits afforded by public blockchains (innate scarcity and composability), these digital assets will increasingly be manifested as NFTs.</p><p>But as growth in digital economies continues to outpace the analog world, CryptoPunks become bigger flexes than Pateks, and the name “Tyler Hobbs” gradually gets uttered more than “Picasso,” NFTs need to be able to better interoperate and compose with the rest of the metaverse.</p><p>Unicly provides this foundational infrastructure that affords NFTs with greater composability, and that’s why we are excited to have <a href="https://news.bitcoin.com/nft-protocol-unicly-raises-10m-led-by-blockchain-capital-and-animoca-brands-before-the-launch-of-v2/">co-led Unicly’s strategic round</a>.</p><h4>Fractionalizing NFTs</h4><p>Fractionalizing something is exactly what it sounds like: you take something whole and split it into many identical pieces (or fractions). For NFTs, this is a godsend: the non-fungibility of NFTs makes them notoriously illiquid, but by fractionalizing it into many fractions, each piece (and therefore the NFT itself) becomes fungible and liquid. As such, we get the best of both worlds: an asset that is unique but whose constituent components are fungible and liquid.</p><p>Unicly’s v2 protocol enables anyone — individuals, communities, and DAOs — to fractionalize collections of unique NFTs,<a href="https://medium.com/unicly/whats-next-for-unicly-1e31eedc18ea"> and by setting an individual “reserve price” for each constituent NFT, any NFT can still be unfractionalized easily</a>. Unicly’s AMM then enables anyone to trade these fractions.</p><p>Unicly is therefore unique in that it is sufficiently expressive to fractionalize everything from high-valued individual NFTs, to collections of floor NFTs, to collections of disparate NFTs. By optimizing for any arbitrary set of NFTs, Unicly is the ideal infrastructure for NFTs — it can be used to make NFTs useful in financial applications that require fungibility and liquidity, or it can be used to enable true collective ownership for investment/collector DAO. In open-source software, easily generalizable building blocks can often unlock rich new sets of use cases.</p><h4>Applications</h4><p><em>DAO Tooling<br></em>2020 was the year of DeFi, 2021 NFTs, and 2022 could be the year of DAOs. Unicly started off as NFT infrastructure but may find its most successful use case as a toolkit for DAOs.</p><p>Currently, many DAOs suffer from points of centralization. DAO-owned assets are often controlled by the founder or by a small number of wallets. The community may vote on decisions, but that does not equate to having real ownership rights. Even assuming that the DAO founder acts with the best of intentions, its members may still not be conferred true property rights. For instance, if the founder gets hit by a bus, do his heirs or DAO members have claim over the assets? A DAO’s assets should ideally be non-custodial and offer guaranteed on-chain governance and ownership rights. This is specifically the type of tooling that Unicly provides.</p><p>NFT fractions created under Unicly act as both representations of fractional ownership and as governance tokens. If they vote to dissolve the vault and receive the sales proceeds, this right is guaranteed on-chain and requires no input from the founder of the DAO.</p><p>Unicly also has other features that make it particularly well suited to supporting DAOs. NFTs can be injected into Unicly vaults retroactively, which gives DAOs time to distribute the governance token while simultaneously offering community members time to vote on which NFTs to fractionalize. In addition, whereas most fractionalization platforms restrain the types of NFTs that can be added to a collection, Unicly empowers DAO members by offering the flexibility to add NFTs originating from different contract addresses and across a wide spectrum of pricing points. Truly decentralized decision-making can take time, collective decision-making can lead to unexpected outcomes, and Unicly is here to support the DAOs on this journey.</p><p><em>Financialization<br></em>NFTs are currently unsuitable for use in financial primitives such as lending protocols or asset management products due to their non-fungibility.</p><p>As a refresher, current DeFi lending protocols work by pooling liquidity from many lenders and allowing users to borrow assets from the pooled liquidity at an interest rate determined by some algorithm. To prevent bad debt, borrowers must post collateral and borrow at collateralization ratios above 100% — this has meant that lending protocols can only accept highly liquid assets as collateral. Due to their non-fungibility, and therefore lack of liquidity, NFTs cannot be safely allowed as collateral in these lending protocols. This, however, changes if lending protocols integrate Unicly: in the event of a default, collateral NFTs can be fractionalized then liquidated; moreover, given Unicly’s NFT fractions function as governance tokens for a vault, lenders can also vote to decide exactly how the NFT would be liquidated.</p><p>Similarly, current DeFi asset management products such as indexes must rebalance periodically and do so using integrations with other DeFi protocols. Given most NFTs currently suffer from a lack of liquidity (aside from floor Punks/Apes), rebalancing large index products is currently next to impossible; however, if these NFTs were fractionalized and made liquid, we might all soon be able to easily ape into metaverse real estate indices.</p><h4>Traction</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/745/1*0vma-5mTRBQ4Gu5RNVKzqg.png" /><figcaption>Unicly v2’s new UI</figcaption></figure><p>After a fair launch in May, Unicly now has over 11,000 NFTs locked with substantial liquidity for many of its vaults, demonstrating strong early traction. With v2 improving user experience by shifting the UI to be more marketplace-like, Unicly will become easier and more intuitive to use, allowing the protocol to continue pressing forward on its mission to enable far greater composability for NFTs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5c5a8530511" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blockchain-capital-blog/right-click-utilize-b5c5a8530511">Right-Click Utilize</a> was originally published in <a href="https://medium.com/blockchain-capital-blog">Blockchain Capital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DAO Treasury/Balance Sheet Management]]></title>
            <link>https://medium.com/blockchain-capital-blog/dao-treasury-balance-sheet-management-ce5e96da34ac?source=rss-7c0f39cb0fa2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce5e96da34ac</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Yuan Han Li]]></dc:creator>
            <pubDate>Tue, 15 Jun 2021 22:10:56 GMT</pubDate>
            <atom:updated>2021-06-15T22:10:56.606Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Recommendations and guidance for DeFi protocol DAOs on various instruments that could be used to manage balance sheets/treasuries.</em></p><p><em>Though this heavily abridged version contains many of the key takeaways from the main report, detailed assessments of the many available instruments and their risks are only in the </em><a href="https://docs.google.com/document/d/1KMpbdLdsj3lKo7nsC9HHWtjkBpY1NCP-BqJTf1puiH4/edit?usp=sharing"><em>full report</em></a><em>.</em></p><p>The purpose of any protocol DAO is to manage and govern its protocol in perpetuity. Protocol DAOs therefore need to capitalize themselves in a way that not only ensures their ongoing operations can continue, but also lets them invest in their protocol’s future growth — this is not dissimilar to how corporations think about capitalizing themselves. Much the same as how traditional corporations can use retained earnings, equity, and debt to finance themselves, DAOs also have a similar universe of options:</p><ul><li>Retain protocol revenue and non-operating income generated from treasury assets</li><li>Sell native tokens for stablecoin/ETH/BTC</li><li>Take on debt</li></ul><p>As can be seen in fig. 1, however, many DeFi DAOs hold nearly all their treasury assets in their native token. Given their operating expenses are denominated in USD/fiat, another sustained bear market might force DAOs to sell native tokens at “fire-sale” prices to finance their normal operations. DAOs therefore ought to generate multiple income streams (i.e., protocol revenue and yield from investments) that can cover these operating expenses; but since the treasury will need to have an asset base to generate yield/non-operating income, DAOs also ought to consider conducting token sales or issue debt to create this asset base.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m-Hm2KmoA4FecDhlo5eTvg.png" /><figcaption>Figure 1. Data as of June 11, 2021</figcaption></figure><h3><strong>Retained Earnings:</strong></h3><p>DAOs have two broad avenues for which they can generate income to retain: protocol revenue and non-operating income (i.e., investment returns).</p><p>Though many DeFi projects now understand the importance of having value accrual as part of their tokenomics, not all of their DAOs retain fees/revenue generated by the protocol. For instance, whereas Aave, Yearn, BadgerDAO, and Index Coop all retain protocol revenue generated in their DAO treasury, Sushi, Compound, Uniswap, and Maker currently do not do this. Similar to any high-growth company (and really any corporation since the Age of Discovery) it doesn’t make sense to pay out “dividends” when the ROI from investing in the core business is higher than the cost of capital. Moreover, DAOs ought to also carefully consider the denomination of the income they generate: both Aave and Yearn generate most of their revenue in yield-bearing stablecoins while Index Coop’s revenue is for the most part denominated in the riskier products they create (e.g. DPI and levered “ETFs” on ETH/BTC). As such, DAOs should retain, at the very least, some of the income generated by the protocol they govern and carefully consider what it is denominated in.</p><p>Especially given the size of the treasuries of many of the DAOs, a large portion of DAO income will likely also be non-operating income/investment returns (at least until the protocols mature). Similar to how traditional corporations invest in a number of assets across varying degrees of risk (ranging from risk-free T-bills and low-risk investments in highly-rated debt to higher risk M&amp;A/venture capital), DAOs would do well to look for analogous categories of on-chain assets to diversify their balance sheets into:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GkgC1kYnTLYtVoa_kZ1YtQ.png" /><figcaption><strong><em>(For a detailed survey of some of the protocols/instruments within these categories, considerations when using them, and a comprehensive assessment of their risks — and ways to mitigate these risks — please see </em></strong><a href="https://docs.google.com/document/d/1KMpbdLdsj3lKo7nsC9HHWtjkBpY1NCP-BqJTf1puiH4/edit?usp=sharing"><strong><em>my full report on DAO Balance Sheet Management</em></strong></a><strong><em>).</em></strong></figcaption></figure><p>Currently, even some of the largest protocols are unable to generate enough revenue to cover operational expenses (audits, salaries/payments to contributors, marketing, etc.). <a href="https://github.com/yearn/yearn-pm/blob/master/financials/reports/2021Q1-yearn-quarterly-report.pdf">Yearn, for instance, operates at a loss even after accounting for non-operating income from yield farming</a>. As such, retaining protocol revenue alone is likely to be insufficient to finance operations (at least until these protocols mature). This means that DAOs will likely have to raise additional financing to create a large enough asset base which they can use to generate a return — this also provides a guide to thinking about how much treasuries should divest: assume a reasonable and low-risk ROI, then use budgeting forecasts to backout a “principal” amount of non-native tokens on the balance sheet. Once DAOs establish a position of reserve assets, they can then evaluate several instruments based on their risks and decide on an allocation strategy that minimizes correlations and exposure to any particular point-of-failure.</p><h3><strong>Raising Financing with Token Sales:</strong></h3><p>The obvious route to diversifying the balance sheet and establishing a substantial position in reserve assets would be through a token sale. There are only a small number of avenues DAOs have to do this:</p><ol><li>Open-market sales at spot prices; but this can be bad for token prices.</li><li><a href="https://gov.pooltogether.com/t/ptip-13-revised-treasury-diversification/1049">OTC sales to strategically aligned investors (negotiate a discount to TWAP, lockup, etc.)</a>; however, a badly negotiated deal can disgruntle other tokenholders and it might be difficult to carefully select only those strategic investors who can be helpful long-term partners to the DAO.</li><li>Auction (can whitelist a set of buyers and impose a lockup, or auction off carefully designed KPI options); however, the auction will then need to be carefully designed, and — especially if the structure gets complicated — marketing the auction could also be difficult.</li><li>Financial engineering (e.g., covered calls, collars/its variants, going short on futures/forwards/perps); however, these options will ultimately still amount to a synthetic sale that will impact token prices at some point, and often the more exotic strategies will require paying exorbitant fees to OTC desks (at least until the DeFi derivatives space really matures).</li></ol><p>DAOs should therefore carefully evaluate their specific needs to decide which approach would be best for them. For instance, a given DAO might ultimately decide to pursue a combination of 2 and 3 to bring in a group of value-add investors and also energize/incentivize existing tokenholders.</p><h3><strong>Raising Financing with Debt:</strong></h3><p>As in traditional finance, debt is an alternative and likely to be a cheaper form of financing than pursuing dilutive token sales. Thus, especially for DAOs capable of generating a large amount of treasury income that can be used to amortize/service this debt, issuing debt could be considered as an alternative to token sales.</p><p>Currently, only overcollateralized debt has become commonplace in DeFi. Despite this, the vast majority of DAOs cannot simply go on Compound/Aave/Maker and open a debt position — even if a DAO’s native token can be found on e.g., CREAM or Unit Protocol, the borrow capacity/debt ceiling for the token likely will be insufficient for the DAO’s needs. As a result, most DAOs that wish to take on debt will likely have to issue bonds (zero-coupon and overcollateralized; using e.g., <a href="https://mbroome02.medium.com/uma-project-yield-dollar-101-3c64d27e9ab0">UMA’s yield-dollars</a>) or convertible-debt like instruments (e.g., <a href="https://medium.com/uma-project/treasury-diversification-with-range-tokens-145d4b12614e">UMA’s range tokens</a>), and then auction them off for stablecoin.</p><p>Although there are options for taking on uncollateralized debt (e.g., CREAM’s Iron Bank), this isn’t an option to the vast majority of DeFi protocols. Even for the lucky few protocols who are approved borrowers of CREAM’s Iron Bank, <a href="https://creamdotfinance.medium.com/introducing-the-iron-bank-bab9417c9a">the loans have credit limits and are intended to only be short-term loans for yield farming purposes rather than longer-term loans for DAO-level operational/capital expenses</a>. There is also nothing stopping a protocol from creating unsecured bonds and auctioning these off, promising to airdrop holders interest payments at predetermined intervals; however, as with all instances where DAOs are given access to unsecured/secured credit, without guarantees on a repayment process/recourse available to creditors in any event of default, it is probably quite unlikely for under/uncollateralized debt to become commonplace. For instance, whereas TradFi creditors can initiate foreclosure proceedings on debtor companies, which would result in e.g., a Chapter 7/11 bankruptcy in the US, there is no agreed-upon/established practices for creditors in DeFi. Thus, until an on-chain “bankruptcy” process emerges, or another set of practices emerge that formalizes the rights of creditors in the on-chain world, it is probably unlikely for under/uncollateralized DAO debt to proliferate.</p><h3><strong>Conclusion:</strong></h3><p>Given DeFi DAOs are charged with supporting its protocol in perpetuity, managing their balance sheets in accordance with their income/expenses is a crucially important activity. Most protocol DAOs currently only hold their native protocol token on their balance sheets. Given the volatile nature of cryptocurrencies, this could mean that DAOs are forced to sell their native tokens during extended bear markets (and therefore at inopportune prices) to finance ongoing operations. Consequently, DAOs should first ensure that they have a revenue stream that is ideally denominated in a reserve asset, and then if the revenue is insufficient to cover operating expenses, DAOs should consider raising additional financing in reserve assets using token sales/debt. Doing so would then provide protocol DAOs with a large reserve asset base on their balance sheets that can be invested to generate additional non-operating income/investment returns to bridge this gap or provide a “buffer”. Following such a playbook would put any DAO in a much better financial position to maintain their protocols even during multi-year crypto bear markets.</p><p><em>If you enjoyed reading this piece, please check out the full report </em><a href="https://docs.google.com/document/d/1KMpbdLdsj3lKo7nsC9HHWtjkBpY1NCP-BqJTf1puiH4/edit?usp=sharing"><em>here</em></a><em>.</em></p><p><em>Special thanks to Derek Hsue, Kinjal Shah, Aleks Larsen, Mason Vollum, 0xMaki, Stani Kulechov, and Hugh Karp for valuable conversations/feedback!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce5e96da34ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blockchain-capital-blog/dao-treasury-balance-sheet-management-ce5e96da34ac">DAO Treasury/Balance Sheet Management</a> was originally published in <a href="https://medium.com/blockchain-capital-blog">Blockchain Capital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>