<?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 LongHash Ventures on Medium]]></title>
        <description><![CDATA[Stories by LongHash Ventures on Medium]]></description>
        <link>https://medium.com/@longhashvc?source=rss-7be833512009------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JZwJxWMV5fFSy4xsTHPoGA.png</url>
            <title>Stories by LongHash Ventures on Medium</title>
            <link>https://medium.com/@longhashvc?source=rss-7be833512009------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 06:08:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@longhashvc/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[Why we invested in Zero Gravity (0G)]]></title>
            <link>https://longhashvc.medium.com/why-we-invested-in-zero-gravity-0g-3561663bdff0?source=rss-7be833512009------2</link>
            <guid isPermaLink="false">https://medium.com/p/3561663bdff0</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[data-availability]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[LongHash Ventures]]></dc:creator>
            <pubDate>Tue, 09 Apr 2024 22:24:42 GMT</pubDate>
            <atom:updated>2024-04-09T22:24:42.438Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1006/1*k4RpnYYU0PO0tTjG7kvOog.png" /></figure><h3><strong>What the </strong>Ethereum Roadmap has to do with the first <strong>Modular AI Chain</strong></h3><p>Crypto stands at the brink of a quantum leap. For the first time in history, high-performance applications may live on-chain: AI, gaming, and order books included. In particular, at the intersection of AIxWeb3 lays the conundrum of providing scalable infrastructure to the most performance-demanding AI applications.</p><p>Sam Altman from Worldcoin has said during a private gathering that “one of the missions of Worldcoin is to ensure that AI remains humanity-aligned.” Six decades ago, Isaac Asimov proclaimed that “Science gathers knowledge faster than society gathers wisdom.”</p><p>Having AI models on-chain is the best way for humanity’s wisdom to grow as AI gains unprecedented capabilities. Unblocking the performance requirements of such a feat, is where ‘modularity’ comes in.</p><p>Modularity is at the heart of the Ethereum roadmap. For good reason. By delineating a monolithic blockchain into consensus, execution, and DA (data availability), each layer could scale independently while retaining composability.</p><blockquote><em>“0G is at its essence a new category of DA Modular Chain, that inherits security from Ethereum as an attested sovereign L1 and finds utility as a Modular AI Chain”</em></blockquote><p>Similar to the Ethereum Foundation’s roadmap adjustment from full sharding towards a rollup-centric architecture, we believe that Ethereum’s DA Layer will find itself blossoming into multiple modular DA chains. Zero Gravity is pioneering as the default DA chain for high-performance execution environments.</p><h3><strong>State of data availability</strong></h3><p>A separate Data Availability space was a crucial component in the rollup-centric roadmap of Ethereum from the very beginning, as mentioned by Vitalik in his recent <a href="https://vitalik.eth.limo/general/2024/03/28/blobs.html#:~:text=From%20the%20very%20beginning%2C%20a%20key%20piece%20of%20the%20rollup%2Dcentric%20roadmap%20was%20the%20idea%20of%20separate%20data%20availability%20space">blog</a>. The recently implemented Dencun upgrade enabled EIP4844. EIP4844 allows a special section of space in a block to hold data for rollups and sets up the basic scaffolding for implementing DAS in the future. However, EIP4844 itself is designed to limit blobspace to 384kb per blob (roughly 0.083Mbps), to persist data for only 4096 epochs (roughly 18 days), and doesn’t offer DAS proofs yet. Suffice to say, 4844 and full danksharding, were never meant to be the end-all-and-be-all for DA. We believe that the Ethereum Foundation will embrace a DA rollup-centric architecture, as it did for execution.</p><p>Celestia, EigenDA, and Avail have also made significant progress on the DA layer. But the growth in the number of L2s and decentralized AI applications warrants significantly more performant and comprehensive DA solutions. Current solutions do ensure the availability of data, but fast retrieval of data is currently not feasible which limits the scope of applications that can be built on top. Innovations at the execution layer such as parallel processing can support significantly higher orders of magnitude of transactions per second. However, the DA layer should be able to propagate more data per second to nodes in order to reach consensus and ensure availability of data. Since EigenDA is not a blockchain but a set of smart contracts that run on Ethereum, it inherits the same finality time as Ethereum i.e 12 to 15 minutes. DA verification can take time when using a fraud-proof-based approach like in the case of Celestia. See the full comparison chart below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/737/1*-kP4GCruBnRoWotIb80VjQ.png" /></figure><h3><strong>How does Zero Gravity address the DA pain point?</strong></h3><p>ZeroGravity is building the most performant, scalable, and secure data availability solution. Instead of injecting entire data blocks into the consensus system and storing them on full nodes, 0G is building the data availability layer directly on top of a decentralized storage system that supports various data types including transactions, key-value, blobs (text, pictures, voice, documents), and metadata logs.</p><h4><strong>Performance:</strong></h4><p>Zero Gravity’s data availability layer and the data storage layer have different consensus networks. This separation enables the heavy lifting of data transfers to occur within the storage layer, which can horizontally scale through strategic partitioning. To ensure data is reliably available, a consensus on data availability sampling (DAS) is reached by the majority of validators.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZtCsZH5B64T-_r_NJ5vMHg.png" /></figure><p>Parallelized block production further augments the performance. To reduce the limitations imposed by authenticated storage access, 0G minimizes the number of disk I/O operations by using a novel data structure instead of MPT (Merkle Patricia Trie).</p><h4><strong>Security:</strong></h4><p>To ensure the highest level of security, the validity of the erasure encoding used by 0G is proved on Ethereum via validity proofs and KZG commitments. 0G has its own consensus with blocks stored on 0G and verified on Ethereum L1. The KZG ceremony for Ethereum happened in 2023 with 141,416 contributions, allowing EIP 4844 to be implemented in the Dencun upgrade and paving the way for Danksharding in the future. By using the same ‘powers of tau’ secret from Ethereum’s KZG ceremony, 0G achieves KZG robustness parity with Ethereum, a benefit that puts it way ahead of competing DA solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/0*HLcG-XpLc1LT0StZ" /></figure><p><em>Michael with the AI and 0G community at his Alma Mater, Stanford University</em></p><p>Fundamentally, 0G is a L1 that is attestable to Ethereum L1, with its own consensus mechanism and data storage layer. This unprecedented architecture is unique to DA layers and allows 0G to scale DA just like Ethereum scaled its execution through Layer2s.</p><p>Through these innovations in the architectural design, 0G exponentially lowers the storage and retrieval costs and offers the highest data propagation speed without impacting security.</p><h3><strong>Modular AI Chain</strong></h3><p>By combining speed and cost efficiency, 0G is exceptionally well-positioned to become the de facto infrastructure layer for the burgeoning ecosystem of advanced, high-performance on-chain AI applications. Already, 0G has announced start of partnerships with Modulus Labs and Ora Chain, with more to be unveiled.</p><p>Aiming to democratize access to AI technology and foster a more collaborative AI development environment, 0G offers high-throughput data storage and retrieval. This capability enables the on-chain storage of Large Language Models (LLMs), metadata, and training data. Additionally, large inference traces can be stored on-chain, empowering on-chain applications to process inference requests. Developers will be able to add ML capabilities to existing smart contracts, making them more autonomous and capable of making decisions based on real-time on-chain data. While the full spectrum of advantages and capabilities unlocked by transitioning the AI stack to an on-chain environment is early to fully envision, the potential it holds is undoubtedly exciting.</p><p>0G is solving most of the pain points of AI applications, but it is also capable of supporting the growing number of L2s, app-chains, and the most demanding high-performance applications like data marketplaces, RWA apps, on-chain gaming, high-frequency DeFi, on-chain order books and many more.</p><h3><strong>The perfect team to build this</strong></h3><p>We first met Michael at Stanford BASS, and knew then that he was a one-in-a-million founder. Not only is he an accomplished builder (YC best company) and a revered lecturer (at Stanford), but he also carries the ethos of Web3 in welcoming the community into infinite scalability. Garten, Michael’s previous venture, was dedicated to enhancing people’s lives by promoting health and well-being, which emerged as a Top YCombinator company. Before all of that, Michael rose through experiences at Bain, Bridgewater, and Microsoft. Few founders carry the deep exposure to web2 and combine it with the ethos of web3 like Michael does. As an interesting twist, Michael’s nickname is Kungfu Panda, for having practiced Kungfu at the Shaolin Temple. The community was quick to meme.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UW6Vlu78eMqcaf-to0aRdA.png" /></figure><p><em>OG (0G) Kungfu Pandas from the community</em></p><p>Ming and Fan were part of the founding team at Conflux, a permissionless public blockchain. Ming’s research work spans topics such as efficient authenticated storage for blockchain to boost throughput and expedite read/write operations, abstractions for storing and accessing application metadata, and frameworks to support efficient and scalable parallel neural network computation on graphs. He has published papers on top conferences in computer systems such as SOSP, OSDI, NSDI, ATC, EuroSys, SoCC, VLDB, etc along with researchers from institutes like Microsoft Research,Cornell University, Tel-Aviv University Peking University, University of Toronto, etc. He also served as the Publication Chair of SOSP’17.</p><p>Led by Michael Heinrich and Ming Wu, the 0G team brings deep expertise in technology, entrepreneurship, cryptography, and product and we believe they are the perfect team to build the first Modular AI Chain.</p><h3><strong>At zero gravity, the moon is the limit</strong></h3><p>Each cycle, crypto evolves as if eons have passed. As crypto natives, we have been yearning for more widely adopted applications. Now that high-performance infrastructure is finally in place, we may just see AI that live on-chain, of the people, by the people, for the people.</p><p>We are thrilled to partner with Michael, Ming, and the stellar team at Zero Gravity to write the next chapter of high-performance infrastructure and applications.</p><p>At zero gravity, the moon is the limit 🚀</p><p>LongHash is a crypto-native venture capital firm since 2017. We invest in and build alongside visionary founders forging the next evolution of the open economy. Follow Roy (<a href="https://twitter.com/0xroylu">x.com/0xroylu</a>) and Raghav (<a href="https://twitter.com/0xRaghav">x.com/@0xRaghav</a>) for cutting-edge research on data availability and AI.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3561663bdff0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Staking, Restaking, and LRTfi: Composable Capital Efficiency and Neutrality (Part II)]]></title>
            <link>https://longhashvc.medium.com/staking-restaking-and-lrtfi-composable-capital-efficiency-and-neutrality-part-ii-47c0a0e60213?source=rss-7be833512009------2</link>
            <guid isPermaLink="false">https://medium.com/p/47c0a0e60213</guid>
            <dc:creator><![CDATA[LongHash Ventures]]></dc:creator>
            <pubDate>Thu, 22 Feb 2024 06:00:29 GMT</pubDate>
            <atom:updated>2024-02-22T06:00:29.320Z</atom:updated>
            <content:encoded><![CDATA[<p><em>We would like to thank Justin Drake from Ethereum Foundation, Amir Forouzani from Puffer, Rok Kopp from EtherFi, Zhuling from Bedrock, Alan Curtis from Rio, Brianna and Sreeram from EigenLayer, Pablo Villalba from Diva, Daniel Dizon from Swell, Kratik Lodha from Renzo, Matthias Ang from SSV, and Max from Obol, for their generous comments and contributions.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qwnvw9BFnvHfullYRuUExw.png" /></figure><p>Contents of this article:</p><ol><li>Composable Capital Efficiency and Staking as Crypto-Native Benchmark Rate</li><li>Technical Deepdive of Staking, Restaking, and LRTfi</li><li>Solving Centralization and Externalities in Re/Staking</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/1*su7Wfvp3RPwhKQJYdofF3g.png" /></figure><p><a href="https://longhashvc.medium.com/staking-restaking-and-lrtfi-composable-capital-efficiency-and-neutrality-part-i-49c7ef21d36d">Link to Article Part I</a></p><h3>Secondary Layer — Restaking</h3><p>The gravitational force pulling in all of crypto.</p><h4>Restaking Mechanisms</h4><p>Restaking has become a gravitational force in crypto. And at its essence, restaking represents modular security.</p><p>Infrastructure such as EigenLayer, Babylon, and Cosmos ICS allow the same tokens to stake on multiple protocols, thereby decentralizing trust beyond their sovereign chains. Through LRTfi, the economic security of one chain, can compose with the economic bandwidth of other chains. The security of multiple chains is interweaving into one meshed network.</p><p>On the positive side, restaking lowers the threshold of launching middleware. Several AVSs are the most highly anticipated launches this year. Because slashing is so rare, economic security may be over-collateralized as things currently stand, and can find additional utility beyond their sovereign chains.</p><p>On the negative side, restaking has seen some controversy due to its externalities. An attack on a foster chain can lower the economic security of its parent chain. Vitalik has openly conveyed that Ethereum should not be expected to fork if for some reason validators face externalities from restaked middleware:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*j4tugM-VrFGoxzxMEAw62g.png" /></figure><p>Across ecosystems, we are seeing innovation in restaking in the 1:1, 1:N and N:N models. Tokens with strong fundamentals, such as Bitcoin, Ethereum, and Solana will likely find middleware willing to adopt its economic security.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HKJHwUVf8F8qXlv0JZBTPg.png" /></figure><p><strong>Babylon</strong></p><p>Babylon allows the restaking of BTC to PoS chains. This feat is enabled by two key innovations: merged mining and ingenious use of Bitcoin opcodes.</p><p>Through merged mining, the same miner can mine for both Bitcoin and Babylon blocks, as long as they use the same signature, at no additional energy cost. Babylon blocks are sent to Bitcoin blocks as a transaction, thereby making Bitcoin the ultimate DA layer. To enable bonding, withdrawal, and slashing, Babylon uses Bitcoin opcodes to support four transactions, ‘staking transaction’, ‘unbonding transaction’, ‘slashing transaction’, and ‘unstaking transaction’.</p><p><strong>EigenLayer</strong></p><p>In Eigenlayer, Ethereum and ERC20 tokens are restaked on middleware services, dubbed as AVS (actively validated services).</p><p>A ZK proof is generated to validate that a particular EigenLayer validator belongs to the associated validator on the Beacon Chain. An EigenPod is instantiated for each validator. Once a state root proof is verified along with a ZK proof provided through an Oracle, the validator can fully restake their ETH to AVS and start to receive rewards. Several interesting edge cases occur, if a validator is slashed on the Beacon Chain, anyone can then call the EigenPod.verifyBalanceUpdate and the pod Owner pays the negative shares.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GNEoodVGH_Dbcias2hnlRA.png" /></figure><h4><strong>Liquid Restaking Tokens</strong></h4><p>LRTs showcase modular security. They allow the same token from one chain’s economic security to participate in other chains’ economic security and bandwidth. As a novel asset class, LRTs have distinct and advantageous features:</p><ul><li><strong>Stability—</strong> LRTs are relatively stable because they are redeemable for the underlying ultrasound tokens such as Bitcoin, Ethereum, and Solana.</li><li><strong>Capital Efficiency —</strong> LRT holders generate yield from staking and restaking at once, and can partake in DeFi activities for additional yield, which we’ll come back to later. While yield from restaking is difficult to estimate, researchers placed the yield at an additional 1% per annum and LRT protocol builders at 3–4% per annum. Highly anticipated AVSs such as Polyhedra, Witness Chain, and Lagrange may surprise. It should be noted, that LRT holders expect airdrops from EigenLayer and AVSs, further incentivizing TVL accumulation. Currently, LRT protocols offer reward points that may be redeemable for protocol tokens soon.</li><li><strong>Convenience —</strong> LRT pools abstract away the complexity and risk management of selecting specific foster chain validators, so that stakers can participate in restaking with minimal mental overhead. Users can simply make decisions on where to restake based on risk-adjusted APY. Running, maintaining, and evaluating client software for AVSs is a complex task, LRT pools take on this task with the additional benefits of smoothing and insurance.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/989/1*NbRmMIaTJuIFO1EQ_2Ehdg.png" /></figure><p>LRT protocols, such as EtherFi (eETH), Rio, Bedrock (uniETH), Puffer (pufETH), KelpDAO (rsETH), Renzo (ezETH), and Swell (rswETH) have demonstrated the appeal of restaking by bootstrapping billions of deposits within a matter of weeks. Of the breadth of protocols, they mainly differ along the vectors of native vs LST restaking, withdrawal enablement, signer protection, and reward mechanism.</p><p>EtherFi, is a native restaking protocol, with DVT implemented and withdrawals enabled, which are features aimed at optimizing user experience. Puffer offers native restaking and is unique in its usage of the secure signing module. Bedrock, launched by professional node operators, offers native restaking, allows withdrawals and differs in its non-rebasing reward mechanism. Rio, Kelp, and Renzo are also native restaking protocols with their own network of validators and EigenPods.</p><p>EigenLayer altogether attracted over $6B in TVL and some of the strongest teams to build on its AVSs, pointing to promising developments in a Cambrian explosion of decentralized non-Nakamoto chains.</p><p>In Cosmos, replicated security distributes 25% back to ATOM holders for the security it provides. While the overall yield is similarly hard to estimate given how early this space is, ATOM holders would slowly accumulate consumer zone tokens and accrue governance voting power.</p><p>In Solana and Bitcoin, restaking is still at an early stage, and we are excited to see these trends develope and mature.</p><p><strong>Slashing</strong></p><p>Slashing puts a twist on an otherwise seemingly straightforward restaking platform. With slashing, sometimes neutrality can be at risk. As an example, a validator could ransom attack its stakers, “Hey if you don’t pay me ETH, I will cause a slashing event”. Game theoretically, the staker would pay up to the full ransom amount. Of course, there are solutions to mitigate this, which we’ll come back to.</p><p>While EigenLayer’s current slashing mechanism is not finalized and may be delegated to individual AVSs, its withdrawal mechanisms are and act as a layer of defense. Essentially what would need to happen is when a validator commits a slashable offense, its ETH collaboral on the Beacon Chain would need to be decreased accordingly. By design, validator withdrawal credentials point at EigenPods, so that EigenLayer can complete the accounting including any penalties before a validator can withdraw its funds.</p><p>Cosmos Replicated Security has its own set of slashing rules and perhaps sets a benchmark for the restaking vertical. Downtime is punishable by 10 minutes of removal from the validator set and 0.01% of the validator’s fund. A slap on the wrist. Slashing is punishable by tombstoning, a permanent removal of the validator, and 5% of the funds. To prevent impact on Cosmos Hub by faulty or compromised consumer chains, a slash throttle is in place so that not too many Cosmos validators can be slashed at once. This is important because a sudden drop in the staked amount could open up the network to 51% attacks if the staked amount drops below TVL.</p><p><strong>Withdrawal</strong></p><p>On EigenLayer, withdrawal credentials for native ETH staking are held by the EigenPod. So that when a withdrawal event occurs, Eigenlayer can finish all of its accounting, net of yields and penalties, before the validator can withdraw its staked ETH. There is a withdrawal period of 7 days. However, with LST restaking, the mechanism is different and potentially more fluid.</p><p>Cosmos has a variety of restaking mechanisms. In Stride, withdrawal is instant. In Persistence and Quicksilver, unbonding is dependent on the native chain. In Cosmos Hub replicated security, ATOM holders will govern the inclusion of consumer zones. If ATOM holders wish to withdraw from a consumer chain, they could unstake their ATOM which requires a 21-day cool-down period. If Cosmos Hub wishes to stop support for a consumer chain, a two-week voting period requiring a 40% quorum will need to take place.</p><h3>Tertiary Layer — LSTfi and LRTfi</h3><p>With heavy competition amongst liquid re/staking protocols, composability is a key feature that LST and LRT protocols lean on to gain market share. DeFi users prefer highly composable LSTs, such as Lido’s stETH, which affords deeper liquidity. These LSTs/LRTs can be deployed across DeFi protocols like DEXes and lending platforms, to boost returns significantly. Therefore, competitors challenge the dominance of stETH in DeFi by focusing their efforts on BD to build out a strong DeFi ecosystem for their LST/LRT.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h7W7bbUDH85JwdTk9pm_CQ.png" /></figure><p>The chart below shows the effect of additional yield generated from utilizing LST in various DeFi strategies; however, as more protocols are utilized to increase yield, the associated risks also increase.</p><ul><li>The first strategy for LSTs is to pair them with ETH in a DEX LP like Curve/Convex to generate additional trading fees and incentive rewards</li><li>The second strategy is to utilize lending protocols such as AAVE to collateralize LST, borrow ETH, swap for more LST, and collateralize more LST to create a leveraged position on the yield-bearing asset</li><li>More exotic protocols like Sturdy allow users to collateralize LP positions, borrow ETH, swap into more LP tokens, and collateralize more LP positions to further increase capital efficiency</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UthvXUBh3zmjtuL3x1LsTg.png" /></figure><p>As shown in the above example, it is possible to increase the capital efficiency of stETH by almost 2x through Curve and AAVE. Capital efficiencies of &gt;2x can be achieved by further stacking yields using a protocol like Sturdy Finance to collateralize on a DEX-like curve. It is possible to get even higher yields on LSTs in DeFi protocols on popular L2s like Optimism and Arbitrum due to the higher trading activity and incentive rewards on L2.</p><h4><strong>Risks</strong></h4><p>By composing LSTfi/LRTfi across DeFi protocols, the user also faces the following types of risk depending on the protocols used:</p><p><strong>Slashing risk — </strong>Potential slashing risk affects all LST/LRT protocols, although the risk is very low as discussed in Part I and node operators are mostly professional. However, loss of capital due to slashing can happen. For example, Lido has had multiple <a href="https://twitter.com/LidoFinance/status/1647150450221936646">slashing events</a> with some of its operators.</p><p><strong>Smart contract risk — </strong>Utilizing LSTs/LRTs across multiple DeFi protocols compounds the smart contract risk since the user is exposed to additional vectors for exploits. As examples, the <a href="https://www.chainalysis.com/blog/curve-finance-liquidity-pool-hack/">Curve finance exploit</a> caused many synthetic ETH pools to be drained and the <a href="https://blog.solidityscan.com/sturdy-finance-hack-analysis-bd8605cd2956">Sturdy finance exploit</a> was attributed to price manipulation of LP tokens to drain the protocol, leading to bad debt.</p><p><strong>Depeg risk — </strong>Even though Beacon Chain withdrawals greatly mitigated depeg risks, the underlying LST/LRT token contract could still be exploited. A depeg can lead to mass liquidations. <a href="https://www.nansen.ai/research/on-chain-forensics-demystifying-steth-depeg">After stETH depegged </a>following the Luna and Celsius collapse in May 2022, cascading liquidations in leveraged stETH positions caused the price of ETH to plummet. Depeg of LST tokens can amplify losses for LPers due to impermanent loss and on concentrated liquidity AMMs</p><p><strong>Restaking risk — </strong>Restaking allows validators who run actively validated services to be slashed if they operate incorrectly or act maliciously. The greater risk of slashing depends on how many services are run per validator. Unintended slashing caused by bugs could lead to cascading slashing across multiple services and validators</p><h4>Innovative diversity in LSTfi/LRTfi</h4><p>There has been an explosion of DeFi protocols tapping into massive pools of liquidity from LSTs/LRTs to unlock new use cases, such as synthetic stablecoins, yield optimization, and yield tokenization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vWVOFTfCaMJnhnJrqlOahw.png" /></figure><p><strong>Synthetic Stables</strong></p><p>With stablecoins being the most popular asset for web3 users seeking stability, many protocols mint decentralized stablecoins from LST collateral.</p><p>Lybra Finance is similar to a CDP protocol like MakerDAO. Lybra’s high collateral ratio of 150% enables it to distribute the staking rewards from the overcollateralized LSTs to all holders of the stablecoin and offer about 25% more yield than the base LST yield (eg. <a href="https://docs.lybra.finance/lybra-finance-docs/overview/introduction-to-the-lybra-protocol/how-does-eusd-generate-interest">Lybra’s eUSD offered ~7% </a>apr when the ETH LST yield was5%). On the other hand, <a href="https://docs.prismafinance.com/">Prisma Finance</a> works with DEXes like Curve and Convex Finance to reward users for staking its stablecoin in DEX LPs.</p><p>However, these protocols are not very capital efficient because of the high collateral ratio and lack of integrations with other DeFi protocols for now due to their early nature. By using perps to hedge the price of the LST collateral for its stablecoin, <a href="https://twitter.com/ethena_labs">Ethena</a> offers a more innovative approach that could be the key to becoming a top decentralized stablecoin. Their approach provides higher capital efficiency, reduced liquidation risk, and could even challenge the dominance of centralized fiat-backed stablecoins.</p><p><strong>LST/LRT Yield Optimization</strong></p><p>Increased yield for LSTs/LRTs is key to attracting TVL. Synthetic ETH and tokenized LST indices are the main forms of yield optimization we are seeing in the market.</p><p>Synthetic ETH protocols take in LSTs or a basket of LSTs as collateral to mint a synthetic version of ETH. Protocols like Alchemix and Zeroliquid offer up to 50% LTV to borrow synth ETH and use the yield on LSTs to pay down the debt on self-repaying loans. Cat-in-a-box allows users to repay loans with the yield or generate additional yield depending on the LTV <a href="https://docs.catinabox.finance/docs/documents/components">(higher health gives boosted yield)</a>. The main use case for Synthetic ETH is to LP them in DEXes for additional trading fee income. It also gives an arbitrage opportunity for users on the peg of the assets. However, it should be noted, that synthetic ETHs minted from these protocols are often volatile and trade below ETH peg which can lead to high impermanent loss for LPers</p><p>For users who want to avoid the hassle of using multiple DeFi protocols, LST index products like <a href="https://yeth.yearn.fi/">Yearn’s yETH</a> and <a href="https://unsheth.xyz/">unshETH</a> are simple and relatively safe ways to boost yield. LST indexes are a basket of LSTs pooled together into an AMM to facilitate easier deposits/withdrawals and rebalancing. The yield optimization is achieved by setting the weights of the LSTs in the index, with higher-yielding LSTs like sfrxETH and swETH representing a larger part of the index. In addition to LST incentives, users also receive yield from swap fees within the AMM as people withdraw/deposit LSTs.</p><p><strong>LST/LRT Yield Tokenization</strong></p><p>Interest rate swaps in TradFi are used to lock in and hedge against volatile interest rates for borrowers. Protocols like Pendle and Flashstake enable similar functionality on LSTs/LRTs in web3.</p><p><a href="https://twitter.com/pendle_fi">Pendle</a> allows DeFi users to split yield-generating assets like LSTs into two components, the principle token which can be redeemed 1:1 for the underlying asset upon maturity and the yield token which receives the yield of the underlying asset. This allows users to perform various strategies on LSTs such as locking in fixed yield on LSTs for stability, arbitrage on the yield and principle tokens for profit, or generating more yield by providing liquidity to pools of principle and yield tokens which have minimum impermanent loss due to their price correlation.</p><p><a href="https://flashstake.io/">Flashstake</a>, another yield tokenization protocol, allows users to deposit yield-bearing LSTs into the protocol to mint time-based tokens (TBTs). These TBTs are a special ERC-20 token that represents the total yield of the assets deposited in a vault. The most common use case for LSTs with Flashstake is to instantly redeem the TBTs from staking an LST to collect the upfront yield from LSTs.</p><h3>Solving Centralization and Externalities in Re/Staking</h3><p>Preserving protocol integrity, one line of code at a time</p><h4>Centralizing and Externalizing Forces</h4><p>Composability of LSTs/LRTs is a centralizing force. The more protocols that offer composability to certain LSTs, the more demand for those LSTs; it’s a continuous feedback loop that concentrates liquidity. To make matters worse, solo stakers may at one point find their yield dip below hardware costs. If solo stakers withdraw from the protocol, decentralization suffers.</p><p>For restaking, risks around externalities exist. If a protocol with restaking causes a massive slashing event, Ethereum staked amount could fall drastically thereby opening it up for attacks. Vitalik has expressed that Ethereum would not fork to bail out large restaked AVSs.</p><p>Luckily, projects are making strides toward preserving decentralization and upholding neutrality. EigenLayer hosts governance votes to include more LSTs into its protocol, thereby increasing decentralization. Lido is adding permissionlessness to its protocol by introducing a staking router to allocate stakes across a variety of validator sets. LRTs pools are exploring the usage of DVT to minimize externalities introduced by restaking. These are directions we are delighted to see.</p><h4><strong>Actionable Solutions</strong></h4><p>For now, risks around centralization and externalities exist and must be mitigated. There are several potential solutions that we are excited about:</p><p><strong>Execution Tickets to Counter Centralization of Validators — </strong>Beacon validators simply proposes inclusion lists and validate such lists, while execution validators can run beefier machines. In this architecture, consensus clients can remain light and decentralized.</p><p><strong>Cap Liquid Staking Using EIP4788, ZK-bridges, or Engine API</strong> <strong>—</strong> whereas the current approach to cap staking pools below the Sybil threshold is community-driven, there’s an opportunity to leverage ZK-bridges or Engine API to trustlessly transfer data from the execution layer back to the consensus layer to keep staking pools below Sybil threshold.</p><p><strong>Simplify Developer Tooling for Solo Stakers —</strong> A DEPIN-style project could be interesting, where a provider sells prepackaged hardware sets with preinstalls of client software to make onboarding new solo stakers as seamless as possible.</p><p><strong>Reputation System for Node operators —</strong> node operators could be rated on vectors of neutrality and code integrity. This is minimally effective as mass slashings are black swan events and reputation systems are not very effective against black swan events.</p><p><strong>Enshrined Smoothing Pool for Validators — </strong>we could encourage more solo staking by creating a smoothing pool that generates higher consistent yield on par with quasi-decentralized staking pools. Ethereum Foundation perceive smoothing pool as attack surface. However, third parties could build one as part of the PBS architecture.</p><p><strong>AVS and LRT Slashing Throttle—</strong> learning from Cosmos, we’d like to see AVS operators and LRT protocols implement real-time slashing throttles to prevent mass slashing events from spilling over to Ethereum. Further, LRT protocols could prioritize AVSs with dual staking and cascade the slashing of AVS tokens first and ETH second.</p><p><strong>Enshrinement of LST</strong>: the composability of enshrined LST could massively benefit solo stakers to enjoy the economic bandwidth that current LST holders enjoy. On smart contract risk, already the deposits for staking on the Beacon Chain sits on a single smart contract in the Execution Layer, so an additional smart contract that mints LSTs doesn’t introduce much additional risk. However, this does add a large burden on EF for maintenance with an already busy development roadmap.</p><p>Case in point on Ethereum Foundation’s keenness to democratize node operations: Portal Network pushes the frontier to modularize and decentralize node operations across three RPC networks: Beacon light client, State network, and History network, so that developers can permissionlessly ping the network for their particular RPC use cases, all in a decentralized fashion.</p><p>If you are actively solving for decentralization and neutrality, we’d love to chat with you.</p><p>Initiatives such as the Portal Network, MEV burn, and LST enshrinement render confidence, that despite the various challenges in staking’s centralizing tendencies, we’d find a path forward towards sustained decentralization, permissionless, and neutrality.</p><h3>Conclusion</h3><p>Staking is the foundation of PoS chains. Decentralization and neutrality must be upheld by virtue of the incentives and disincentives around staking, restaking, and LRTfi.</p><p>Staking is the crypto-native benchmark rate. The advent of LSTs/LRTfi opened up composibility based on re/staking yield. Through LSTfi/LRTfi, we get a glimpse of what composability could mean for traditional finance. LSTfi/LRTfi is a hallmark of the benefits of web3 — frictionless, low-minimum, self-custody. These are benefits that could bring tremendous efficiency and open up participation in traditional finance.</p><p>Through first principles thinking, we find that various LSTfi/LRTfi strategies would be evaluated along the vectors of composability and capital efficiency, where risk is a boundary condition.</p><p>Looking a few years ahead, the Primary Layer around staking is maturing in Solana and Polygon, while Ethereum, Bitcoin and Cosmos staking are evolving. In Ethereum, the end game could look one of two ways: oligopoly if Ethereum values are upheld, where top players reach as close as to 33% without breaching it, or, enshrinement of LSTs if Ethereum values are not upheld. The Secondary Layer of restaking is igniting a race to the top of capital flowing toward the highest yield, especially to LRT protocols. EigenLayer AVSs are some of the most anticipated launches this year, and Bitcoin, Cosmos, and Solana retaking are all at the Cambrian stage. At the Tertiary Layer, capital efficiency is bound to be the highest. Protocols would compete along the vector of highest composability and lowest risk.</p><p>An economic stack built on re/staking is all wonderful and great. However, composability and capital efficiency are centralizing forces that could threaten the core values of Ethereum.</p><p>Akin to the tragedy of the commons, individual actors would maximize their composability and capital efficiency, while diminishing the common goods of decentralization and neutrality. However, there are proactive solutions that could be built to mitigate centralization and externalities.</p><p>Alignment with decentralization and neutrality must be the guiding principle and boundary condition within which the staking industry explores its powerful composability and economic prosperity.</p><p>(end of Article)</p><p>Sources:</p><ul><li>Eth Slashing penalty: <a href="https://eth2book.info/capella/part2/incentives/slashing/">https://eth2book.info/capella/part2/incentives/slashing/</a></li><li>Cosmos proposal #187, lambda upgrade <a href="https://forum.cosmos.network/t/proposal-187-accepted-v9-lambda-upgrade-with-replicated-security/8766">https://forum.cosmos.network/t/proposal-187-accepted-v9-lambda-upgrade-with-replicated-security/8766</a></li><li>Rewards: <a href="https://kb.beaconcha.in/rewards-and-penalties">https://kb.beaconcha.in/rewards-and-penalties</a></li><li>Rewards: <a href="https://docs.rocketpool.net/guides/node/responsibilities.html">https://docs.rocketpool.net/guides/node/responsibilities.html</a></li><li>Rocket pool rewards: <a href="https://rocketpool.net/node-operators">https://rocketpool.net/node-operators</a></li><li>Enshrining LSDs: <a href="https://vitalik.eth.limo/general/2023/09/30/enshrinement.html">https://vitalik.eth.limo/general/2023/09/30/enshrinement.html</a></li><li>Eth Beacon docs: <a href="https://kb.beaconcha.in/ethereum-2.0-depositing">https://kb.beaconcha.in/ethereum-2.0-depositing</a></li><li>Polygon validator: <a href="https://wiki.polygon.technology/docs/pos/design/validator/core-components/staking">https://wiki.polygon.technology/docs/pos/design/validator/core-components/staking</a></li><li>Babylon whitepaper</li><li>EigenLayer docs: <a href="https://github.com/Layr-Labs/eigenlayer-contracts/tree/master/docs">https://github.com/Layr-Labs/eigenlayer-contracts/tree/master/docs</a></li><li>Cosmos slashing v9 lambda upgrade <a href="https://forum.cosmos.network/t/proposal-187-accepted-v9-lambda-upgrade-with-replicated-security/8766">https://forum.cosmos.network/t/proposal-187-accepted-v9-lambda-upgrade-with-replicated-security/8766</a></li><li>Vitalik on Zones of Sovereignty: <a href="https://old.reddit.com/r/ethereum/comments/rwojtk/ama_we_are_the_efs_research_team_pt_7_07_january/hrngyk8/">https://old.reddit.com/r/ethereum/comments/rwojtk/ama_we_are_the_efs_research_team_pt_7_07_january/hrngyk8/</a></li><li>EigenLayer LST addition contest: <a href="https://www.blog.eigenlayer.xyz/eigenlayer-lst-addition-contest-in-partnership-with-jokerace/">https://www.blog.eigenlayer.xyz/eigenlayer-lst-addition-contest-in-partnership-with-jokerace/</a></li><li>Lido staking router: <a href="https://docs.lido.fi/contracts/staking-router/">https://docs.lido.fi/contracts/staking-router/</a></li><li>Lido DVT trial: <a href="https://blog.lido.fi/lido-on-ethereum-obol-network-testing-v2/">https://blog.lido.fi/lido-on-ethereum-obol-network-testing-v2/</a></li><li>Portal Network: <a href="https://ethereum.org/en/developers/docs/networking-layer/portal-network/">https://ethereum.org/en/developers/docs/networking-layer/portal-network/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47c0a0e60213" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Staking, Restaking, and LRTfi: Composable Capital Efficiency and Neutrality (Part I)]]></title>
            <link>https://longhashvc.medium.com/staking-restaking-and-lrtfi-composable-capital-efficiency-and-neutrality-part-i-49c7ef21d36d?source=rss-7be833512009------2</link>
            <guid isPermaLink="false">https://medium.com/p/49c7ef21d36d</guid>
            <category><![CDATA[staking]]></category>
            <category><![CDATA[restaking]]></category>
            <category><![CDATA[eigenlayer]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[liquid-staking]]></category>
            <dc:creator><![CDATA[LongHash Ventures]]></dc:creator>
            <pubDate>Thu, 22 Feb 2024 00:56:42 GMT</pubDate>
            <atom:updated>2024-02-23T03:30:55.249Z</atom:updated>
            <content:encoded><![CDATA[<p><em>We would like to thank Justin Drake from Ethereum Foundation, Amir Forouzani from Puffer, Rok Kopp from EtherFi, Zhuling from Bedrock, Alan Curtis from Rio, Brianna and Sreeram from EigenLayer, Pablo Villalba from Diva, Daniel Dizon from Swell, Kratik Lodha from Renzo, Matthias Ang from SSV, and Max from Obol, for their generous comments and contributions.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qwnvw9BFnvHfullYRuUExw.png" /></figure><p>Contents of this article:</p><ol><li>Composable Capital Efficiency and Staking as Crypto-Native Benchmark Rate</li><li>Technical Deepdive of Staking, Restaking, and LRTfi</li><li>Solving Centralization and Externalities in Re/staking</li></ol><p>In this article, we dissect the technical aspects of staking and restaking, while exploring the tension between composable capital efficiency and the value of decentralization. Why capital efficiency? Capital efficiency invites yield-seeking behavior. And PoS chains rely on game theoretic incentives to protect their integrity. A rational node operator would run the most profitable version of client software. By the same token, a rational staker would stake their tokens to maximize their yields and token composability. Successful protocol design would incentivize participants to find Nash equilibrium where protocol security is preserved and where values of decentralization and neutrality are upheld. Studying composable capital efficiency across the staking stack points towards that global Nash equilibrium.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/1*su7Wfvp3RPwhKQJYdofF3g.png" /></figure><p>Link to Part II: <a href="https://medium.com/@longhashvc/staking-restaking-and-lrtfi-composable-capital-efficiency-and-neutrality-part-ii-47c0a0e60213">https://medium.com/@longhashvc/staking-restaking-and-lrtfi-composable-capital-efficiency-and-neutrality-part-ii-47c0a0e60213</a></p><p>In our landscaping, the Primary Layer is maturing in Ethereum, Solana, and Polygon, while Bitcoin and Cosmos staking are evolving. In Ethereum, the end game could look one of two ways: oligopoly if Ethereum values are upheld, where top players reach as close as to 33% without breaching it, or, enshrinement of LSTs if Ethereum values are not upheld. In Cosmos, ICS is in its first inning, and in Solana, staking is at 90%.</p><p>The Secondary Layer of restaking is igniting a race to the top with capital flowing towards the highest yield, especially towards LRT pools. Blast and Manta, as the first staking-enshrined L2s, fired the shot heard round the world, instantly bootstrapping over $1B in TVL. Where the supply is abundant and hungry, the expected yield from AVSs and restaked L2s is unclear at best. Further, restaking in Bitcoin, Cosmos, and Solana are all at the Cambrian stage.</p><p>At the Tertiary Layer, synthetic stables, yield optimization, and yield tokenization are directions that add to innovative diversity. At this layer, capital efficiency and risk eclipse composability. Unlocking the widest composability with the lowest risk would be key to success in this layer.</p><h3>Composable Capital Efficiency and Staking as the Crypto-Native Benchmark Rate</h3><p>Composability is the hallmark of web3 — frictionless, low-minimum, self-custody. In contrast, yield stacking faces high friction in traditional finance. For example, collateralizing treasury bonds for borrowing incurs multiple friction points — third-party custodians, case-by-case judging of LTV ratio, and high minimum to justify the labor costs involved, just to name a few.</p><p>The advent of LSTs unlocks the composability of consensus layer yields to execution layer DeFi activities. Such composability enabled DeFi summer in 2020. Fast forward three years, composability now feels so natural that it’s almost taken for granted. We have come to expect frictionless yield stacking to boost capital efficiency. For example, we expect to stack yield by minting LP tokens for staking (superliquid staking) or minting LSTs to deposit into LP positions.</p><p>Self-custodial, low minimum, and frictionless — these features are unique to web3 and highlight the potential for efficiency gains for the broader financial market. Imagine if you could tokenize your stock holdings and use it to LP into stock exchanges. Imagine if you could tokenize your real estate equity and easily put it to restaking yields. Through LSTfi, we get a glimpse of what composability could mean for traditional finance.</p><blockquote>“Through LSTfi, we get a glimpse of what composability could mean for traditional finance.”</blockquote><p>Fundamentally, there are five types of yield sources in crypto, and they are stackable — in other words, composable. The IOU token of one yield source can be used as the input token of another yield source.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aMnZnJBDbd8VfTgZTLNacw.png" /></figure><p>Of course, risks go hand in hand with yields. Of the five fundamental yields, staking yield is the safest. Merely 226 node operators out of 959 thousand node operators have been slashed since Ethereum staking began. On the other hand, while sovereign treasury bonds are often touted as the least risky, most recently Italy, Spain, Portugal, Ireland, and Greece (not to mention serial defaulter nations Venezuela and Ecuador) have defaulted on their bonds. Even the gold standard, US bonds, had ‘defaulted’ when it went off the gold peg in the 1930s to service debt with uncapped fiat printing. The default of treasury bonds is tied to a nation’s ability to pay off its debt. Its risk level is more similar to ‘lending yield’ risk than ‘staking yield’ risk. Whereas sovereign bond yield is based on future expectations of debt servicing, staking yield is tied to the current level of network usage.</p><p>Because of such, <strong>we consider staking as the crypto-native benchmark rate.</strong></p><p>Atop staking sits the capital efficiency engine that drives the yield-stacking rocket. We have begun to see innovations such as staking-enshrined L2s a la Blast and Manta, cross-domain restaking a la Picasso and Babylon, and LST looping a la Gravita.</p><p><strong>The composable nature of LSTs would drive further innovation in yield-stacking designs.</strong></p><h3>Staking, Restaking, and LSTfi/LRTfi</h3><p>Staking is the security foundation of POS chains and the risk-free benchmark rate in web3.</p><p>Justin Drake ascribes ETH to two purposes, <a href="https://www.youtube.com/watch?app=desktop&amp;v=jlGc0npwkeU">Economic Security and Economic Bandwidth</a>. LSTs and LRTs allow the same ETH to participate in both, by composing with various DeFi and restaking activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/1*a1aI1VXidgaYTG3to08_1A.png" /></figure><p>Where economic security is concerned, decentralization and neutrality must be safeguarded in PoS chains to mitigate potential collusion. It’s a balancing act to game-theoretically design the protocol in a way that preserves decentralization and neutrality. We’ll come back to this tension soon.</p><p>First, let’s visit the stack, using Ethereum as an example of PoS chains. The primary layer allows users to stake their ETH, and get back LSTs such as stETH, cbETH, wbETH, and rETH. In the secondary layer, the LSTs or ETH can be restaked to provide security to other staked services, and get back LRTs such as eETH, uniETH, and pufETH. The tertiary layer then composes LSTs and LRTs with various DeFi activities for yield stacking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zTEcarV6HnArXuF1BIz4TQ.png" /></figure><p>To understand the incentives driving adoption, we answer three questions:</p><ol><li>Which combination of strategies would produce the highest yield? This pertains to capital efficiency.</li><li>Which output token allows access to the deepest liquidity and participation in the widest set of DeFi activities? This touches on composability.</li><li>Which strategy is the safest source of yield? This concerns risk mitigation.</li></ol><p>As such, composability and capital efficiency are the primary adoption-driving factors, while risk is a boundary condition that caps the choice set.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lep01ldUR-jxhEenVXMs-g.png" /></figure><h3>Primary Layer — Staking</h3><p>At the primary layer, validators deposit native tokens such as ETH, ATOM, and SOL to secure the PoS networks and get transaction fees as rewards.</p><p>Because staking is the least risky form of yield generation in crypto, over time, we expect Ethereum (23% staked) to catch up to Solana (90% staked) and Atom (70% staked), which represents hundreds of billions if not trillions in market expansion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NkUQQxnEzSqEh_bNh5PVwg.png" /></figure><p>There are three categories of staking: centralized, quasi-decentralized, and decentralized. Centralized and quasi-decentralized staking trades custody for convenience and composability. Decentralized staking, referring to solo staking, is the most secure for the protocol, but is challenging to maintain and lacks composability. In theory, a self-custodial node could issue LSTs too, but no rational thinker would buy it due to the lack of composability.</p><p><strong>Posting Bonds</strong></p><p>In plain vanilla solo staking, validators create two pairs of keys, one as validator key and one as withdrawal key, then send 32 ETH to Eth 1.0 deposit smart contract. The base fee gets burnt and transaction tips get sent to validators. Only 8 validators per epoch or 1800 per day can get activated.</p><p>Staking pools such as Rocket Pool, Diva, and Swell, allow independent node operators to support staking pools comprised of deposits from stakers. From the perspective of an operator, the lower the bond, the higher its capital efficiency, because they could earn a share of the commission from deposited ETH. At its essence, lowering bond requirements allows greater leverage.</p><ul><li>Rocket Pool: 8 ETH Bond</li><li>Stader: 4 ETH Bond</li><li>Puffer: 1 ETH Bond</li></ul><p>In some estimates, node operators can earn up to 6–7% in ETH rewards and up to 7.39% in staking pool token rewards.</p><p>In Polygon, validators are permissioned. Validators must apply to join the validator set, and can only join when an approved validator unbonds. In Solana, validators can join permissionlessly and Solana Foundation provides clusters for validators to choose from. Solana also officially tracks the number of validators in superminority that together hold over 33% of SOL staked.</p><p>In CEX staking, the mechanism of bond posting is opaque. Retail stakers could front up to the full amount of bond and the centralized node operator could shift all potential penalties to retail. However, stakers also automatically benefit from smoothing, which in most cases, generates a higher yield than solo staking.</p><p><strong>Getting Rewards</strong></p><p>Every 2–3 days, Ethereum Beacon chain sweeps the validators and distributes rewards. Besides the consensus layer, validators can also get execution layer rewards through priority fees and MEV. Protocols such as Jito in Solana is taking advantage of MEV to boost its LST yield.</p><p>MEV-boost redistributes MEV from block builders to validators, which in turn can distribute rewards to stakers. Ultimately, MEV burn may be implemented to return value to ETH holders. At its essence, MEV redistribution is a philosophical question around fairness. But for now, MEV can be used to boost staking rewards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nil-2_f2RZv4RixUyhsTAw.png" /></figure><p>Validator rewards are notoriously spiky. Because of the inherent randomness in validator selection, rewards can be uneven. In Ethereum, deterministic randomness involving a hash and a seed from the previous block is used to select the next validator.</p><p>To this end, Rocket Pool provides a smoothing pool on an opt-in basis. Smoothing pool would accumulate the rewards from the validators that opt in. As a rule of thumb, if the validator has fewer minipools than the number of nodes in the smoothing pool, it is more likely to get greater yield from the smoothing pool. For projects such as Lido, the smoothing function is built into the smart contract.</p><p>In CEXes, smoothing is automatic, wherein stakers can expect a consistent yield over time.</p><p><strong>Slashing</strong></p><p>Slashing is an extremely rare event. Merely 226 node operators out of 959 thousand node operators have been slashed since Ethereum staking began.</p><p>A validator could receive penalties when they 1) Fail to produce a block, or 2) Fail to produce an attestation when expected. The penalty is small. Generally, the validator can make back its yield in the same number of hours that it went off for. On the other hand, slashing penalties are more severe.</p><p>Slashing happens when one of three conditions is met. 1) Double Signing: Signing two different beacon blocks for the same slot. 2) Signature Wrapping: Attestor signs an attestation around another one. 3) Double Signing: Signing two different attestations with the same target. A validator would include evidence of wrongful doing in a block to socialize with the validator set, and when all validators sign off on the evidence, slashing commences.</p><p>In the event of slashing, the following repercussions can occur</p><ul><li>Initial Penalty: 1/32 of its effective balance slashed</li><li>Correlation Penalty: up to the effective balance could be slashed, if there are many violations within a short span. Quadratic slashing deters collusion.</li><li>The boot: the validator is entered into withdrawal within 8192 epochs (36 days)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/0*ewXwDHayFr6394IJ" /></figure><p>DVTs are designed to reduce slashing risks and boost staking pool security by protecting validators from failing to produce a block or an attestation. DVTs implement distributed key generation (DKG), multi-party computation (MPC), and threshold signature scheme (TSS) over a redundant set of validators.</p><p>SSV is implemented as a DVT network that is a fully permissionless, decentralized, and open-source public good, and is currently <a href="https://blog.lido.fi/lido-on-ethereum-ssv-network-testing-v2/">in trial for protocols such as Lido</a>. Obol runs Charon, a non-custodial middleware between the validator client and consensus client communication. Diva uses its own DVT implementation to power its LST in a permissionless manner, where anyone can run a node. Puffer’s Secure-Signer is a remote signing tool backed by an Ethereum Foundation grant designed to prevent slashable offenses using Intel SGX currently. Puffer’s Secure-Signer manages validator keys on behalf of the consensus client.</p><p>At face value, from a capital efficiency standpoint, running multiple clients via a DVT is a drain on computational resources. In implementation, the same hardware may participate in multiple sets of DVTs. Importantly, DVTs boost protocol security so that if a set of node operators goes offline or behaves erratically, the staking pool can continue to function correctly.</p><p>Cosmos Interchain Security has an interesting approach to slashing (proposal #187). Because ICS is nascent, a governance vote takes space to arbitrate all potentially slashable events. While this was intended to prevent any security contagion from consumer chains to the hub, governance leaves decision-making in the hands of human arbitration instead of code, at least for now.</p><p><strong>Withdrawal</strong></p><p>In Ethereum, 4 exits are allowed per epoch. Because of the mismatch in entry and exit throttle, 8 validators per epoch and 4 validators per epoch respectively, there can be a long queue for exits. Once a withdrawal is initiated, validators must wait for 256 epochs.</p><p>In Solana, delegation is enshrined. Standard delegation to a staking pool requires a cooldown period to withdraw. However, via staking pools, liquid staking does not require a cooldown in withdrawal.</p><p><strong>Looking onwards</strong></p><p>As Ethereum staking ratio increases, network usage held equal, base yields should asymptotically approach 1.8% which is the floor set by the Ethereum Foundation, but increases in gas costs and MEV might counterbalance this to some degree.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OC6uRATsCxQGFNA0dokbMA.png" /></figure><p>Usually, opportunity costs would prompt stakers to stop staking when yield drops below the next available yield source. However, LSTs mitigate the opportunity cost, as holders can participate in both Economic Security and Economic Bandwidth. Therefore, stakers are likely to continue to deposit despite low returns and use their LSTs to participate in DeFi for additional yields.</p><p>Another phenomenon due to lowered Eth staking yield is centralization. Solo Stakers will find their yield continue to diminish and at one point flip hardware costs. There are some methods of mitigation in order to encourage more solo staking. We’ll come back to detail solutions to the problem of centralization and externalities.</p><p>(end of Part I)</p><p><strong>In Part II, we cover Restaking, LRTfi, and Solutions to Centralization and Externalities: </strong><a href="https://longhashvc.medium.com/staking-restaking-and-lrtfi-composable-capital-efficiency-and-neutrality-part-ii-47c0a0e60213"><strong>https://longhashvc.medium.com/staking-restaking-and-lrtfi-composable-capital-efficiency-and-neutrality-part-ii-47c0a0e60213</strong></a></p><p>Sources:</p><ul><li>Eth Slashing penalty: <a href="https://eth2book.info/capella/part2/incentives/slashing/">https://eth2book.info/capella/part2/incentives/slashing/</a></li><li>Cosmos proposal #187, lambda upgrade <a href="https://forum.cosmos.network/t/proposal-187-accepted-v9-lambda-upgrade-with-replicated-security/8766">https://forum.cosmos.network/t/proposal-187-accepted-v9-lambda-upgrade-with-replicated-security/8766</a></li><li>Rewards: <a href="https://kb.beaconcha.in/rewards-and-penalties">https://kb.beaconcha.in/rewards-and-penalties</a></li><li>Rewards: <a href="https://docs.rocketpool.net/guides/node/responsibilities.html">https://docs.rocketpool.net/guides/node/responsibilities.html</a></li><li>Rocket pool rewards: <a href="https://rocketpool.net/node-operators">https://rocketpool.net/node-operators</a></li><li>Enshrining LSDs: <a href="https://vitalik.eth.limo/general/2023/09/30/enshrinement.html">https://vitalik.eth.limo/general/2023/09/30/enshrinement.html</a></li><li>Eth Beacon docs: <a href="https://kb.beaconcha.in/ethereum-2.0-depositing">https://kb.beaconcha.in/ethereum-2.0-depositing</a></li><li>Polygon validator: <a href="https://wiki.polygon.technology/docs/pos/design/validator/core-components/staking">https://wiki.polygon.technology/docs/pos/design/validator/core-components/staking</a></li><li>Babylon whitepaper</li><li>EigenLayer docs: <a href="https://github.com/Layr-Labs/eigenlayer-contracts/tree/master/docs">https://github.com/Layr-Labs/eigenlayer-contracts/tree/master/docs</a></li><li>Cosmos slashing v9 lambda upgrade <a href="https://forum.cosmos.network/t/proposal-187-accepted-v9-lambda-upgrade-with-replicated-security/8766">https://forum.cosmos.network/t/proposal-187-accepted-v9-lambda-upgrade-with-replicated-security/8766</a></li><li>Vitalik on Zones of Sovereignty: <a href="https://old.reddit.com/r/ethereum/comments/rwojtk/ama_we_are_the_efs_research_team_pt_7_07_january/hrngyk8/">https://old.reddit.com/r/ethereum/comments/rwojtk/ama_we_are_the_efs_research_team_pt_7_07_january/hrngyk8/</a></li><li>EigenLayer LST addition contest: <a href="https://www.blog.eigenlayer.xyz/eigenlayer-lst-addition-contest-in-partnership-with-jokerace/">https://www.blog.eigenlayer.xyz/eigenlayer-lst-addition-contest-in-partnership-with-jokerace/</a></li><li>Lido staking router: <a href="https://docs.lido.fi/contracts/staking-router/">https://docs.lido.fi/contracts/staking-router/</a></li><li>Lido DVT trial: <a href="https://blog.lido.fi/lido-on-ethereum-obol-network-testing-v2/">https://blog.lido.fi/lido-on-ethereum-obol-network-testing-v2/</a></li><li>Portal Network: <a href="https://ethereum.org/en/developers/docs/networking-layer/portal-network/">https://ethereum.org/en/developers/docs/networking-layer/portal-network/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49c7ef21d36d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we invested in Kakarot]]></title>
            <link>https://longhashvc.medium.com/why-we-invested-in-kakarot-799d18a9b6fc?source=rss-7be833512009------2</link>
            <guid isPermaLink="false">https://medium.com/p/799d18a9b6fc</guid>
            <dc:creator><![CDATA[LongHash Ventures]]></dc:creator>
            <pubDate>Tue, 21 Nov 2023 02:07:33 GMT</pubDate>
            <atom:updated>2023-11-21T02:07:33.662Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kOUfkIxpMRqdy5b2hGKmIQ.png" /></figure><p><strong>Introduction</strong></p><p>Zero knowledge rollups (ZK-rollups) have emerged as one of the most viable solutions for scaling Ethereum in its rollup-centric roadmap. On-chain data availability, faster finality than optimistic rollups, cryptographic validity proofs, and increasing optimizations in the ZK stack are some of the reasons for their increasing popularity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kt166Sp6FEfn6wrd" /><figcaption><em>Image Source: </em><a href="https://www.theblock.pro/research/classifying-blockchain-scaling-solutions-241157"><em>Classifying Blockchain Scaling Solutions</em></a><em> by The Block</em></figcaption></figure><p><strong>Challenges with ZK rollup</strong></p><p>While ZK-rollups rely on trustless cryptographic mechanisms for security instead of the honesty of incentivized actors as with optimistic rollups, ZK-rollups are difficult to build due to the complexity of zero-knowledge technology and EVM not being ZK friendly. One of the key challenges for zkEVMs is implementing Keccak MPT in a provable and cost-effective way. Due to the non ZK friendly design of EVM, all ZK rollups are required to make a trade-off between EVM compliance and performance. High compatibility with EVM and existing Ethereum infrastructure leads to poor performance (higher proving time and cost) and optimizing for performance by using ZK-friendly VM and language leads to poor EVM compatibility. For more details on the performance and compatibility tradeoff, refer to this <a href="https://vitalik.ca/general/2022/08/04/zkevm.html">article</a> by Vitalik.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/0*Qj1K2mWcXJVlciP_" /><figcaption><em>Image Source: </em><a href="https://vitalik.ca/general/2022/08/04/zkevm.html"><em>The different types of ZK-EVMs</em></a><em> by Vitalik Buterin</em></figcaption></figure><p>Many different teams are currently building ZK-rollups and most of them have a slightly different approach. Taiko is striving for full Ethereum compatibility by supporting all opcodes and precompiles of ethereum and maintaining the same data structures and in-consensus logic. Scroll and Polygon zkEVM have focused their efforts on building a bytecode-compatible zkEVM. Native EVM bytecode can be executed on L2 but there are some differences from Ethereum, particularly in data structures like the block structure and state tree. zkSync and Starknet have optimized for performance by building highly performant and ZK-friendly VMs and adding support for Solidity and Ethereum tooling as an additional layer on top.</p><p><strong>Kakarot Overview</strong></p><p>Kakarot is a new type 2.5 zkEVM positioned to emerge as one of top scaling solutions. It is an implementation of the Ethereum Virtual Machine (EVM), developed using Cairo. Cairo is a programming language that can generate computational traces that can be used to generate STARK-based ZK Proofs. Starknet leverages Cairo to express smart contract execution within the blocks of the chain.</p><p>Kakarot’s approach can be compared to Geth’s EVM, which is written in Golang. The main differentiating factor for an EVM written in Cairo is that Cairo computation can generate execution traces through the CairoVM which then can generate Stark Proofs using Stone or Sharp. Since all the cryptography is handled by Starknet and CairoVM, Kakarot only needs to focus on the engineering of the EVM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_ChWZQfjdZQ792ck" /><figcaption><em>Image Source: </em><a href="https://www.kakarot.org/"><em>Kakarot as an enshrined EVM</em></a></figcaption></figure><p><strong>How did it all start?</strong></p><p>On 20th July 2022, Sahar Papini from the Starkware team <a href="https://twitter.com/PapiniShahar/status/1549815657776259083?s=20">tweeted</a> the idea of building a zkEVM on top of Cairo. Abdel, the lead of Starkware’s exploration team and part of the core Ethereum developer team, started implementing it in October 2022. Around the same time, the open-source builder community of Starknet, gathered together with Onlydust’s help, began a similar project in parallel. The former absorbed the latter during StarknetCC in Lisbon. After one week of work by core contributors at a hacker house in Lisbon, the Kakarot team was formed. Kakarot adopted the principles of open-source, open contributions, and community-driven technical strategy from Day 1. By December 2022, Kakarot had <a href="https://twitter.com/dimahledba/status/1606270836922585098?s=20">achieved</a> 100% EVM opcode compatibility. As of today, Kakarot has close to 50 unique contributors.</p><p><strong>How does Kakarot address the challenges of ZK rollups?</strong></p><p>Kakarot’s design allows it to optimize for compatibility, performance, and flexibility without sacrificing much on any of them.</p><p><strong>Compatibility: </strong>Kakarot enables developers to write their programs in Solidity and use existing Ethereum tools. This significantly improves the developer experience as they don’t have to worry about learning a new language and can continue to use the developed tooling ecosystem of Ethereum (Foundry, Hardhat, Wagmi). Kakarot supports all the EVM opcodes and 8 out of 9 pre-compiles. dApps written in Solidity or any other EVM-supported language can be deployed onto Kakarot without requiring any modifications to the existing code and without requiring extensive auditing. The end-users can also interact with dApps with their usual toolchain (Metamask, Wallet connect, etc.). As per Vitalik’s classification, Kakarot is Type 2.5 and is finalizing all the pre-compiles and exploring gas equivalence which will make it Type 2 zkEVM.</p><p><strong>Performance: </strong>Kakarot leverages Starknet’s CairoVM and STARK Validity proofs. This allows Kakarot to leverage validity proofs that do not require any kind of trusted setup and are quantum-resistant. With quantum computing research progressing at a rapid pace, STARK proofs provide a future-proof tech stack to Kakarot. In terms of performance, STARK proofs are extremely promising. Celer Network recently conducted an exercise to <a href="https://blog.celer.network/2023/08/04/the-pantheon-of-zero-knowledge-proof-development-frameworks/">benchmark</a> the performance of SHA-256 using different zk proving frameworks. starky (STARK framework from Polygon Zero) and Boojum (STARK-based implementation by zkSync) had one of fastest proof generation times and lower memory consumption than other frameworks although at the cost of much larger proof size. This is not a comprehensive comparison as it only compares the performance of SHA-256 and does not include Starknet prover but it does provide some early evidence of the STARK framework’s capabilities.</p><p>StarkWare pioneered the use of STARK validity proofs to address Ethereum’s scalability issues in 2018. Since then, the StarkWare team has demonstrated excellent research capabilities along with the ability to build and engineer cutting-edge products. Along with general purpose StarkNet L2 and Cairo, the team has also built StarkEx enabling large-scale dapps such as Immutable X, Sorare, and rhino.fi to launch their dedicated rollups on top of Ethereum. StarkWare has recently open sourced the StarkWare’s STARK Prover, Stone. This will allow the community to innovate and contribute to their prover and further improve the performance. While StarkWare has achieved significant milestones, it is yet to be adopted widely by developers because of the challenges of learning Cairo and the lack of a time-tested and familiar developer tooling ecosystem. Kakarot allows Starknet to solve both these challenges.</p><p><strong>Flexible implementation:</strong></p><p>As of today, Kakarot could choose to settle on Ethereum and become Ethereum L2 zkEVM or it could also settle on Starknet and become Ethereum L3 zkEVM. Depending on performance and key metrics (gas price, congestion, etc.), Kakarot can be deployed on mainnet as an L2 or as an L3 as well. Kakarot also boasts of a very small codebase (a few thousand lines), making auditing and keeping up with EVM changes very easy. If and when new opcodes or precompiles are added to EVM, they can be very easily and quickly implemented by Kakarot.</p><p><strong>The road ahead</strong></p><p>The first major milestone for Kakarot will be to deploy EVM inside Starknet L2, bringing EVM compatibility to the Starknet ecosystem. Kakarot will provide interoperability with native Starknet protocols and composability between protocols. Kakarot could also enable developers to easily launch L3 zkEVMs by leveraging Madara. Madara is a RUST-based Starknet sequencer built on the Substrate framework. The Kakarot team has been contributing to the open-source development of Madara. L3s will significantly lower the transaction cost and increase the TPS. The design could be modular as the projects should be able to choose between Starknet L2 or new data availability solutions, such as Celestia or EigenDA, for posting transaction data. Developers will have the choice between a more secure option or a more cost-effective solution. Given Kakarot’s positioning and expertise in Cairo and EVM, Kakarot is not limited to being purely an L2, and many other possibilities could be easily explored. Kakarot also aims to prove Ethereum L1 possibly increases security for the entire Ethereum ecosystem besides just contributing to the scalability aspect.</p><p><strong>Conclusion</strong></p><p>Kakarot is strategically positioned to offer tremendous value to a multi-chain future by offering scalability and by abiding by the ethos of open source, security, and freedom to developers. The modular approach of separating the cryptography and EVM engineering allows the Kakarot team to iterate faster, maintain high security, and benefit from all the optimizations by the Starknet team and open-source community. By leveraging CairoVM’s ability to generate proof of execution, the strong ecosystem of Starknet, and allowing developers to use the existing tools and languages, Kakarot effectively manages the tradeoff between performance and EVM compatibility.</p><p>We believe that ZK-rollups are one of the most promising long-term solutions for scaling Ethereum. Great teams have made significant advancements but achieving performance along with EVM compatibility has been a challenge. Kakarot has been designed to pair convenience with performance. Kakarot is positioned to benefit from advancements in EVM design, ethereum tooling, and Starknet’s proving framework and we expect it to emerge as one of the top scaling solutions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=799d18a9b6fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Storage proofs: Achieving state awareness across time and chains]]></title>
            <link>https://longhashvc.medium.com/storage-proofs-achieving-state-awareness-across-time-and-chains-0f6e4e898550?source=rss-7be833512009------2</link>
            <guid isPermaLink="false">https://medium.com/p/0f6e4e898550</guid>
            <dc:creator><![CDATA[LongHash Ventures]]></dc:creator>
            <pubDate>Wed, 11 Oct 2023 12:07:34 GMT</pubDate>
            <atom:updated>2023-10-17T07:49:09.966Z</atom:updated>
            <content:encoded><![CDATA[<p><em>We would like to thank Kacper Koziol and Tiago Neto from Herodotus, Mo Dong from Brevis, Ismael Hishon-Rezaizadeh from Lagrange Labs, Yi Sun from Axiom and Roy Lu from LongHash Ventures for reviewing and providing their valuable feedback</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EpRuuF4iIV1U6TEHRiGf-w.png" /></figure><p><strong>Introduction</strong></p><p>What if you lost your memory every hour? And you need to constantly ask someone to tell you what you have done? That is the current state of smart contracts. On blockchains like Ethereum, smart contracts cannot directly access states beyond 256 blocks. This problem is further exacerbated in the multi-chain ecosystem, where retrieval and verification of data across different execution layers is even more difficult.</p><p>In 2020, Vitalik Buterin and Tomasz Stanczak <a href="https://eips.ethereum.org/EIPS/eip-2935">proposed</a> a way to access data across time. While the EIP has become stagnant, its need has resurfaced in the roll-up-centric multi-chain world. Today, storage proofs have emerged as a frontier, to give awareness and memory to smart contracts.</p><p><strong>Accessing on-chain data</strong></p><p>There are a number of ways in which dapps can access data and state. All of the approaches require the application to place trust in humans/entities or crypto economic security or code and have some tradeoffs:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*8czqKjgj8tsEU8H_bfycTA.jpeg" /></figure><p><strong>Trust in humans/entities:</strong></p><ul><li><strong>Archive nodes: </strong>Operators could run an archive node themselves or rely on archive node service providers like Alchemy or Infura to access all the data since the Genesis block. They provide all the same data as a Full Node but also all the historical state data of the entire blockchain. Off-chain services like Etherscan and Dune Analytics use archive nodes to access on-chain data. Off-chain actors can attest to the validity of this data, and on-chain smart contracts can verify the data was signed by a trusted actor/committee. The integrity of the underlying data is not verified. This approach requires the dapp to trust that the archive node service provider is running the infrastructure correctly and without any malicious intent.</li></ul><p><strong>Trust Crypto economic security:</strong></p><ul><li><strong>Indexers: </strong>The indexing protocol organizes all the data on the Blockchain, allowing developers to build and publish open APIs that applications can query<strong>. </strong>Individual indexers are node operators that stake tokens to provide indexing and query processing services. However, disputes can occur when the data served is incorrect and the arbitration process can take time. Moreover, data from indexers like The Graph cannot be directly utilized by the business logic of smart contracts and is used in the web2-based data analytic context.</li><li><strong>Oracles: </strong>Oracle service providers use the data aggregated from many independent node operators. The challenge here is that the data available from Oracles might not get updated frequently and is limited in scope. Oracles like Chainlink usually only maintain specific states, such as price feeds and for application-specific states and history they are not feasible. Moreover, this approach also introduces a certain level of deviation in the data and requires trust in node operators.</li></ul><p><strong>Trust Code:</strong></p><ul><li><strong>Special Variable and Functions: </strong>Blockchains like Ethereum have special variables and functions that are mainly used to provide information about the blockchain or are general-use utility functions. It is only possible for a smart contract to <a href="https://docs.soliditylang.org/en/v0.4.24/units-and-global-variables.html#block-and-transaction-properties">access the block hash</a> of 256 most recent blocks. The block hashes are not available for all blocks for scalability reasons. Having access to historical block hashes would be useful as it could allow verification of proofs against them. There is no opcode in EVM execution that allows access to old block contents or previous transaction contents or receipt outputs, so a node can safely forget those things and still be able to process new blocks. This method is also limited to a single blockchain.</li></ul><p>Given the challenges and limitations of these solutions, there is a clear need to store and provide block hashes on-chain. This is where storage proofs come in. In order to better understand storage proofs, let’s take a quick look at the data storage in blockchains.</p><p><strong>Data storage in a blockchain</strong></p><p>A blockchain is a public database that is updated and shared across many computers in a network. Data and state are stored in consecutive groups called blocks and each block cryptographically references its parent by storing the hash of the previous block header.</p><p>Let’s take the Ethereum block as an example. Ethereum leverages a particular type of Merkle tree known as the “Merkle Patricia tree” (MPT). Ethereum block headers contain roots of four different Merkle-Patricia tries i.e. State trie, Storage trie, Receipts trie, and Transaction Trie. These 4 tries encode mappings that comprise all Ethereum data. Merkle Trees are used due to their efficiency in data storage. Using recursive hashes, only the root hash eventually needs to be stored, saving a lot of space. They allow anyone to prove the existence of an element in the tree by proving that recursively hashing the nodes leads to the same root hash. Merkle proofs allow light clients on Ethereum to get answers to questions like:</p><ul><li>Does this transaction exist in a particular block?</li><li>What is the current balance of my account?</li><li>Does this account exist?</li></ul><p>Instead of downloading every transaction and every block, a “light client” can only download the chain of block headers and verify the information using Merkle Proofs. This makes the overall process highly efficient. Refer to this <a href="https://vitalik.ca/general/2021/06/18/verkle.html">blog</a> by Vitalik and Maven11 research <a href="https://maven11.substack.com/p/beyond-ibc">article</a> to better understand the implementation, advantages, and challenges associated with Merkle Trees.</p><p><strong>Storage Proofs</strong></p><p>Storage proofs allow us to prove that something is committed in the database and is valid as well using cryptographic commitments. If we can provide such proof, it is a verifiable claim that something happened on the blockchain.</p><p><strong>What can storage proofs enable?</strong></p><p>Storage proofs permit two main functionalities:</p><ol><li>Access historical on-chain data beyond the last 256 blocks, all the way back to the genesis block</li><li>Access on-chain data (historical as well as current) of one blockchain on another blockchain with the assistance of consensus verification or L1-L2 bridge in case of L2s</li></ol><p><strong>How do storage proofs function?</strong></p><p>Storage proofs at a very high-level check if the specific block is part of the blockchain’s canonical history and then verify if the specific data requested is part of the block. This could be achieved via:</p><ul><li><strong>On-chain processing:</strong> dapps could<strong> </strong>take the initial trusted block, pass the block as calldata to access the previous block, and traverse all the way back to the genesis block. This requires a lot of computation on-chain and a huge amount of call data. This approach is not at all practically feasible due to the huge amount of computation required on-chain. <a href="https://github.com/aragon/evm-storage-proofs">Aragon tried</a> using the on-chain approach in 2018, but it was not feasible due to high on-chain cost.</li><li><strong>Using ZK proofs</strong>: The approach is similar to on-chain processing except for the fact that ZK prover is used to move the complex computation off-chain.</li></ul><ol><li>Accessing data on the same chain: ZK proof can be used to assert that an arbitrary historical block header is an ancestor of one of the 256 most recent block headers that are accessible within the execution environment. The other approach is to index the entire history of the source chain and generate a ZK proof of the same to prove that the indexing happened correctly. This proof is updated regularly as new blocks are added to the source chain. Accessing data across chains: The provider collects the block headers of the source chain on the destination chain and attests to the validity of these block headers using ZK consensus proof. It is also possible to use an existing AMP solution like Axelar, Celer, or LayerZero to query the block headers.</li><li>A cache of hashes of block headers of the source chain, or the root hash of an off-chain block hash accumulator, is maintained on the destination chain. This cache is updated on a regular basis and is used to efficiently prove on-chain that a given block exists and has cryptographic linkage to a recent block hash accessible from the state. This process is known as proving the continuity of the chain. It is also possible to use a dedicated blockchain to store the block headers of all the source chains.</li><li>The historical data/block is accessed from off-chain indexed data or on-chain cache (depending on the complexity of the request) as requested by the dapp on the destination chain. While the cache of a hash of block headers is maintained on-chain, the actual data might be stored off-chain.</li><li>The existence of data in the specified block is checked via merkle inclusion proofs and a zk proof for the same is generated. This proof is combined with the zk proof of correct indexing or ZK consensus proof and the proof is made available on-chain for trustless verification.</li><li>The dapps can then verify this proof on-chain and use the data to execute the desired action. Along with the verification of the ZK proof, public parameters like the block number and block hash are checked against the cache of block headers maintained on-chain.</li></ol><p>Some of the projects adopting this approach are Herodotus, Lagrange, Axiom, Hyper Oracle, Brevis Network, and nil foundation. While significant effort is being made to make applications state-aware across multiple blockchains, IBC (Inter Blockchain Communication) stands out as an interoperability standard that enables applications like ICQ (Interchain queries) and ICA (Interchain accounts). ICQ enables applications on Chain A to query the state of chain B by including the query in a simple IBC packet and ICA allows one blockchain to securely control an account on another blockchain. Combining them can enable interesting cross-chain use cases. RaaS providers like Saga offer these functionalities to all their app chains by default by using IBC.</p><p>There are many ways in which storage proofs can be optimized to find the right balance of memory consumption, proving time, verification time, compute efficiency, and developer experience. The overall process can be broadly divided into 3 main sub-processes.</p><ul><li><strong>Data access</strong></li><li><strong>Data processing</strong></li><li><strong>ZK Proof generation for data access and processing</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dB8lf6WTxcbc47kdl8hdfg.png" /></figure><p><strong>Data access: </strong>In this subprocess, the service provider accesses the block headers of the source chain natively on the execution layer or via maintaining an on-chain cache. For data access across chains, verification of the source chain consensus on the destination chain is required. Some of the approaches and optimizations being adopted include:</p><ul><li><strong>The Existing Ethereum Blockchain:</strong> The Ethereum blockchain’s existing structure can be used to prove the value of any historical storage slot with respect to the current blockheader using ZKP. This can be thought of as one large inclusion proof. It is proof that, given a recent block header X at height b, there exists blockheader Y which is an ancestor of X at height b-k. It is based on the security of Ethereum’s consensus and requires a fast-proving system for efficiency. This is the approach used by Lagrange.</li><li><strong>On-chain Merkle Mountain Ranges (MMR) cache: </strong>A Merkle Mountain Range can be viewed as a list of Merkle trees where the individual Merkle trees are combined when two trees reach the same size. The individual Merkle trees in the MMR are combined by adding parent nodes to the trees’ previous roots. MMR is a data structure similar to Merkle trees with some additional benefits, such as efficient appending of elements and efficient data queries, particularly when reading sequential data from large datasets. Appending new headers via Merkle tree would require passing all the sister nodes at each level. In order to append data efficiently, Axiom uses MMR to maintain a cache of the hash of block headers on-chain. Herodotus stores the root hash of the MMR block hash accumulator on-chain. This allows them to check the fetched data against these block header hashes via inclusion proofs. This approach requires the cache to be updated on a regular basis and brings in liveness concerns if not decentralized.</li><li>Herodotus maintains two different MMR. Depending on the specific blockchain or layer, accumulators can be tailored to utilize different hashing functions, optimizing efficiency and computational costs. For proving on Starknet, poseidon hash might be used but Keccack hash might be used for EVM chains.</li><li><strong>Off-chain MMR cache:</strong> Herodotus maintains an off-chain cache of previously fetched queries and results to allow for faster fetching in case the data is requested again. This requires additional infrastructure than simply running an archive node. The optimizations done on off-chain infrastructure can potentially decrease costs for the end user.</li><li><strong>Dedicated blockchain for storage</strong>: Brevis relies on a dedicated ZK rollup (aggregation layer) to store all the block headers of all the chains they attest to. Without this aggregation layer, each chain would need to store the block headers for every other chain, resulting in O(N2) “connections” for N blockchains. By introducing an aggregation layer, each blockchain only needs to store the state root for the rollup, reducing the overall connections to O(N). This layer is also used to aggregate multiple proofs for block headers/query results and a single proof for verification on each connected blockchain can be submitted.</li><li><strong>L1-L2 message passing: </strong>Verification of source chain consensus can be avoided in the case of L2s because L2s support native messaging for updating L2 contracts on L1. The cache could be updated on Ethereum and L1-L2 message passing can be used to send the block hash or root of the tree compiled off-chain to other L2s. Herodotus is adopting this approach but this is not feasible for alt L1s.</li></ul><p><strong>Data processing:</strong></p><p>Along with access to data, smart contracts should also be able to do arbitrary computations on top of data. While some use cases may not require computation, it is an important value-added service for a lot of other use cases. Many of the service providers enable computations on the data as a zk proof of the computation can be generated and provided on-chain for validity. Because existing AMP solutions like Axelar, LayerZero, Polyhedra Network could potentially be used for data access, data processing could become a differentiator for storage proof service providers.</p><p>Hyper Oracle, for instance, allows developers to define custom off-chain computations with JavaScript. Brevis has designed an open marketplace of ZK Query Engines that accepts data queries from dApps, and processes them using the attested block headers. The smart contract sends a data query, which is picked up by a prover from the marketplace. The Prover generates a proof based on the query input, relevant block headers (from the Brevis aggregation layer), and results. Lagrange has introduced ZK Big Data Stack to prove distributed programming models like SQL, MapReduce, and Spark/RDD. The proofs are modular and can be generated from any block header originating from existing cross-chain bridges and AMP protocols. ZK MapReduce, the first product in the Lagrange ZK BigData stack, is a distributed computation engine (based on the well-known MapReduce programming model) for proving results of computation involving sizable sets of multi-chain data. For example, a single ZKMR proof can be used to prove changes in the liquidity of a DEX deployed on 4–5 chains over a specified time window. For relatively simple queries, the computation can also be done directly on-chain as being done by Herodotus at the moment.</p><p><strong>Proof generation:</strong></p><ul><li><strong>Updatable proofs: </strong>Updatable proofs can be used when a proof needs to be computed and efficiently maintained over a moving stream of blocks. When a dapp wishes to maintain a proof for a moving average for a contract variable (such as token price), as new blocks are being created, without recomputing the new proof from scratch, existing proofs can be updated efficiently. To prove dynamic data-parallel computation on an on-chain state, Lagrange builds a batch vector commitment, called a Recproof, on top of a portion of MPT, updates it on the fly, and dynamically computes over it. By recursively creating a Verkle tree on top of MPT, Lagrange is able to compute large amounts of dynamic on-chain state data efficiently.</li><li><strong>Verkle Trees: </strong>Unlike Merkle trees, where we need to provide all the nodes that share a parent, Verkle Trees require only the path to the root. This path is much smaller compared to all the sister nodes in the case of the Merkle tree. <a href="https://notes.ethereum.org/Yn_mwNa2SeeQHnKsRgekKg">Ethereum is also exploring</a> the use of Verkle trees in future releases to minimize the amount of state that Ethereum full nodes are required to hold. Brevis leverages Verkle Tree to store attested block headers and query results in the aggregation layer. It significantly reduces the data inclusion proof size, especially when the tree contains a large number of elements, and also supports efficient inclusion proof for a batch of data.</li><li><strong>Mempool monitoring for faster proof generation: </strong>Herodotus recently announced turbo, which allows developers to add a few lines of code to their smart contract code to specify the data query. Herodotus monitors the mempool for smart contract transactions that interact with the turbo contract. The proof generation process begins when the transaction is in the mempool itself. Once the proof is generated and verified on-chain, the results are written into the on-chain turbo swap contract. Results can only be written to the turbo swap contract once they are authenticated by storage proofs. Once this happens, a portion of the transaction fees is shared with the sequencer or block builder, incentivizing them to wait a little longer to collect the fees. For simple data queries, it is possible that the requested data is made available on-chain before the transaction from the user is included in the block.</li></ul><p><strong>Application of state/storage proofs</strong></p><p>State and storage proofs can unlock many new use cases for smart contracts at application, middleware and infrastructure layer. Some of these are:</p><p><strong>Application Layer:</strong></p><p><strong>Governance:</strong></p><ul><li><strong>Cross-chain Voting: </strong>An on-chain voting protocol could allow users on Chain B to prove ownership of assets on Chain A. Users will not have to bridge their assets to gain voting power on a new chain. Example: SnapshotX on Herodotus</li><li><strong>Governance token distribution: </strong>Applications could distribute more governance tokens to active users or early adopters. Example: <a href="https://gov.optimism.io/t/building-a-verifiable-retropgf/6374">RetroPGF on Lagrange</a></li></ul><p><strong>Identity and Reputation:</strong></p><ul><li><strong>Proof of ownership: </strong>A user can provide proof of ownership of a certain NFT, SBT, or assets on chain A<strong>, </strong>enabling them to perform certain actions on Chain B. For example, a gaming app-chain may decide to launch its NFT collection on another chain with existing liquidity like Ethereum or any L2. This will allow the game to tap into liquidity that exists elsewhere and bridge the NFT utility without actually requiring NFTs to be bridged.</li><li><strong>Proof of usage: </strong>Users could be awarded discounts or premium features based on their historical usage of the platform (prove that the user-traded X volume on Uniswap)</li><li><strong>Proof of OG: </strong>A user can prove that he/she owns an active account that is more than X days old</li><li><strong>On-chain credit score: </strong>A multichain credit score platform can aggregate data from multiple accounts of a single user to generate a credit score</li></ul><p>All the above proofs can be used to provide a customized experience to users. Dapps could offer discounts or privileges to retain experienced traders or users and offer a simplified user experience for novice users.</p><p><strong>Defi:</strong></p><ul><li><strong>Cross-chain lending: </strong>Users could lock in assets on Chain A and take out a loan on Chain B instead of bridging the tokens</li><li><strong>On-chain insurance: </strong>Failures can be determined by accessing historical on-chain data and insurance can be settled fully on-chain.</li><li><strong>TWAP of the asset price in a pool: </strong>An application could calculate and fetch the average price of an asset in an AMM pool over a specified period of time. Example: <a href="https://www.axiom.xyz/blog/uniswap">Uniswap TWAP Oracle with Axiom</a></li><li><strong>Option pricing: </strong>an on-chain options protocol may price an option using the volatility of an asset over the past n blocks on a decentralized exchange.</li></ul><p>The last two use cases will require the proof to be updated every time a new block is added to the source chain.</p><p><strong>Middleware:</strong></p><ul><li><strong>Intents: </strong>Storage proofs will allow users to be more articulate and clear with their intents. While it is the solvers&#39; job to execute the necessary steps to fulfill the intent of the user, a user could more clearly specify the conditions based on on-chain data and parameters. Solvers can also prove the validity of on-chain data leveraged to find the optimal solution.</li><li><strong>Account Abstraction: </strong>Users could rely on data coming from other chains using storage proofs to set rules via Account Abstraction. Example: Every wallet has a nonce. We can prove that one year ago, the nonce was a particular number, and currently the nonce is the same. This can be used to prove that this wallet has not been used at all and the access to the wallet can then be delegated to another wallet.</li><li><strong>On-chain Automation: </strong>Smart contracts could automate certain actions based on predefined conditions that depend on on-chain data. Automated programs are required to call smart contracts at certain intervals to maintain the AMM’s optimal price flow or to keep lending protocols healthy by avoiding bad debt. Hyper Oracle enables automation along with access to on-chain data.</li></ul><p><strong>Infrastructure</strong></p><ul><li><strong>Trustless on-chain Oracle: </strong>Decentralized oracle networks aggregate responses from numerous individual oracle nodes within an oracle network. Oracle Networks can eliminate this redundancy and leverage cryptographic security for on-chain data. Oracle network could ingest data from multiple chains (L1s, L2s, and alt L1s) onto a single chain and simply prove existence using storage proofs elsewhere. DeFi solutions with significant traction could work on a custom solution as well. For example, Lido Finance, the largest liquidity staking provider, has teamed up with Nil Foundation, to <a href="https://twitter.com/LidoFinance/status/1691554712749842573?s=20">fund the development of zkOracle</a>. The solutions will enable trustless data access to in-EVM historical data and secure $15B in Lido Finance staked Ethereum liquidity.</li><li><strong>AMP Protocols: </strong>Existing AMP solutions could increase the expressivity of their messages by partnering with storage proof service providers. This is an approach suggested by Lagrange in their <a href="https://medium.com/@lagrangelabs/interoperability-for-modular-blockchains-the-lagrange-thesis-41352740914f">Modular Thesis</a> article.</li></ul><p><strong>Conclusion</strong></p><p>Awareness empowers technology companies to better serve their customers. From user identity to purchasing behavior to social graphs, technology companies leverage awareness to unlock capabilities such as precision targeting, customer segmentation, and viral marketing. Traditional tech companies need explicit permission from their users and have to be careful while managing user data. However, all the user data on permissionless blockchains is publicly available without necessarily revealing user identity. Smart contracts should be able to leverage the publicly available data to better serve users. Development and adoption of more specialized ecosystems will make state awareness across time and blockchains an increasingly important problem to be solved. Storage proofs can enable Ethereum to emerge as an identity and asset ownership layer along with being a settlement layer. Users could maintain their identity and key assets on Ethereum which could be used across multiple blockchains without bridging assets all the time. We continue to remain excited about the new possibilities and use cases that will be unlocked in the future.</p><p><strong>Sources:</strong></p><ul><li>Merkle Trees and Proofs: <a href="https://blog.ethereum.org/2015/11/15/merkling-in-ethereum">https://blog.ethereum.org/2015/11/15/merkling-in-ethereum</a></li><li>Herodotus: <a href="https://herodotusdev.medium.com/herodotus-101-ab1dd19155cb">https://herodotusdev.medium.com/herodotus-101-ab1dd19155cb</a></li><li>MMR: <a href="https://codyx.medium.com/over-the-proofs-a-world-of-trees-merkle-mountain-ranges-edition-%EF%B8%8F-dd4ac0e540fc">https://codyx.medium.com/over-the-proofs-a-world-of-trees-merkle-mountain-ranges-edition-%EF%B8%8F-dd4ac0e540fc</a></li><li>Ethereum stateless roadmap: <a href="https://notes.ethereum.org/Yn_mwNa2SeeQHnKsRgekKg">https://notes.ethereum.org/Yn_mwNa2SeeQHnKsRgekKg</a></li><li>Recproofs: <a href="https://uploads-ssl.webflow.com/6460ebf2b6ff254688bebf1c/64e4dd54d9198fde8d58ef44_main.pdf">https://uploads-ssl.webflow.com/6460ebf2b6ff254688bebf1c/64e4dd54d9198fde8d58ef44_main.pdf</a></li><li>Axiom: <a href="https://docs.axiom.xyz/">https://docs.axiom.xyz/</a></li><li>Hyper Oracle: <a href="https://docs.hyperoracle.io/">https://docs.hyperoracle.io/</a></li><li><a href="https://www.axiom.xyz/blog/how-axiom-works">https://www.axiom.xyz/blog/how-axiom-works</a></li><li><a href="https://notes.ethereum.org/@vbuterin/verkle_and_state_expiry_proposal">https://notes.ethereum.org/@vbuterin/verkle_and_state_expiry_proposal</a></li><li><a href="https://lagrange-labs.gitbook.io/lagrange-labs/overview/what-is-the-lagrange-protocol">https://lagrange-labs.gitbook.io/lagrange-labs/overview/what-is-the-lagrange-protocol</a></li><li><a href="https://www.youtube.com/watch?v=GbiV6exphuw">https://www.youtube.com/watch?v=GbiV6exphuw</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0f6e4e898550" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LongHashX Accelerator Partners with Protocol Labs to Launch the FVM Genesis Cohort, the World’s…]]></title>
            <link>https://longhashvc.medium.com/longhashx-accelerator-partners-with-protocol-labs-to-launch-the-fvm-genesis-cohort-the-worlds-9916f10be6b2?source=rss-7be833512009------2</link>
            <guid isPermaLink="false">https://medium.com/p/9916f10be6b2</guid>
            <dc:creator><![CDATA[LongHash Ventures]]></dc:creator>
            <pubDate>Thu, 03 Aug 2023 13:46:38 GMT</pubDate>
            <atom:updated>2023-08-17T15:09:45.731Z</atom:updated>
            <content:encoded><![CDATA[<h3>LongHashX Partners with Protocol Labs to Launch the FVM Genesis Accelerator, One of the World’s First Web3 Accelerators Focused on the Intersection of Web3 and AI</h3><p><em>The 12-week program offers two distinct routes to equip builders and founders with the knowledge, funding, and network needed to successfully launch their projects on the Filecoin Virtual Machine (FVM)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D2gm4qTf1FTmPhH1d5bLdQ.png" /></figure><p>LongHashX, one of the world’s leading Web3 accelerators, with the strongest network in Asia, is continuing its longstanding partnership with Protocol Labs, the creator of Filecoin and IPFS, to launch the historic first <a href="https://www.longhash.vc/accelerator/fvmgenesis/">Filecoin Virtual Machine (FVM) Genesis Accelerator</a>. The 12-week program, which comprises the FVM Accelerator Program as well as the FVM Builders’ Fellowship Program, aims to accelerate the growth of 25–30 projects leveraging the power of data programmability now enabled in Filecoin through FVM.</p><p>The FVM mainnet successfully launched on March 14, 2023, after more than a year of rigorous planning and iterations. With the introduction of smart contracts, FVM unlocks exciting possibilities for diverse applications to be built on the Filecoin network, including Artificial Intelligence (AI), DeFi, DAOs and others.</p><p>In particular, recent <strong>Artificial Intelligence</strong> breakthroughs, exemplified by the release of several powerful deep learning models like DALL-E 2, GPT-4, LaMDA, and others, require the input of enormous data to perform various human-like tasks. This has raised grave concerns around data privacy, centralization, and innovation restrictions. FVM is best positioned to disrupt the space and address these issues by empowering open-source AI development and compute-over-data, fostering a decentralized and collaborative approach to AI development.</p><p>This will be the fourth time that LongHashX and Protocol Labs work together to grow and support the developer community of the Filecoin ecosystem. Established in early 2018, LongHashX is the pioneer and leader in partnering with leading Web3 ecosystems to bootstrap their developer communities. Since its inception, LongHashX has partnered with Safe, Neutron, ATOM Accelerator DAO, Filecoin, Axelar, and Polkadot, among others, to accelerate more than 75 Web3 projects, including five unicorns, and helped them raise more than US$150m in funding. Notable program alumni include Astar, Balancer, Manta Network, Lit Protocol, Huddle01, Tranchess and Peanut Protocol.</p><p><em>“FVM is a game changer for the data economy. It enables us to reimagine entire verticals such as truly open AI models and Web3 social apps. This is made possible by novel Web3-native ideas like Data DAOs, to crowdsource and steward content, or compute over data that preserves privacy and data sovereignty. We are very excited to invest in and support early-stage builders on FVM to go from idea to Web3-native startup.” </em>said <a href="https://twitter.com/emmacui"><strong>Emma Cui</strong></a><strong>, Founding Partner and CEO of LongHash Ventures</strong>.</p><p>FVM Genesis Accelerator aims to identify, fund, and accelerate early-stage Web3 projects with compelling FVM use cases. With FVM’s general programmability on the Filecoin storage network, Web3 apps can operate seamlessly, automating processes while referencing data stored on the Filecoin network.</p><p><em>“The launch of the Filecoin Virtual Machine is a major milestone for the open data economy. Our partnership with LongHashX is part of our global strategy to drive innovation in this new era of decentralized compute-over-state and compute-over-data. Together, we invest in the architects of future data primitives. I can’t wait to kick off this cohort.” </em>said <a href="https://twitter.com/xxi_eth"><strong>Ruben Amenyogbo</strong></a><strong>, Partner and FOUNDERS Program Lead at Protocol Labs</strong>.</p><p><strong>Call for Applications</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fjLumeFMHH33HuRXXp49rw.png" /></figure><p>FVM unlocks a myriad of possibilities within the Filecoin network. LongHashX is particularly interested in the following use cases built on top of FVM:</p><ul><li><strong>Artificial Intelligence: </strong>Create truly open AI models by introducing decentralization and privacy in each step of the AI model production:</li></ul><ol><li><em>Data Collection and Provenance</em>: Utilize the collective and attributable governance found in DAOs to crowdsource, curate, and monetize diverse datasets used for training foundation AI models.</li><li><em>Model Training</em><strong>:</strong> Create decentralized training frameworks where the community collaboratively and privately trains foundation AI models, utilizing community-driven data and computational resources.</li><li><em>Model Inference</em><strong>:</strong> Ensure that the foundation AI model produces accurate and verifiable outputs based on the datasets sourced from the community.</li></ol><ul><li><strong>DeFi Use Cases:</strong> Introduce necessary DeFi use cases such as DEXes, lending/borrowing protocols, cross-chain bridges, staking or liquid staking protocols and others in FVM to improve liquidity and facilitate asset transfers.</li><li><strong>Decentralized Social:</strong> Create new social experiences where users can verify and manage their own social data on-chain.</li><li><strong>Open Category:</strong> Welcome any other use cases that could now be made possible using FVM. More potential use cases were listed by Protocol Labs here in the <a href="https://rfs.fvm.dev/#165717ed56aa44288669a698816ec7ae">Request for Startups guide</a>.</li></ul><p><strong>Two Tracks to Choose From</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_xjMbu3B9oceTZfL8oQ7Tw.png" /></figure><p><strong>FVM Accelerator Program</strong></p><p>Five projects building on FVM will be accepted into the LongHashX FVM Accelerator Program and each project will receive US$200,000 in funding.</p><p>On top of the funding received, these projects will also undergo the most Web3-native curriculum and hands-on support. The 12-week program in this cohort will include a series of workshops and fireside chats across seven modules, including Web3 Product Strategy &amp; Design, Ecosystem Deep Dive, Tokenomics &amp; Governance, Community Building, Smart Contract Security, Web3 Legal, and Fundraising.</p><p>Each project participating through this route will have a dedicated Program Lead and Venture Builder, who will meet them weekly for problem-solving sessions and to be a thought partner to help the founders with their toughest challenges.</p><p>In addition to the mentors from Filecoin and Protocol Labs, the selected projects will also get access to LongHash Web (LHW), the world’s first soulbound token-based on-chain contribution network, to meet one-on-one with notable mentors in the wider Web3 space that include leading founders, investors, and developers. LHW’s 100+ mentors include founders of Safe, Axelar, AltLayer, Balancer, Dodo; investors at Pantera, Polychain, Gumi, Multicoin, Collab+Currency, Hashkey, and DeFiance; and contributors at zkSync, Lens, Linea, Scroll, and Protocol Labs.</p><p>For these five projects, the program culminates in a Demo Day where they will have the opportunity to pitch to investors.</p><p><strong>FVM Builders’ Fellowship Program</strong></p><p>20–25 projects will be chosen for the FVM Builders’ Fellowship Program. These selected projects will receive the technical and developer support from Filecoin and Protocol Labs, will participate in workshops and fireside chats, and will have access to Mentor Office Hour sessions with LongHashX Venture Builders.</p><p>LongHashX will also facilitate a fast-tracked grant application process for these teams if they choose to apply for grants from Filecoin/ Protocol Labs.</p><p>The <a href="https://www.longhash.vc/accelerator/fvmgenesis/">LongHashX FVM Genesis Accelerator and Builders’ Fellowship Program</a> are scheduled to start around end of October. Builders have until 30 September 2023 11:59pm (GMT+8) to apply. Teams and projects interested in applying for the program can do so directly <a href="https://longhashventures.typeform.com/fvmgenesis">here</a>.</p><p>Read more about the cohort in this <a href="https://blockworks.co/news/filecoin-accelerator-program">article</a> covered by Blockworks.</p><h3>About LongHashX Accelerator</h3><p>LongHashX is one of the world’s leading Web3 accelerators, with the strongest network in Asia. We partner with the leading Web3 ecosystems and infrastructure protocols to build their developer communities by funding and venture building with early-stage founders.</p><p><strong>For more information, please visit:</strong> <a href="https://www.longhash.vc/accelerator/">Website</a> | <a href="https://twitter.com/LongHashX">Twitter</a></p><h3>About LongHash Ventures</h3><p>LongHash Ventures specializes in bootstrapping Web3 ecosystems. Our venture funds invest in early-stage Web3 protocols, and our LongHashX Accelerator partners with ecosystems and protocols to accelerate early-stage founders.</p><p><strong>For more information, please visit:</strong> <a href="https://www.longhash.vc/">Website</a> | <a href="https://twitter.com/LongHashVC">Twitter</a> | <a href="https://www.linkedin.com/company/longhashventures/mycompany/">LinkedIn</a></p><h3>About Filecoin</h3><p>Filecoin, the world’s largest decentralized storage network, enables users to store, request, and transfer data via a verifiable marketplace. Filecoin’s advanced technology provides a robust foundation to store the world’s most valuable datasets. An alternative to costly cloud storage, the Filecoin network offers efficiently priced and geographically decentralized storage, minimizing financial barriers and allowing users to take advantage of its unmatched network capabilities. Filecoin is completely open source, enabling people from all over the world to participate.</p><p><strong>For more information, please visit:</strong> <a href="https://filecoin.io/">Website</a> | <a href="https://twitter.com/Filecoin">Twitter</a></p><h3>About Protocol Labs</h3><p>Protocol Labs is an open-source research, development, and deployment laboratory that builds protocols, tools, and services to radically improve the internet. Protocol Labs’ projects are designed to fortify and democratize the web include <a href="https://ipfs.io/">IPFS</a>, <a href="https://filecoin.io/">Filecoin</a>, <a href="https://libp2p.io/">libp2p,</a> and more. As a fully distributed organization, Protocol Labs is dedicated to driving breakthroughs in computing to push humanity forward.</p><p><strong>For more information, please visit:</strong> <a href="https://protocol.ai/">Website</a> | <a href="https://twitter.com/protocollabs">Twitter</a> | <a href="https://www.linkedin.com/company/protocollabs/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9916f10be6b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Future of Smart Accounts: Modular, Specialised & Multichain]]></title>
            <link>https://longhashvc.medium.com/future-of-smart-accounts-modular-specialised-multichain-d04f083375a6?source=rss-7be833512009------2</link>
            <guid isPermaLink="false">https://medium.com/p/d04f083375a6</guid>
            <category><![CDATA[crypto-wallet]]></category>
            <category><![CDATA[account-abstraction]]></category>
            <category><![CDATA[erc-4337]]></category>
            <dc:creator><![CDATA[LongHash Ventures]]></dc:creator>
            <pubDate>Mon, 31 Jul 2023 11:36:09 GMT</pubDate>
            <atom:updated>2023-08-04T07:35:31.992Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Thanks to Aniket, Ahmed, Sachin, and Fil from Biconomy, Lukas &amp; Clem from Safe, Derek from ZeroDev, Corbin from Patch Wallet, and Konrad from Rhinestone for their feedback.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FUY-ZRhrwLEb1AcvquE-uw.png" /></figure><p>About 10 years ago, frontend frameworks like React, Angular, and Vue accelerated Web2 adoption by shifting server-side logic to client-side. Frontend and backend decoupled, and users began interacting with applications more seamlessly.</p><p>Similarly, as smart accounts bring more logic to the user’s direct control (e.g. batched transactions, customised gas payments), they are well-positioned to improve crypto UX and accelerate Web3 adoption.</p><p>To achieve this, we believe two shifts will occur:</p><ol><li>The shift from externally-owned accounts to <em>modular</em> smart accounts</li><li>The shift from generalised wallets to <em>specialised</em> smart wallets</li></ol><p><strong>Why Modular</strong></p><p>Developing and maintaining AA infrastructure for batched transactions, paymasters, and session keys are non-trivial. Session keys, for instance, require secure session key storage infrastructure. In order for future wallets to maintain account feature parity with their competitors without the burden of maintaining infrastructure, they are more likely to integrate bundlers, paymasters, and session keys built by specialised infra players rather than build the same capabilities in-house.</p><p>Additionally, wallets may integrate modules to extend their functionality (e.g. privacy) or provide safeguards for transactions (e.g. spending limits). These modules require thorough audits, so wallets may opt to integrate <em>verified</em> modules rather than build their own.</p><p>Wallets may also integrate external modules to:</p><ul><li>Integrate ready-made capabilities for convenience (e.g. Safe {Wallet} integrating <a href="https://twitter.com/safe/status/1673324154182053889">Redefine’s transaction risk scanner</a>), or;</li><li>Leverage modules that have built network effects (e.g. a future scam prevention module that maintains the greatest coverage of scams)</li></ul><p>The stack for developers to create their own smart wallets or embed them into their dApps is as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ywYp_69W6FMkRpla8NpAKA.png" /></figure><p>Building on top of the individual components, three players are emerging as aggregators of signing methods, logic modules, and execution infrastructure, akin to “module app stores”: Safe {Core}, Biconomy, and ZeroDev. They simplify the developer experience of building smart accounts with all-in-one, extensible wallet-as-a-service solutions. ZeroDev, for example, aggregates and routes userOps through various bundler &amp; paymaster infrastructure to abstract 4337 complexity from the developer, while providing various web3 onboarding/signing solutions to choose from.</p><p>While full-stack solutions aggregate existing established infrastructure, the market for modules remains relatively immature. At the time of writing, and as we can see from the figure below, most modules have been built in-house by the “module app stores”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MBfiav-ndqtW09Q5mJKYVA.png" /></figure><p>One of the factors modules would consider to choose which ecosystems to enter is by assessing the customers they’d have access to. We see early signs of this with modules like <a href="https://twitter.com/anirudh_chohan/status/1674367012817227776">Redefine</a> &amp; <a href="https://twitter.com/anirudh_chohan/status/1674367008962641921">Tenderly</a> choosing to build on top of Safe to leverage their existing customer base around DeFi-focused institutions.</p><p>Beyond customer access, we expect the leading ecosystems to be built by a factor of perceived security, developer experience, and importantly, their network effects from their ecosystem of extensible modules/plugins.</p><p>These “module marketplaces” appear to be the most monetisable area in smart account infrastructure today, as they can build moats around the network effects accrued by its ecosystem of modules and customers, and subsequently earn from revenue sharing, platform fees, MEV, and audits for the modules.</p><p><strong>Why Specialised</strong></p><p>We believe that as web3 use cases and users become increasingly diverse, generalist wallets will leave unmet needs that customised wallets can satisfy. The Safe {Wallet} has been a prime example — filling the security needs for organisations that the retail-focused Metamask left unmet. Metamask themselves is now spinning up Snaps to customise for certain use cases, albeit remaining as EOAs.</p><p>Modular smart accounts allow for permissionless combinations of smart account modules to create specialised wallets. By permissionlessly augmenting their smart accounts with modules, users would have access to wallets that more closely align to their web3 needs.</p><p>Castle, for instance, specialises their smart wallet to high-net-worth NFT owners by leveraging Safe’s battle-tested multisig contracts to secure their NFTs, and will incorporate scam prevention and transaction simulation modules to provide additional security in the future.</p><p>Rhinestone is a new project that envisions a future wherein users can drag-and-drop smart account modules to create their own custom wallets. This would enable casual mobile gamers, for example, to create wallets where they can sign in using face ID on their secure enclave, use session keys, and lend NFTs within a certain time limit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lcUK6mt0zLapBqg5JoZwRA.png" /><figcaption>Screenshot from Rhinestone’s ETHDenver demo.</figcaption></figure><p>As new sectors of Web3 find product-market-fit, we expect specialist wallets to capture market share as they tailor more closely to specific user needs. Gamers, DeFi users, and NFT collectors already have existing smart wallets to use, but the sectors remain relatively competitive (with no clearly dominant player).</p><p>The emerging sector of web3 social is also yet to have its go-to smart wallet. <a href="https://app.patchwallet.com/">Patch Wallet</a> is a new project that allows anyone with a Twitter account to have a smart account by default (even before they sign up), which bridges web2 social graphs with crypto wallets, but few others stand out so far.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9JoNz7ZO2lGDU-nNwisTlA.png" /><figcaption><em>Current landscape of specialised wallets and wallets-as-a-service, and the markets they serve.</em></figcaption></figure><p>While gaming and DeFi attract the most number of crypto users, web3 social is an emerging sector that has yet to have a prominent smart wallet.</p><p>We believe that smart accounts will be customised by vertical in the following ways:</p><ul><li><strong>Organisations &amp; High-Net-Worth Individuals (HNWIs)</strong>: Prioritising battle-tested security, it is difficult to imagine institutions &amp; high net-worth individuals opting out from wallets built on top of the Safe protocol, which has acquired Lindy effects as their moat. Wallets built on top of the protocol, such as their own Safe Multisig {Wallet}, may incorporate privacy, delegation, and scam prevention modules. An institution-focused mobile wallet secured by Safe, that eases accessibility &amp; UX, remains a white space.</li><li><strong>Gamers</strong>: There is often limited interoperability of gaming assets, and gaming studios prioritise smooth onboarding of new users. Hence, we believe embedded wallets-as-a-service that prioritise smooth, low-cost onboarding and key management, with transaction delegation (e.g. allowing the dapp to return NFT assets to the lender after the rental period automatically) and session keys will capture majority market share here.</li><li><strong>DeFi Traders &amp; Farmers</strong>: Financial actors rarely differentiate between apps, prioritising aggregated liquidity, automation, and multichain coverage. We predict that an app-based DeFi wallet akin to a platform that aggregates liquidity, curates DeFi strategies, and abstracts multichain complexity will emerge as a market leader for DeFi-focused smart accounts. It may also include MEV-proficient bundlers who auction off MEV from users’ transactions and return it back as rebate.</li><li><strong>NFTs</strong>: As a space riddled by scams, the next modular smart account focused on NFTs will incorporate transaction simulation and scam prevention for security, while facilitating NFT discovery through curation and personalisation on its frontend.</li><li><strong>Social</strong>: Key to decentralised social is interoperable identity. As a result, social-focused smart accounts will need to be interoperable across social networks (rather than embedded). Mobile wallets enable better accessibility but needs to provide access to a range of social networks through aggregation, API, or as a mobile browser extension (a-la <a href="https://www.dawnwallet.xyz/">Dawn Wallet</a>).</li></ul><p>Across verticals, we expect bundled transactions and sponsored gas to be commoditised and popularised as default features of specialised smart wallets.</p><p>Heavy on-chain users, institutions/organisations, and HNWIs may also be drawn towards wallets integrated with privacy modules to protect their on-chain footprints. In order for privacy to gain mainstream retail adoption, however, the process to privatise transactions must be completely frictionless (see: <a href="https://elusiv.io/">Elusiv</a>).</p><p><strong>The Endgame</strong></p><p>Moving forward, we need the following for modular smart accounts to succeed:</p><ol><li>Interoperability, through a standard which ensures that modules can be composable with one another (<a href="https://ethereum-magicians.org/t/erc-6900-modular-smart-contract-accounts-and-plugins/13885">EIP-6900</a> is being drafted for this).</li><li>Discovery, through the aforementioned “module app stores” and registries such as <a href="https://docs.rhinestone.wtf/">Rhinestone</a></li><li>Security, possibly through a minimum viable standard that modules should abide by to prevent issues such as <a href="https://safe.mirror.xyz/P83_rVQuUQJAM-SnMpWvsHlN8oLnCeSncD1txyMDqpE">storage collision</a></li></ol><p>Importantly, in a future where a user will deploy multiple smart contract accounts across chains, we need to <em>abstract the multichain experience</em>.</p><p>It would be extremely cumbersome, for instance, if a user would need to sign multiple transactions across chains to change his guardian or add an authorisation module. He should be able to sign once, and allow the dApp/wallet to execute multiple userOps on multiple chains.</p><p>Vitalik <a href="https://vitalik.ca/general/2023/06/09/three_transitions.html">suggests</a> that smart account keys may be located on one chain (e.g. L1 or L2) where a “keystore contract” would be deployed. Verification logic on other chains’ accounts would point towards the keystore contract, and spending from accounts on other chains would require a proof (e.g. zk-snark) going into the contract.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/381/0*RPpbEV6Syr2CkjNW.png" /></figure><p>Biconomy is also building a “Multichain Session Keys” module to allow dApps to embed smart accounts that can execute UserOps on multiple chains with one signature by constructing Merkle trees (see implementation <a href="https://github.com/bcnmy/scw-contracts/blob/feat-Multichain-SessionKey-management/contracts/smart-account/modules/MultichainValidator.sol">here</a>). And to simplify the experience of transferring funds to different addresses across chains, <a href="https://peanut.to/">Peanut Protocol</a> is leveraging Axelar to enable cross-chain transfers with URLs.</p><p>In the more distant future, we expect smart accounts to incorporate <strong>intents</strong> and <strong>LLMs</strong>.</p><p>We envision the future smart wallet to be able to:</p><ol><li>Use LLMs to decode user intents into atomic transactions</li><li>Allow a user to delegate transaction execution to the smart wallet within certain user-defined limits, while maintaining self-custody</li><li>Prompt for user’s approval once the intent is parsed</li><li>Abstract the cross-chain experience &amp; execute the user’s intent with a decentralised network of AI agents / solvers</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5nwmFUOtHSdxxxBDwZCy3g.png" /></figure><p>To realise this vision, we need:</p><ul><li>A progressively-decentralised, permissionless network of AI agents to find “best paths forward” for the user to obtain his/her intent, akin to CoW Protocol’s solvers</li><li>Embeddings to applications across chains, possibly through an AMP (arbitrary-message-passing) protocol (e.g Axelar, Layer Zero)</li></ul><p>The key challenge is to build an intent-centric network of solvers that is sufficiently decentralised. To ensure this, the solvers may be open-source AI agents themselves (once they are sufficiently efficient vs centralised solvers). If so, intents could become the default way for users to interact in a multichain world.</p><p>The first AI-powered cross-chain smart account may be generalised, but they may be vertical-specific thereafter. The ambitious team at Banana Wallet is incorporating Axelar to abstract the multichain experience for Safe smart accounts, and hacked an <a href="https://www.youtube.com/live/NVuMhlU3Faw?feature=share&amp;t=4354">intent-centric wallet application</a> at ETHcc. We’d be excited to meet projects building towards a vision of intent-centric, AI-driven, cross-chain smart accounts while maintaining the values of self-custody.</p><p>In sum, we expect accounts to shift from monolithic to modular, and generalised to specialised. They could abstract the multichain experience and incorporate intents to become the default way for web3 users to interact in a multichain world.</p><p>Driving this transition will be the module builders. While batched transactions and sponsored gas are necessary features to improve crypto UX, the innovation from module builders — especially those focused on abstracting the multichain experience — will drive the significant step-changes required for crypto to transition from EOAs to modular smart accounts.</p><p>Gone are the days where wallets are simply a pop-up to sign; they are now the new battleground of permissionless and composable innovation.</p><p><strong>References:</strong></p><ul><li>Safe Modular Architecture: <a href="https://safe.mirror.xyz/t76RZPgEKdRmWNIbEzi75onWPeZrBrwbLRejuj-iPpQ">https://safe.mirror.xyz/t76RZPgEKdRmWNIbEzi75onWPeZrBrwbLRejuj-iPpQ</a></li><li>Cross-chain Safe accounts: <a href="https://forum.safe.global/t/how-can-a-safe-hold-asset-on-multiple-chains/2242?u=longhash_ventures">https://forum.safe.global/t/how-can-a-safe-hold-asset-on-multiple-chains/2242?u=longhash_ventures</a></li><li>Three Transitions by Vitalik: <a href="https://vitalik.ca/general/2023/06/09/three_transitions.html">https://vitalik.ca/general/2023/06/09/three_transitions.html</a></li><li>Banana’s intent-centric wallet hack: <a href="https://www.youtube.com/live/NVuMhlU3Faw?feature=share&amp;t=4354">https://www.youtube.com/live/NVuMhlU3Faw?feature=share&amp;t=4354</a></li><li>ZeroDev Docs: <a href="https://docs.zerodev.app/extend-wallets/overview">https://docs.zerodev.app/extend-wallets/overview</a></li><li>Biconomy Modular Architecture: <a href="https://www.biconomy.io/post/making-biconomy-smart-accounts-modular">https://www.biconomy.io/post/making-biconomy-smart-accounts-modular</a></li><li>EIP-6900, modular smart account standard: <a href="https://ethereum-magicians.org/t/erc-6900-modular-smart-contract-accounts-and-plugins/13885">https://ethereum-magicians.org/t/erc-6900-modular-smart-contract-accounts-and-plugins/13885</a></li><li>Safe, Redefine &amp; Tenderly: <a href="https://twitter.com/safe/status/1673324154182053889">https://twitter.com/safe/status/1673324154182053889</a></li><li>Safe In-house Modules: <a href="https://github.com/safe-global/safe-modules/tree/master">https://github.com/safe-global/safe-modules/tree/master</a></li><li>Safe {Core} SDK: <a href="https://safe.global/core">https://safe.global/core</a></li><li>Permissive module docs: <a href="https://docs.permissive.dev/documentation/what-is-permissive">https://docs.permissive.dev/documentation/what-is-permissive</a></li><li>Permissive &amp; Safe: <a href="https://twitter.com/permissivelabs/status/1657486440115191810">https://twitter.com/permissivelabs/status/1657486440115191810</a></li><li>Castle, Safe-based NFT wallet: <a href="https://castle.link/">https://castle.link/</a></li><li>Patch Wallet: <a href="https://app.patchwallet.com/">https://app.patchwallet.com/</a></li><li>Users by vertical, <a href="https://dappradar.com/blog/state-of-blockchain-gaming-in-q1-2023">Q1</a> and <a href="https://dappradar.com/blog/state-of-the-dapp-industry-in-q2-2023">Q2</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d04f083375a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LongHashX & Safe Launch the Safe{AAccelerator}, the World’s First Account Abstraction Accelerator…]]></title>
            <link>https://longhashvc.medium.com/safe-and-longhashx-launch-safe-aaccelerator-the-worlds-first-account-abstraction-accelerator-to-3727bf37b6b7?source=rss-7be833512009------2</link>
            <guid isPermaLink="false">https://medium.com/p/3727bf37b6b7</guid>
            <dc:creator><![CDATA[LongHash Ventures]]></dc:creator>
            <pubDate>Thu, 27 Jul 2023 12:06:13 GMT</pubDate>
            <atom:updated>2023-08-17T15:10:31.664Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>LongHashX &amp; Safe Launch the <em>Safe{AAccelerator}, the</em> World’s First Account Abstraction Accelerator to Fast-Track the Transition to Smart Accounts</strong></h3><p><em>The 12-week program comprises an accelerator and a builder fellowship program, both designed to provide founders and builders with the necessary knowledge, funding, and network to launch their projects successfully on the Safe{Core} Smart Account Standard and scale it for different use-cases.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cV8FcBPpaCsqQbd-" /></figure><p>LongHashX, one of the world’s leading Web3 accelerators with the strongest network in Asia, has announced the launch of its 13th cohort, the world’s first accelerator program for projects building on top of the Safe{Core}, focused on the adoption of Smart Accounts. The 12-week program, which comprises the Safe Accelerator Program as well as the Safe Builders’ Fellowship Program, aims to accelerate the growth of 25–30 projects leveraging Safe{Core}, the modular and open source Account Abstraction stack.</p><p>LongHashX partners with leading Web3 ecosystems to bootstrap their developer communities. Since its inception in early 2018, LongHashX has partnered with Filecoin, Polkadot, Axelar, Algorand and ATOM Accelerator DAO, among others, to accelerate more than 75 Web3 projects, including five unicorns, and helped them raise more than US$150m in funding. Notable program alumni include Astar, Balancer, Manta Network, Lit Protocol, Huddle01, Tranchess and Peanut Protocol.</p><p><em>“The Safe team is working tirelessly to realize a seamless future within Web3. The growth of Safe{Core} will allow developers to select specific features to ensure the best UX for their end users. As investors in Safe, we are excited to accelerate projects that are contributing to the expansion of Safe{Core} and those who are growing the utilization of Safe{Core} through our accelerator arm, LongHashX. We believe account abstraction is the key to lowering the barrier to onboarding the next billion users, and we are very excited to invest in and support early-stage builders on Safe{Core}.</em>” says<strong> </strong><a href="https://twitter.com/emmacui"><strong>Emma Cui</strong></a><strong>, Founding Partner and CEO of LongHash Ventures.</strong></p><p><strong>Call for applications</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pKR0ppa06bTaSK8X" /></figure><p>The Safe{Accelerator} is interested in accelerating projects building on top of Safe. Specifically, projects that are interested in bringing the broad range of Account Abstraction capabilities that Safe{Core} can offer, and expanding them, to new and existing users/markets, especially those in under-tapped verticals such as onchain infra, identity, gaming, social, e-commerce and institutional amongst others.</p><p>In order to unlock these innovative use cases with Safe, eligible projects can:</p><ol><li><strong>Build new Safe Plugins</strong> (also known as Modules), and add any custom logic and features to the Safe contracts such as (non-exhaustive):<br>- Role based access control<br>- Automated payment streams<br>- Recovery mechanisms<br>- Session keys</li><li><strong>Develop new Safe Hooks</strong> (also known as Guards) which enforce an additional onchain security layer to Safe contracts, and can enable(non-exhaustive):<br>- App/protocol allow &amp; deny lists<br>- Spending policies<br>- Conditional security checks</li><li>Projects can also <strong>extend the functionalities of the </strong><a href="https://safe.mirror.xyz/t76RZPgEKdRmWNIbEzi75onWPeZrBrwbLRejuj-iPpQ"><strong>Function Handler</strong></a> to prevent Safes from encountering any errors in an ever changing Web3 landscape. Or bring new <a href="https://safe.mirror.xyz/t76RZPgEKdRmWNIbEzi75onWPeZrBrwbLRejuj-iPpQ">Signature Verifiers</a> to augment the signing experience of the next billion users coming to Web3.</li><li>Any project is also free to <strong>further augment and leverage the Safe{Core} Account Abstraction kits</strong>, which offer direct SDK integrations to improve UX in 3 domains, namely:<br>- <a href="https://docs.safe.global/learn/safe-core/safe-core-account-abstraction-sdk/auth-kit">Auth Kit</a>: Onboard new users via their social login credentials<br>- <a href="https://docs.safe.global/learn/safe-core/safe-core-account-abstraction-sdk/onramp-kit">Onramp Kit</a>: Purchase tokens directly using fiat<br>- <a href="https://docs.safe.global/learn/safe-core/safe-core-account-abstraction-sdk/relay-kit">Relay kit</a>: Pay gas fees using any ERC-20 tokens</li></ol><p><em>“We are at the dawn of a new era in Web3, where smart accounts bring opportunities for innovation and growth. The launch of the Safe Accelerator and Builders’ Fellowship Program will enable teams that are building on Safe, the most battle-tested smart account. Our aim is to inspire and equip a new generation of builders who can unlock the full potential of Safe{Core}, expanding its reach and impact to serve the next billion users of Web3.</em>” <strong>said </strong><a href="https://twitter.com/SchorLukas"><strong>Lukas Schor</strong></a><strong>, co-founder of Safe.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MGLZ1mMGPaffmtsVaeflsg.jpeg" /></figure><p><strong>Safe Accelerator Program</strong></p><p>Five projects building on Safe will be accepted into the LongHashX Accelerator Safe Cohort and each project will receive US$200,000 in funding.</p><p>On top of the funding received, these projects will also undergo the most web3-native curriculum and hands-on support. The 12-week program in this cohort will include a series of workshops and fireside chats across seven modules, including Web3 Product Strategy &amp; Design, Ecosystem Deep Dive, Tokenomics &amp; Governance, Community Building, Smart Contract Security, Web3 Legal, and Fundraising.</p><p>Each project participating through this route will have a dedicated Program Lead and Venture Builder, who will meet them weekly for problem-solving sessions and to be a thought partner to help the founders with their toughest challenges.</p><p>In addition to the mentors from Safe, the selected projects will also get access to LongHash Web (LHW), the world’s first soulbound token-based on-chain contribution network, to meet one-on-one with notable mentors in the wider Web3 space that include leading founders, investors, and developers. LHW’s 100+ mentors include founders of Safe, Axelar, AltLayer, Balancer, Dodo; investors at Pantera, Polychain, Gumi, Multicoin, Collab+Currency, Hashkey, and DeFiance; and contributors at zkSync, Lens, Linea, Scroll, and Protocol Labs.</p><p>For these five projects, the program culminates in a Demo Day where they will have the opportunity to pitch to investors.</p><p><strong>Safe Builders’ Fellowship Program</strong></p><p>20–25 projects will be chosen for the Safe Builders’ Fellowship Program. These selected projects will receive the technical and developer support from Safe, will participate in workshops and fireside chats, and will have access to Mentor Office Hour sessions with LongHashX Venture Builders.</p><p>LongHashX will also facilitate a fast-tracked grant application process for these teams if they choose to apply for grants from Safe.</p><p>The <a href="https://www.longhash.vc/accelerator/safe-cohort/">LongHashX Safe Accelerator and Builders’ Fellowship Program</a> are scheduled to start in mid-October. Builders have until 29 September 2023 11:59pm (GMT+8) to apply. Teams and projects interested in applying for the program can do so directly <a href="https://longhashventures.typeform.com/safecohort">here</a>.</p><h3>About LongHashX Accelerator</h3><p>LongHashX is one of the world’s leading Web3 accelerators, with the strongest network in Asia, and works closely with ecosystem and infrastructure partners to accelerate the world’s next generation of early-stage founders.</p><p><strong>For more information, visit:</strong> <a href="https://www.longhash.vc/accelerator/">Website</a> | <a href="https://twitter.com/LongHashX">Twitter</a></p><h3>About LongHash Ventures</h3><p>LongHash Ventures specializes in bootstrapping Web3 ecosystems. Our venture funds invest in early-stage Web3 protocols, and our LongHashX Accelerator partners with ecosystems and protocols to accelerate early-stage founders.</p><p><strong>For more information, visit:</strong> <a href="https://www.longhash.vc/">Website</a> | <a href="https://twitter.com/LongHashVC">Twitter</a> | <a href="https://www.linkedin.com/company/longhashventures/mycompany/">LinkedIn</a></p><h3>About Safe</h3><p>Safe (previously Gnosis Safe) is a decentralized custody protocol, securing <a href="https://dune.com/safe/all">~$60 Billion</a> in assets today. It is establishing a universal standard for the secure custody of digital assets, data, and identity. With Safe{Wallet}, its flagship web and mobile wallet, and Safe{Core} Smart Account infrastructure, Safe is on a mission to unlock digital ownership for everyone in web3 including DAOs, enterprises, retail, and institutional users.</p><p><strong>For more information, visit:</strong> <a href="https://safe.global/">Website</a> | <a href="https://twitter.com/Safe">Twitter</a> | <a href="https://safe.mirror.xyz/">Mirror</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3727bf37b6b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we invested in Neutron]]></title>
            <link>https://longhashvc.medium.com/why-we-invested-in-neutron-855b5af3a711?source=rss-7be833512009------2</link>
            <guid isPermaLink="false">https://medium.com/p/855b5af3a711</guid>
            <dc:creator><![CDATA[LongHash Ventures]]></dc:creator>
            <pubDate>Fri, 07 Jul 2023 11:06:17 GMT</pubDate>
            <atom:updated>2023-07-07T11:06:17.999Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The Cosmos ecosystem was designed with the vision of creating an internet of blockchains. The philosophy behind the architecture was that each project should be able to spin up their own dedicated blockchain, modify it to a large extent based on their application requirements, and retain the security properties while having the ability to interoperate with each other. All the modules of the CosmosSDK and Inter-Blockchain Communication (IBC) were designed with this purpose in mind. This architecture did solve a lot of problems that exist in other blockchain architectures like limited scalability, network congestion, and less flexibility for developers. However, this approach had a few challenges of its own.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*14jmRxrYsF9Ct1M-" /></figure><p><strong>Current Challenges</strong></p><p>For applications that already have good traction, for example dydx, it makes more sense to build your own app-specific chain. However, developing a blockchain for early-stage applications is challenging since it requires good technical knowledge and is time-consuming. Since each blockchain is responsible for its own security, they are required to bootstrap their own network of validators. This is resource-intensive and time-consuming. Moreover, achieving a high level of security with a new token is not feasible because the total capital staked by validators is quite low before the application gets significant traction and the token price appreciates. This poses a chicken-and-egg problem as applications struggle to achieve traction before the blockchain is secure. This slows the iterations and inhibits early-stage developers from experimenting with novel use cases in Cosmos. DeFi adoption in Cosmos has lagged behind other ecosystems due to low liquidity, low security of Cosmos smart contract platforms, and competition from high staking rewards.</p><p><strong>ATOM Community Alignment</strong></p><p>A pure app-chain approach also does not lead to any value accrual to ATOM tokens on a long-term basis leading to a lack of alignment with the ATOM community. While there exists some alignment via airdrops as most new projects in Cosmos airdrop their tokens to ATOM holders, this is not an ongoing relationship.</p><p><strong>Neutron Approach</strong></p><p>In order to solve these challenges, the Proposal 72, proposed in June 2022, marked a soft consent in favor of Replicated Security (RS). RS is a shared security system that allows a larger chain (for example Cosmos Hub), known as the provider chain, to provide security to a smaller chain, known as the consumer chain. Using IBC, the provider chain sends a series of messages to the consumer chains’ consensus engine. These messages will notify the consumer chain of the validators participating in its validator set as well as the share of voting power that these validators obtained by staking on the provider chain. In exchange, the provider chain receives fees and revenue from the consumer chain as part of a flexible security agreement. Neutron is the first consumer chain to leverage the Cosmos Hub as the provider chain. Proposal 72 also accelerated this development through the earmarking of 150k ATOM from the community pool to fund projects that support and that are supported by RS, including Neutron.</p><p>By launching as the consumer chain of Replicated security, Neutron</p><ul><li>Has the highest level of security in the Cosmos ecosystem from the day of launch</li><li>Has immediate incentive-alignment with the ATOM community by sharing 25% of the transaction fees and MEV revenue with the Hub</li><li>Marks the beginning of Atom Economic Zone (AEZ), which is an ecosystem comprising of the Cosmos Hub and its Partner/Consumer Chains which are synergistically aligned around the hub to mutually strengthen the ecosystem.</li></ul><p>Neutron is a permissionless blockchain that allows anyone to easily launch their application by using CosmWasm smart contracts. Neutron lets projects leverage RS as smart contracts without generating any additional cost for the Hub. Now, projects have the option to launch their application in the Cosmos ecosystem without any concerns about security and without spending too much time and resources on blockchain development. Neutron has been designed to develop a strong cross-chain DeFi ecosystem and strengthen ATOM’s position as Cosmos’ base asset. This is being done by leveraging the power of Interchain Accounts (ICA), Interchain Queries (ICQ), CosmWasm smart contracts, and modular governance. The functionality of ICA and ICQ can be achieved today even without the ICA and ICQ modules, but it requires the logic to be coded at the chain level. ICA and ICQ will allow projects to leverage these functionalities at the smart contract level in a standardized format making the applications more programmable.</p><p><strong>Interchain Accounts (ICA)</strong></p><p>ICA allows one blockchain to securely control an account on another blockchain, using IBC. Cosmos ecosystem blockchains can access the application features of another chain and carry out any action native to that chain. Before ICA, if a user had different tokens like $ATOM, $OSMO, $EVMOS staked across the ecosystem, they were required to go to each chain to claim rewards. Using ICA, they can perform these actions from a single blockchain. This will be particularly useful for liquid staking application, Lido, which will soon launch on Neutron.</p><p><strong>Interchain Queries (ICQ)</strong></p><p>ICQ enables applications on Chain A to query chain B to perform some transactions on chain A. With ICQ, queries are packaged as an IBC packet on the querying chain. With an IBC channel established with the target chain, the IBC packet carrying the query is simply sent to the target chain with the help of relayers. On arrival, the IBC packet is unpacked by the ICQ module to reveal the query which is then executed on the application layer of the target chain, just as normal domestic queries within a homogenous blockchain network. Finally, the response of the query is sent to the querying chain within the returned IBC packet acknowledgment. ICA and ICQ together can be used to perform multichain liquid staking. ICQ can be used to query the accrued reward balance for liquid staking on another chain and ICA can be used to transfer the rewards to the delegation account on the host chain.</p><p><strong>Governance and Liquidity Module</strong></p><p>Modular governance has been designed in Neutron to avoid voter fatigue, allow the chain economy to adapt to market conditions, and incentivize users to provide more liquidity. In return for bonding NTRN tokens, users will get voting power in the DAO which controls the treasury or the community pool. The tokens in the reserve pool are not liquid and are released based on the on-chain activity. High on-chain activity and revenue translate to more tokens being released by the reserve, which instead of directly going to the treasury, pass through a distribution module. The distribution module can direct a certain portion of the tokens to a module like a liquidity module from where they can be directed to different liquidity pools. The users, based on their voting power, can decide the allocation of tokens across different pools. This creates a strong incentive for users to provide liquidity. Users can provide liquidity, get voting power based on provided liquidity and use the voting power to programmatically direct the liquidity from the reserve into pools of their choice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IcE2UnU12_YXP97D" /></figure><p><strong>New Era for DeFi</strong></p><p>ICA and ICQ will together unlock new composable utilities. By leveraging ICA, ICQ, modular governance along with CosmWasm, Neutron will foster the development of applications that will enable users to use native and liquid-staked ATOM to provide liquidity, lend, borrow, wield governance power, strip bonds, and more. Astroport is an excellent example of the kind of cross-chain applications that will be built on Neutron. Astroport was initially a single blockchain protocol operating solely on Terra. It has now expanded to other networks such as Neutron and Injective, with an upcoming launch on Sei Network. As a next-generation AMM and DEX, Astroport embraces the power of IBC to create a unified, cross-chain experience and supports cross-chain governance, token transfers, and fee collection. Other projects working on integrating with Neutron include:</p><ul><li>Lido (Liquid staking derivatives platform)</li><li>Mars Protocol (looking to deploy the second outpost on Neutron after launching the first outpost on Osmosis)</li><li>Catalyst (cross-chain swaps between Neutron and other Catalyst-enabled chains)</li><li>Pulsar Finance (cross-chain portfolio management platform)</li><li>Amulet Finance (self-repaying loans)</li><li>Coinhall (Track real-time price charts &amp; analytics for all token pairs)</li><li>Celaton (smart-contract explorer already live on Neutron)</li></ul><p>Primitives such as DAODAO, Timewave, and Gitcoin could possibly launch on Neutron, enabling the Hub to have the tools to enter secure, programmatic agreements with other chains, protocols, and treasuries like tokenswaps, quadratic funding rounds, loan agreements, protocol-owned liquidity, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PDK0v9yYaGPLOcZk" /></figure><p><strong>Conclusion</strong></p><p>Neutron’s highly secure nature, neutral positioning, and a feature set designed for cross-chain smart contracts make it an attractive home for DeFi and other cross-chain dApps. Neutron will empower developers and users to transact and innovate without borders or limitations. LongHash Ventures is committed to playing an active role in the adoption and growth of Neutron by actively contributing to the discussions in governance forums and launching an AEZ Accelerator &amp; Builders’ Fellowship in partnership with ATOM Accelerator DAO. Having incubated more than 70 projects in the past in partnership with ecosystems like Polkadot, Filecoin, and Axelar, Our accelerator arm LongHashX will now support 25–30 startups and accelerate the growth of the 5 most promising projects building on Neutron and the ATOM Economic Zone. We strongly believe that Neutron is ushering a new era to Cosmos and is in a prime position to power a new generation of cutting-edge composable cross-chain applications.</p><p><strong>About LongHash Ventures</strong></p><p><em>LongHash Ventures specializes in bootstrapping Web3 ecosystems. Our venture funds invest in early-stage Web3 protocols, and our LongHashX Accelerator partners with ecosystems and protocols to accelerate early-stage founders.</em></p><p><strong>About LongHashX</strong></p><p><em>LongHashX is one of the world’s leading Web3 accelerators with the strongest Asian network. We partner with the leading Web3 ecosystems and infrastructure protocols to build their developer communities by funding and venture-building with early-stage founders.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=855b5af3a711" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LongHashX Accelerator Partners with ATOM Accelerator DAO & Neutron to Launch the World’s First…]]></title>
            <link>https://longhashvc.medium.com/longhashx-accelerator-partners-with-atom-accelerator-dao-neutron-to-launch-the-worlds-first-ccb3cd630bb8?source=rss-7be833512009------2</link>
            <guid isPermaLink="false">https://medium.com/p/ccb3cd630bb8</guid>
            <category><![CDATA[accelerator]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[atom]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[investment]]></category>
            <dc:creator><![CDATA[LongHash Ventures]]></dc:creator>
            <pubDate>Mon, 03 Jul 2023 23:43:14 GMT</pubDate>
            <atom:updated>2023-10-02T03:33:54.277Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>LongHashX Accelerator Partners with ATOM Accelerator DAO &amp; Neutron to Launch the World’s First Accelerator And Builders’ Fellowship Program for Cosmos Partner Chains</strong></h3><p><em>The 12-week program offers two distinct routes, designed to provide founders and builders with the necessary knowledge, funding, and network to successfully launch their projects on Cosmos’ Partner Chains</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AguPf-qR-oOrFN_gIL0IvQ.png" /></figure><p>LongHashX, the world’s leading Web3 accelerator, has announced the launch of the historic first program focusing on accelerating projects on Cosmos’ Partner Chains, in partnership with Neutron and ATOM Accelerator DAO. The 12-week program, which comprises the Cosmos Accelerator Program as well as the Cosmos Builders’ Fellowship Program, aims to accelerate the growth of applications built in the ATOM Economic Zone including those building on Neutron.</p><p>LongHashX partners with leading Web3 ecosystems to bootstrap their developer communities. Since its inception in early 2018, LongHashX has partnered with Filecoin, Polkadot, Axelar, and Algorand, among others, to accelerate more than 70 Web3 projects. Notable program alumni include Acala, Astar, Balancer, Mintable, Xanpool, Manta network, Lit Protocol, Tranchess, Lighthouse, and Huddle01. LongHashX has helped these projects raise more than US$150m in funding and has accelerated five unicorns. This will be the 12th cohort of the LongHashX Accelerator program and it will be their inaugural Cosmos cohort.</p><p>This two-tracked program will pioneer the selection, funding, and acceleration of the first few early-stage applications built on top of Neutron and Cosmos’ Partner Chains. Neutron and the ATOM Accelerator DAO decided to launch this first-of-its-kind Cosmos Genesis Accelerator cohort with LongHashX, the accelerator arm of LongHash Ventures.</p><p>“The advent of Partner Chains revolutionized Cosmos completely. What would have been Appchains before, now have the ability to focus on providing their service, such as Neutron, with its smart contract platform, and Stride with its liquid staking, without the need to bootstrap their own validator set. ATOM holders, on the other hand, can now provide security to these new application-focused chains while attracting new utility to the Cosmos Hub. On top of this, applications built on Neutron can leverage Interchain Accounts and Interchain Queries to build highly robust, cross-chain applications. We believe a chain-agnostic future for end users is unveiling at an unprecedented rate, therefore we are very excited to invest in and support early-stage builders in Cosmos to go from idea to Web3-native startup.” said <a href="https://twitter.com/emmacui"><strong>Emma Cui</strong></a><strong>, Founding Partner and CEO of </strong><a href="https://www.longhash.vc/"><strong>LongHash Ventures</strong></a><strong>.</strong></p><p>“This partnership is an exciting pilot for ATOM Accelerator DAO. We exist to provide grants to talented teams building on cosmos but some projects need more than financial support. This partnership enables projects in the ATOM Economic Zone to benefit from coaching and venture-building support that will enable them to go to the next level.” said <a href="https://twitter.com/BetterCio"><strong>Better Future</strong></a>, <strong>Program Manager of</strong> <a href="https://www.atomaccelerator.com/"><strong>ATOM Accelerator DAO</strong></a>.</p><p>“Replicated Security creates strong political and economic ties between the Cosmos Hub and Partner Chains like Neutron. As the first chain to have launched on Replicated Security, we are proud that Neutron’s community has chosen to join forces with the ATOM Accelerator DAO and LonghashX to launch a joint Accelerator program. Collaboration within the ATOM Economic Zone will be crucial to the success of Neutron, Cosmos Hub, and its future partner chains and this initiative is testament to the strength and alignment that exists within the AEZ,” said <a href="https://twitter.com/0xSpaydh"><strong>Avril Dutheil</strong></a><strong>, Core Contributor of </strong><a href="https://neutron.org/"><strong>Neutron</strong></a><strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5p9x_npEJ-295K_ipGmUYw.png" /></figure><p><strong>Cosmos Accelerator Program</strong></p><p>Five projects building on Neutron or Cosmos Partner Chains will be accepted into the LongHashX Accelerator Cosmos Cohort and each project will receive US$100,000 in funding.</p><p>On top of the funding received, these projects will also undergo the most web3-native curriculum and hands-on support. The 12-week program in this cohort will include a series of workshops and fireside chats across seven modules: Web3 Product Strategy &amp; Design, Ecosystem Deep Dive, Tokenomics &amp; Governance, Community Building, Smart Contract Security, Web3 Legal, and Fundraising.</p><p>Each project participating through this route will have a dedicated Program Lead and Venture Builder, who will meet them weekly for problem-solving sessions and to be a thought partner to help the founders with their toughest challenges.</p><p>In addition to the mentors from ATOM Accelerator DAO, Neutron &amp; other Cosmos’ Partner Chains, the selected projects will also get access to LongHash Web (LHW), the world’s first soulbound token-based on-chain contribution network, to meet one-on-one with notable mentors in the wider Web3 space that include leading founders, investors, and developers. LHW’s 100+ mentors include founders of Strangelove, Axelar, Saga, Squid, Safe, and Balancer; investors at Pantera, Polychain, Gumi, Multicoin, Collab+Currency, Hashkey, and DeFiance; and contributors at zkSync, Lens, Linea, Scroll, and Protocol Labs.</p><p>For these five projects, the program culminates in a Demo Day where they will have the opportunity to pitch to investors.</p><p><strong>Cosmos Builders’ Fellowship Program</strong></p><p>20–25 projects will be chosen for the Cosmos Builder’s Fellowship Program. These selected projects will receive the technical and developer support from Neutron and ATOM Accelerator DAO, will participate in workshops and fireside chats, and will have access to Mentor Office Hour sessions with LongHashX Venture Builders.</p><p>LongHashX will also facilitate a fast-tracked grant application process for these teams if they choose to apply for grants from ATOM Accelerator DAO or Neutron Grants DAO.</p><p>The <a href="https://www.longhash.vc/accelerator/aez/">LongHashX AEZ Accelerator and Builders’ Fellowship Program</a> are scheduled to start in mid-October. Builders have until 13 October 2023 11:59pm (GMT+8) to apply. Teams and projects interested in applying for the program can do so directly <a href="https://longhashventures.typeform.com/cosmos?utm_source=pr&amp;utm_medium=xxxxx&amp;utm_campaign=xxxxx&amp;utm_term=xxxxx&amp;utm_content=xxxxx">here</a>.</p><h3>About LongHashX Accelerator</h3><p>LongHashX is one of the world’s leading Web3 accelerators, with the strongest network in Asia, and works closely with ecosystem and infrastructure partners to accelerate the world’s next generation of early-stage founders.</p><p><strong>For more information, visit:</strong> <a href="https://www.longhash.vc/accelerator/">Website</a> | <a href="https://twitter.com/LongHashX">Twitter</a></p><h3>About LongHash Ventures</h3><p>LongHash Ventures specializes in bootstrapping Web3 ecosystems. Our venture funds invest in early-stage Web3 protocols, and our LongHashX Accelerator partners with ecosystems and protocols to accelerate early-stage founders.</p><p><strong>For more information, visit:</strong> <a href="https://www.longhash.vc/">Website</a> | <a href="https://twitter.com/LongHashVC">Twitter</a> | <a href="https://www.linkedin.com/company/longhashventures/mycompany/">LinkedIn</a></p><h3>About ATOM Accelerator DAO</h3><p>ATOM Accelerator DAO focuses on incubating projects in the Cosmos ecosystem through providing grants to public goods, open source projects, and ecosystem initiatives. They support contributors to various verticals including Replicated Security, Governance, Decentralized Identity amongst others.</p><p><strong>For more information, visit:</strong> <a href="https://www.atomaccelerator.com/">Website</a> | <a href="https://twitter.com/ATOMAccelerator">Twitter</a> | <a href="https://www.linkedin.com/company/atom-accelerator-dao/">LinkedIn</a></p><h3>About Neutron</h3><p>Neutron is a highly secure cross-chain smart contract platform for Interchain DeFi. Built with the Cosmos SDK and native support for CosmWasm, it enables developers to build smart contracts affordably and securely with high interoperability across apps and chains.</p><p><strong>For more information, visit: </strong><a href="https://neutron.org/">Website</a> |<a href="https://twitter.com/Neutron_org"> Twitter</a> |<a href="https://t.me/neutron_community"> Telegram</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ccb3cd630bb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>