<?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 Alejandro Diaz on Medium]]></title>
        <description><![CDATA[Stories by Alejandro Diaz on Medium]]></description>
        <link>https://medium.com/@alejandrodiaz_71295?source=rss-eaaf9a2a9e1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_ZchbKDkW2iDDZkN666CtQ.png</url>
            <title>Stories by Alejandro Diaz on Medium</title>
            <link>https://medium.com/@alejandrodiaz_71295?source=rss-eaaf9a2a9e1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:40:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alejandrodiaz_71295/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[Announcing Turms MAD Stores: A 
Completely Decentralized, Anonymous Marketplace Using Ethereum…]]></title>
            <link>https://medium.com/coinmonks/announcing-turms-mad-stores-a-completely-decentralized-anonymous-marketplace-using-ethereum-738c58e72ccd?source=rss-eaaf9a2a9e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/738c58e72ccd</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[cryptocurrency-news]]></category>
            <category><![CDATA[anonymous]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Alejandro Diaz]]></dc:creator>
            <pubDate>Wed, 24 Jul 2019 20:53:49 GMT</pubDate>
            <atom:updated>2020-08-26T12:29:01.898Z</atom:updated>
            <content:encoded><![CDATA[<h3>Announcing Turms MAD Stores: A <br>Completely Decentralized, Anonymous Marketplace Using Ethereum Smart Contracts</h3><p>I’ve been working on MAD Stores for over a year. It’s a completely decentralized online marketplace, with no backend server at all. I’m pleased to announce that I have a proof-of-concept version ready for testing on the Ropsten testnet. You can view all the source code on <a href="https://github.com/AlejandroDiaz666/mad-stores">github</a>. The contracts are also published on etherscan.io <a href="https://ropsten.etherscan.io/address/0x19626b86bac95a5f6671f91b51dbf6dc08f9266f#code">here</a> and <a href="https://ropsten.etherscan.io/address/0x2195b7ff79b24806a239747cf21a95d455966d7d#code">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gSYy0s-rF1A3lwxY_oFZow.png" /></figure><h4>About MAD Stores</h4><p>MAD Stores is an online marketplace like ebay or Amazon, but it’s completely decentralized — so there’s no central authority managing, supervising or controlling the marketplace. Another difference between ebay and MAD Stores is that sellers can remain anonymous, or at least pseudonymous; that is, buyers and sellers are only known by their Ethereum addresses (or ENS names). All communications between buyers and sellers is via <a href="https://medium.com/@ananyaagarwal_42559/turms-anonymous-message-transport-step-by-step-9729ce829697">Turms Anonymous Message Transport</a>. <br> <br>The obvious question about a decentralized, anonymous marketplace is how do we stop cheaters from ripping people off, since there’s no central authority to keep people in line or to resolve disputes — You might not even have any contact information for the other party (other than their Ethereum address, which you use to send messages via Turms Anonymous Message Transport). <br> <br>The answer is <em>MAD Escrow</em></p><h4>MAD Escrow</h4><p>MAD stands for Mutually Assured Destruction. In every purchase transaction both parties place a bond into escrow. If either party cheats, then both parties lose their deposits! <br> <br>When you purchase an item in MAD Stores you will deposit 150% of the price into an escrow account. Automatically, the seller will also deposit a bond into the escrow account, equal to 50% of the purchase price. All funds are released from the MAD Escrow when the buyer confirms satisfactory delivery of the product. If the product was not as advertised, or if it was not delivered, then the buyer and seller are encouraged to communicate, using Turms Anonymous Message Transport, to work out a satisfactory resolution. In case no resolution can be reached, the buyer has the option to “burn” the escrow. That is, to destroy all the funds that are held in the Escrow. <br> <br>There’s much more to say about how MAD Stores works, and about all the edge cases that can crop up in real-life usage. I’ll be releasing a much more in-depth article to cover these topics. But for now, I encourage anyone interested to jump in and try it out on the Ropsten testnet. (The DApp includes an introduction and FAQ).</p><h4>How To Try It Out!</h4><p>MAD Stores is released for testing on the Ropsten testnet. To try it out follow these steps:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/983/1*EnpLe8TWRHmBAfzwTlNGsA.png" /><figcaption>Set Metamask to use the Ropsten testnet</figcaption></figure><ol><li><strong>Set MetaMask to use the Ropsten testnet</strong>:<br>Ropsten testnet Ether is free. It is specifically for testing DApps without using expensive real ETH. To enable MetaMask to use the Ropsten testnet, click at the top of the MetaMask dialog box where it says Main Ethereum Network and select Ropsten Test Network.</li><li><strong>Get some Ropsten test ether</strong>:<br>Just go to <a href="https://faucet.ropsten.be/">https://faucet.ropsten.be/</a> and enter your Ethereum address. Or you can go to <a href="https://faucet.metamask.io/">https://faucet.metamask.io</a>, and click on the<br> request 1 ether from faucet button. Wait a few seconds and then open the MetaMask dialog box to confirm that you’ve received your test ETH.</li><li><strong>Create a Turms AMT account on the <em>Ropsten version</em> of Turms AMT</strong>:<br>I created a version of Turms Anonymous Message Transport that works on the Ropsten testnet. Even if you’re already using Turms AMT on the Ethereum Mainnet, you’ll need to create a new account on the Ropsten version. This will be just for testing MAD Stores. You can access the Ropsten version on IPFS, for example at:<br><a href="https://cloudflare-ipfs.com/ipns/ropsten.messagetransport.turmsanonymous.io/">cloudflare-ipfs.com/ipns/ropsten.messagetransport.turmsanonymous.io/</a><br> or<br><a href="https://ipfs.io/ipns/ropsten.messagetransport.turmsanonymous.io/">ipfs.io/ipns/ropsten.messagetransport.turmsanonymous.io/</a><br>Make sure MetaMask is unlocked and set to the Ropsten testnet.</li><li><strong>Get some Ropsten </strong><a href="https://github.com/bokkypoobah/WeenusTokenFaucet"><strong><em>Weenus</em></strong></a><strong> tokens</strong>:<br>When the real MAD Stores is released on the Ethereum Mainnet, it will price everything in <a href="https://makerdao.com/en/">Maker</a> DAI; but for the purpose of testing on Ropsten we’re using Weenus in place of DAI. In the DApp your Weenus balance will be displayed as a DAI balance. To get 1000 Weenus just send zero Ropsten ETH to the <a href="https://ropsten.etherscan.io/address/0x101848D5C5bBca18E6b4431eEdF6B95E9ADF82FA#code">Weenus Token Contract</a>. (You can read more about Weenus <a href="https://github.com/bokkypoobah/WeenusTokenFaucet">here</a>. By the way, hearty hat tip to BokkyPooBah for making Weenus!)</li><li><strong>Fire up the MAD Stores DApp</strong>:<br>The MAD Stores DApp is on IPFS, for example at:<br><a href="https://cloudflare-ipfs.com/ipns/ropsten.madstores.turmsanonymous.io/">cloudflare-ipfs.com/ipns/ropsten.madstores.turmsanonymous.io/</a><br> or<br><a href="https://ipfs.io/ipns/ropsten.madstores.turmsanonymous.io/">ipfs.io/ipns/ropsten.madstores.turmsanonymous.io/</a><br>There’s a nice little intro at the beginning that will get you started. Feel free to purchase any items that you see for sale — they won’t actually be delivered — because this is just make-believe for testing purposes. Or you can create your own store selling any sort of make-believe products you can think of.</li><li>Send your comments to me! <br>MAD Stores is still under development. If you have questions or suggestions please send them to me via Turms AMT at imontoya.eth, or by email to Alejandro.Diaz.666@protonmail.com. Be sure to provide your Ethereum address because we’ll be awarding 1,000 Turms Tokens for the 10 best comments.</li></ol><h4>Summary</h4><p>Decentralized commerce is the killer DApp for Ethereum. Turms MAD Stores is still in testing, and we need some input from the Ethereum community, but it’s poised to be one of the most real-world-useful DApps ever made. Please give it a try and contribute your suggestions!</p><p>Alejandro Diaz</p><blockquote><a href="https://coincodecap.com/?utm_source=coinmonks">Get Best Software Deals Directly In Your Inbox</a></blockquote><figure><a href="https://coincodecap.com/?utm_source=coinmonks"><img alt="" src="https://cdn-images-1.medium.com/max/584/0*OJ-qb5G6i863msBB.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=738c58e72ccd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinmonks/announcing-turms-mad-stores-a-completely-decentralized-anonymous-marketplace-using-ethereum-738c58e72ccd">Announcing Turms MAD Stores: A 
Completely Decentralized, Anonymous Marketplace Using Ethereum…</a> was originally published in <a href="https://medium.com/coinmonks">Coinmonks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Perfect Forward Secrecy in Turms Anonymous Message Transport]]></title>
            <link>https://medium.com/coinmonks/perfect-forward-secrecy-in-turms-anonymous-message-transport-f770527992bd?source=rss-eaaf9a2a9e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f770527992bd</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[messaging]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Alejandro Diaz]]></dc:creator>
            <pubDate>Wed, 12 Jun 2019 09:12:48 GMT</pubDate>
            <atom:updated>2020-08-26T12:52:12.487Z</atom:updated>
            <content:encoded><![CDATA[<p>Turms AMT (Anonymous Message Transport) is a peer-to-peer messaging system for sending encrypted messages between Ethereum addresses (See <a href="https://medium.com/@alejandrodiaz_71295/introducing-turms-anonymous-message-transport-2e40b31dbdc2?source=friends_link&amp;sk=1cdec02ea57b2fd0bb66d5e711d0a256">Introducing Turms Anonymous Message Transport</a>).</p><p>Encrypted messaging on a public, un-encrypted blockchain is a challenge. So in this article I’m going to explain how we did it in Turms AMT.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*-IE3iiP4UWsoy5OgAxjd8w.jpeg" /></figure><p>We had the following encryption goals in Turms AMT:</p><ul><li>Both the sender and receiver should be able to decrypt messages with the same key — a key that only they can derive.</li><li>The key derivation must not require a “handshake”; that is, it needs to work even when one side is offline.</li><li>The encryption technology should encompass “perfect forward secrecy”; that is, the key to decrypt one message should be unable to decrypt any future messages.</li><li>encrypted messages should be un-hackable with modern, state of the art hardware.</li></ul><h4>Perfect Forward Secrecy</h4><p><em>Perfect Forward Secrecy</em> is the idea that a decryption key changes with every message — so that even if a decryption key for one message is compromised, it only facilitates decrypting a single message (and not an entire thread of messages). This is particularly useful for Turms AMT: We imagined that people would use Turms AMT to store important messages on the blockchain, like enforceable contracts or financial obligations; And, at some point people might want to reveal the contents of one of those messages to a third party, for example to prove what was sent. Perfect Forward Secrecy would make it possible to share the encryption key of one message while still keeping all other messages secure — even messages from the same Turms account.</p><h4>A Mouthful</h4><p>To achieve our encryption goals we settled on using a sort of Diffie-Hellman-Merkle key exchange between the sender and receiver to generate a PMK (Pairwise-Master-Key); and then hash a nonce (a value updated with each message) together with the PMK to generate a PTK (Pairwise Temporal Key), which is used to AES encrypt each message.</p><p>That’s a mouthful!</p><p>I promise I’ll break it all down more simply in the coming paragraphs.</p><h4>Basic Encryption Concepts</h4><p>In an encrypted communication a <em>plain-text</em> message is encoded, using an encryption-key, into a <em>cipher-text</em> message that can only be decoded using a decryption-key. There are many different encoding/decoding algorithms, called ciphers. But broadly speaking ciphers can be classified as either symmetrical, meaning that the encryption-key is the same as the decryption-key, or asymmetrical, meaning that the two keys are different. In the case of asymmetrical encryption each side of the communication actually has a <em>key-pair</em>; that is, two keys that work together, one public and one private. A message that is encrypted with the public-key can only be decrypted with the private-key, and vice-versa. Each side of the encrypted channel shares its public key, which is used by the other side to encrypt messages before sending them. Upon receiving an encrypted message each side uses its private key, which is never shared, to decrypt the message.</p><h4>The Key Distribution Problem</h4><p>It’s not enough for an encryption cipher to make a conversation opaque to nefarious eavesdroppers who do not posses the appropriate decryption keys. There’s an additional problem, known as the “Key Distribution Problem”, which is how to get the decryption key to the intended recipient of the message in such a way that it can’t be intercepted by a third party. The Key Distribution Problem is not such an issue when using asymmetrical encryption — each side only gives out its public encyrption key. So assuming that you know that the public key really belongs to the other endpoint, you can encrypt messages, secure in the knowledge that only the holder of the corresponding private key is able to decrypt the cipher text.</p><p>But when using symmetrical encryption, the key that encrypts a message is the same key that is used to decrypt it. In that case there’s a very real problem of getting the endpoints to agree on what key to use, in a way that prevents a third party, who could be monitoring the key negotiations, from learning the key. This problem is analogous to me wanting to send you a treasure, but not trusting the mailman. I can send the treasure locked in a box; but how can I send you the key to the lock in such a way that the mailman can’t make a copy of it?</p><h4>Diffie-Hellman-Merkle key exchange</h4><p>Diffie-Hellman-Merkle key exchange is a clever system of negotiating private keys, such that even if a nefarious third party is able to observe the <em>entire </em>negotiation (because it’s on the public blockchain), they still can’t acquire the negotiated symmetrical keys! The Diffie-Hellman protocol relies on a mathematical one-way function:</p><pre>f(g,s,p) = g^s % p</pre><p>In the formula above the hat is the exponentiation operator, and the percent is the <em>modulo</em> operator; that is, the formula means “raise <strong>g</strong> to the power <strong>s</strong>, and then find the <em>remainder</em> when you divide by <strong>p</strong>.</p><p>In this context we call the function one-way because, even if you know <strong>g</strong> and <strong>p</strong>, and also know the result, (<strong>g</strong>^<strong>s</strong> % <strong>p</strong>), it is still not possible to derive <strong>s</strong>. The reason is that exponentiation and division operations are very fast in modern computers, even for crazy-large numbers. But knowing the <em>remainder</em> of a division doesn’t tell you what the dividend was, even if you know the divisor; and checking <em>every possible</em> divisor (<strong>g</strong>^<strong>s</strong>) can be prohibitively time-consuming. For a typical example, <strong>g</strong> will be set to 2, <strong>s</strong> will be a secret number and <strong>p</strong> will be a known prime number. Both <strong>s</strong> and <strong>p</strong> are 2,048 bits, which is pretty huge. But with <strong>s</strong> being a 2048 bit number, <strong>g</strong>^<strong>s</strong> is super huge (for comparison, consider that there are only about 2²⁵⁶ atoms in the universe).</p><h4>The Key Derivation</h4><p>In a Diffie-Hellman-Merkle key exchange, <strong>s</strong> is a secret that is never revealed. But it is not the encryption key. Each side (side a and side b) has their own secret, <strong>s</strong> — we’ll call them <strong>sa</strong> and <strong>sb</strong>. And each side computes their own <em>public</em> key, <strong>fa</strong> and <strong>fb</strong> as shown below, using their secret, and predefined values of <strong>g</strong> and <strong>p</strong>:</p><pre>fa = (g^sa) % p<br>fb = (g^sb) % p</pre><p>Each side announces their public keys (<strong>fa</strong> and <strong>fb</strong>), <em>in the open</em>! To compute the private key, which will be known only to the two sides, each side uses the same one-way function, but this time replaces <strong>g</strong> with the public key that was announced by the other side:</p><pre>key(a) = (fb^sa)%p = ([(g^sb)%p] ^ sa) % p<br>key(b) = (fa^sb)%p = ([(g^sa)%p] ^ sb) % p</pre><p>Because of a wonderful theorem of modular mathematics, it turns out that key(a) will be equal to key(b). That is to say, swapping the order of the exponentiation operations doesn’t change the final result.</p><h4>Diffie-Hellman-Merkle key exchange In Turms AMT</h4><p>We start by generating a super private <em>key-encryption-key</em>. This is a 256 bit symmetrical key that will never be saved on your computer, and never be transmitted anywhere, to anyone. This is the key that is derived from the Keccak signature that you generate whenever you start Turms AMT.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*i6NlL9vEG0C7Wc2mb3cDTA.png" /></figure><p>Note that no one else has the ability to generate your super private key-encryption-key. To do so they would need to be able to forge your Keccak signature — and if they could do that, then the security of the entire Ethereum blockchain could be compromised — so the point is: <em>they can’t</em>.</p><p>But 256 bits is not enough to create a future-proof, secure Diffie-Hellman secret. So when you register your Ethereum address with Turms Anonymous Message Transport, we generate a random 2048 bit Diffie-Hellman secret, <strong>s</strong>. We use the super secret key-encryption-key to encrypt that secret, and store the encrypted secret on the blockchain. Also when you register your Turms AMT account, we generate a Diffie Hellman public key, (<strong>g</strong>^<strong>s</strong>) % <strong>p</strong>, and store that on the blockchain (unencrypted), in the Turms AMT smart contract.</p><p>Whenever you start Turms AMT we read your encrypted secret from the the blockchain, and decrypt it using your super secret key-encryption-key. That’s how you get <strong>s</strong>.</p><p>When you want to encrypt or decrypt a message to/from another address you first compute a PMK (Pairwise Master Key), which is unique to the combination of your address and the other address. You compute this using the Diffie-Hellman technique: you have your own Diffie-Hellman secret, <strong>s</strong>, and the other side’s Diffie-Hellman public key, which was stored in the Turms AMT smart contract. So now both you and the other side compute the same key, which is the PMK; But neither of you will ever use the PMK to actually encyrpt or decrypt anything — and you certainly never send it anywhere or save it.</p><p>Instead, you use the PMK to compute a PTK (Pairwise Transient Key), which is only used to encrypt/decrypt a single message. You compute the PTK by creating a hash of the PMK and your Ethereum address, and the other side’s Ethereum address, and the number of messages that have been sent from the sending side. For every message received you both compute the same PTK, which can be used to both encrypt and decrypt one message. This is how we achieve “Perfect Forward Secrecy” — even if the PTK used to encrypt one message was somehow hacked, or intentionally revealed — it would still be impossible to decrypt any of the other messages that were sent between the same two parties.</p><h4>Limitations</h4><p>In strict Perfect Forward Secrecy it’s necessary for the sender and receiver to use new values of <strong>p</strong> and <strong>g</strong> for every “session”. But this is not practical in Turms AMT, because of the fact that there is no handshake between the sender and receiver. This added security of strict Perfect Forward Secrecy only makes sense if there are multiple “sessions”, since it protects one session even when the PMK of a different session is exposed. The <em>Perfect Forward Secrecy</em> that Turms AMT implements only protects a message when the <em>PTK</em> of a different message is exposed. This is in line with the intended goal of being able to expose the PTK of an individual message without compromising any others. This limitation underscores the importance of keeping your Ethereum private key secure.</p><h4>Summary</h4><p>Turms AMT lets you send encrypted messages between Ethereum address. It’s released now on ipfs:<br> <a href="https://cloudflare-ipfs.com/ipns/messagetransport.turmsanonymous.io/">https://cloudflare-ipfs.com/ipns/messagetransport.turmsanonymous.io/</a><br>or<br> <a href="https://ipfs.io/ipns/messagetransport.turmsanonymous.io/">https://ipfs.io/ipns/messagetransport.turmsanonymous.io/</a><br>Go ahead and send me a message — My Ethereum address is imontoya.eth and I’d love to hear from you!</p><p>Alejandro Diaz</p><blockquote><a href="https://coincodecap.com/?utm_source=coinmonks">Get Best Software Deals Directly In Your Inbox</a></blockquote><figure><a href="https://coincodecap.com/?utm_source=coinmonks"><img alt="" src="https://cdn-images-1.medium.com/max/584/0*OJ-qb5G6i863msBB.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f770527992bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinmonks/perfect-forward-secrecy-in-turms-anonymous-message-transport-f770527992bd">Perfect Forward Secrecy in Turms Anonymous Message Transport</a> was originally published in <a href="https://medium.com/coinmonks">Coinmonks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bulk Mailer for Turms Anonymous Message Transport]]></title>
            <link>https://medium.com/coinmonks/bulk-mailer-for-turms-anonymous-message-transport-6370aa823544?source=rss-eaaf9a2a9e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6370aa823544</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[messaging]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[advertising]]></category>
            <dc:creator><![CDATA[Alejandro Diaz]]></dc:creator>
            <pubDate>Thu, 23 May 2019 00:44:29 GMT</pubDate>
            <atom:updated>2020-09-20T20:18:30.421Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*4QGOxf1OdyJT7vnOCJLSaA.jpeg" /></figure><p><a href="https://medium.com/@alejandrodiaz_71295/introducing-turms-anonymous-message-transport-2e40b31dbdc2?source=friends_link&amp;sk=1cdec02ea57b2fd0bb66d5e711d0a256">Turms AMT</a> (Anonymous Message Transport) is a peer-to-peer messaging system for sending messages between Ethereum addresses. For now there’s only one reason to use it: <strong><em>it pays you Ether for receiving spam!</em></strong></p><p>There are going to be some incredible DApps that are going to be built on Turms AMT. But they don’t exist yet. And in the meantime it’s pretty tough to get people to try out a new messaging system. So for now the reason to try it is that it pays you a <em>little</em> bit of Ether each time you receive a message — a little more than the gas you’ll spend when you execute the register-transaction.</p><p>That’s why introducing the bulk-mailer is important — because it’s the first step in getting marketers to send advertisements (spam) to people who have registered with Turms AMT.</p><p>The bulk-mailer is a DApp. Here’s how it looks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tef4MEkn7tfAhnNF2ZAKpA.png" /></figure><h4>Notes:</h4><ul><li>The bulk mailer uses the same contracts as Turms AMT</li><li>The contracts were audited by Solidified</li><li>All Turms messages are peer-to-peer encrypted</li><li>When you register your Ethereum address you can limit the amount of spam you receive by setting a high “spam fee”</li><li>The system is completely decentralized<br> —It is based on a simple Ethereum smart contract<br> —By default messages are stored on the Ethereum blockchain<br> —Optionally messages can be stored on Swarm<br> —There is no backend server</li><li>The bulk-mailer code is all open source, on <a href="https://github.com/AlejandroDiaz666/bulk-mailer">github</a></li></ul><h4>Bulk-Mailer Not Hosted</h4><p>In order to avoid having to sign each transaction individually for each recipient, the bulk-mailer requires you to enter an Ethereum private key. This is different than the <a href="https://ipfs.io/ipns/messagetransport.turmsanonymous.io/">Turms AMT DApp</a>, which uses MetaMask to send messages, so it never asks you to enter a private key. Of course your private key is never transmitted or saved. But it’s poor form for any website to ask you to enter a private key. Because of this, the bulk-mailer is not hosted on any website — you need to run it in a sand-boxed environment on your own computer.</p><h4>High Quality Spam?</h4><p>It’s worth noting that Turms AMT spam will probably be of higher quality than typical email spam. The reason is simple: since senders need to pay for every message, they’re going to think twice about sending throw-away messages. At any rate, if you decide that you’re getting too many messages, just increase your spam fee to 1000 Ether.</p><h4>Register Now</h4><p>Now that there’s a bulk-mailer, I expect that within the next few weeks a couple of intrepid marketers will begin sending out advertisements (aka. spam) — to all Ethereum addresses that have registered with Turms AMT — and the spam-fees will begin to trickle in. If you have an Ethereum address and haven’t registered yet, go to the <a href="https://ipfs.io/ipns/messagetransport.turmsanonymous.io/">Turms AMT Dapp </a>— it only costs a few pennies in gas fees — and you’ll more than make that up in spam fees that you’ll collect.</p><p>You can find links and articles about Turms on the <a href="https://diazgonewild.com/">Alex Diaz un-website</a>.</p><p>Alejandro Diaz</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6370aa823544" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinmonks/bulk-mailer-for-turms-anonymous-message-transport-6370aa823544">Bulk Mailer for Turms Anonymous Message Transport</a> was originally published in <a href="https://medium.com/coinmonks">Coinmonks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decentralization, the Heart of Crypto]]></title>
            <link>https://medium.com/coinmonks/decentralization-the-heart-of-crypto-708763b2b31c?source=rss-eaaf9a2a9e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/708763b2b31c</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[messaging]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[decentralization]]></category>
            <dc:creator><![CDATA[Alejandro Diaz]]></dc:creator>
            <pubDate>Tue, 14 May 2019 08:07:33 GMT</pubDate>
            <atom:updated>2020-08-26T13:17:53.039Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the last few years Ethereum has brought us hundreds of Decentralized <br>Applications, or DApp’s — And more are introduced to us every few days. <br>Let’s take a moment to review the anatomy of a DApp, and why DApp’s are so <br>important.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*Tf9Zbphw0kNBkTPwsdgU6w.jpeg" /></figure><h4>The What</h4><p>A DApp is an application that is not controlled by a central authority. That <br>is to say, it operates based on a program or a set of egalitarian rules that cannot be changed by any authoritarian individual or bureaucracy. The whole point of decentralization is to eliminate the need to trust an individual management entity.</p><p>As a trivial example, think of the difference between two childhood games: In Musical Chairs there was always an adult, who was in charge of starting and stopping the record player (Yes, I’m dating myself), and who would settle any arguments when two kids sat on a chair simultaneously. Although the adult was <em>involved</em> with the game, she was not an equal participant.</p><p>This created a very different dynamic between the kids compared to, for example “Tag” — in Tag there was some rule for selecting the next searcher, (“not it!”), and the same rules applied to <em>everybody</em>. Everyone involved was an equal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*3ybmWKlJyn7mAa61U5AM3w.jpeg" /></figure><p>This feature is more important than you might appreciate at first. Think of <br>all the times in human history in which monarchs, dictators, heads of state, <br>or corporations have set up unfair (sometimes <em>unknown</em>) rules. When our institutions give way to DApps we are taking another step towards egalitarian justice.</p><h4>The How of Decentralization</h4><p>Crypto-currencies, like Bitcoin and Ethereum are probably the most accessible examples of DApps. They operate based on strict rules, and are not controlled by any privileged management team or authority. Note, this is not to say that different players can’t play different roles. I’ll never “mine a block” on the Bitcoin blockchain; and I might never generate an “EIP”, or Ethereum <br>Improvement Proposal to the Ethereum core developers. The point is that <br>the rules are the same for everyone (the Bitcoin protocol) — there is nothing <br>in the system preventing me, or thousands of people from all around the world, from doing those things.</p><h4>Anatomy of a DApp</h4><p>The typical architecture for a DApp is very simple:</p><ul><li>Business logic is coded in an Ethereum smart contract. The source code for the contract must be published — this is critical to ensure that the rules of the system are fair; that is, the author didn’t sneakily reserve some special privileges for themselves.</li><li>A user interface for interacting with the smart contract.</li></ul><p>The user interface must:</p><ol><li>Be open source:<br>This is so that users can verify that the code does what it is purported to do, and nothing else.</li><li>Run entirely on the user’s computer and be verifiable:<br>Code that runs on a back-end server is a black-box…. There’s no way to know what it’s actually doing. So most DApp front-ends are written in javascript. One of the reasons is that you can press &lt;control-shift-i&gt; in your browser to see the actual source code that is executing. Of course only a minority of people will <em>actually</em> check the code that is running, but in most cases that’s enough — if there’s anything amiss it only takes one person to sound the alarm. There are ways that make the code even more verifiable, which I’ll get to shortly.</li><li>Not be “hosted” on a centralized server. <br>This is important for several reasons. Firstly for reliability and censorship resistance, since any single server or small cluster of servers can fail, or can be censored. But more importantly, when a website comprising a DApp’s user interface is hosted on a centralized server, the content can be modified willy-nilly. If on the other hand the DApp program is hosted on a decentralized, distributed system, like IPFS or Swarm, then the content is uniquely identified by a hash that would change if even one line of the <br>program was tampered with.</li></ol><p>The foregoing is the prototypical architecture for a DApp. However there are also more elaborate models, for example Distributed Autonomous Organizations, or DAO’s, in which specific players take the traditional “management” roles. The essential feature remains the same — the management roles must be open to everyone, because the system does not give privileges to any one person or group above any other.</p><h4>My Dapps, My Pledge</h4><p>In case you haven’t guessed yet, I write DApps. I also frequently check out DApps written by other individuals and groups. I always consider it a red flag when a new DApp doesn’t make it explicitly clear how it is decentralized. It’s not a good sign when I can’t tell if a system uses a back-end server even after reading the whitepaper.</p><p>All of the DApps I write are 100% decentralized. I put together a little website at <a href="https://diazgonewild.com/">diazgonewild.com</a> for links and articles about those DApps. My most recent DApp is <a href="https://ipfs.io/ipns/messagetransport.turmsanonymous.io">Turms Anonymous Message Transport</a>, which provides truly decentralized messaging between Ethereum accounts. Like my other projects it is open source on <a href="https://github.com/AlejandroDiaz666/message-transport">github</a>; anyone can rebuild the user interface from source, and see that the git tag, which is embedded in the code matches the git tag on the version that is hosted on IPFS (shown in the options panel below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/1*4Y_lThcUKPp92uLlGZCOlw.png" /></figure><p>I made <a href="https://ipfs.io/ipns/messagetransport.turmsanonymous.io">Turms Anonymous Message Transport</a> to lay the groundwork for another DApp that I’m working on right now. If you like my direction, then please check it out.</p><p>Demand decentralization my friends! <br>Alejandro Diaz</p><blockquote><a href="https://coincodecap.com/?utm_source=coinmonks">Get Best Software Deals Directly In Your Inbox</a></blockquote><figure><a href="https://coincodecap.com/?utm_source=coinmonks"><img alt="" src="https://cdn-images-1.medium.com/max/584/0*OJ-qb5G6i863msBB.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=708763b2b31c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinmonks/decentralization-the-heart-of-crypto-708763b2b31c">Decentralization, the Heart of Crypto</a> was originally published in <a href="https://medium.com/coinmonks">Coinmonks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Information Website for Turms Anonymous Message Transport]]></title>
            <link>https://medium.com/@alejandrodiaz_71295/information-website-for-turms-anonymous-message-transport-8496b8dfc0b9?source=rss-eaaf9a2a9e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/8496b8dfc0b9</guid>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[dapps]]></category>
            <dc:creator><![CDATA[Alejandro Diaz]]></dc:creator>
            <pubDate>Fri, 10 May 2019 05:55:34 GMT</pubDate>
            <atom:updated>2019-05-10T05:55:34.786Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*VXSOa8SEA_omEBkJJO_g3Q.png" /></figure><p>I put together a <a href="https://diazgonewild.com/">website</a> for all the projects that I’ve worked on this year. In particular this will be a place for me to put documents relating to Turms AMT. With an alarming lack of modesty, I call the site <a href="https://diazgonewild.com/">diazgonewild.com</a>.</p><h4>Two New Turms AMT Documents</h4><p>There are two heretofore unpublished documents on diazgonewild.com: <a href="https://diazgonewild.com/doc/message_transport_whitepaper-v1.pdf">Turms AMT Whitepaper</a> and <a href="https://diazgonewild.com/doc/message_transport_faq.pdf">Turms AMT FAQ</a>.</p><h4>Other Projects</h4><p>Turms Anonymous Message Transport, which is a <strong>100% decentralized solution for sending encrypted messages between Ethereum addresses</strong>, is my preeminent project. But the website also has links and information for my other 100% decentralized projects, including the Pirate Lottery, and a Front-end for Christian Lundkvist’s Simple Multisig Wallet.</p><h4>More Projects Planned</h4><p>I’m hard at work building new DApps. It is my hope that having a single repository for articles and links to my projects will help people to discover them.</p><p>Alejandro Diaz</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8496b8dfc0b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turms Anonymous Message Transport — Now Using Swarm]]></title>
            <link>https://medium.com/coinmonks/turms-anonymous-message-transport-now-using-swarm-b447e0cd76f2?source=rss-eaaf9a2a9e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b447e0cd76f2</guid>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[ethereum-news]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Alejandro Diaz]]></dc:creator>
            <pubDate>Mon, 06 May 2019 07:27:11 GMT</pubDate>
            <atom:updated>2020-08-26T13:21:11.664Z</atom:updated>
            <content:encoded><![CDATA[<h3>Turms Anonymous Message Transport — Now Using Swarm</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/485/1*g_CwhW40dVrL4RZsZqTwqg.png" /></figure><p>I write DApps. But the most compelling DApps I could imagine needed a messaging system that could be integrated into smart contracts — and for all the impressive Ethereum development work, I couldn’t find a contract-integrate-able messaging system.</p><p>So I wrote Turms AMT (Anonymous Message Transport). It’s a peer-to-peer, fully encrypted, pseudonymous messaging system based on the Ethereum blockchain (See <a href="https://medium.com/@alejandrodiaz_71295/introducing-turms-anonymous-message-transport-2e40b31dbdc2?source=friends_link&amp;sk=1cdec02ea57b2fd0bb66d5e711d0a256">Introducing Turms Anonymous Message Transport</a>). In the initial release of Turms AMT all messages were stored on the Ethereum blockchain as event logs. I chose this approach because:</p><ol><li>It was the simplest technique with the fewest “moving parts;” that is, the Ethereum blockchain is mature, stable, and represents the lowest risk in terms of breaking developments.</li><li>The DApps that I was envisioning would require guaranteed persistence for message storage — I was thinking about a blockchain-based marketplace for high-value transactions — and currently other decentralized storage solutions don’t have guaranteed persistence.</li><li>Using event logs to store data isn’t prohibitively expensive for the applications I envisioned, which would pass much less data than a general-purpose mail system. (Note: storing data in an event log consumes much less gas than storing it in the state trie.)</li></ol><p>But since introducing Turms AMT I realized that enabling optional <a href="https://swarm-gateways.net/bzz:/theswarm.eth/">Swarm</a> storage of message-data would open it up new application possibilities. Today I’m happy to announce that this feature is available in Turms AMT Version 1.4+.</p><p>Enabling Swarm storage of message-data provides the following benefits:</p><ul><li>Sending large messages is much cheaper when the data is stored on swarm. That’s because no matter the size of the message you only need to store the Swarm hash (32 bytes) on the blockchain.</li><li>The maximum size of a message stored on Swarm is governed by the Swarm-gateway-imposed limit. For swarm-gateways.net this is about ten times greater that the maximum amount of data that can be stored as an Ethereum event log.</li></ul><p>Of course when you store a message on Swarm you lose the guarantee of persistence, so it’s not be appropriate for all applications (such as the decentralized commerce DApp, which I’m working on now).</p><p>To enable Swarm storage in Turms AMT just open the ‘options panel’:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*jvUVaByuv5bt0yX4NDm_Ag.png" /></figure><p>In the drop-down selector labeled ‘Select message storage’ you have three options:</p><ol><li>The default is to store all message data as Ethereum event logs.</li><li>Your second option is to store all message data on Swarm</li><li>Lastly, you can choose to store any messages that have attachments on Swarm, and all other messages as Event logs.</li></ol><p>Whenever you choose to save message data on Swarm you’ll have the opportunity to specify a gateway:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/363/1*BFfx8g9BDMD1Yl3jrygqzQ.png" /></figure><p>Turms AMT is still slower than email; and it’s still more expensive; and less user-friendly. But now with the ability to store message data either on the Ethereum blockchain or on Swarm, I expect it will find plenty of applications (including the aforementioned commerce DApp).</p><p>Turms AMT is encrypted, peer-to-peer, completely 100% decentralized, accessible to smart-contracts, and pseudonymous — Your Ethereum address is your recipient address. You can try it out at:</p><p><a href="https://ipfs.io/ipns/messagetransport.turmsanonymous.io/">https://ipfs.io/ipns/messagetransport.turmsanonymous.io/</a></p><p><a href="https://ipfs.io/ipns/messagetransport.turmsanonymous.io/">Turms Anonymous Message Transport</a></p><p>Alejandro Diaz</p><blockquote><a href="https://coincodecap.com/?utm_source=coinmonks">Get Best Software Deals Directly In Your Inbox</a></blockquote><figure><a href="https://coincodecap.com/?utm_source=coinmonks"><img alt="" src="https://cdn-images-1.medium.com/max/584/0*OJ-qb5G6i863msBB.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b447e0cd76f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinmonks/turms-anonymous-message-transport-now-using-swarm-b447e0cd76f2">Turms Anonymous Message Transport — Now Using Swarm</a> was originally published in <a href="https://medium.com/coinmonks">Coinmonks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Four Applications of Turms
Anonymous Message Transport]]></title>
            <link>https://medium.com/coinmonks/four-applications-of-turms-anonymous-message-transport-9505d9ba2388?source=rss-eaaf9a2a9e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9505d9ba2388</guid>
            <category><![CDATA[messaging]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[dapps]]></category>
            <dc:creator><![CDATA[Alejandro Diaz]]></dc:creator>
            <pubDate>Mon, 22 Apr 2019 15:28:14 GMT</pubDate>
            <atom:updated>2020-08-26T13:36:00.577Z</atom:updated>
            <content:encoded><![CDATA[<p>Turms AMT (Anonymous Message Transport) is a peer-to-peer messaging system based on the Ethereum blockchain (See <a href="https://medium.com/@alejandrodiaz_71295/introducing-turms-anonymous-message-transport-2e40b31dbdc2?source=friends_link&amp;sk=1cdec02ea57b2fd0bb66d5e711d0a256">Introducing Turms Anonymous Message Transport</a>). It’s expensive and slow — so it’s not a replacement for email. But it is <em>important — </em>It facilitates direct encrypted messaging between Ethereum addresses.</p><p>To spark your imagination, here are four applications that can be built using Turms AMT:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*Xbx2nzo5J8rxOrWpehe3-w.jpeg" /></figure><h4>1. Simple Online Digital Product Sales</h4><p>Ethereum should be the natural currency for online sales of gift cards, video unlock codes, or any other digital products. With Turms AMT it can be incredibly easy to make an automated delivery system:</p><ul><li>Monitor an Ethereum address for payments — a different address for each product.</li><li>For each payment received, send the digital product via a Turms message to the originating address.</li></ul><p>This sort of online store would be <em>totally anonymous</em> — You wouldn’t even need to provide an email address. How cool would that be?</p><h4>2. Communications with ICO Investors</h4><p>Some people bemoan the fact that unregulated ICO’s are able to sell tokens to “unqualified,” anonymous investors. Personally I appreciate the caveat’ emptor stance — I believe that people should be free to invest in a venture anonymously, without getting “permission” from some government entity. Turms AMT makes it possible to send a message to an ICO investor<br>when the only thing you know about them is their Ethereum address.</p><h4>3. Crypto Commerce</h4><p>Commerce is the acid-test of a currency. With a couple of clever smart-contracts, Ethereum can facilitate a unique form of crypto-commerce, similar to Ebay or Amazon, but <em>completely</em> decentralized. A project like this requires an encrypted messaging system <em>between Ethereum addresses</em>, to place orders and to communicate order status. And that system should be as anonymous, secure, and persistent as Ethereum itself. Sneak-peek: I’m already working on a decentralized crypto-commerce solution based on Turms AMT — Fasten your seat belts… it’s coming!</p><h4>4. Efficient Advertising</h4><p>Everyone hates spam… It wastes our time. Companies send out millions of advertising emails, just to catch a few people who are actually interested in their message. But Turms AMT is a different sort of messaging system, because the recipient gets <em>paid</em> to receive messages — and it will lead to a different advertising model.</p><p>When you register your Ethereum address with Turms AMT you set a parameter called a “spam fee.” It’s the amount of Ether that <em>you</em> want to be paid whenever someone sends you spam. Set the fee according to how much spam you <em>want</em> to receive.</p><p>Turms AMT makes it possible for an advertising agency to target their messages to people who have indicated their openness to receiving “spam” (for a fee). In turn, you can earn some Ether, just by reading advertisements now and then.</p><h4>In Conclusion</h4><p>Turms Anonymous Message Transport is a simple system — but it brings anonymous encrypted messaging to Ethereum. It’s Completely decentralized and it works <em>now</em>. Applications are coming…</p><p>Try it at:<br><a href="https://ipfs.io/ipns/messagetransport.turmsanonymous.io/">https://ipfs.io/ipns/messagetransport.turmsanonymous.io/</a></p><p>Alejandro Diaz</p><blockquote><a href="https://coincodecap.com/?utm_source=coinmonks">Get Best Software Deals Directly In Your Inbox</a></blockquote><figure><a href="https://coincodecap.com/?utm_source=coinmonks"><img alt="" src="https://cdn-images-1.medium.com/max/584/0*OJ-qb5G6i863msBB.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9505d9ba2388" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinmonks/four-applications-of-turms-anonymous-message-transport-9505d9ba2388">Four Applications of Turms
Anonymous Message Transport</a> was originally published in <a href="https://medium.com/coinmonks">Coinmonks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Turms Anonymous
Message Transport]]></title>
            <link>https://medium.com/@alejandrodiaz_71295/introducing-turms-anonymous-message-transport-2e40b31dbdc2?source=rss-eaaf9a2a9e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e40b31dbdc2</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[ethereum-news]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[messaging]]></category>
            <dc:creator><![CDATA[Alejandro Diaz]]></dc:creator>
            <pubDate>Tue, 16 Apr 2019 01:16:57 GMT</pubDate>
            <atom:updated>2019-06-11T06:23:16.233Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*d1h0WimkTc2hr20ciOFRiA.jpeg" /></figure><p>Turms AMT (Anonymous Message Transport) is a peer-to-peer messaging system built on an Ethereum smart contract. Its most important properties are:</p><ul><li>Your Ethereum address is your messaging address</li><li>All messages are encrypted</li><li>The system is completely decentralized:<br>◦ It is based on a simple Ethereum <a href="https://etherscan.io/address/0x6a973275f5bccfe0c7309c9934d7f945c3138dfd#code">smart contract</a><br>◦ All messages are stored on the Ethereum blockchain<br>◦ There is no backend server<br>◦ The front-end (user interface) is hosted on IPFS</li><li>The code is all open source<br><a href="https://github.com/AlejandroDiaz666/message-transport">https://github.com/AlejandroDiaz666/message-transport</a></li></ul><p>In addition to the foregoing, Turms AMT has the following notable features:</p><ul><li>Sending a message incurs either a “spam fee” or a “message fee.”<br>◦ 70% of the spam/message fee is paid to the recipient of the message.<br>◦ 15% of the spam/message fee is paid to Turms token holders.<br>◦ 15% of the spam/message fee is <em>burned</em>.</li><li>Turms AMT was developed by an individual programmer. There is no ICO.</li><li>The Turms AMT smart contracts were <a href="https://github.com/AlejandroDiaz666/message-transport/blob/master/Audit%20Report%20-%20Turms%20Message%20Transport.pdf">audited</a> by Solidified</li><li>Turms AMT alpha testing is complete. The beta version of the user interface can be used now:<br><a href="https://ipfs.io/ipns/messagetransport.turmsanonymous.io/">https://ipfs.io/ipns/messagetransport.turmsanonymous.io/</a></li></ul><p>As a consequence of the fact that Turms messages are stored on the Ethereum blockchain there are a couple of limitations:</p><ul><li>Turms messages are not cheap. Expect to pay about $0.20 in gas fees for a moderately sized message — more if you attach a small image — and large attachments are not supported.</li><li>Turms messages persist forever (encrypted).</li><li>Turms AMT is not as fast or as flexible as email.</li></ul><p>The foregoing makes Turms AMT more suitable for serious commerce or business related messages than for casual social messaging.</p><p>The long and short of it is that if you know someone’s email address; and you don’t need your message to be encrypted; and you don’t need to remain anonymous — then you can just use email… But also I believe there are a myriad of new Ethereum DApps just waiting for anonymous, encrypted<br>communication between Ethereum addresses. I made Turms AMT to fill that niche.</p><p>You can find out more about Turms AMT at my un-website, <a href="https://diazgonewild.com/">diazgonewild.com</a>.</p><p>Alejandro Diaz</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e40b31dbdc2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Token Transfers with the Simple MultiSig Wallet]]></title>
            <link>https://medium.com/@alejandrodiaz_71295/token-transfers-with-the-simple-multisig-wallet-6ceb3efd2de6?source=rss-eaaf9a2a9e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ceb3efd2de6</guid>
            <category><![CDATA[multisig]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[erc20]]></category>
            <dc:creator><![CDATA[Alejandro Diaz]]></dc:creator>
            <pubDate>Tue, 12 Mar 2019 07:22:44 GMT</pubDate>
            <atom:updated>2019-03-12T16:21:26.363Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article I’m going show how to use Christain Lundkvist’s MultiSig Wallet to transfer ERC-20 tokens.</p><h4>Background</h4><p>Over a year ago Christian Lundkvist came up with a very elegant, simple <br>idea for a rock-solid multisig wallet. (See E<a href="https://medium.com/@ChrisLundkvist/exploring-simpler-ethereum-multisig-contracts-b71020c19037">xploring Simpler Ethereum Multisig-Contracts</a>.) But the thing that makes this wallet incredibly secure, namely its simple, spartan, no-frills design, is the same thing that makes it somewhat difficult to use. I wrote a front-end (user interface) for this contract to make it a bit more accessible to a wide audience. This front-end is on IPFS at: <a href="https://ipfs.io/ipns/simplemultisig.io/wallet">https://ipfs.io/ipns/simplemultisig.io/wallet</a></p><p>I’ve already written a <a href="https://medium.com/@alejandrodiaz_71295/simple-multisig-step-by-step-75429d9a4d61?source=friends_link&amp;sk=295c1137cff480240eedb8e872216220">Hand-Holding Guide to the Simple MultiSig Wallet</a>, which shows how to use a wallet that transacts in Ether. In this article I’m going to use the Simple MultiSig Wallet to transfer ERC-20 tokens. Although there are a lot of manual steps, conceptually it’s easier than you might think!</p><h4>The Setup</h4><p>I’m going to assume that you already know how to create and deploy a multisig wallet. If you’re not sure, then check out the previous article, <a href="https://medium.com/@alejandrodiaz_71295/simple-multisig-step-by-step-75429d9a4d61?source=friends_link&amp;sk=295c1137cff480240eedb8e872216220">Hand-Holding Guide to the Simple MultiSig Wallet</a>. For this example I set up a two-party multisig wallet, with me and my mom as owners… It’s really a convenience wallet, (which is to say I trust her), so I set the “threshold” to 1 so that either one of us can execute transactions. Here you can see how it looks when I view the wallet:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cuw28PwLJ2DFg_iwvsskog.png" /></figure><h4>Funding the Wallet</h4><p>Sending Dai to the wallet is like sending to any other address. You can use <a href="https://mycrypto.com/">MyCrypto</a>, or MetaMask, or whatever you normally use for sending tokens. Here I’m going to use MetaMask to transfer 1 Dai. (You can skip this section if you already know how to transfer tokens.) I start by copying the wallet address:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eZjBmaKndtS1kc5405cMpw.png" /></figure><p>Next I click on the MetaMask icon, and then click on the menu icon towards the upper left of the MetaMask dialog. MetaMask immediately shows the tokens that are owned by my address:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eLefknNozjJWidLY_5XN0A.png" /></figure><p>When I select Dai, I’m presented with the Send-Tokens dialog shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qa-PFduUkQKyDh4UstrXTA.png" /></figure><p>I paste the wallet address in the To field, enter the number of Dai that I want to send (1 Dai), and click Next. I then confirm the transaction, which is shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KQRGB0Wg6xLscQJfInEfWg.png" /></figure><h4>Creating the Token-Transfer Hex Data</h4><p>Wouldn’t you know it, but shortly after I deposited the Dai my mom called up and asked me to transfer 1 Dai out of the multisig wallet to her address. Here’s where things get tricky. The first thing we need is the ERC20 interface ABI. This is essentially a formal specification of functions that are included in the ERC20 standard. You can get this from the <a href="https://github.com/ethereum/wiki/wiki/Contract-ERC20-ABI">ethereum.org wiki</a>. Copy the entire ABI from the open bracket to the close bracket:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k2eBqAv_OL_a-aQUL8TZEg.png" /></figure><p>Alternately, for your convenience I’ve provided the ERC20 ABI in a condensed format (I removed the new-lines). You can copy the text below:</p><pre>[{&quot;constant&quot;:false,&quot;inputs&quot;:[{&quot;name&quot;:&quot;spender&quot;,&quot;type&quot;:&quot;address&quot;},{&quot;name&quot;:&quot;value&quot;,&quot;type&quot;:&quot;uint256&quot;}],&quot;name&quot;:&quot;approve&quot;,&quot;outputs&quot;:[{&quot;name&quot;:&quot;ok&quot;,&quot;type&quot;:&quot;bool&quot;}],&quot;payable&quot;:false,&quot;stateMutability&quot;:&quot;nonpayable&quot;,&quot;type&quot;:&quot;function&quot;},{&quot;constant&quot;:false,&quot;inputs&quot;:[{&quot;name&quot;:&quot;from&quot;,&quot;type&quot;:&quot;address&quot;},{&quot;name&quot;:&quot;to&quot;,&quot;type&quot;:&quot;address&quot;},{&quot;name&quot;:&quot;value&quot;,&quot;type&quot;:&quot;uint256&quot;}],&quot;name&quot;:&quot;transferFrom&quot;,&quot;outputs&quot;:[{&quot;name&quot;:&quot;ok&quot;,&quot;type&quot;:&quot;bool&quot;}],&quot;payable&quot;:false,&quot;stateMutability&quot;:&quot;nonpayable&quot;,&quot;type&quot;:&quot;function&quot;},{&quot;constant&quot;:true,&quot;inputs&quot;:[{&quot;name&quot;:&quot;who&quot;,&quot;type&quot;:&quot;address&quot;}],&quot;name&quot;:&quot;balanceOf&quot;,&quot;outputs&quot;:[{&quot;name&quot;:&quot;value&quot;,&quot;type&quot;:&quot;uint256&quot;}],&quot;payable&quot;:false,&quot;stateMutability&quot;:&quot;view&quot;,&quot;type&quot;:&quot;function&quot;},{&quot;constant&quot;:false,&quot;inputs&quot;:[{&quot;name&quot;:&quot;to&quot;,&quot;type&quot;:&quot;address&quot;},{&quot;name&quot;:&quot;value&quot;,&quot;type&quot;:&quot;uint256&quot;}],&quot;name&quot;:&quot;transfer&quot;,&quot;outputs&quot;:[{&quot;name&quot;:&quot;ok&quot;,&quot;type&quot;:&quot;bool&quot;}],&quot;payable&quot;:false,&quot;stateMutability&quot;:&quot;nonpayable&quot;,&quot;type&quot;:&quot;function&quot;},{&quot;constant&quot;:true,&quot;inputs&quot;:[{&quot;name&quot;:&quot;owner&quot;,&quot;type&quot;:&quot;address&quot;},{&quot;name&quot;:&quot;spender&quot;,&quot;type&quot;:&quot;address&quot;}],&quot;name&quot;:&quot;allowance&quot;,&quot;outputs&quot;:[{&quot;name&quot;:&quot;remaining&quot;,&quot;type&quot;:&quot;uint256&quot;}],&quot;payable&quot;:false,&quot;stateMutability&quot;:&quot;view&quot;,&quot;type&quot;:&quot;function&quot;},{&quot;anonymous&quot;:false,&quot;inputs&quot;:[{&quot;indexed&quot;:true,&quot;name&quot;:&quot;from&quot;,&quot;type&quot;:&quot;address&quot;},{&quot;indexed&quot;:true,&quot;name&quot;:&quot;to&quot;,&quot;type&quot;:&quot;address&quot;},{&quot;indexed&quot;:false,&quot;name&quot;:&quot;value&quot;,&quot;type&quot;:&quot;uint256&quot;}],&quot;name&quot;:&quot;Transfer&quot;,&quot;type&quot;:&quot;event&quot;},{&quot;anonymous&quot;:false,&quot;inputs&quot;:[{&quot;indexed&quot;:true,&quot;name&quot;:&quot;owner&quot;,&quot;type&quot;:&quot;address&quot;},{&quot;indexed&quot;:true,&quot;name&quot;:&quot;spender&quot;,&quot;type&quot;:&quot;address&quot;},{&quot;indexed&quot;:false,&quot;name&quot;:&quot;value&quot;,&quot;type&quot;:&quot;uint256&quot;}],&quot;name&quot;:&quot;Approval&quot;,&quot;type&quot;:&quot;event&quot;}]</pre><p>After copying the ERC20 ABI, head over to <a href="https://abi.hashex.org/">https://abi.hashex.org/</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*izB2I9eCLN9YHfeHPfGAGw.png" /></figure><p>Left-click once where it says “Enter you ABI…” and then paste the ERC20 ABI that you copied, and then click Parse:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lJG33vzNvuEbe_qYQye3sQ.png" /></figure><p>Now from the drop-down selector I select the Transfer function and fill in the function parameters. For the To address I pasted my mom’s address. For the Value parameter I entered a 1 followed by 18 zeros. The reason for the 18 zeros is that Dai uses 18 decimals, just like Ether.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_WZjBHZV0_eBx5P1yWj6_w.png" /></figure><p>I copied the resulting hex string. Then I opened up the multisig wallet, clicked on the Transaction tab, selected the ‘Token Xfer Test’ wallet, and pasted the hex string it into the Data text-box. Note that I prefixed the hex data with ‘0x’:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GFG7xk1z2dReU0FHDIbuFg.png" /></figure><h4>Getting the Token Contract Address</h4><p>We’ve filled in the Data text-box — that was the hard part. The next step is to head over to etherscan.io to look up the address of the Dai token contract:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LGdTtwSvtv5L2iM8QYyx4A.png" /></figure><p>Click on the entry for Dai, and then copy the address of the contract:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*4N0wlek-2fE8JOo7hscfSw.png" /></figure><p>Going back to the Simple MultiSig Wallet page, I paste the Dai Token Contract address into the To field:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZQbcAwy9nY2OTSBZSWCbsw.png" /></figure><p>I set the Value field to zero, because we’re not sending any Ether in this transaction. But I modified the Gas Limit from 21,000 to 210,000 to pay for the execution of the Transfer function. In fact the token transfer transaction only needs about 140,000 gas, but it doesn’t hurt to provide a <em>little</em> extra, since it is refunded at the completion of a successful transaction. I set the Executor address to my own address, since I’m going to execute the transaction; but I also could have set it to ‘0x0’, since that allows <em>anyone</em> to execute the transaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y3PKpnVfdnp1_iHjKBEw0w.png" /></figure><p>Finally I can sign the transaction. Since only one signature is required, I can immediately execute the transaction:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qXON6463hFCkGAr6K0X8aQ.png" /></figure><p>When I click ‘Execute this transaction’ I’m presnted with a MetaMask dialog to confirm:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lxC9vfg508XWcmOpoWFVzg.png" /></figure><p>After confirming I only need to wait a few moments for the transaction to be mined on the Blockchain:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ibaHKDmntcsUBPnxbxB7qA.png" /></figure><p>Clicking the View-transaction link opens an etherscan.io page where you can see that (after the transaction is confirmed) indeed 1 Dai was transferred to my mom’s address:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vPEQSF5jxPSbGN-XtebWzA.png" /></figure><h4>Summary</h4><p>We’ve walked through all the steps to transfer Dai into and out of the Simple MultiSig Wallet. The same technique can be used to direct the Simple MultiSig contract to execute pretty much any function from any other contract. In this way the Simple MultiSig contract is incredibly powerful.</p><p>If this was your first time digging into contract ABI’s and such it might seem a bit daunting. But let it settle in. A part of the beauty of the Simple MultiSig Wallet is that it doesn’t hide any of its function. That is part of what makes it so versatile and so secure.</p><p>Alejandro Diaz</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ceb3efd2de6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple MultiSig — Step by Step]]></title>
            <link>https://medium.com/@alejandrodiaz_71295/simple-multisig-step-by-step-75429d9a4d61?source=rss-eaaf9a2a9e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/75429d9a4d61</guid>
            <category><![CDATA[multisig]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[wallet]]></category>
            <dc:creator><![CDATA[Alejandro Diaz]]></dc:creator>
            <pubDate>Thu, 28 Feb 2019 05:51:59 GMT</pubDate>
            <atom:updated>2019-03-02T21:49:50.666Z</atom:updated>
            <content:encoded><![CDATA[<h3>Simple MultiSig — Step by Step</h3><h4>hand-holding guide to the Simple MultiSig Wallet, with plenty of screenshots</h4><p>A multi-party transaction is a classic example of something you can do more easily with Ethereum than with fiat currencies. Yet many people don’t realize how easy it is to use MultiSig Wallets for multi-party transactions.</p><p>In this article I’m going to introduce a typical use-case for a MultiSig wallet, and then walk you through how to execute multisig transactions using <a href="https://medium.com/@ChrisLundkvist/exploring-simpler-ethereum-multisig-contracts-b71020c19037">Christian Lundkvist’s Simple MultiSig Wallet</a>. I’ll be using the user interface for the Simple MultiSig Wallet that I wrote — it’s completely free to use and available on IPFS:</p><p><a href="https://ipfs.io/ipns/simplemultisig.io/wallet">https://ipfs.io/ipns/simplemultisig.io/wallet</a></p><p>The walk through will have lots of screenshots. I know that format can be tedious for some people — but if you’re setting up a MutiSig Wallet with large sums of ETH it can be re-assuring to actually see how the screens will look.</p><h4>The Setup</h4><p>My two business partners and I each have personal stores of Ether that we own, independent of our business together. We know we’re going to need to sell some to finance our business, but we don’t know how much or when. So we agree that we’ll fund a MultiSig Wallet with 300 ETH and we’ll sell the ETH as needed to pay our business expenses. Each of us will deposit 100 from our personal holdings; and any two of us will sign to make a withdrawal from the group wallet. This is akin to the 3 us opening a business bank account that requires at least 2 signatures to write a check or to make a withdrawal.</p><p>Note: I’m going to run this example on the Mainnet — just because it’s more exciting with real Ether. But since I don’t have 300 ETH lying around I’ll be using 300 Finney :)</p><h4>Creating the Wallet</h4><p>First of all, point your browser at <a href="https://ipfs.io/ipns/simplemultisig.io/wallet,">https://ipfs.io/ipns/simplemultisig.io/wallet,</a> and log into MetaMask. Note that whenever you change MetaMask accounts you’ll need to reload the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k4tiOMAUJjslLKF7s1j66w.png" /></figure><p>After logging in to MetaMask, and selecting the desired MetaMask account, and reloading the page, I click on the “New Wallet” button:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4WzmBCJajIOdYJaHxpUZ5g.png" /></figure><p>Now I enter a name for the new wallet — I chose “Biz Expenses”, and I enter the Ethereum address of each of the partners. My own address is pre-populated, so all I need to do is modify the owner-label from its default value, “My Account”, to my name Alex Diaz. Then I click “Add Owner.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5kl1uDpfisvyuWLuy3OC1w.png" /></figure><p>Next I enter the (public) Ethereum addresses of my partners. The User Interface accepts ENS names, and my first partner’s ens name is “imontoya.eth”, so I enter that, and leave the label field blank (since it will be auto-populated), and again I click add-owner. The third partner doesn’t have an ens name, so I simply enter his Ethereum address, 0x3B66…FeCf, and I set the owner label to his nickname, “Grasshopper”, and again click add-owner. Before moving on, I set the “Threshold” from the drop-down to 2. This indicates than any transaction from this wallet will require 2 of our signatures. Here’s how the screen looks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OJtixEG4YxQVTlBamOgDbg.png" /></figure><p>Everything looks good, so I’m going to click “Deploy contract”; I confirm<br>the transaction in the MetaMask dialog, and then wait for the transaction<br>to be confirmed on the blockchain:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GHfdygx7HtYjE7xPoy7tyA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nwYptAE7FaSn-P6TYGJy9A.png" /></figure><p>The wallet is now deployed on the blockchain. But in order to sign transactions each of my partners will need to be able to access it. So I click on the “View Wallet” button, and select the “Biz Expenses” wallet from the wallet-selector:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f3cDy84-zaRM1uBTXswx9w.png" /></figure><p>Now I copy the wallet data out of the text-box that says JSON. And I send that by email to each of my partners. Now, for a moment we’re going to switch to Grasshopper’s computer, where he has clicked on the “Import Wallet” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Djea4w8I3b3Q9yhB33guQA.png" /></figure><p>He copies the data into the text-box that says JSON, clicks “Load wallet from JSON”, and then clicks “Save this wallet locally” — and now he has a copy of the wallet:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wzPHfBIW88lYR6JXy5Nnhg.png" /></figure><p>My other partner, imontoya will do the same.</p><h4>Funding the Wallet</h4><p>Now it’s time to fund the wallet. Click on the “view Wallet” button and select the “Biz Expenses” wallet from the wallet-selector. The wallet address is shown just beneath the wallet selector. It’s 0xc7013…c972</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SwOHJ5ALx8w-GPDolK0u-Q.png" /></figure><p>Each of us sends 100 Finney to the wallet address. So the total balance of the<br>wallet is 300 Finney. When I reload the page the new balance is shown:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hHylpLwAmH-T3_OlaKH3Ag.png" /></figure><h4>Making a transaction</h4><p>Here we are, a few days later, and Grasshopper and I have decided that we need to withdraw 10 Finney to make a business purchase (recall that only two of the partners need to sign off on any transaction). We have an employee who’s in charge of selling the ETH for cash, and actually making the purchase — sort of a CFO; so we’ll send the 10 Finney to his account. btw, his ens name is “bobthebuilder.eth.”</p><p>To get started I click on the “Transaction” button. In the wallet-selector <br>drop-down I select the “Biz Expenses” wallet. The screen looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BOYzB-tdAp0YyaMerQ_oPA.png" /></figure><p>Now I enter the transaction details. In the “To Address” field I enter, “bobthebuilder.eth”. As soon as I press the tab key his ethereum address is filled-in. Then I enter the value, 10 Finney, and the executor address. The executor address is the address of the person that is allowed to actually execute this transaction (after the required number of signatures have been collected). You can enter 0x0 to allow anyone to execute the transaction — <br>but in our case our CFO, bobthebuilder, will do it, so I enter “bobthebuilder.eth” in that field. For a simple Ether transaction you can leave the data text-box empty, and the nonce and gas limit at their default values. So now my screen looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RPA6hP9pCDSQemW09ibPng.png" /></figure><p>After I click the “Sign this transaction” button, MetaMask presents me with the EIP-712 signature dialog. This is one of the new features of this multisig wallet — namely it shows what you are signing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ute0wgeyWhBSJm0UEApi7A.png" /></figure><p>Note that my signature is also included in the JSON that is displayed in the JSON text-box. At this time I copy the JSON from that text-box and send it (by email) to Grasshopper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J55N_GgNwOaFyHf85oNi9w.png" /></figure><p>For a moment we’re going to switch to Grasshopper’s computer, where he has clicked on the “Transaction” button and selected the “Biz Expenses” wallet:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RiDkV7TtvuY8uNzITN35jA.png" /></figure><p>He pastes the JSON that I sent to him, and clicks “Load transaction from JSON”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*88ww0H8UctFzicYmp9MYvw.png" /></figure><p>After he verifies that the transaction looks right, he clicks the “Sign this transaction” button and signs the MetaMask dialog (check the MetaMask icon, because the dialog might not pop up) — and now his signature is also added to the JSON.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r7I4OK-gi7hCAV0ShNizKQ.png" /></figure><p>So now Grasshopper copies the new JSON data out of the JSON text box and sends it (by email) to our executor, AKA bobthebuilder. The executor also needs to load the wallet JSON, since transactions only work in their own specific wallet. In the image below the executor has loaded the wallet and also loaded the transaction JSON data that he received from grasshopper, which included two signatures. You can see that now the “Execute this transaction” button is enabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j67-x8_xfA19RVWlb3Mcow.png" /></figure><p>After the executor clicks the “Execute this transaction” button, he needs to confirms the transaction in MetaMask:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p9i5oqvjIeVvl6zlIBI-kA.png" /></figure><p>While the transaction is pending confirmation on the blockchain, a link is provided to view it on etherscan.io:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V9hddB-8dMkWUrYmxNX3yw.png" /></figure><p>Clicking on the “View this transaction” link opens the etherscan.io page, where (after the transaction is confirmed) you can see that 10 Finney has been transferred to bobthebuilder’s account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/837/1*yCLtBr2BKPrMnoHV9yCV-g.png" /></figure><h4>Summary</h4><p>In this article I’ve tried to show almost every step of creating a MultiSig Wallet and sending a typical MultiSig transaction. Thanks to Christian Lundkvist for writing the Simple MultiSig contract; and I’m pretty proud of the User Interface, which I added. <br> <br>Use them for good! <br>Alex</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75429d9a4d61" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>