<?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 Consensys Diligence on Medium]]></title>
        <description><![CDATA[Stories by Consensys Diligence on Medium]]></description>
        <link>https://medium.com/@ConsenSysAudits?source=rss-d210fc95f79------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*q5TbCOhmnsL6RLrsJvlIiQ.png</url>
            <title>Stories by Consensys Diligence on Medium</title>
            <link>https://medium.com/@ConsenSysAudits?source=rss-d210fc95f79------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:27:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ConsenSysAudits/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[Building a Philosophy of Secure Smart Contracts]]></title>
            <link>https://medium.com/consensys-media/building-a-philosophy-of-secure-smart-contracts-1a2af03aa10?source=rss-d210fc95f79------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a2af03aa10</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Consensys Diligence]]></dc:creator>
            <pubDate>Wed, 22 Aug 2018 18:02:11 GMT</pubDate>
            <atom:updated>2019-01-24T14:34:59.228Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The philosophy of smart contract development, part 2. Part 1: </em><a href="https://media.consensys.net/the-mindset-of-a-smart-contract-developer-6bcf7b082411"><em>The Mindset of a Smart Contract Developer</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MPHlkSJ3svIZguDFo-Is4A.jpeg" /></figure><p>ConsenSys Diligence is a service that takes raw smart contract code and, using a specialized set of skills, locates potential vulnerabilities in the code, and gives recommendations for fixing them. This is toward the goal of the whole Ethereum ecosystem being better. Our long-term goal is to solve smart-contract security.</p><p>When I started working with ConsenSys Diligence I didn’t expect them to so fully live up to their name. <a href="https://media.consensys.net/the-mindset-of-a-smart-contract-developer-6bcf7b082411">Last week I wrote an article</a> about the stringent attitude a developer must take if s/he is to develop smart contracts correctly, and compared and contrasted this attitude to traditional software takes/mentalities. The point of this article was to demonstrate how a developer’s mindset must change if they are going to make the move to developing smart contracts from developing in traditional software frameworks.</p><p>One of the earliest audits we completed was the <a href="https://github.com/ConsenSys/0x-review">0x v. 1 audit</a> a little over one year ago. Although we’ve developed a more attractive user interface for our audit reports since then, (e.g. <a href="https://github.com/ConsenSys/Interactive-Crowdsale-Audit/blob/master/IICO-audit-report.md">the IICO audit</a>), this earlier report style is grittier and helps the reader sense what an audit is like and how the auditor is knee-deep in code for weeks at a time.</p><p>Audits are a messy business. You can’t perform a software audit without getting your hands dirty. You have to get into the mindset of the contract author and think like they think to anticipate what mistakes they might make in their contract code. This allows the auditor — playing the role of a malicious hacker — to find vulnerabilities the contract author would miss.</p><p>It also means understanding the code on a level that even the contract authors themselves might not. It means pulling out all the stops to do damage to this contract. This makes for a perfect setting to explain the mindset of a smart contract developer by showing examples of it in practice.</p><p>Many people think philosophies are useless unless they translate into action. I happen to agree. For that reason, let’s take a look at the <a href="https://github.com/ConsenSys/0x-review">0x v. 1 audit</a> to see how the higher-level philosophy I explained in my previous post played out empirically through the reports of the Diligence team.</p><p>The first thing you might notice when clicking on the 0x audit link posted above is the formality of it. This formality is important because our clients need to know exactly when their audit occurred, and exactly what it was supposed to cover.</p><p>It can be dangerous to add last-minute changes to the codebase of an audit, because a thorough software audit requires a body of code and several weeks to chart out all of the interactions between different parts of the code. This means it’s not possible to adequately review a new piece of code that is added to a contract in just a short amount of time. If the code makes function calls into several other parts of the contract (as last-minute code frequently does), then the complexity of the whole contract is increased, not just the extra piece of code.</p><p>But it’s not just dangerous to the client, it’s also dangerous to us. It’s dangerous to us because as the auditors of a contract, we are tasked with the expectation of finding any major vulnerabilities in the contract that they might have missed. This means if we fail to identify a vulnerability because of some extra code thrown in at the last minute, the consequences to our reputation will be nothing short of catastrophic. We stand not only to lose business, but also to lose the trust of the ecosystem. This realization takes us back to my previous article where I put some of our philosophy in the same style as The Zen of Python:</p><p><em>Safe is better than unsafe.<br>Boringness is better than notoriousness.<br>Constant is better than inconstant.<br>Straightforward is better than intricate.</em></p><p>All of these properties are a mindset we are required to take on in order to do our audits well. You can see how this is reflected in our request for clients to provide a single, complete contract that is deployed once, rather than bits of contracts deployed piecemeal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BWCQED7UNeEcJT3juT3JzA.jpeg" /></figure><p>Moving back to the 0x v. 1 audit. From the main page, click on the link that says:</p><p><strong>3 — General Findings<br></strong>You will notice right away the section that says:</p><p><strong>3.1 Critical<br></strong><em>ConsenSys Diligence found no general issues of critical severity during our review.</em></p><p>Every vulnerability in our report gets a severity rating from 1 to 4. The severity rating can be imagined to be saying: “If you publish this smart contract in its current state…”</p><blockquote><strong>1 = Critical</strong>; …some people will be able to take all your money and/or halt your contract (i.e. on the level of The DAO Hack, allowing tens of millions of dollars’ worth of ETH to be drained).</blockquote><blockquote><strong>2 = Major</strong>; …some people will be able to do annoying things that interfere with your business logic significantly.</blockquote><blockquote><strong>3 = Medium</strong>; …some people, if they’re smart enough, will be able to exploit vulnerabilities in the contract that may or may not lend them an advantage, just for fun. This will affect the smart contract, but is not likely to break it.</blockquote><blockquote><strong>4 = Minor</strong>; …this is not an actively exploitable issue, but it is something of note. Perhaps a best practice has been violated, or some other rule of thumb can be applied for best results, from a security perspective.</blockquote><p>You can imagine the sigh of relief you might breathe then when you get your audit report back and see it says:</p><p><em>ConsenSys Diligence found no general issues of critical severity during our review.</em></p><p>But to best see how ConsenSys Diligence adheres to and applies a consistent philosophy of mind behind our actions, skip down to the part of the review past the <strong>Medium</strong> and <strong>Major</strong> issues, and go right to the <strong>Minor</strong> ones. Minor issues would be easy to leave out of our report, because they don’t necessarily present a threat to security. But because we believe that safe is better than unsafe, we do not do this. We report on every last thing.</p><p>Philosophies aren’t always easy to apply. In fact, sometimes they can be downright difficult. But consistency is a strength in smart contracts, as well as humans, and we apply a consistent philosophy of smart contract development behind all our audits. This can be demonstrated by many of our audits, but the 0x audit is especially useful because it’s gritty and demonstrates a high-level of detail very early in the ecosystem, before we developed our more advanced user-interface for our audit reports and before <a href="https://consensys.net/diligence/">smart-contract auditing</a> was “cool” in the eyes of many people.</p><p>We find it a privilege to work with community members like those of the 0x team, and look forward to auditing many more contracts from other members and groups in the community as time goes on. <em>Interested in having your smart contract audited? For a free readiness assessment, e-mail your request to diligence@consensys.net.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F13e0a7%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F13e0a7%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/eb70db0a21c4e8715b29a5306af17d39/href">https://medium.com/media/eb70db0a21c4e8715b29a5306af17d39/href</a></iframe><p><em>Disclaimer: The views expressed by the author above do not necessarily represent the views of Consensys AG. ConsenSys is a decentralized community with </em><a href="https://medium.com/consensys-media"><em>ConsenSys Media</em></a><em> being a platform for members to freely express their diverse ideas and perspectives. To learn more about ConsenSys and Ethereum, </em><a href="https://consensys.net/"><em>please visit our website.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a2af03aa10" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consensys-media/building-a-philosophy-of-secure-smart-contracts-1a2af03aa10">Building a Philosophy of Secure Smart Contracts</a> was originally published in <a href="https://medium.com/consensys-media">ConsenSys Media</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Audit the Deployed Smart Contract, Not Github!]]></title>
            <link>https://medium.com/consensys-media/audit-the-deployed-smart-contract-not-github-16082b2fcb1b?source=rss-d210fc95f79------2</link>
            <guid isPermaLink="false">https://medium.com/p/16082b2fcb1b</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <dc:creator><![CDATA[Consensys Diligence]]></dc:creator>
            <pubDate>Wed, 13 Dec 2017 20:53:01 GMT</pubDate>
            <atom:updated>2019-01-24T14:32:23.845Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://consensys.net/diligence/"><em>Audits on a smart contract</em></a><em> should be performed on a release candidate (RC), which should be deployed on mainnet before an audit is performed.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*pydVG-8s5wz7br0E_QULzg.jpeg" /></figure><p>Suppose Mallory is looking to have her smart contract audited so she gives <a href="https://en.wikipedia.org/wiki/Alice_and_Bob">Bob</a>, her auditor, some git hash, or (gasp!) a zip file of the source code. Mallory has taken care to follow the <a href="https://medium.com/@matthewdif/towards-responsible-token-sales-icos-291e69cc9ccf">first rule of a responsible token sale</a> by implementing a staggered release of funds and vesting contracts. Bob clones the repo, audits and reports issues, checks the fixes, and proclaims the audit is completed. Mallory announces the audit results, launches her ICO, and collects millions. The next day, however, all the funds, which were supposedly locked, have been sent to mysterious addresses and Mallory is never to be found again. A simple post-mortem finds that the smart contract Mallory deployed had a subtle backdoor that was added to the source code Bob had audited.</p><p>In a software release life cycle, a <a href="https://en.wikipedia.org/wiki/Software_release_life_cycle#Release_candidate">release candidate</a> (RC) is the final stage before software is launched. To minimize <a href="https://medium.com/the-ethereum-name-service/security-lessons-from-the-ens-launch-c5bc96bf439e#6cb8">code churn</a>, an audit should be performed on an RC. An RC does not change, and it eventually <em>becomes the release itself</em>, unless there are <a href="https://en.wikipedia.org/wiki/Showstopper">showstopper</a> bugs, which then get fixed and another RC is generated. Historically, an RC is managed by a <a href="https://en.wikipedia.org/wiki/Version_control">version control</a> system, but where does a smart contract RC belong? On the blockchain!</p><p>An auditor&#39;s responsibility to the community should include ensuring that what they audit is what is released to the community to use. Auditors can audit the RC that&#39;s actually on the blockchain, not some malleable code on Github that might get deployed. Auditors should ask their clients for the Ethereum mainnet addresses of the RC contracts. The community should request that bug bounty programs refer to Ethereum mainnet addresses. This methodology has four main benefits. Though we&#39;ll be speaking in terms of a single smart contract, the methodology is also applicable to a system of smart contracts.</p><p><strong>Four Benefits</strong></p><p>First, auditing the deployed smart contract eliminates scenarios where the audited source code is accidentally or maliciously changed then deployed to mainnet. The smart contract is already on mainnet and its code cannot be changed.</p><p>Second, using a mainnet address <strong>signifies readiness</strong> for an audit and reduces code churn. Let&#39;s take Alice, who thinks her code is ready for an audit. Is it really ready? Or is there one more change or tweak left? Not having a mainnet address suggests that the contract isn&#39;t quite ready. By actually deploying the contract, Alice makes a distinct decision that the code is as ready as can be at that point in time. Even though it only costs $1 to pay the gas for deploying her contracts, Alice is unlikely to make code commits and redeploy several times. Bob is relieved because he can&#39;t audit a moving target.</p><p>Third, by actually deploying the contracts to mainnet, Alice <strong>increases her readiness</strong> for launch. In the ideal case that there are no showstoppers, the RC becomes the release and Alice can simply announce her launch! Note that before a mainnet deploy, any respectable development team will have addressed security as early as possible in development and have done rigorous testing, including testnets.</p><p>Fourth, <strong>ecosystem synergies</strong> can emerge. Since Bob has audited a contract with an address, he can have a registry of all the contracts he&#39;s audited. Charlie, another auditor can have a uPort attestation to Bob&#39;s registry as well as his own registry. User interfaces can be built in which someone can input an address and see who&#39;s audited the contract. Tools like MetaMask and Etherscan can tap into these, and further creative tools and DApps can leverage the ecosystem and expand it.</p><p><strong>How the audit process might look</strong></p><ol><li>Alice deploys her wallet contract and gets the address 0x851b7f3ab81bd8df354f0d7640efcd7288553419.</li><li>Alice uploads and verifies her source code on etherscan.</li><li>Bob gets the source code at <a href="https://etherscan.io/address/0x851b7f3ab81bd8df354f0d7640efcd7288553419#code">https://etherscan.io/address/0x851b7f3ab81bd8df354f0d7640efcd7288553419#code</a>.</li><li>Bob runs <a href="https://www.npmjs.com/package/eth-bytecode-verifier">verifier</a> to ensure that the source code compiled bytecode matches the bytecode on the blockchain.</li><li>Bob audits the source code (splitting it into smaller pieces if it helps him).</li><li>Alice makes required fixes and repeats the process (typically only one more loop). The process can end immediately here if it&#39;s deemed that there are no showstoppers that need to be fixed.</li></ol><p><strong>Verifying the source code from the blockchain</strong></p><p>Perhaps people have been trusting contract source code on Etherscan too much. Alex Luoyuan has built a tool to help verify that the deployed bytecode at a given address matches the compiled output from source code:</p><p><a href="https://www.npmjs.com/package/eth-bytecode-verifier">https://www.npmjs.com/package/eth-bytecode-verifier</a></p><p>Source code verification is only available on Etherscan for now, but stay tuned for further developments. Infura has plans for mainnet verification and currently has the following testnet:</p><p><a href="https://explorer.infuranet.io/contract/verify">https://explorer.infuranet.io/contract/verify</a>.</p><p><strong>Smart Contract Design</strong></p><p>Alice may need to design or refactor her contract to support at least two states:</p><ol><li>ContractDeployed</li><li>ContractReady</li></ol><p>For example, if Alice had a token sale contract that started as soon as it was deployed, it would need to be modified so that auditors, bug bounty programs, and the public could examine the contract while it is in a ContractDeployed state and before the sale has commenced. The act of launching would then involve sending a transaction to configure and transition the contract to a ContractReady state where the token sale can accept contributions.</p><p>In practice, we don&#39;t really see such contracts that support two states breaking the functionality of the contract. If there are exceptions, they can be examined. Also, less interactive contracts such as a wallet don&#39;t need to necessarily support two states.</p><p><strong>What do you think?</strong></p><p>Auditing deployed smart contracts is the closest thing to auditing what users will actually interact with. If you&#39;re an auditor, ask your clients for their mainnet contract addresses: it will save everyone time, make the audit process more secure, and help tap into ecosystem synergies. Learnings from this methodology will be described in a future post.</p><p><em>-JosephC. Thanks to Maurelian, Gonçalo Sá, Alex Luoyuan, Eva Shon, and Bernhard Mueller for providing feedback on this article.</em></p><p><em>If you have a knack for diving deeply into Solidity and the EVM, and an interest in smart contract security, we’re looking for people to join </em><a href="https://media.consensys.net/introducing-consensys-diligence-cf38f83948c"><em>ConsenSys Diligence</em></a><em> (</em><a href="https://consensys.net/open-positions/?gh_jid=609611"><em>apply here</em></a><em>). This post is an extension of </em><a href="https://media.consensys.net/preparing-for-a-smart-contract-code-audit-83691200cb9c"><em>Preparing for a Smart Contract Code Audit</em></a><em> and part of a series on </em><a href="https://media.consensys.net/designing-safer-smart-contracts-d8389ba10d81"><em>Designing Safer Smart Contracts</em></a><em>.</em></p><p><em>If you made it this far in the post, but don’t meet the exact criteria in the job description, that’s OK. Just include a message mentioning this post, and calling out your experience with, and interest in Ethereum.</em></p><blockquote>Disclaimer: The views expressed by the author above do not necessarily represent the views of Consensys AG. ConsenSys is a decentralized community with <a href="https://medium.com/consensys-media">ConsenSys Media</a> being a platform for members to freely express their diverse ideas and perspectives. To learn more about ConsenSys and Ethereum, <a href="https://consensys.net/">please visit our website.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16082b2fcb1b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consensys-media/audit-the-deployed-smart-contract-not-github-16082b2fcb1b">Audit the Deployed Smart Contract, Not Github!</a> was originally published in <a href="https://medium.com/consensys-media">ConsenSys Media</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing ConsenSys Diligence]]></title>
            <link>https://medium.com/consensys-media/introducing-consensys-diligence-cf38f83948c?source=rss-d210fc95f79------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf38f83948c</guid>
            <category><![CDATA[token-sale]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Consensys Diligence]]></dc:creator>
            <pubDate>Fri, 30 Jun 2017 14:15:04 GMT</pubDate>
            <atom:updated>2019-01-24T00:30:34.672Z</atom:updated>
            <content:encoded><![CDATA[<h4>Raising the bar for <a href="https://consensys.net/diligence/">security best practices in the Ethereum ecosystem</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rZuoPyu8k4SwPhoM1j2OAg.jpeg" /></figure><p>The Ethereum blockchain is skyrocketing in popularity. Last month, Fred Wilson of Union Square Ventures <a href="https://www.youtube.com/watch?v=2wyC9AEUoYI">predicted</a> that the market cap of Ethereum will surpass Bitcoin’s in 2017, and The New York Times’ Dealbook <a href="https://www.nytimes.com/2017/06/19/business/dealbook/ethereum-bitcoin-digital-currency.html">seems to agree with him</a>. In addition to increasing awareness of the <a href="https://entethalliance.org/">Enterprise Ethereum Alliance</a> and capabilities of smart contracts on the Ethereum platform, <a href="https://medium.com/@balajis/thoughts-on-tokens-436109aabcbe">token</a> launches are attracting <a href="https://qz.com/1004892/the-bancor-ico-just-raised-153-million-on-ethereum-in-three-hours/">higher</a> and <a href="https://www.inc.com/brian-d-evans/status-ico-raised-over-100-million-for-ethereum-powered-dapps-on-ios-and-androi.html">higher</a> amounts of money. Developers want to capitalize on this movement by getting their tokens out as quickly as possible, and they feel immense pressure to quickly write and deploy contracts. <br> <br>The paradoxical outcome is that<strong> the stakes are higher, but people are becoming less cautious.</strong><br> <br>Let’s not forget the lessons learned from ‘<a href="https://media.consensys.net/the-dao-heist-faq-ef95a7f310f0">The DAO</a>’. In the wake of the June 2016 exploit, developers turned their attention toward security and <a href="https://github.com/ConsenSys/smart-contract-best-practices">best practices</a> for smart contract development. And yet, it seems that as time passes, the painful memory of The DAO is beginning to fade. <br> <br>To usher in the new era of decentralized innovation, we need people to participate in the ecosystem — a lot of people. And we need their optimism to work for them, not against them. We need the community to help each other and watch out for each other. That’s why we created ConsenSys Diligence.</p><h3>ConsenSys Diligence: Raising the bar for security best practices in the Ethereum ecosystem</h3><p><strong>ConsenSys Diligence </strong>is committed to improving the Ethereum ecosystem by promoting technical excellence, security best practices, legal precautions, and ethical business practices. <br> <br>Currently we are working with specific high-impact projects as they prepare to deploy their contract systems. We encourage projects to launch when <a href="https://medium.com/@billgleim/shaping-crowdfund-rollout-readiness-at-weifund-e79198cc4e7f">ready</a>, rather than trying to time markets. Our criteria for readiness extends beyond a basic code review, to include requirements for specifications, test drivers, static analysis, and staged roll outs. <br> <br>This approach is informed by our experience working with clients like <a href="https://gnosis.pm/">Gnosis</a>, <a href="http://weifund.io/">WeiFund</a>, <a href="https://singulardtv.com/">SingularDTV</a>,<a href="https://www.uport.me/"> uPort</a>, and <a href="https://adchain.com/">adChain</a>. ConsenSys Diligence is also actively involved in writing and reviewing code deployed in production systems on private chains at some of the largest Fortune 500 companies in the world. <br> <br>In the future, we plan to expand these services to include assessment of legal structures and business cases. We’ll look beyond the white paper, into the fundamentals of the business plan, team, and code behind a project.<br> <br>As a part of ConsenSys, <strong>our incentives are aligned with the long-term health of the ecosystem rather than short-term revenue. </strong>The ecosystem will always be our priority — over potential clients, business practices, and revenues. When there is a conflict between what a client desires and what’s good for the ecosystem, we side with the ecosystem. When we discover code or actions that are not improving the ecosystem and community, our priority is to inform the community about them.</p><h3>Want to work with us?</h3><h4>Projects:</h4><p>Were looking to work with clients who:</p><ul><li>Display a long-term planning horizon and vision</li><li>Are willing to prioritize readiness over a sense of urgency</li><li>Have a project with potential to make a significant impact on the ecosystem</li><li>Have a history of contributions to the community</li></ul><p>If this sounds like you, please feel free to reach out to us at <a href="/service/mailto:diligence@consensys.net">diligence@consensys.net</a>.</p><h4>Prospective Teammates:</h4><p>We are also looking to expand our team. If you have deep knowledge about Solidity and the Ethereum Virtual Machine, a passion for security, and the self-motivation to work on what you think is most valuable to the ecosystem, we’d <a href="https://consensys.net/open-positions/?gh_jid=609611">love to meet you</a>. <br> <br>For all developers interested in the conversation, please stop by the Smart Contract Best Practices <a href="https://gitter.im/ConsenSys/smart-contract-best-practices">Gitter channel</a>.</p><p><strong><em>Like this piece? Sign up </em></strong><a href="http://consensys.us11.list-manage.com/subscribe?u=947c9b18fc27e0b00fc2ad055&amp;id=257df01285"><strong><em>here</em></strong></a><strong><em> for our weekly newsletter.</em></strong></p><blockquote>Disclaimer: The views expressed by the author above do not necessarily represent the views of Consensys AG. ConsenSys is a decentralized community with <a href="https://medium.com/consensys-media">ConsenSys Media</a> being a platform for members to freely express their diverse ideas and perspectives. To learn more about ConsenSys and Ethereum, <a href="https://consensys.net/">please visit our website.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf38f83948c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consensys-media/introducing-consensys-diligence-cf38f83948c">Introducing ConsenSys Diligence</a> was originally published in <a href="https://medium.com/consensys-media">ConsenSys Media</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>