<?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 Richard Meissner on Medium]]></title>
        <description><![CDATA[Stories by Richard Meissner on Medium]]></description>
        <link>https://medium.com/@richard_93619?source=rss-704a41d408d3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*TvvVtMomYC9Bwr97.</url>
            <title>Stories by Richard Meissner on Medium</title>
            <link>https://medium.com/@richard_93619?source=rss-704a41d408d3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 10:12:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@richard_93619/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[The Impact of Phishing on Web 3.0]]></title>
            <link>https://medium.com/gnosis-pm/the-impact-of-phishing-on-web-3-0-a62385c81310?source=rss-704a41d408d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/a62385c81310</guid>
            <category><![CDATA[multisig-wallet]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[multisignature]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[gnosis-safe]]></category>
            <dc:creator><![CDATA[Richard Meissner]]></dc:creator>
            <pubDate>Fri, 13 Mar 2020 12:07:36 GMT</pubDate>
            <atom:updated>2020-03-17T16:27:03.497Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to keep your smart wallets safe</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uP2ulco2aX6GF9O788gSXA.png" /></figure><p>Phishing has always been an easy way to trick users into exposing private information. There are many recommendations¹ on how to avoid these tricks, but usually these suggestions protect against known attacks for web 2.0 — not web 3.0.</p><p>In actuality, with web 3.0, best practices against phishing become even more critical than ever before. When the user trusts a malicious website, it is the next worst thing after getting their private keys compromised. When a user starts out using a DeFi app, it usually requires a token approval call, meaning a confirmation that a target contract in the app can make use of an unlimited amount of a specific token in the user’s wallet. If the user does not verify what address is used for the approval, their funds might be at risk.</p><p>Most wallets decode these standard contract interactions, such as the token approval call. MetaMask even allows you to adjust the token approval amount to avoid that you approve an unlimited amount of funds. However, smart contracts are very flexible and not every contract interaction can be decoded. When you add smart contract wallets such as the Gnosis Safe into the mix, this becomes even more complex.</p><p>A recent <a href="https://blog.openzeppelin.com/backdooring-gnosis-safe-multisig-wallets/">blog post by OpenZeppelin</a> mentions just such a scenario, where a malicious website is used to deploy a misconfigured Gnosis Safe. The data used to trigger this deployment is extremely complex. Without using more technical tools, it is nearly impossible to understand what is going on. The following is the hex data for a simple Gnosis Safe with 3 owners. For technical users, it might be possible to understand the data partially, but this is not feasible nor desirable for an average user.</p><pre>0x61b69abd00000000000000000000000034cfac646f301356faa8b21e94227e3583fe3f5f000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000001a4b63e800d0000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000180000000000000000000000000d5d82b6addc9027b22dca772aa68d5d74cdbdf440000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000dcbeffbecce100cce9e4b153c4e15cb88564319300000000000000000000000032565cd5562a4f10462cbfc27d126d365a74634c0000000000000000000000009c28f1bb95d7e7fe88e6e8458d53be127cc2dc4f000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</pre><p>To avoid this scenario, you should employ the same best practices against phishing that you normally would with web 2.0 applications, such as online banking, and be sure to check URLs and security certificates. We also strongly recommend that you only use trusted interfaces that perform additional offline checks and manage deployments and integrations. An example of this would be using the canonical Gnosis Safe mobile application available in app stores.</p><p>However, as mentioned in the OpenZeppelin blog post, we felt that this approach is a limited way to access a trusted Gnosis Safe instance. <strong>That’s why we deployed a simple </strong><a href="https://github.com/gnosis/safe-contracts/issues/175"><strong>Safe factory</strong></a><strong>² to fix this for users.</strong> This factory creates a Safe (Version 1.1.1) with one owner, being the account that triggered the transaction. And the only thing that the user needs to do is to send a transaction to the factory address 0x1337A824F3131c718b7a336E18CADb4BA0faffFc. If you send some ETH along with the transaction, it will be deposited to your newly created Safe. To be sure that you use the correct factory, check the Identicon and the address, or simply use the ENS name <strong>factory.safe.eth</strong>, which will always point to the secure factory for the latest version. <strong>A tutorial at the end of this post goes over how to do this in just a few easy steps.</strong></p><p>Please be aware that a trusted Gnosis Safe setup is only the first step in securing your account against phishing. You need to make sure that you closely pay attention to every transaction performed with your Safe. For this, we recommend using our web app <a href="http://www.gnosis-safe.io/app/">www.gnosis-safe.io/app/</a>. There you can easily create and review transactions, as well as check your current Safe configuration, such as owners and required signatures.</p><p>Transaction decoding is an important topic within the Ethereum development ecosystem, and there are many interesting, related initiatives. Here are some recommendations to learn more:</p><ul><li><a href="https://medium.com/@chriseth/closing-the-trust-gap-part-1-590a0765ac9d">https://medium.com/@chriseth/closing-the-trust-gap-part-1-590a0765ac9d</a></li><li><a href="https://medium.com/@chriseth/closing-the-trust-gap-part-2-86c974cfd1ae">https://medium.com/@chriseth/closing-the-trust-gap-part-2-86c974cfd1ae</a></li></ul><h3>Factory Contracts Release</h3><p><a href="https://github.com/gnosis/safe-factories/releases/tag/v1.1.1">https://github.com/gnosis/safe-factories/releases/tag/v1.1.1</a></p><p><strong>Identicon (visual ID) and address info:</strong></p><ul><li>Blockies Identicon and address of factory: 0x1337…ffFc</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/0*Ow_KAUhAXnzxd09Q" /></figure><ul><li>MetaMask Identicon and address of factory: 0x1337…ffFc</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/0*i5IclQFhhGn9a2J2" /></figure><p><strong>Contract Interaction:</strong> The Safe factory is at the target address given above, but no data is required.</p><p><strong>0.1 ETH:</strong> Initial amount of funds that should be sent to the new Safe on creation.</p><h3>Tutorial for Creating a New Safe… Extra Safely</h3><ol><li>Send a transaction to 0x1337A824F3131c718b7a336E18CADb4BA0faffFc.</li></ol><ul><li>Enter no Hex Data: the field should stay empty.</li><li><em>Optional: </em>The amount can be used to fund the newly created Safe.</li><li>The gas limit should be around 380K.</li><li>Choose a gas price or accept what gas price your wallet suggests.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/0*ChyqIf2YjBYz6MzA" /></figure><p>2. Check the Identicon, address, and transaction details.</p><ul><li>The address should start with 0x1337 and end with ffFc.</li><li>The Identicon should look like the examples given in the previous section.</li><li>The amount should correspond to the amount of funds you would like to send to your new Safe.</li><li>Fees should be slightly higher than the amount (depends on gas price and gas limit).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/0*U93UFnFzgVCLiDx4" /></figure><p>3. Confirm transaction and wait for it to be confirmed.</p><ul><li>Review the transaction on Etherscan.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7v4gla6Ntu527L8c" /></figure><p>4. On Etherscan, double check the event logs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*erAKZfIziD7zjS9D" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t7qwzhZUG94qRy6q" /></figure><p>5. Finally, inspect your created Safe (proxy) and navigate to <a href="https://gnosis-safe.io/app">https://gnosis-safe.io/app</a>.</p><h4>Footnotes</h4><p>[1]: <a href="https://www.consumer.ftc.gov/articles/how-recognize-and-avoid-phishing-scams">https://www.consumer.ftc.gov/articles/how-recognize-and-avoid-phishing-scams</a><br><a href="https://www.phishing.org/10-ways-to-avoid-phishing-scams">https://www.phishing.org/10-ways-to-avoid-phishing-scams</a><br>[2]: <a href="https://github.com/gnosis/safe-factories">https://github.com/gnosis/safe-factories</a><br><a href="https://github.com/gnosis/safe-contracts/issues/175">https://github.com/gnosis/safe-contracts/issues/175</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a62385c81310" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gnosis-pm/the-impact-of-phishing-on-web-3-0-a62385c81310">The Impact of Phishing on Web 3.0</a> was originally published in <a href="https://medium.com/gnosis-pm">GnosisDAO</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Formal Verification of the Gnosis Safe Contracts]]></title>
            <link>https://medium.com/gnosis-pm/formal-verification-of-the-gnosis-safe-contracts-faca6664950?source=rss-704a41d408d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/faca6664950</guid>
            <category><![CDATA[formal-verification]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[gnosis-safe]]></category>
            <category><![CDATA[wallet]]></category>
            <category><![CDATA[mobile-wallets]]></category>
            <dc:creator><![CDATA[Richard Meissner]]></dc:creator>
            <pubDate>Fri, 30 Nov 2018 13:05:34 GMT</pubDate>
            <atom:updated>2018-11-30T13:05:34.138Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JMtXgZtuyobroo84hCtykg.png" /></figure><h4>An Update to the Mainnet Release</h4><p>This week, we released the Mainnet version of the Gnosis Safe for Android, and we received quite a lot of feedback and questions. One of the most important questions that we’d like to address here relates to security:</p><h4><strong>How does Gnosis ensure that there are no bugs in the deployed contracts, considering the issues with the Parity multi-sig wallet earlier in 2018?</strong></h4><p>At Gnosis, <strong>we only consider a version production-ready if we have done an external audit or a formal verification of the smart contract code</strong>. For this Safe Mainnet release, we have taken the following security measures:</p><p>An external audit was performed on <a href="https://github.com/gnosis/safe-contracts/blob/v0.0.1/docs/alexey_audit.md">version 0.0.1</a> of the Safe contracts and <strong>the formal verification for the current version (0.1.0) is in progress</strong>. The biggest changes that have been made between versions 0.0.1 and 0.1.0 are the following:</p><ul><li><a href="https://github.com/ethereum/EIPs/blob/master/EIPS/eip-712.md">Used EIP-712 to generate the signatures for signed messages</a></li><li><a href="https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1271.md">Added support for EIP-1271 signatures</a></li><li>Upgrade to Solidity 0.5.0</li></ul><p>Unfortunately, the upgrade to Solidity 0.5.0 delayed the formal verification of the Safe’s current version (0.1.0), but the first results can already be seen. You can follow progress at: <a href="https://github.com/runtimeverification/verified-smart-contracts/tree/master/gnosis">https://github.com/runtimeverification/verified-smart-contracts/tree/master/gnosis</a>.</p><p>Due to the ongoing formal verification, we decided to not mark the contracts as a 1.x version, but as a 0.1.x version. This is not properly reflected in the store entries of the mobile app and browser extension. For this reason, we decided to make this more explicit in the title of the Play Store entries by changing the app’s name to “Gnosis Safe — Mainnet Beta.” We have also added more details on the formal verification progress to the Play Store app description.</p><p>We want to gather early feedback from everyone and encourage the usage of the Safe. Going forward, we will provide detailed documentation on the release process and share it with everyone. <strong>Part of this process will include that the smart contracts will be published and verified on Mainnet before they will be available through mobile app stores</strong>. Additionally, an audit or formal verification will be performed for every update to the contracts.</p><h3>Stefan George on Twitter</h3><p>1/3 Security Advice: @gnosisSafe is still a beta product and should be used with caution. Don&#39;t move all your funds before we do! Contracts were audited by @realLedgerwatch. Based on the audit changes were done and reviewed internally.</p><p><em>Follow us on </em><a href="https://twitter.com/gnosisSafe"><em>Twitter</em></a><em> and </em><a href="https://blog.gnosis.pm/tagged/safe"><em>Medium</em></a><em> to stay on top of our latest updates. We also very much welcome feedback from the community, so please do get in touch via our brand new </em><a href="https://chat.gnosis.pm/"><em>Riot chat</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=faca6664950" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gnosis-pm/formal-verification-of-the-gnosis-safe-contracts-faca6664950">Formal Verification of the Gnosis Safe Contracts</a> was originally published in <a href="https://medium.com/gnosis-pm">GnosisDAO</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>