<?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 Iwopietak on Medium]]></title>
        <description><![CDATA[Stories by Iwopietak on Medium]]></description>
        <link>https://medium.com/@iwopietak12?source=rss-a7c6f5bf5480------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*vvGm8OQy7tS1AlZB</url>
            <title>Stories by Iwopietak on Medium</title>
            <link>https://medium.com/@iwopietak12?source=rss-a7c6f5bf5480------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:45:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iwopietak12/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[WalletConnect Integration Grants for Cardano Wallet and DApp Developers!]]></title>
            <link>https://medium.com/dcspark/walletconnect-integration-grants-for-cardano-wallet-and-dapp-developers-38d32a4d8f10?source=rss-a7c6f5bf5480------2</link>
            <guid isPermaLink="false">https://medium.com/p/38d32a4d8f10</guid>
            <category><![CDATA[grant]]></category>
            <category><![CDATA[wallet]]></category>
            <category><![CDATA[walletconnect]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[cardano]]></category>
            <dc:creator><![CDATA[Iwopietak]]></dc:creator>
            <pubDate>Thu, 18 May 2023 20:46:44 GMT</pubDate>
            <atom:updated>2023-05-18T22:17:03.156Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g3uw6ji3jWuXzmbCasdi0Q.png" /></figure><p>We are thrilled to announce that, thanks to the Catalyst Community, we are launching an exciting opportunity for all Cardano builders.</p><p><strong>Introducing the WalletConnect Integration Grant, designed to empower developers in seamlessly integrating WalletConnect into their Cardano wallets and DApps.</strong></p><p>With WalletConnect becoming the go-to protocol for connecting wallets and DApps, we want to ensure that Cardano builders have the tools and support they need to be at the forefront of this movement. <strong>Through the generous support of the Cardano Catalyst Community, we are offering $100,000 grant to Cardano wallet and DApp developers who successfully integrate WalletConnect into their projects.</strong> This is an incredible opportunity to enhance the functionality and accessibility of your products while contributing to the growth of the Cardano ecosystem.</p><p>Whether you’re an experienced developer or just starting your journey in Cardano, this grant is open to all Cardano builders. To initiate your grant application, please proceed by filling out the form available <a href="https://airtable.com/shrCeiBoyuhYVxSvW">here</a>.</p><h3><strong>What is WalletConnect?</strong></h3><p>WalletConnect is one of web3’s most popular connectors for wallets and DApps. It significantly simplifies the user’s web3 journey by allowing them to connect their mobile (or desktop) wallet to any desktop DApp, simply by scanning a QR code. This provides users with a simple, and always familiar, access point to the world of web3 — greatly improving the user experience, all while enhancing wallet and DApp interoperability <strong>(and now Cardano protocols can utilize this connection standard!)</strong>.</p><p>End-to-end encryption ensures that the information a user sends, i.e. the signing of a transaction, stays private, and users can disconnect from a DApp whenever they want to. WalletConnect currently works with DApps and wallets on Ethereum, Solana, and Cosmos and, to date, has been integrated by over 700 wallets and DApps including OpenSea, MetaMask, UniSwap, MyEtherWallet, LedgerLive, and Aave. WalletConnect has also been integrated by some of the world’s most popular apps, Twitter and Instagram, allowing them to incorporate web3 elements into their platforms.</p><h3><strong>Grants for Integrating WalletConnect</strong></h3><p>dcSpark made an exciting announcement in March regarding the integration of WalletConnect into Flint Wallet. Wingriders, the prominent decentralized exchange (DEX) on Cardano, has now become the pioneering DEX in the ecosystem to integrate with WalletConnect. This integration significantly strengthens the Cardano ecosystem by enabling users to securely and conveniently interact with Wingriders through WalletConnect.</p><p>To promote the integration of WalletConnect, we have allocated the remaining funds from our milestone agreement with Project Catalyst to establish a grant program. This program aims to incentivize established Cardano DApps and wallets to adopt WalletConnect. Flint wallet, as a proof-of-concept, has already successfully integrated WalletConnect support and stands as the first in Cardano to do so. We encourage other projects to follow the lead set by Flint and Wingriders.</p><p><strong>We are pleased to provide you with the details of the WalletConnect Integration Grants for Cardano Wallet and DApp Developers</strong></p><ul><li>Total grant amount: $100,000</li><li>Deadline for WalletConnect Integration: <strong>July 31st, 2023</strong></li><li>Each project can receive a maximum award of $15,000, irrespective of the number of applicants.</li><li>After <strong>July 31st, 2023</strong>, all successful applicants will receive an equal share of the total funds, up to $100,000.</li><li>Applicants must have a live product functioning on the Cardano mainnet and have a well-established presence within the Cardano ecosystem.</li><li>To be eligible for the grant funds, developers must submit proof of evidence of the completed integration.</li></ul><p>To initiate the grant application process, kindly fill out the short form available <a href="https://airtable.com/shrCeiBoyuhYVxSvW">here</a>. Once your application is submitted, the dcSpark team will carefully review it and provide you with the necessary information regarding the deliverables required for official participation in the grant.</p><p>We are excited to see Cardano developers collaborate and integrate WalletConnect into the Cardano Ecosystem. For further information on integrating your Cardano project with WalletConnect, we encourage you to visit the adalib repository on GitHub (https://github.com/dcSpark/adalib), explore the SDK documentation section, and refer to the examples for development guidance.</p><blockquote>The Adalib SDK (https://github.com/dcSpark/adalib) has been developed to offer DApps a streamlined solution for enabling Cardano wallet connections through a common Connector interface. It attempts to closely emulate the CIP-30 standard within the connectors. A dapp developer can use these connectors to retrieve the enabled CIP-30 API, and benefit from the included typings this library provides. The SDK provides DApp developers with the ability to support a wide range of Cardano wallets, while adhering to the WalletConnect Provider interface, which ensures universal support for any blockchain.</blockquote><p>We express our gratitude to the voters of Project Catalyst and the Cardano community for their support in funding this proposal. As we move forward, we eagerly anticipate the integration of WalletConnect by exceptional DApps and wallets, which will further enrich the Cardano ecosystem. Make sure you follow us on<a href="https://twitter.com/dcspark_io"> Twitter</a> and<a href="https://medium.com/dcspark"> Medium</a> to keep up with all the work we’re doing!</p><p><strong>Follow dcSpark:</strong></p><p><strong>Website:</strong><a href="https://www.dcspark.io/"> dcspark.io</a><br><strong>Twitter:</strong><a href="https://twitter.com/dcspark_io"><strong> </strong>@dcspark_io</a><br><strong>Discord:</strong><a href="https://discord.gg/dcspark"><strong> </strong>/dcSpark</a><br><strong>Medium:</strong><a href="https://medium.com/dcspark"> /dcSpark</a><br><strong>GitHub:</strong><a href="https://github.com/dcSpark"><strong> </strong>/dcSpark</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38d32a4d8f10" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dcspark/walletconnect-integration-grants-for-cardano-wallet-and-dapp-developers-38d32a4d8f10">WalletConnect Integration Grants for Cardano Wallet and DApp Developers!</a> was originally published in <a href="https://medium.com/dcspark">dcSpark</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving Data Availability with Projective Rollups]]></title>
            <link>https://medium.com/dcspark/improving-data-availability-with-projective-rollups-c31b75b4271?source=rss-a7c6f5bf5480------2</link>
            <guid isPermaLink="false">https://medium.com/p/c31b75b4271</guid>
            <category><![CDATA[cardano]]></category>
            <category><![CDATA[layer-2]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Iwopietak]]></dc:creator>
            <pubDate>Fri, 10 Mar 2023 11:34:06 GMT</pubDate>
            <atom:updated>2023-03-10T11:34:06.963Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6xi6Kxcn5n0YptXdRQhhKQ.jpeg" /></figure><p><strong>In this article we’re going to introduce a new layer 2 concept in a class of rollups called projective </strong>rollups. We’ll look at the benefits this new class of rollups offers and why this solution is needed. We’ll also discuss how this technology relates to existing layer 2 and sidechain technology and how it can be implemented into existing and future iterations of these solutions.</p><blockquote><em>Note: Projective rollups were first described in</em><a href="https://www.youtube.com/watch?v=XgOK4Gf9tO8"><em> this video</em></a><em> by Sebastien Guillemot, CTO and Co-founder of</em><a href="https://dcspark.io/"><em> dcSpark</em></a><em>. This post is based on that video.</em></blockquote><h3><strong>What are Projective Rollups?</strong></h3><p>Projective rollups are a new class currently being researched and developed at dcSpark. They are not a new type of rollup; instead, <strong>projective rollups are a new class or “family” of rollups that allow developers to easily project a state from the Layer 1 to the Layer 2</strong> (and partially extendable to sidechain even though they are not L2s)<strong>.</strong> Such data projection is currently difficult -at times impossible- to do.</p><p>We believe that projective rollups are the next natural step in the development of layer 2 solutions, allowing layer 2s to add to the ecosystem they’re a part of instead of fracturing it, which is what they currently do.</p><h3><strong>Why is Data Projectivity Important?</strong></h3><p>Each blockchain has its own architecture, consensus mechanism, execution environment, and other unique elements that enable it to function. But these also restrict what can be done on that blockchain. In order to extend blockchain protocols, advance them, and give them new functionality, new technology has been developed. The first of these developments were sidechains, and these were quickly followed by rollups — on which extensive and exciting R&amp;D is ongoing!</p><p>As these solutions were implemented across the blockchain space, we saw expanded functionality -like when<a href="https://milkomeda.com/"> Milkomeda C1</a> brought EVM functionality and Solidity smart contracts to the Cardano ecosystem- along with significant improvements in both the user and developer experience. But, <strong>as individual blockchain ecosystems became distributed across these new layer 2s there was a fracturing of application state and a resulting reduction in the composability of that data. In some instances, such as oracles, fracturing state also leads to lower security as data providers are fractured between L2s and the L1. This fracturing of state by the propagation of layer 2 technology led to the ideation and development of projective rollups.</strong></p><h4>The Oracle Example</h4><p>Data is a necessity for applications running on top of blockchains, and off-chain data, supplied by oracles, is crucial for the correct functioning of many elements of the blockchain ecosystem. This is particularly visible in DeFi, where protocols rely on oracles to supply reliable, up-to-date data points from off-chain sources. Without this off-chain data provided by oracles, many current and future uses of blockchain technology would not be possible.</p><p>Building a trustworthy and robust oracle system requires a huge feat of engineering, and a large enough set of trusted actors to maintain this data availability system. The importance and value-add that oracles have in the ecosystem can further be underscored by the large number of attacks we’ve seen trying to manipulate or undermine oracles to draw a profit in a malicious way.</p><p>So, blockchain ecosystems require oracles with the highest possible level of security and assurance. However, when you distribute an ecosystem across numerous layer 2s and sidechains, an instance of the oracle service needs to be implemented, from scratch, on each of these ecosystem fragments, as well as on the layer 1, so everyone can access the data. This essentially divides the oracle’s security budget -and, potentially, their validator set- between each of these instances. Reducing that budget’s overall effectiveness at protecting each of their services, and therefore protecting their users, from exploitation by attackers.</p><p><strong>Projective rollups introduce the ability to project data from the layer 1 to these layer 2s, meaning that oracles will only need to deploy one instance of their oracle to the layer 1, a.k.a. mainchain, and then project that data to all the layer 2s. </strong>This allows the oracle provider to focus their whole security budget on building a robust and secure, single instance of their oracle that the entire ecosystem can then rely on.</p><p>Oracles are our example here, but projective rollup technology can be used with almost any piece of on-chain data. Next, we’ll look at the existing world of sidechains and rollups and how, and even if, we can implement projective rollup technology on each of these solutions.</p><h3><strong>Sidechains, Rollups, and Projective Rollups</strong></h3><p>Sidechains and the different forms of rollups currently deployed in the blockchain world can be put on a spectrum where we have solutions with high developer flexibility but, typically, lower security at one end, and we have higher security solutions with a much lower level of developer flexibility at the other end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/0*ecYyN2fTcWXFoO4b" /></figure><p>The above solutions are each described below, along with links to examples, before we also explain how it is possible to project data onto each of them. Each solution is different and brings with it its own challenges for building data projection capabilities, and implementing a data projection solution gets progressively harder as we move along the scale from left to right.</p><h4>Sidechains</h4><p><strong>Examples:</strong><a href="https://milkomeda.com/"> Milkomeda C1</a> <a href="https://polygon.technology/">— Polygon</a></p><p><strong>Description:</strong> A sidechain is a separate blockchain that is philosophically aligned with the mainchain, extends it, but doesn’t inherit the security of that mainchain. Instead of building their own independent ecosystem, the builders of a sidechain want to stay connected to and aligned with the ethos of the mainchain and their ecosystem while giving themselves greater flexibility, e.g. a new consensus model, different smart contracting languages, different block times, etc.</p><p><strong>Data Projection:</strong> Data projection is the most simple for sidechains. The preferred method would be to implement an enshrined messaging protocol into the bridge that connects the sidechain to the mainchain. The validators are then not only passing transactions but also messages containing data.</p><p>We will soon be releasing <strong>Wrapped Smart Contracts for Milkomeda</strong>, which make use of an enshrined messaging protocol and allow users to call and execute sidechain smart contracts from the mainchain and vice-versa. This will give the Milkomeda C1 sidechain data projection capabilities as states can be passed from mainchain smart contacts to the sidechain through this protocol, allowing DApps on the sidechain to source oracle data and more directly from Cardano.</p><h4>Sovereign Rollups</h4><p><strong>Examples:</strong><a href="https://celestia.org/"> Celestia</a> — Paima Engine (by<a href="https://paimastudios.com/"> Paima Studios</a>)</p><p><strong>Description: </strong>Sovereign rollups, are rollups that post their data to the layer 1 as raw data, i.e. not through a smart contract. Transactions are secured by the rollup’s nodes and, as a result, sovereign rollups don’t require a proof system on the layer 1 like their more secure optimistic and zero-knowledge cousins do. It is easy to move assets to a sovereign rollup, but difficult to transfer them back from the rollup to the layer 1 as there is no canonical way to do so.</p><p><strong>Data Projection: </strong>Unlike optimistic and zk rollups, sovereign rollup do not project their state back onto the layer 1, meaning that, like with sidechains, they only need to worry about receiving the data from the layer 1 and not about making it backward compatible for validation purposes — ultimately meaning that data projection for sovereign rollups is relatively simple. Paima Engine takes full advantage of this quality of sovereign rollups, and the team at Paima Studios is already utilizing data projection techniques.</p><h4>Optimistic Rollups</h4><p><strong>Examples:</strong><a href="https://milkomeda.com/"><strong> </strong>Milkomeda A1</a> <a href="https://www.optimism.io/">— Optimism</a><strong> </strong><a href="https://offchainlabs.com/">— Arbitrum</a></p><p><strong>Description:</strong> Optimistic rollups post their transaction data on the layer 1 in batches, and this data is assumed to be correct by the users of the rollup (it is this assumption that data is correct that give optimistic rollups their name). Once a batch of transaction data has been posted to the layer 1 there is a set window of time where anyone can dispute the authenticity of that data. If someone disputes the batch’s authenticity a fraud proof system is run on the layer 1 to validate the transactions in that batch.</p><p>If no one disputes the batch’s authenticity during the allotted time frame then the transactions are considered confirmed by the mainchain. Optimistic rollups can be used to bring different programming languages and VMs to an ecosystem — like Milkomeda A1 does, delivering Ethereum Virtual Machine functionality and Solidity to Algorand. These rollups are currently more popular than the more secure zk rollups as the fraud proof systems used are easier to write than a full zk system.</p><p><strong>Data Projection:</strong> Optimistic rollups can support projective rollup technology. However, it is difficult because previous data projections need to be made available for the fraud proof systems used to validate the rollup data during a dispute. Currently, these fraud proof systems only have access to the current state of the layer 1, not the historic state, meaning they can’t check previous layer 1 states and confirm the projected data.</p><p>Some complicated techniques can be employed to enhance a fraud proof system and allow it to access this historic state, but this is not easily doable with Ethereum in its current form. As core contributors to Milkomeda, dcSpark is currently in talks with the core developers at Algorand about what changes might be needed to Algorand to allow for the use of projective rollup technology for optimistic rollup systems, like Milkomeda A1, on Algorand.</p><h4>Zk Rollups</h4><p><strong>Examples:</strong><a href="https://zksync.io/"> zkSync</a></p><p><strong>Description:</strong> Zk rollups rely on zero knowledge (zk) proofs to secure their transactions and are designed using zk systems. To update a zk rollup a summary of the changes to the rollup’s state are published to the layer 1, along with a cryptographic validity proof that proves the correctness of those changes. Once the layer 1 smart contract has accepted the validity proof then the transactions are considered confirmed.</p><p>This technique allows you to add new VMs on top of the layer 1, but it has very limited flexibility as the VM’s code needs to be compatible with zk circuits, specific elliptical curves, specific arithmetic, and other constraints derived from the blockchain the rollup is built on top of.</p><p><strong>Data Projection:</strong> It is not feasible to add data projection functionality to zk rollups built on chains, like Ethereum, that are not built on zk technology. This is because the rollup needs to be able to prove the data that has been projected onto it, and Ethereum and other non-zk-based chains cannot compress their own state into the zk proof that the rollup needs to do this.</p><p>If you are using zk rollups on a zk-based chain then recursive snarks can be used to make this proof available to the rollup. For example,<a href="https://minaprotocol.com/"> Mina</a>, a zk-based, layer 1 blockchain that does support recursive snarks, allows you to create constant proofs of the state of the Mina layer 1 and transfer these proofs around; meaning that blockchains like Mina can support projective zk rollups.</p><h3><strong>Developing Projective Rollup Technology at dcSpark!</strong></h3><p>Projective rollups are at the cutting edge of layer 2 development, and the utility and possibilities this technology can offer to layer 2s across the blockchain ecosystem are very exciting! The team here at dcSpark, along with our partners at Paima Studios, have been working hard to develop the techniques explained above and implement projective rollup techniques into multiple sidechain and layer 2 solutions.</p><p>This is an inspiring time as we don’t believe that the above methods are the only ways data can be projected from a layer 1 to a layer 2. We are actively exploring new cryptographic techniques that can enable different security modes from layer 2s and different methods of data projection.</p><p>If you want to learn more about our developments in this area, or if you have any questions on this topic, please don’t hesitate to reach out to us on Twitter or join our developer Discord to get in touch and join the conversation!</p><p><strong>Follow dcSpark:<br>Website:</strong><a href="https://www.dcspark.io/"> dcspark.io</a><br><strong>Twitter:</strong><a href="https://twitter.com/dcspark_io"><strong> </strong>@dcspark_io</a><br><strong>Discord:</strong><a href="https://discord.gg/dcspark"><strong> </strong>/dcSpark</a><br><strong>Medium:</strong><a href="https://medium.com/dcspark"> /dcSpark</a><br><strong>GitHub:</strong><a href="https://github.com/dcSpark"><strong> </strong>/dcSpark</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c31b75b4271" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dcspark/improving-data-availability-with-projective-rollups-c31b75b4271">Improving Data Availability with Projective Rollups</a> was originally published in <a href="https://medium.com/dcspark">dcSpark</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[dcSpark Catalyst Proposal Updates]]></title>
            <link>https://medium.com/dcspark/dcspark-catalyst-proposal-updates-5d2cef655e2d?source=rss-a7c6f5bf5480------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d2cef655e2d</guid>
            <category><![CDATA[catalyst]]></category>
            <category><![CDATA[grant]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cardano]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Iwopietak]]></dc:creator>
            <pubDate>Fri, 03 Feb 2023 18:06:32 GMT</pubDate>
            <atom:updated>2023-02-03T18:06:32.097Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*N9AEKJGhK4n6JGH1" /></figure><p>We’ve recently been putting out some feelers to learn more about community sentiment around dcSpark, in particular, how we’re perceived by the Cardano community and what the community would like to see more of (if you’re interested in these conversations, you can listen to<a href="https://twitter.com/dcspark_io/status/1615439226031702017?cxt=HHwWgoDQ_djamOssAAAA"> this Twitter Space</a>, our first with the community on this topic).</p><p>One of the things mentioned by some community members was related to the number of <a href="https://projectcatalyst.io/">Project Catalyst</a> proposals dcSpark have had funded, and where they can find progress on them. For those unfamiliar with Project Catalyst — shortened to just <em>Catalyst</em> by many- it is a decentralized funding mechanism launched in 2020 by IOG, the founders and core contributors to the Cardano blockchain. In Project Catalyst, community members propose solutions to various and wide-ranging challenges selected by the community in each funding round. Community members then upvote and downvote these proposals, with their ADA holdings equaling their voting power, to decide on which proposed solutions should be funded. Funds are drawn from the Project Catalyst treasury and the total funds are capped in each funding round. Head to the new <a href="https://projectcatalyst.io/">Project Catalyst</a> website to learn more!</p><p><strong>To answer these questions in the best way possible for all, we’ve produced this blog post to highlight our progress on all of dcSpark’s funded Catalyst proposals.</strong> We’ve split this into two sections, <em>completed proposals</em> and those that we are still working on, <em>in-progress</em>.</p><p>If you want to see the official Catalyst reporting status for all the proposals ever funded, you can go to<a href="https://docs.google.com/spreadsheets/d/1bfnWFa94Y7Zj0G7dtpo9W1nAYGovJbswipxiHT4UE3g/edit#gid=938310766"> this spreadsheet</a> — where, not only can you see the progress of work done on every proposal, you can see the evidence of the hard work and diligence completed by the Project Catalyst Coordinators and Managers. If you want to stay up-to-date with the progress on just dcSpark’s proposals you can head to the <a href="https://dcspark.io/grants/">grants page</a> on our website where we regularly update the progress we’re making.</p><h3><strong>In-Progress Proposals</strong></h3><p>These proposals are the ones we are actively pursuing. We’ve included the most recent update as of this writing, in relation to our January Monthly Reporting.</p><h4>CIP Editor Time: Sebastian for 1 Year</h4><p><strong>Fund 8 </strong>— Open Standards &amp; Interoperability <a href="https://cardano.ideascale.com/c/idea/400716">— Proposal</a></p><blockquote><strong>TLDR:</strong> One of dcSpark’s cofounders, Sebastian Guillemot, has been an unpaid <a href="https://github.com/cardano-foundation/CIPs/tree/master/CIP-0001">CIP</a> (Cardano Improvement Proposal) editor for over two years, helping to define and improve technical standards for Cardano and continuing to move the blockchain forward. This proposal is funding that work for 1 year so he can dedicate time in his schedule to continuing to contribute to this process. The timeline for this proposal is from April 2022 to April 2023.</blockquote><p>Sebastian was one of the initial CIP editors and helped to set up and structure the CIP process for proposing improvements to the Cardano ecosystem and processes. He has been a long-term, 2+ years, CIP editor and an unpaid contributor to the CIP process — reviewing proposals, attending biweekly meetings, and authoring and co-authoring multiple CIP proposals. This proposal ensures that Sebastian can set time aside to continue dedicating himself to the CIP process and the continued improvement of Cardano. Sebastion’s work can be seen throughout the <a href="https://github.com/cardano-foundation/CIPs">Cardano Foundation CIP Repository</a> where CIPs are proposed, discussed, and edited.</p><h4>Cotalker Integration</h4><p><strong>Fund 8</strong> — Business Solutions (B2B &amp; B2C) <a href="https://cardano.ideascale.com/c/idea/400690">— Proposal</a></p><blockquote><strong>TLDR: </strong>Here we proposed to create a solution for Cotalker -a company that provides solutions for digitizing and automating operational processes- to be able to write data to the Cardano blockchain. This increases Cardano’s exposure to the enterprise world and provides a tool that businesses can use to integrate with Cardano. This proposal is almost complete with 1 of 2 trials underway with Cotalker’s clients.</blockquote><p>Cotalker is a logistics company based in Latin America, operating as a part of the global supply chain. Cotalker have created a tool to track the products they ship on Milkomeda, which also records an estimate of the carbon emissions from their journey. This tool tokenizes carbon credits, allowing the companies whose goods are shipped through Cotalker to not only track their goods and their related carbon emissions but, if they wish, to offset those carbon emissions by burning the tokenized carbon credits they have bought. Once the carbon credits have been offset a certificate for “Carbon Neutral Delivery” will be available to the end consumer when they scan the QR code located on the product.</p><p>Currently, Cotalker has a contract with one company for transporting 200 containers of fruit from Chile to the US, Portugal, England, the Netherlands, China, and other countries. The technology designed as a part of this proposal is being utilized to track these products on the blockchain, and their journey’s carbon emissions. It then provides a certificate, that the end consumer can easily access via a QR code, once the company has burnt the carbon credit tokens to offset the products emissions.</p><p><strong>Cotalker is currently following up on leads to close a second trial and complete the work outlined in this proposal. Once this is completed we are going to issue a blog post detailing this solution and the outcome of Coltalkers implementation.</strong></p><h4>Milkomeda Mobile</h4><p><strong>Fund 8 </strong>— DApps &amp; Integrations <a href="https://cardano.ideascale.com/c/idea/400673">— Proposal</a></p><blockquote><strong>TLDR:</strong> We’re developing a way for users to be able to interact with smart contracts on Milkomeda C1 through their mobile devices. This increases the accessibility of the Milkomeda network, and the Cardano DApps deployed on it, making interacting with Cardano much more user friendly. We have <a href="https://twitter.com/FlintWallet/status/1617020089135497218">released EVM support</a> for Flint and are working on the final parts of being able to interact with Milkomeda smart contracts!</blockquote><p>This proposal is almost complete. <strong>This month the incredible team behind</strong><a href="https://flint-wallet.com/"><strong> Flint wallet</strong></a><strong> has been finalizing EVM integration into the desktop and mobile versions of Flint.</strong> Last month we sent evidence to Catalyst as a part of our report, which showed that we could display balances from the EVM-based Milkomeda C1 sidechain in the Flint wallet. This month we also included two videos where we successfully conducted <a href="https://drive.google.com/file/d/1XK427KvlL9Vy4_EVpf5PSjrABCGVDmH1/view">a mADA transaction</a> and <a href="https://drive.google.com/file/d/1DzFXoBMpw-Buwks0H1V_HuHY8NW1fbP_/view">a token transaction</a> on the Milkomeda C1 mainnet!</p><p>We’re also very proud and very excited to have recently announced the <a href="https://twitter.com/FlintWallet/status/1617020089135497218">released Flint 2.0</a>, which introduces the ability for Flint users to interact with Milkomeda directly from Flint on both desktop and mobile! This means that, once you’ve updated to Flint 2.0, you’ll be able to use Flint to send mADA from one wallet to another! Our next step, on which work has already started, is to build in support for connecting to Milkomeda DApps which, once implemented will enable you to use Flint’s<a href="https://medium.com/dcspark/flint-wallets-innovative-mobile-dapp-browser-c77d68f5b10b"> fully-open mobile DApp browser</a> to interact with DApps on Milkomeda C1!</p><h4>Cardano Wallet OneBox</h4><p><strong>Fund 9</strong> — Developer Ecosystem <a href="https://cardano.ideascale.com/c/idea/419161">— Proposal</a></p><blockquote><strong>TLDR:</strong> Currently developers must deploy and combine multiple tools to build a working Cardano wallet. To increase Cardano adoption we need to make Cardano wallet deployment easier and this proposal will create a single image, that developers can use to deploy their own wallet and all the supporting components. Notably, it will be based on our stack for Flint which uses: Carp, Blockfrost, Ogmios, Token info service, Price feed service and cardano-node.</blockquote><p>We have recently encountered challenges in progressing with this proposal, specifically due to the observance of regional and cultural holidays by our globally distributed team over the recent holiday period. Additionally, there has been limited developer availability on the part of our partner, Txpipe. As a result, we have primarily focused on conducting repository maintenance for this proposal in the past month.</p><p>We are pleased to report that these obstacles have been overcome, and Txpipe has confirmed that they are nearing the completion of the demo of the relevant tool. This tool is a critical prerequisite for this project, and we are looking forward to progressing on this exciting initiative.</p><h4>Catalyst SDK dRep Support</h4><p><strong>Fund 9</strong> — dRep Improvement and Onboarding <a href="https://cardano.ideascale.com/c/idea/419171">— Proposal</a></p><blockquote><strong>TLDR:</strong> Project Catalyst is introducing dReps to the voting process -allowing users to delegate their voting power to a representative- and created a <a href="https://cardano.ideascale.com/c/campaigns/26601/about">Challenge in Fund 9</a> to improve the dRep concept. The work done for this proposal will create an SDK that Cardano wallet developers can use to implement dRep support, removing a barrier of entry that might have prevented users from being able to utilize this new functionality. We are currently working on updating the existing SDK that will form the base of the final product for this proposal.</blockquote><p>This proposal was initially blocked by some needed refactoring work for CML, however, our team found this blocker and resolved it last month; here’s the<a href="https://github.com/dcSpark/cardano-multiplatform-lib/pull/159"> pull request</a>. We also found a bug in the CIP36 specification, and IOG<a href="https://github.com/cardano-foundation/CIPs/pull/426"> submitted a fix</a> to the bug we found.</p><p><strong>We are continuing discussions with IOG regarding the changes to the Catalyst registration process and dRep functionality.</strong> In these discussions, there have been talks of dcSpark making the necessary updates to CIP30 that are required for dRep support, which may also end up falling under the scope of this proposal.</p><p>The work that we are currently doing on this proposal involves updating our Catalyst registration SDK to use the new rust codegen solution that will result from<a href="https://cardano.ideascale.com/c/idea/419158"> this proposal</a> (progress discussed below), updating our Catalyst registration SDK to support dRep functionality, adding dRep indexing to Carp using said updated SDK, and integrating the SDK and the Carp endpoint into Flint wallet.</p><h4>DcSpark (The Company Itself)</h4><p><strong>Fund 9</strong> — DApps, Products, &amp; Integrations <a href="https://cardano.ideascale.com/c/idea/419153">— Proposa</a>l</p><blockquote><strong>TLDR:</strong> At dcSpark we have built, and continue to maintain, multiple tools that are widely used in Cardano, e.g. Flint, Carp, Fracada, Rust SDKs, and many others found on our <a href="https://github.com/dcSpark">GitHub</a>. The majority of these are open sourced and, therefore, don’t make money. This proposal funded a loan from Project Catalyst to dcSpark that we will begin paying back, 1 year after the full payment was received, with an interest rate of 6%.</blockquote><p>This proposal was designed as a loan to help support the dcSpark team as we continue to build for the Cardano ecosystem. <strong>We want to give our deepest thanks to the voters of Project Catalyst for recognizing the work that we do and choosing to fund this proposal. </strong>This proposal covers our work on building and maintaining the multiple tools we’ve created for Cardano, including Carp, Rust SDKs, Milkomeda, Flint, Fracada, and many more protocols &amp; tools you can find on our<a href="https://github.com/dcSpark"> GitHub</a>.</p><p>The loan was for 400,000 USD and is being paid in four installments over four months, the first being when Catalyst began distributing payments for Fund 9. The loan conditions were laid out in the proposal. These were that there would be a one-year grace period from the first payment to the time of the first repayment and that we would pay the loan back month-by-month with an interest rate of 6%.</p><p>When requesting this loan, the Catalyst Treasury had no way of receiving payments, but Sebastian created a<a href="https://github.com/cardano-foundation/CIPs/pull/269"> pull request</a> to build this functionality into the treasury. This proposal could also be used as an initial test run to examine the possibility of Project Catalyst distributing loans as a way to sustain the treasury in the future.</p><h3>Fracada Addressing Audit</h3><p><strong>Fund 9</strong> — DApps, Products, and Integrations <a href="https://cardano.ideascale.com/c/idea/422500">— Proposal</a></p><blockquote><strong>TLDR:</strong> After auditing our open sourced <a href="https://github.com/dcSpark/fracada-il-primo">Fracada smart contract</a> for fractionalizing NFTs, the Fracada Addressing Audit proposal requested funds to address the concerns raised by the audit and release both the audited code and the audit. This would allow users to deploy the contract, safe in the knowledge that basic, known, and common attack vectors can’t be used to attack a deployed version of the contract. We are currently addressing the concerns from the report.</blockquote><p><a href="https://github.com/dcSpark/fracada-il-primo">GitHub Repository</a></p><p>This code was first audited in June 2022, after which a set of findings were informally reported to our team. Before continuing with the audit we chose to address these findings in order to maximize the time spent auditing the scripts.</p><p>Once these initial findings were addressed, the audit was resumed in December 2022. Due to the significant changes in the code that were made after the initial, informal findings were reported to the team, it was not feasible to properly audit the new contract’s design and implementation. This resulted in a mixed approach, which formalized the initial findings and briefly checked the new implementation to acknowledge that these initial findings had been <a href="https://github.com/dcSpark/fracada-il-primo/pull/5">addressed by the work done</a>. The audit on the Fracada v2 code has been completed and was delivered by the MLabs Audit Team on January 12th, 2023.</p><h3>WalletConnect for Cardano</h3><p><strong>Fund 9</strong> — DApps, Products, &amp; Integrations <a href="https://cardano.ideascale.com/c/idea/419164">— Proposal</a></p><blockquote><strong>TLDR:</strong> WalletConnect is a highly user-friendly connection standard for connecting mobile wallets to desktop DApps that is widely used and has been integrated by some of the world’s most popular DApps and apps — however, it doesn’t yet support Cardano. For this proposal we are building Cardano support for WalletConnect and have almost finished! <a href="https://twitter.com/dcspark_io/status/1620844609193775104?cxt=HHwWgMDQ8bPlsv4sAAAA">Here’s a video</a> of us connecting Flint wallet to a test DApp using WalletConnect!</blockquote><p>We are very close to finishing this proposal and should release WalletConnect support for Cardano son! For this proposal, we’ve created a <a href="https://github.com/dcSpark/adalib">library</a> that allows Cardano wallets to integrate with WalletConnect and an SDK that enables DApps to easily integrate themselves with WalletConnect and have successfully tested this with Flint and a demo DApp, using regular injection methods and by presenting a WalletConnect QRCode modal to the user. With the WalletConnect team’s guidance, we have created a <a href="https://github.com/WalletConnect/walletconnect-monorepo/pull/1880">pull request</a> on the WalletConnect UniversalProvider package to add support for a CardanoProvider that facilitates the connection between Cardano DApps, WalletConnect’s relay servers, and Cardano wallets.</p><p>This integration has been designed to complement CIP30 and also to allow users to easily switch between connection methods, i.e., the mobile and desktop versions of their wallet. When we release this, we will also publish a blog post and documentation detailing what we’ve accomplished and how wallet and DApp developers can integrate WalletConnect for Cardano into their products.</p><p>As a part of our milestone agreement with Project Catalyst for this proposal, the remaining funds are being used to create <strong>a grant program to incentivize established Cardano DApps and wallets to integrate WalletConnect Support. </strong>As detailed in our <a href="https://docs.google.com/spreadsheets/d/1ToDLA6CO_nKf41YeoQFzwT3XaABqZm9ipeHhHchlb5U/edit#gid=1672366179">milestones for this proposal</a>,<strong> </strong><a href="https://flint-wallet.com/">Flint wallet</a> is being used as a proof-of-concept and will be the first in Cardano to integrate WalletConnect support! Watch our social media for more details coming soon!</p><h3><strong>Completed Proposals</strong></h3><p>Below are all the proposals whose work has been completed by dcSpark, across all Project Catalyst funding rounds. We have linked to the Project Close Out Reports and Project Close Out Videos where available. If you’re interested in more information on the products of these proposals, e.g. if you want to implement one in your product, please feel free to contact us using your preferred method.</p><h4>Cardano Connector [MetaMask-like]</h4><p><strong>Fund 5 </strong>— DApps &amp; Integrations <a href="https://cardano.ideascale.com/c/idea/352482">— Proposal</a></p><p>We built and released a MetaMask-style DApp connector for Cardano wallets, standardizing the way Cardano wallets connect to Cardano DApps, making these interactions much more user friendly. This was outlined in<a href="https://github.com/cardano-foundation/CIPs/tree/master/CIP-0030"> CIP30</a> and has been implemented into our own wallet,<a href="https://flint-wallet.com/"> Flint</a>, and some of Cardano’s other most popular wallets. We also created, and still maintain,<a href="https://www.cardano-caniuse.io/"> a website</a> where users can check which registered wallets support which elements of CIP30.</p><h4>Cardano Rust SDK Update for Alonzo</h4><p><strong>Fund 5</strong> — Developer Ecosystem <a href="https://cardano.ideascale.com/c/idea/352480">— Proposal</a></p><p><a href="https://github.com/Emurgo/cardano-serialization-lib/releases/tag/8.0.0">GitHub Repository</a></p><p>We successfully delivered CSL 8.0.0 in time for the Alonzo hardfork in September 2021. This is depended upon by dozens of companies and their users, including exchanges like Coinbase and wallets like Yoroi, and would have failed to continue working after the hardfork had we not completed this proposal.</p><h4>Developer Evangelist Japan</h4><p><strong>Fund 5 </strong>— Proposer Outreach <a href="https://cardano.ideascale.com/c/idea/352484/">— Proposal</a></p><p><a href="https://medium.com/dcspark%E6%97%A5%E6%9C%AC/project-catalyst%E3%81%A7%E6%8F%90%E6%A1%88%E3%82%92%E6%89%BF%E8%AA%8D%E3%81%95%E3%82%8C%E3%81%9Fdcspark%E3%81%AF-%E6%97%A5%E6%9C%AC%E3%81%AE%E3%82%AB%E3%83%AB%E3%83%80%E3%83%8E%E3%82%B3%E3%83%9F%E3%83%A5%E3%83%8B%E3%83%86%E3%82%A3%E3%82%92%E3%82%B5%E3%83%9D%E3%83%BC%E3%83%88-d808f801f174">Medium Post</a></p><p>Cardano is popular amongst the Japanese community, and Japan is also where an<a href="https://cardano.org/genesis/"> initial distribution of ADA</a> took place. This proposal funded the hiring of an individual who translated much of our material into Japanese and helped to increase Cardano and dcSpark’s, and our tooling, exposure to a Japanese audience. We also used these funds to attend the 2021 Blockchain Expo Tokyo as a Cardano booth operator, presenting these materials and more about the latest Cardano developments to the exhibition’s attendees.</p><p>The AI Expo and IT Expo were also being held at nearby venues at the same time that year, and members of the dcSpark team promoted Cardano to interested professionals and developers from these industries at the same time.</p><h4>Basic Plutus Voting dApp</h4><p><strong>Fund 7</strong> — DAOs ❤️ Cardano <a href="https://cardano.ideascale.com/c/idea/384821">— Proposal</a></p><p><a href="https://drive.google.com/file/d/1m61Y2KOkWIFvNukNPFadLssNBadQUEt2/view">Project Close Out Report</a> — <a href="https://drive.google.com/file/d/1g2ug916IM5FunY7tG8ucw1_ZmpE8yFNl/view">Project Close Out Video</a></p><p><a href="https://github.com/dcSpark/plutus-voting-dapp">GitHub Repository</a></p><p>We created and open-sourced (MIT license) a smart contract written in Plutus for DAO treasury voting. This allows DAOs built on Cardano to hold a decentralized vote for whether or not to pay out, from their treasury to a single address — if the vote receives enough votes from participants in relation to the chosen quorum. This was the first such voting contract written in Plutus and allows Cardano DAOs to operate like true DAOs, without the need to use trusted 3rd parties to distribute funds.</p><p>This smart contract takes advantage of the UTxO model and allows users to vote with their own UTxOs, independent of others, maximizing the throughput of this voting protocol. For this proposal we wrote the smart contract code, complete with on-chain validation checks, created off-chain endpoints for interacting with the smart contract, and implemented tests to show off and ensure the functionality of the contract.</p><h4>Cardano Omnibus — UTXO Management</h4><p><strong>Fund 7</strong> — Open Source Developer Ecosystem <a href="https://cardano.ideascale.com/c/idea/384606">— Proposal</a></p><p><a href="https://docs.google.com/document/u/1/d/1qCQF2ugt7b_kRercQf-eUEEMlHeMbgOa6s197r52GaU/edit?usp=sharing">Project Close Out Report</a> — <a href="https://www.youtube.com/watch?v=cao6gF1FwoA">Project Close Out Video</a></p><p>We created a new algorithm for managing UTxO outputs from a transaction, resulting in the reorganization of UTxO -specifically the grouping of dust- and, most importantly, reducing the fees for the user. We’ve named this algorithm <em>Thermostat,</em> and it is currently being utilized by the Milkomeda bridge to optimize UTxOs and fees for users. This work has been <a href="https://github.com/dcSpark/utxo-selection-benchmarking">open sourced on GitHub</a> under the MIT license.</p><p>When creating this algorithm, we also developed some tools around it, namely a UTxO selection library, fee estimation mechanics, and <a href="https://github.com/dcSpark/dcspark-core/pull/12">UTxO selection algorithm benchmarking library</a>. Using these libraries users can create their own UTxO selection algorithm and can measure how well a particular algorithm performs compared to the other algorithms.</p><h4>Fractionalized NFTs v2 (Fracada)</h4><p><strong>Fund 7</strong> — DApps &amp; Integrations <a href="https://cardano.ideascale.com/c/idea/384625">— Proposal</a></p><p><a href="https://github.com/dcSpark/fracada-il-primo">GitHub Repository</a></p><p><a href="https://medium.com/dcspark/fracada-il-primo-3fa777b80cc2">Explainer Blog Post</a></p><p><a href="https://medium.com/dcspark/fracada-il-primo-for-developers-5055dc0834e">Blog Post for Developer</a></p><p>We built and open sourced (MIT license) a Plutus smart contract for fractionalizing NFTs on Cardano into a user-selected number of tokens; allowing Cardano NFT DAOs to relinquish their reliance on third parties to store assets and become true NFT DAOs. This is the second version of this NFT fractionalizing contract and the functionalities added in this version include being able to fractionalize multiple NFTs in one contract, and the ability to add more NFTs to the contract after the initial NFT deposit and token mint. These additions all significantly increase the utility of this contract for anyone, e.g., NFT investment DAOs, that chooses to use it.</p><p><strong>We are currently working on addressing the findings of an audit completed on the Fracada v2 code and will soon be updating the repository with these updates.</strong></p><h4>Smart Contract Upgradability</h4><p><strong>Fund 7</strong> — DAOs ❤️ Cardano <a href="https://cardano.ideascale.com/c/idea/384819">— Proposal</a></p><p><a href="https://drive.google.com/file/d/15WZpY_mKpcQPhNntg7PVnVchGH1WO-XO/view">Project Close Out Report</a> — <a href="https://drive.google.com/file/d/1w--XLhASqUf2IlzWm-JPg5ShuJTrXPrM/view">Project Close Out Video</a></p><p><a href="https://github.com/dcSpark/plutus-smart-contract-upgrade-dApp">GitHub Repository</a></p><p>We created and open sourced (MIT License) the code for a Plutus smart contract that can be used to upgrade a DApp’s smart contract; this allows the likes of DAO treasuries and multisignature contracts to be upgraded over time, in a decentralized manner, to become more complex as Cardano evolves.</p><p>This code can be used to move the UTxO of a DApp, using multisigs, from an old validator script to a new validator script. You can also upgrade the Datum and the data being held within that Datum. We produced an example for upgrading a treasury UTxO to a new smart contract if enough signatures are used to validate the upgrade.</p><h4>Cardano Rust SDK Babbage</h4><p><strong>Fund 8 </strong>— Open Source Development Ecosystem <a href="https://cardano.ideascale.com/c/idea/400675">— Proposal</a></p><p><a href="https://docs.google.com/document/d/1hw1qFzbkt0hRU8PblSt-QM17hYnfQHCxwxBtLZO5514/edit#heading=h.pzr4ci634f95">Project Close Out Report</a> — <a href="https://www.youtube.com/watch?v=SsOeWwSuC3k">Project Close Out Video</a></p><p>This proposal upgraded the /cardano-multiplatform-lib repository to be ready to support the new features, such as those in Plutus v2, that were introduced by the Vasil (a.k.a. Babbage) hardfork — Without this update, the many projects on Cardano that rely on this library would cease to function.</p><p>We updated this SDK according to the specifications and released the updated version 1 month before the Vasil hardfork, allowing the many community projects that depend on CML to update their projects before the hardfork event. The update was released on <a href="https://github.com/dcSpark/cardano-multiplatform-lib">GitHub</a>, <a href="https://crates.io/crates/cardano-multiplatform-lib/1.0.0">crates.io</a>, and <a href="https://www.npmjs.com/package/@dcspark/cardano-multiplatform-lib-nodejs/v/1.0.0">npm</a>.</p><h4>Chamber of Digital Commerce</h4><p><strong>Fund 8</strong> — Lobbying for Favorable Legislation <a href="https://cardano.ideascale.com/c/idea/400719">— Proposal</a></p><p><a href="https://digitalchamber.org/about/members/">Members List on the CODC Website</a></p><p><a href="https://twitter.com/dcspark_io/status/1532410756989345794">We Joined in June 2022</a></p><p>The Chamber of Digital Commerce (CODC) is an American advocacy group and world-leading trade association that promotes the emerging industry behind blockchain technology, Bitcoin, digital currency, and digital assets. As a result of this funding, we joined the “President’s Circle” of the Chamber of Digital Commerce. This has enabled us to participate and provide insight into the conversations and discussions related to digital assets and the blockchain industry happening with the US government and other regulatory entities.</p><p>We will continue to be involved in both virtual and digital events, discussions, and working groups, and will continue to participate in and help shape the discussion and regulation around blockchain technology and digital assets in a positive way.</p><h4>Db-sync Replacement in Oura</h4><p><strong>Fund 8</strong> — Open Source Development Ecosystem <a href="https://cardano.ideascale.com/c/idea/400674">— Proposal</a></p><p><a href="https://drive.google.com/file/d/15fcP5uxGuepqM_LOVktWAQjnMYJlERmZ/view">Project Close Out Report</a> — <a href="https://drive.google.com/file/d/1YzIhKXbCPQFKwcbPTLjk3ejvw3wjzkfn/view">Project Close Out Video</a></p><p><a href="https://github.com/dcSpark/carp">GitHub Repository</a></p><p><a href="https://dcspark.github.io/carp/docs/intro/">Carp Documentation</a></p><p><a href="https://medium.com/dcspark/carp-new-cardano-sql-indexer-replacement-for-db-sync-b990243a329e">Article Explaining Carp</a></p><p>Carp is a flexible, modular, fast, type-safe, and well-documented alternative to Cardano’s db-sync, and allows developers to create databases that service their unique needs without collecting arbitrary information. This new indexer allows Cardano developers to deliver their users the data they want in the timely manner they expect in today’s modern world. Carp’s release also diversifies the Cardano indexing tools available to developers and reduces the ecosystem’s reliance on what could be a single point of failure. When we replaced db-sync with Carp for our Flint wallet we saw a 25x increase in the load speed of transactions!</p><h4>Self-Hosted Pricefeed for Wallets</h4><p><strong>Fund 8</strong> — DApps &amp; Integrations <a href="https://cardano.ideascale.com/c/idea/405401">— Proposal</a></p><p><a href="https://twitter.com/dcspark_io/status/1604830574111518721?s=61&amp;t=PyimMTDslNLe4zH5h6iJZ">Release Tweet Thread</a></p><p><a href="https://github.com/dcSpark/carp/blob/main/indexer/execution_plans/dex_prices.toml#L44..L54">Implementation in Carp GitHub Repository</a></p><p>We added support to the lightweight and modular Cardano indexer,<a href="https://github.com/dcSpark/carp"> Carp</a>, for querying token prices from the on-chain data of three Cardano DEXes (WingRiders, SundaeSwap, and Minswap), enabling wallets can use this to display live token prices in their interface for their users. The completion of this proposal significantly reduces the ecosystem’s reliance on centralized APIs for this data point, as the information used to produce this data point in Carp is drawn entirely from on-chain data! Along with an endpoint for current prices, we have also added an endpoint to allow for the querying of historical token prices.</p><h4>Carp Over-Budget + Maintenance</h4><p><strong>Fund 9</strong> — Developer Ecosystem <a href="https://cardano.ideascale.com/c/idea/419159">— Proposal</a></p><p>The work for this proposal was completed as we drafted this post and is now live and usable in the <a href="https://github.com/dcSpark/carp">Carp GitHub Repository</a>. Our team has begun work on completing the Project Close Out Report and Video to finalize the delivery of this proposal for Project Catalyst. This proposal funded necessary maintenance to Carp, a flexible Cardano indexer, that is growing in popularity in the Cardano ecosystem as an alternative to db-sync.</p><p>For this proposal we have worked on upgrading and maintaining multiple elements of Carp, including<a href="https://github.com/dcSpark/carp/pull/125"> storing swaps and mean token prices from DEXes</a> (finished) and adding support to allow Carp users to add other data sources (<a href="https://github.com/dcSpark/carp/pull/116">pull request 116</a>,<a href="https://github.com/dcSpark/carp/pull/120"> pull request 120</a>). To use Carp head over to the <a href="https://github.com/dcSpark/carp">Carp GitHub Repository</a>, which contains all the code for deploying Carp along with links to the developer documentation.</p><h4>CIP25 (NFT) Rust &amp; WASM Library</h4><p><strong>Fund 9</strong> — Developer Ecosystem <a href="https://cardano.ideascale.com/c/idea/419160">— Proposal</a></p><p>We are proud to announce that we very recently completed this proposal and the library containing the work done can be found <a href="https://github.com/dcSpark/cip25-lib">here</a>. Our team has started writing the Project Close Out Report and the recording of the Project Close Out Video will begin shortly afterwards, allowing us to fulfill the reporting needs to officially close this proposal out with Project Catalyst.</p><p>This proposal made supporting the NFT metadata standards (CIP25) natively possible in many of the Cardano tools written in Rust, such as Oura, Carp, CSL and CML. This allows these tools to fully index NFT metadata and removes the possibilities of the subtle bugs that could emerge in the methods previously used to parse this data.</p><p>In the work done for this proposal we completed the initial code generation and mixed V1 and V2 in the CIP25 repo linked above. We also made some<a href="https://github.com/dcSpark/cardano-multiplatform-lib/pull/164"> API and test improvements</a>,<a href="https://github.com/dcSpark/cardano-multiplatform-lib/pull/160"> added build scripts</a> for the Rust and WASM libraries, and completed a<a href="https://github.com/dcSpark/cardano-multiplatform-lib/pull/165"> cleanup of the code</a>. We have published the npm packages for the first versions of CIP25 and we are planning on incorporating this into Flint wallet soon.</p><h4>Rust SDK — Fix Critical CBOR Encoding</h4><p><strong>Fund 9 </strong>— Developer Ecosystem <a href="https://cardano.ideascale.com/c/idea/419158">— Proposal</a></p><p>This proposal was recently completed and our team has started writing the Project Close Our Report, who’s submission, along with a Project Close Out Video, will officially close this proposal with the Project Catalyst team. This proposal allowed Cardano’s widely used Rust-based tooling to support multiple encoding possibilities, ensuring the reliability of this Rust-based tooling for the many DApps built on top of it. When working on this proposal we fixed the issues which were noted in the proposal, as evidenced by<a href="https://github.com/dcSpark/cardano-multiplatform-lib/pull/143"> pull request 143</a>,<a href="https://github.com/dcSpark/cardano-multiplatform-lib/pull/153"> pull request 153</a>, and<a href="https://github.com/dcSpark/cardano-multiplatform-lib/pull/164"> pull request 164</a>.</p><p>We also worked on the regeneration and improvements for the CML structures to enable support for multiple encodings, completed the refactoring of the repository structure, created WASM and Rust code for the crypto structures, and added a core-WASM crate as a part of the CBOR encoding fixes. The necessary work has been done in the cddl-codegen library, and the generated code now supports multiple CBOR encoding possibilities, fulfilling our promises in the proposal.</p><h3><strong>Follow Us To Stay Up-to-Date on Our Progress!</strong></h3><p>We hope that this, relatively long, blog post has provided you with the information and resources to understand what we’ve accomplished with the Catalyst funding we’ve received, and what we’ll soon be bringing to the ecosystem with our proposals that are still in-progress!</p><p>If you have any questions about these proposals, be they completed ones or the ones we’re working on, then please reach out to us either on Twitter, <a href="https://twitter.com/dcspark_io">@dcspark_io</a>, or on our <a href="https://discord.com/invite/dcspark">Discord server</a> — where you’ll also find many other community members who like to keep up with our development updates. If you have any questions about anything else dcSpark or Cardano please feel free to reach out to us; we’re always happy to chat! Finally, follow us on Twitter and our <a href="https://medium.com/dcspark">Medium blog</a> to keep up with the latest things coming out of dcSpark.</p><p><strong>Follow dcSpark:</strong></p><p><strong>Website:</strong><a href="https://www.dcspark.io/"><strong> dcspark.io</strong></a><strong><br>Twitter:</strong><a href="https://twitter.com/dcspark_io"><strong> @dcspark_io</strong></a><strong><br>Discord:</strong><a href="https://discord.gg/dcspark"><strong> /dcSpark</strong></a><strong><br>Medium:</strong><a href="https://medium.com/dcspark"><strong> /dcSpark</strong></a><strong><br>GitHub:</strong><a href="https://github.com/dcSpark"><strong> /dcSpark</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d2cef655e2d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dcspark/dcspark-catalyst-proposal-updates-5d2cef655e2d">dcSpark Catalyst Proposal Updates</a> was originally published in <a href="https://medium.com/dcspark">dcSpark</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What a Year! A Look Back at Flint in 2022!]]></title>
            <link>https://medium.com/dcspark/what-a-year-a-look-back-at-flint-in-2022-dec8a687f64f?source=rss-a7c6f5bf5480------2</link>
            <guid isPermaLink="false">https://medium.com/p/dec8a687f64f</guid>
            <category><![CDATA[cardano]]></category>
            <category><![CDATA[ada]]></category>
            <category><![CDATA[wallet]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[interoperability]]></category>
            <dc:creator><![CDATA[Iwopietak]]></dc:creator>
            <pubDate>Wed, 28 Dec 2022 16:02:49 GMT</pubDate>
            <atom:updated>2022-12-28T16:02:49.601Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hyEjGR4fykDTK7EbMtVvoQ.jpeg" /></figure><p>Over the past year, the development of<a href="https://flint-wallet.com/"> Flint wallet</a> has come on in leaps and bounds! The functionalities, user-friendliness, and capabilities introduced to Flint this year have kept it on the cutting edge of Cardano wallet development and helped Flint to maintain its position as one of the most popular wallets in the Cardano ecosystem.</p><p>We’ve taken a look back at the features and improvements we introduced to Flint throughout 2022 and handpicked some of the biggest and best to highlight here!</p><h3><strong>Flint Mobile was Released!</strong></h3><p>In May Flint went live for iOS devices on the<a href="https://apps.apple.com/app/dcspark-flint-wallet/id1619660885"> Apple App Store</a>, and June saw Flint hit the<a href="https://play.google.com/store/apps/details?id=io.dcspark.flintwallet&amp;hl=en&amp;gl=US&amp;pli=1"> Google Play Store</a> and Android devices. These releases made Flint one of the first Cardano wallets to go mobile and allowed users to perform their NFT trades, use DeFi, and other blockchain activities on the go.</p><p>A few months later we also released the ecosystem’s first fully open mobile DApp browser (read more<a href="https://medium.com/dcspark/flint-wallets-innovative-mobile-dapp-browser-c77d68f5b10b"> here</a>). This features a URL bar that allows you to explore the entire world of Cardano DApps through popular search engines. You can also bookmark DApps to make it even quicker to return to the DApps you love!</p><h3>Flint with Milkomeda C1 mode!</h3><p>All the way back at the beginning of February, we<a href="https://twitter.com/FlintWallet/status/1489585017852358656"> launched</a> ADA wrapping support for the soon-to-be-released<a href="https://milkomeda.com/"> Milkomeda</a> C1 sidechain for Cardano. Flint was the first Cardano native wallet to offer support for the wrapping of assets to the Milkomeda bridge.</p><p>Flint supports a variety of Cardano native tokens, including those that can be bridged to the Milkomeda C1 platform. These tokens can be viewed on the <a href="https://bridge-explorer.milkomeda.com/cardano-mainnet/tokens">Milkomeda Bridge Explorer</a> token page.</p><h3><strong>We Introduced Deep Links to Cardano</strong></h3><p>Late in September, we brought the first deep links generator to the Cardano ecosystem. This allows users, businesses, and DApps to create links that open a pre-filled payment in Flint wallet — which users then simply sign and send-, and to create links that open a specific DApp page in Flint’s open mobile DApp browser.</p><p>You can get started with deep links using our simple<a href="https://flint-wallet.com/deep-link-generator"> Deep Link Generator</a>, and learn a bit more about them in the<a href="https://medium.com/dcspark/deep-links-mobile-dapp-bookmarks-and-other-flint-updates-ba931c5acf90"> Flint update</a> we posted back in September.</p><h3><strong>Biometrics For Flint Mobile</strong></h3><p><a href="https://twitter.com/FlintWallet/status/1597332803384840192">Biometric unlocking</a> for Flint mobile was released in late November. Since then you’ve been able to use your face or your fingerprint to effortlessly unlock Flint mobile on Android and iOS devices.</p><p>You can also use your biometrics to sign a transaction instead of having to enter your spending password! This makes the mobile Flint experience one of the most effortless and secure in the Cardano ecosystem, allowing you to quickly and easily interact with the Cardano blockchain.</p><h3><strong>There was So Much More in 2022!</strong></h3><p>Gabriel Garrett, Flint Team Lead, had the following to share about Flint’s progress in 2022:</p><blockquote>Flint’s first year saw leaps and bounds in improvements. Thanks to the steady stream of feedback we received from the community, we were able to guide Flint to new frontiers in the Cardano ecosystem in ways that will benefit the development of all Cardano wallets moving forward.</blockquote><p>Feedback from the community, both bugs and feature requests, help to steer the development of Flint so that it keeps up with what users expect from a best-in-class non-custodial wallet. With that in mind, we’ve created a brief list of some of the other features that were introduced to Flint this year, many of which were requests from the community:</p><p><strong>QR Code Scanner for Mobile:</strong> To make sending assets and retrieving another user’s address even easier, we added a QR code scanner to Flint Mobile.</p><p><strong>ADA Handle Support:</strong><a href="https://adahandle.com/"><strong> </strong>ADA Handle</a><strong> </strong>is the Cardano community’s most popular human-readable address resolution system, and this year we added support for sending to ADA Handles. Simply type a “$” into the “Receiver’s Address” field and Flint will recognize your intentions and search for the $handle you type after it.</p><p><strong>Compatibility Mode: </strong>This allows you to inject Flint into any DApp as a different Cardano wallet. This is very useful if that DApp does not yet have support for Flint. Head to the “Connected apps” section of Flint’s settings to access this feature and select which Cardano wallet you want to inject Flint as.</p><p><strong>Carp Integration:</strong> In May we<a href="https://medium.com/dcspark/carp-new-cardano-sql-indexer-replacement-for-db-sync-b990243a329e"> released Carp</a>, our own open-sourced and Project Catalyst-funded flexible alternative to the core Cardano component db-sync. In August we<a href="https://medium.com/dcspark/carp-has-been-integrated-into-flint-what-does-this-mean-d08082a69907"> integrated Carp into Flint</a><strong>, </strong>and users of Flint were quick to take to<a href="https://twitter.com/RichardMcCrackn/status/1561800865253580801?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1561800865253580801%7Ctwgr%5E6c984c39d24d0704d8efcd8b6f29389745b7adc3%7Ctwcon%5Es1_&amp;ref_url=https://cdn.embedly.com/widgets/media.html?type=text2Fhtmlkey=a19fcc184b9711e1b4764040d3dc5c07schema=twitterurl=https3A//twitter.com/richardmccrackn/status/1561800865253580801image=https3A//i.embed.ly/1/image3Furl3Dhttps253A252F252Fabs.twimg.com252Ferrors252Flogo46x38.png26key3Da19fcc184b9711e1b4764040d3dc5c07"> social media</a> to note the speed gains from this change — seeing an average 25x increase in load speed for their Flint wallets!</p><p><strong>Bluetooth Hardware Wallet Support: </strong>Both the mobile and desktop versions of Flint wallet now support Bluetooth connections for the Ledger Nano X hardware wallet. Increasing the speed and ease with which users can use their tokens secured in cold storage.</p><p><strong>Multi-Asset Transactions: </strong>Using Flint you can now send multiple different assets to the same receiver in a single transaction. Simply select multiple assets in the top corner of the send page to start building a multi-asset transaction. Flint will also automatically add the right amount of ADA to pay the transaction fee if your transaction doesn’t include ADA.</p><p><strong>Comments as Transaction Metadata: </strong>In line with CIP-20, users of Flint wallet can now add notes to transactions, e.g. “Subscription Payment”, so they can pass a message or detail the purpose of a transaction to the receiver.</p><p><strong>Support for Multiple CIPs: </strong>Alongside support for other CIPs added to Flint throughout the year, we recently added support for CIP-30. This CIP sets a standard that allows DApps to more easily integrate with Cardano wallets, and complying with this means that Flint is ready, in the most effortless way possible, to be integrated into DApps by developers.</p><p><strong>Dark Mode and UI Improvements:</strong> Dark mode was a big community request that we implemented in the middle of the year, and throughout the year we’ve also made other UI tweaks that make using Flint both easier and more streamlined. If there’s a UI improvement you’d like to see or a bug you’d like to report please join our<a href="https://discord.gg/dcspark"> Discord</a> to tell us about it!</p><p><strong>Export Transactions to a CSV File: </strong>Easily being able to export your transactions to a CSV file makes completing your taxes even easier and is a feature that is also of great help to DApp builders.</p><p><strong>Milkomeda Bridge Transaction Browser: </strong>When you used Flint to send a transaction across the Milkomeda bridge you were previously only directed to the Cardano side of the transaction when you clicked on that transaction. An update we implemented means that you are now directed to the<a href="https://bridge-explorer.milkomeda.com/cardano-mainnet"> Milkomeda Bridge Explorer</a><strong>, </strong>where you can see both sides of the transaction, on both the Cardano and the Milkomeda C1 side.</p><p><strong>Vasil Hardfork Preparations: </strong>We made sure we were prepared well in advance for the protocol changes brought forth by the Vasil hardfork. As a result, Flint and Flint users experienced minimal disturbance and no noticeable changes after the Vasil hardfork event.</p><p><strong>Bug Fixes:</strong> We have fixed multiple bugs, both technical and aesthetic fixes, that all improve the user experience and keep Flint functioning at the highest level.</p><p><strong>NFT Gallery Returns to iOS: </strong>When Apple made some changes to its policies on NFT support the NFT Gallery was removed from Flint mobile for iOS. A few months later we managed to bring the gallery back! Meaning you can now look at and show off your NFTs on your iOS device!</p><p><strong>Japanese Language Support:</strong> Cardano has a large and vibrant Japanese community and we aim to service them. Adding support for the Japanese language to Flint wallet did just that. Keep your eyes peeled as support for other languages is coming in the near future.</p><p><strong>Download Flint Wallet Today!</strong></p><p>If you haven’t tried Flint wallet then today is as good as any to start using one of Cardano’s most popular community wallets. You can download Flint for desktop, iOS, and Android from the<a href="https://flint-wallet.com/"> Flint website</a>, and on our website you can find more out about<a href="https://flint-wallet.com/deep-link-generator"> deep links</a> and some of the other features we have planned for 2023! These include a blockchain education section for Flint, address book functionality, EVM integration and… we can’t tell you all of them here as the list is very long! So follow us on<a href="https://twitter.com/FlintWallet/"> Twitter</a> and<a href="https://medium.com/dcspark"> Medium</a> to stay up with our latest feature releases.</p><p>Many features come at the request of community members. If you have feature requests or feedback, be it good or bad, for Flint then please join our friendly community on<a href="https://discord.com/invite/dcspark"> Discord</a> to let us know!</p><p><strong>Connect with Flint:<br>Website:</strong><a href="https://flint-wallet.com/"><strong> </strong>flint-wallet.com</a><br><strong>Twitter:</strong><a href="https://twitter.com/FlintWallet/"> @FlintWallet</a><br><strong>Medium:</strong><a href="https://medium.com/dcspark"> /dcSpark</a><br><strong>Discord:</strong><a href="https://discord.gg/dcspark"><strong> </strong>/dcSpark</a><br><strong>Apple App Store:</strong><a href="https://apps.apple.com/app/dcspark-flint-wallet/id1619660885"> Flint Wallet</a><br><strong>Google Play Store:</strong><a href="https://play.google.com/store/apps/details?id=io.dcspark.flintwallet&amp;hl=en&amp;gl=US"> Flint Wallet</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dec8a687f64f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dcspark/what-a-year-a-look-back-at-flint-in-2022-dec8a687f64f">What a Year! A Look Back at Flint in 2022!</a> was originally published in <a href="https://medium.com/dcspark">dcSpark</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>