<?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 Marvin Kruse on Medium]]></title>
        <description><![CDATA[Stories by Marvin Kruse on Medium]]></description>
        <link>https://medium.com/@marvinkruse?source=rss-28ab8e733ade------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OrxsKWEtjR02t_xpsGOTuQ.png</url>
            <title>Stories by Marvin Kruse on Medium</title>
            <link>https://medium.com/@marvinkruse?source=rss-28ab8e733ade------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:56:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@marvinkruse/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[Berlin Blockchain Week]]></title>
            <link>https://medium.com/ditcraft/berlin-blockchain-week-dcbd098406c8?source=rss-28ab8e733ade------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcbd098406c8</guid>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[web3-summit]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethberlin]]></category>
            <category><![CDATA[events]]></category>
            <dc:creator><![CDATA[Marvin Kruse]]></dc:creator>
            <pubDate>Tue, 22 Oct 2019 08:49:20 GMT</pubDate>
            <atom:updated>2019-10-22T08:58:10.334Z</atom:updated>
            <content:encoded><![CDATA[<h3>Berlin Blockchain Week’19</h3><h4>Event Summary</h4><p>The ditCraft team attended this years’ <strong>Berlin Blockchain Week</strong> — and we had a blast 🎉 Our mission was to gather new insights and receive valuable feedback regarding our platform and get in touch with the community: the most valuable asset that we have. We spoke with a lot of interesting and different people and gained a lot of new ideas about the more important features of our platform and where we need to improve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mrLcAuF4XJJjhB5gV-vTWQ.png" /><figcaption>Best conversation starter: fancy t-shirts!</figcaption></figure><p>Apart from direct conversations we also spread the word on-stage with <strong>two conference talks</strong> and <strong>our very own codeDAO meet-up.</strong></p><h3>Web3 Summit</h3><p>With so many events happening in one week it’s easy to lose track — but we did our best to attend the most important conferences and meet-ups. It all started of with the <strong>Web3 Summit</strong> <em>(by </em><a href="https://medium.com/u/d6954f1a46d9"><em>Web3 Foundation Team</em></a><em>)</em>, where big names like <em>David Chaum,</em> <em>Edward Snowden</em> and <em>Gavin Wood</em> delivered inspiring talks, mesmerising the audience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AWwyP0hKwCE6QU_t_M08aA.png" /></figure><p>Part of this is also the so-called “Hackerspace”, where interested coders are hanging out to learn about other projects. Our <strong>CTO </strong><a href="https://medium.com/u/3d4de1db47a9"><strong>Yannik Goldgräbe</strong></a> did a <strong>live hack</strong> including a hands-on demo and presentation of the ditCLI and ditExplorer working in conjunction.</p><h3><strong>DappCon</strong></h3><p>With the Web3 Summit coming to an end, the next big conference got going: <strong>DappCon</strong> <em>(by </em><a href="https://medium.com/u/e7281ad70ea"><em>Gnosis</em></a><em>)</em>. With a big focus on Ethereum-related projects, a lot of prominent community members where attending the conference: <a href="https://medium.com/u/587a00dbce51">Vitalik Buterin</a>, <a href="https://medium.com/u/aa9bb0a9d2ad">Vlad Zamfir</a>, <a href="https://medium.com/u/6a370863659c">Joseph Lubin</a> and many more!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jWKCubZKqO9SFExs16q3wA.png" /></figure><p>Perfectly equipped with our <em>“dit is the new git” </em>t-shirts we had the best conversation starter imaginable for this event: a lot of developers where fascinated by our idea and mission to solve the issues of centralisation, malgovernance and lacking incentivisation in the software development space — especially in the open source area.</p><p>Our <strong>Chief Scientist </strong><a href="https://medium.com/u/b0a55f61d505"><strong>Sebastian Gajek</strong></a> was part of a panel revolving around governance and DAOs on Ethereum.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fvideoseries%3Flist%3DPLqZa0BiECeEisr_0pBYOrkm4ENVfpCDkW&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D4ycvGKvano8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F4ycvGKvano8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/dc4da6f1c008cb6c723b4c2de407cc51/href">https://medium.com/media/dc4da6f1c008cb6c723b4c2de407cc51/href</a></iframe><p>Part of the DappCon were also two one-day conferences happening on Friday: <strong>Token Engineering Global Gathering</strong> <em>(by TokenEngineering/</em><a href="https://medium.com/u/1453c5815266"><em>Angela Kreitenweis</em></a><em>)</em> and <strong>Decentralized Storage Summit </strong><em>(by </em><a href="https://medium.com/u/eb39e24daee9"><em>1kx</em></a><em>)</em>.</p><h4><strong>Token Engineering Global Gathering</strong></h4><p>Our <strong>CEO </strong><a href="https://medium.com/u/28ab8e733ade"><strong>Marvin Kruse</strong></a> was delighted to be part of the <strong>Token Engineering Global Gathering</strong>, presenting ditCraft and our cryptoeconomic incentive model to a broad audience with a research and token engineering background.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDGooYutPxSE%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDGooYutPxSE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDGooYutPxSE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e3ef9a30d1b325aef557e7e238864208/href">https://medium.com/media/e3ef9a30d1b325aef557e7e238864208/href</a></iframe><h4><strong>Decentralized Storage Summit</strong></h4><p>At the same time, <strong>CTO </strong><a href="https://medium.com/u/3d4de1db47a9"><strong>Yannik Goldgräbe</strong></a> was giving a talk at the <strong>Decentralized Storage Summit</strong>, going into the details of the things you can do with the ditCLI and the ditExplorer for a very technical and interested audience.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Ff2lwfpgXnIo%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Df2lwfpgXnIo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Ff2lwfpgXnIo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3dd779cef25f71d23e301c7caa227ebe/href">https://medium.com/media/3dd779cef25f71d23e301c7caa227ebe/href</a></iframe><h3><strong>codeDAO — the ditCraft Meet-Up</strong></h3><p>A lot of conferences and events were happening during Berlin Blockchain Week, especially in the evening, where most of the meet-ups took place. While we also attended some very interesting meet-ups in the space, we took the opportunity to host our very own one — the <strong>codeDAO meet-up</strong>. Sponsored by the <em>Innogy Innovation Hub,</em> we featured <strong>speakers</strong> <strong>from</strong> <a href="https://medium.com/u/b1f8f81b9c0c"><strong>Samsung NEXT</strong></a><strong>, Gitcoin and Innogy </strong>themselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Bc41yRH3rnbVHCxqK0berw.png" /></figure><p><a href="https://medium.com/u/6434deb7e78d"><strong>Ricardo J. Méndez</strong></a>, the technical director of <a href="https://medium.com/u/b1f8f81b9c0c">Samsung NEXT</a>, explored ideas on how to supported so-called “randos” — the seemingly random people developing the open-source software that the world is running on. <a href="https://medium.com/u/194c20cf90b6"><strong>Kevin Owocki</strong></a> from Gitcoin shed light on web3-native business models and the ones that exist in the current web 2.0 and how these might transform into the web3 paradigm. <a href="https://medium.com/u/28ab8e733ade"><strong>Marvin Kruse</strong></a><strong> </strong>presented ditCraft’s codeDAO approach to guide the open source space into a more sustainable and decentralized future. <strong>Kerstin Eichmann </strong>and<strong> Torsten Dahmen </strong>from the innogy innovation hub presented their “maslow for machines” framework dealing with strategic investments in blockchain startup and explored the concept of an energyDAO. All of the talks can be found on our <a href="https://www.youtube.com/watch?v=T4bhebJ7ui4&amp;list=PLqZa0BiECeEiPI4R8Ksm97Det6V3ePqxq"><strong>YouTube channel</strong></a><strong> </strong>as well.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fvideoseries%3Flist%3DPLqZa0BiECeEiPI4R8Ksm97Det6V3ePqxq&amp;url=https%3A%2F%2Fwww.youtube.com%2Fplaylist%3Flist%3DPLqZa0BiECeEiPI4R8Ksm97Det6V3ePqxq&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FT4bhebJ7ui4%2Fhqdefault.jpg%3Fsqp%3D-oaymwEWCKgBEF5IWvKriqkDCQgBFQAAiEIYAQ%3D%3D%26rs%3DAOn4CLAme5zFTqCNyb3hkFFWjV8jHbEX3w&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="853" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/217253b32ba0cbd2f0aab5a2922c092e/href">https://medium.com/media/217253b32ba0cbd2f0aab5a2922c092e/href</a></iframe><h3>EthBerlinZwei Hackathon</h3><p>The grand finale of Berlin Blockchain Week was — without a doubt — the EthBerlinZwei Hackathon. Hundreds of hackers were eagerly hacking night and day to win challenges or just play around with awesome ideas and concepts. More than 80 projects where submitted in the end — a huge success! The team of <strong>ditCraft</strong> used the hackathon to directly get in touch with a lot of developers and gather feedback on the frontlines. We also took the opportunity to hack on something ourselves and integrated <a href="https://medium.com/u/7cedca298e8f"><strong>KyberNetwork</strong></a><strong> </strong>token swaps. We deployed their protocol for an easy on- and off-ramp into our system to swap xDAI and ETH. This way cashing in/out xDAI on the ditPlatform is considerably simplified. For the ditPlatform the merits of the feature are clear: users shall onboard with ease and comfortably liquidize their token rewards. We are working on improving the customer story here. More to come in future posts. Not only the ditCraft team was surprised about the seemingly integration of token swap mechanisms, but also <a href="https://medium.com/u/7cedca298e8f">KyberNetwork</a> <a href="https://blog.kyber.network/berlin-blockchain-week-2019-recap-ee92d730344f">liked what the team produced</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HRfS1CG9yoUZ1LxLLbAhCw.png" /><figcaption>ditCraft &lt;&gt; Kyber Network @ ETHZWEI Hackathon</figcaption></figure><p>All in all we can say that Berlin Blockchain Week was an absolute blast 🔥 We got so much good and valuable feedback, made new contacts and spread the word about ditCraft. We are looking forward to the next conferences, hackathons and meet-ups! Keep us on the radar!!</p><h3>ditCraft is about community! ditCraft is about you!</h3><p>If you like the idea of decentralized, incentivized and democratic coding, we highly encourage you to</p><ul><li>try out the <a href="https://github.com/ditcraft/cli">ditCLI</a> and <a href="https://explorer.ditcraft.io/">ditExplorer</a>,</li><li>watch some <a href="https://www.youtube.com/channel/UCl3oAs5_z6y7FfxwMNWFMgw">youtube</a> tutorials and conference talks (for a low-cost intro),</li><li>read the ditProtocol <a href="https://ditcraft.io/dl/ditcraft_whitepaper.pdf">whitepaper</a> (for a deep dive),</li><li>join the product discussion and request new features on <a href="http://discord.ditcraft.io/">discord</a> (for telling us what we need to do better),</li><li>follow us on Twitter to get updates. (We only communicate news/updates via <a href="https://twitter.com/ditcraft">Twitter</a>.)</li><li>leave some claps. (Applause is the spur of noble minds)</li><li>are humbled if you spread the word to the open source community (ditCraft is from the community for the community)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcbd098406c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ditcraft/berlin-blockchain-week-dcbd098406c8">Berlin Blockchain Week</a> was originally published in <a href="https://medium.com/ditcraft">ditCraft</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PoW#01: Releasing ditCLI v0.2 and other Updates]]></title>
            <link>https://medium.com/ditcraft/pow-01-releasing-dit-v0-2-and-other-updates-5d67cb4d12a?source=rss-28ab8e733ade------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d67cb4d12a</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[pow]]></category>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Marvin Kruse]]></dc:creator>
            <pubDate>Thu, 02 May 2019 12:36:46 GMT</pubDate>
            <atom:updated>2019-05-25T21:57:39.703Z</atom:updated>
            <content:encoded><![CDATA[<h4>Progress Report on the ditcraft technology stack</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8c333d_YNEHG4q3UDb1wTA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/5fNmWej4tAA?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Helloquence</a> on <a href="https://unsplash.com/search/photos/work?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Recently we released an extensive update to the ditCraft technology stack. This update included so many different things in a lot of components, that a lot of them could have been missed easily. This is why we came up with our own version of “<strong>Proof-of-Work</strong>” in the form of this article.</p><p>We released an update to the <strong>ditCLI</strong>, namely version 0.2, containing many improvements on the user experience and more detailed information on the individual results of votes. In addition to this we launched our own version of a <strong>KYC</strong> — or as we call it <strong>Know-Your-Coder</strong> — where users just send a simple tweet to our Twitter account in order to get verified.</p><p>On the <strong>smartcontract</strong> side we prepared everything to be <strong>easily upgradeable</strong> in the future and deployed all the contracts to the <strong>xDai network</strong>. In addition to the quick 5 second blocktimes it is also a lot cheaper to interact with our smartcontracts there, reducing the estimated yearly cost for a developer using dit from &gt;$100 USD to just <strong>some cents</strong>.</p><p>We are also working on a <strong>new webUI</strong>, which will allow anyone to easily interact with our ecosystem without needing to enter the command line. Furthermore, we now started to migrate the git integration of our ditCLI to the <strong>native git library</strong> to move from a proof-of-concept to something that is ready to be used in live development systems.</p><h4><strong>ditCLI v0.2</strong></h4><p>With the most prominent part of the ditCraft family being the ditCLI, a lot of time has been spent on improvements here. Special emphasis was put on the user experience, since we believe that a smooth UX is the key to establish the ditCLI as something that people actually <strong>like</strong> to use every day. This includes simple warnings when a user is about to delete an existing Ethereum key-pair during a setup of the CLI, but also an improved process of updating the CLIs’ config after an update of the CLI itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/793/1*r_Fs_-mHXUD_Jo892fHZZQ.png" /><figcaption>Users being warned when they might lose their Ethereum keys</figcaption></figure><p>Also, we increased the amount of information a user receives after a vote has been finalized. Now you will not only see whether a proposed commit has been accepted or not, but also how many validators have participated and the percentage of their votes. In addition to this, users may now easily switch between the <em>demo </em>and the <em>live </em>mode of the CLI. While the <em>demo</em> mode is essentially the same as the <em>live</em> mode, the staked currency and knowledge tokens (<em>KNW</em>) are just for testing purposes. Users may play around with the CLI and test its features there before moving to the <em>live</em> mode, where real xDai is being staked and real KNW are minted (<em>and potentially burnt</em>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-BSqEDQ3M6bdYftz56eKtA.png" /><figcaption>More detailed output after a vote has ended</figcaption></figure><h4>KYC — or Know-Your-Coder</h4><p>One of the biggest challenges and threats when designing the protocol behind ditCraft are Sybil attacks. With public and permission-less blockchains like Ethereum, it’s incredibly easy to create thousands of accounts on the matter of a second and participate in public protocols like the one we implemented.</p><p>To mitigate this, we came up with the idea of a <strong>KYC</strong>, which in our case stands for <strong>Know-Your-Coder</strong>. The idea is quite simple: we only allow users to use our ditCLI and smartcontracts after they have proven to be a legitimate person instead of a Sybil or fake bot account. Since Twitter is incredibly famous in the Ethereum community, we are starting of with a Twitter-based KYC. To do this, we wrote a Twitter bot, that is able to automatically handle these KYC requests.</p><p><strong>So how does it work?</strong></p><p>The user downloads the ditCLI and is being asked to perform the KYC by tweeting the CLIs’ generated Ethereum address like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*qjEK98tEdPVPo3jNKKRgpw.png" /><figcaption>Interaction during a KYC with our Twitter bot</figcaption></figure><p>Our Twitter bot then performs a KYC based on the users profile by taking the amount of followers, tweets and the accounts’ age into account. After the user passed this hurdle, the bot automatically enables the user to interact with our smartcontracts by adding their address to the list of authorized addresses.</p><h4>Future Smartcontract Upgrades</h4><p>While we didn’t change anything about the basic idea and concept of the smartcontracts and their logic, we did some improvements. The most important one being that we restructured them in order to be upgradeable. The idea behind our upgrade concept is actually quite simple: each contract has two additional address variables: <em>lastContract</em> and <em>nextContract</em>. Upon the first deployment (<em>v1</em>), these two variables are empty. If we now update the smartcontract or add new features to it, we deploy the new smartcontract to the network (<em>v2</em>) — but this time, the <em>lastContract</em> variable will be set to the address of the old contract (<em>v1</em>). This way, everyone who interacts with the new contract (<em>v2</em>) will know that there exists an older version of the contract, where previous information about votes can be obtained. Upon deployment of the new contract (<em>v2</em>), the variable nextContract in the old contract (<em>v1</em>) will be set to the one of the new contract (<em>v2</em>). This way, we can limit interaction (<em>namely the initiation of new votes</em>) with the old contract and CLIs who still try to reach the old contract may obtain the new address through this variable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*I6Pl-G9QmilPM9O3KhO_OA.png" /><figcaption>The upgradeContract function in one of our smartcontracts</figcaption></figure><p>Since publicly accessible functions in a smartcontract need to be secured in some way to prevent abuse, we introduced something called the <em>ditManager</em>. Only the <em>ditManager</em> is allowed to perform the upgrade of a smartcontract through the <em>upgradeContract(_addressOfNewContract)</em> function. While in the beginning the <em>ditManager</em> will be an address held be the ditCraft team, it is close to our heart to hand this control over to a smartcontract-based DAO such that the ditCraft community is able to vote on these upgrades to further decentralize the whole process.</p><h4>Deployment on xDai (PoA) Network</h4><p>With our recent update, we also deployed our smartcontracts to the <a href="https://poa.network/xdai">xDai network</a>, an Ethereum sidechain run by <a href="https://medium.com/u/c6dce655e286">POA Network</a> that uses xDai as its native token (<em>instead of ETH</em>). While we are big advocates of Ethereum and its mainchain, we believe that a faster blocktime and a stable gas price is something that dit immensely benefits from. We want our users to use the ditCLI on a regular basis, not just every couple of days to interact with an important vote. Nearly every commit to the master branch of a repository can be turned into a vote — but only if it’s quick and affordable. Even if the gas price stays as low as it is today on the Ethereum mainnet, our potential users would face a yearly cost of $70 to &gt;$250 USD, while also waiting at least 15 to 60 seconds for a transaction to go through. With the xDai network, we are able to cut that yearly estimated cost down to not even $0.40 USD, while transaction are confirmed in 5 seconds (<em>the blocktime of xDai</em>). To give you more of a concrete idea on how much cheaper it is, lets look at the following examples:</p><ul><li>Cost of a proposal on Ethereum Mainnet: $0.10 to $0.50 USD</li><li>Cost of a proposal on xDai: <strong>$0.0006 USD</strong></li><li>Cost of a vote on Ethereum Mainnet: $0.05 to $0.25 USD</li><li>Cost of a vote on xDai: <strong>$0.0003 USD</strong></li></ul><p>An additional benefit is the fact that xDai, being a representation of <a href="https://medium.com/u/743224aba00c">MakerDAO</a>s <a href="https://makerdao.com/">DAI</a>, is a stable coin that is pegged to the US dollar. One xDai is always worth one US dollar, instead of fluctuating like Ether. So even if you initiate a long vote through an important commit to the code, the amount that you staked in the beginning will still have the same value on the last day of the vote. This wouldn’t be possible with ETH.</p><h4>ditCraft webUI (ditExplorer)</h4><p>As you might have seen during our latest <a href="https://twitter.com/ditcraft/status/1121771062323236865">sneak peek on Twitter</a>, we are now working on a webUI. As this is still in early stage, we cannot really tell much about it, rather than just showing little screenshot. But stay tuned, the first version of the webUI might come sooner, rather than later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OnZs8NUdtk2LHYp6drtOSg.png" /><figcaption>Sneak peek of the new dit webUI</figcaption></figure><h4>Whats next?</h4><p>While we are quite happy with the current version of the ditCLI, it lacks the fine granularity of git commands that the native git command-line-client offers. This is what we are currently working on, namely integrating the native git library <a href="https://libgit2.org/"><em>libgit2</em></a><em> </em>into the CLI in the form of <a href="https://github.com/libgit2/git2go"><em>git2go</em></a>, since the ditCLI is written in Go.</p><p>In parallel, we are working in the first version of the webUI mentioned above. A first version where users are able to see their KNW balance in a web browser and search through the different proposals and votes will be released next.</p><h4>We need you!</h4><p>If you like the idea of dit, we highly encourage you to try the ditCLI, we are eagerly waiting for feedback. Just head over to our <a href="https://github.com/ditcraft/client">GitHub</a> and get right started. If you need help, just let us know on <a href="https://twitter.com/ditcraft">Twitter</a>, and we’ll help you out!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*2XbOSKiaoJZhMsLNaA2HvQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d67cb4d12a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ditcraft/pow-01-releasing-dit-v0-2-and-other-updates-5d67cb4d12a">PoW#01: Releasing ditCLI v0.2 and other Updates</a> was originally published in <a href="https://medium.com/ditcraft">ditCraft</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Verifiable Deployment of Smart Contracts]]></title>
            <link>https://medium.com/weeves-world/verifiable-deployment-of-smart-contracts-abc0bd82f4b9?source=rss-28ab8e733ade------2</link>
            <guid isPermaLink="false">https://medium.com/p/abc0bd82f4b9</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <dc:creator><![CDATA[Marvin Kruse]]></dc:creator>
            <pubDate>Wed, 09 May 2018 17:10:35 GMT</pubDate>
            <atom:updated>2018-06-07T08:18:38.923Z</atom:updated>
            <content:encoded><![CDATA[<p>In Solidity, there is the concept of a so-called <strong>factory. A factory</strong> is a smart contract that is able to deploy other smart contracts — contrary to the <em>“traditional”</em> way of deploying a smart contract all by yourself, without any other smart contracts being involved in the process. The concept of a factory gives way for many innovative and cool things to be built, with factories being used in various ways in projects that exist in the Ethereum space.</p><h4><strong>What’s so special about these factories?</strong></h4><p>The concept of factories is nothing new, but the way in which they are being used is constantly evolving. Currently, dynamic code factories are being used quite often, which is basically a smart contract with a function that is accepting a dynamically-sized byte array (this would be the bytecode of a compiled smart contract). This function will then deploy this code as a smart contract onto the blockchain.</p><p>These kind of factories are called dynamic since they are not limited to a single variant of a smart contract that can be deployed and they don’t even need to store the contracts bytecode for themselves before deploying it (which is good — we don’t want to clutter our dearest blockchain too much, do we?).</p><h4><strong>How does verified deployment come into play here?</strong></h4><p>Dynamic factories are a very convenient way of including libraries, saving gas and avoiding unnecessary data lying around on the blockchain — but we wanted to go one step further. Since the code that is being deployed through a dynamic factory is often stored off-chain and then included in a transaction, we can’t make use of the trustless nature of the blockchain in this case: we need to verify that the code that will be deployed is valid and trusted — <strong>otherwise a malicious network participant could easily spawn manipulated contracts leading to the loss of data and/or tokens</strong>.</p><p>What we call “verified deployment” is a verification method based on a hash of the contracts code, analogous to checksums. If you download a program from an alternative source in the internet you can make sure that this really is the original program through a hash-based checksum. The programs’ code will be hashed directly in the smart contract — and due to the deterministic nature of hashing and the trustworthy nature of computation on the Ethereum Virtual Machine the validity of the program can unquestionably be proven.</p><h4><strong>How is Weeve utilizing this?</strong></h4><p>The concept of a checksum-aided factory is being used in the <a href="https://weeve.network/">Weeve Network</a> as we are hashing the smart contracts code before deploying it to the blockchain through our factory. If the hash is valid (e.g. is contained in a constantly maintained list of “trustworthy” hashes of registry- or marketplace-variants) the corresponding smart contract will be deployed and activated through our factory. We implemented a specific initialisation-function in our registries and marketplaces that can only be called by its deploying factory. Only if this function was successfully called (by the factory) the corresponding registry or marketplace can be used and is active. This enables us to create a curated list of registries and marketplaces whose code is trustworthy and has been reviewed.</p><h4><strong>Explaining “verifiable deployment” with an example</strong></h4><p>To get more familiar with the concept of verifiable deployment let’s take the creation of a new registry for cars as an example:</p><ol><li>Alice wants to create a new registry for cars on the Weeve Network and selects the modules that she wants in her registry through our web interface</li><li>Supposing Alice has enough WEEV (Weeve token) staked as a collateral for her new registry, a transaction containing the parameters and the code of the new registry is sent to the weeveFactory contract</li><li>The weeveFactory hashes the contract code and checks whether this hash in contained in the list of trustworthy registry code-bases.</li><li>Supposing that this check succeeds and the code is valid, the weeveFactory then deploys and initialises the new new registry (while using the necessary libraries in the process)</li><li>The new registries’ address is stored in the weeveFactory and Alice is now able to use her new car registry according to her parameters</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u0lsddtdhOIqc3YXY5s4Pg.png" /><figcaption><em>An example of our factory deploying a new registry</em></figcaption></figure><h4><strong>How are the participants of the Weeve Network benefitting from this?</strong></h4><p>If you are accessing a curated list of marketplaces and registries you can be sure that the underlying code of them is working as intended. No-one has tampered with the code and there won’t be any hidden backdoors in the smart contract.</p><h4><strong>Is there already an implementation online?</strong></h4><p>We are hosting the Weeve Network’s code publicly on <a href="https://github.com/weeveiot/weeveNetwork">GitHub</a> since we think that especially in the world of smart contracts there shouldn’t be any secrets. Every smart contract that we are currently working on is on there, ready to be peer-reviewed!</p><p>Just go to our <a href="https://github.com/weeveiot/weeveNetwork">GitHub</a> and have a look for yourself. If you have any questions, suggestions or you just want to chat about the development itself feel free to head over to our <a href="https://gitter.im/weeveiot/weeveNetwork">gitter channel</a> — we really appreciate any feedback and discussion!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abc0bd82f4b9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/weeves-world/verifiable-deployment-of-smart-contracts-abc0bd82f4b9">Verifiable Deployment of Smart Contracts</a> was originally published in <a href="https://medium.com/weeves-world">weeve&#39;s World</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>