<?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[Ethereum Research - Medium]]></title>
        <description><![CDATA[Blog for work done over blockchain in general and Ethereum in particular - Medium]]></description>
        <link>https://medium.com/ethereum-research?source=rss----b3ad8715019c---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Ethereum Research - Medium</title>
            <link>https://medium.com/ethereum-research?source=rss----b3ad8715019c---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:38:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/ethereum-research" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Ethereum Privacy presented to AssEth]]></title>
            <link>https://medium.com/ethereum-research/ethereum-privacy-presented-to-asseth-3bf344efdf66?source=rss----b3ad8715019c---4</link>
            <guid isPermaLink="false">https://medium.com/p/3bf344efdf66</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum-privacy]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Guénolé de Cadoudal]]></dc:creator>
            <pubDate>Tue, 02 Jul 2019 18:16:19 GMT</pubDate>
            <atom:updated>2019-07-02T18:16:19.632Z</atom:updated>
            <content:encoded><![CDATA[<p>On June 26th 2019 I was invited to present how Ethereum Privacy can solve the private blockchain building with no effort while keeping it fully decentralised (no BaaS)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*MHMWbUFRl1ibJIxvtaIL1g.jpeg" /></figure><p><em>I would like to thanks </em><a href="https://www.asseth.fr/"><em>Asseth</em></a><em> and </em><a href="https://rockside.io/"><em>Rockside</em></a><em> for their warm welcoming and support.</em></p><p><em>You can also find the recording of the session on Facebook below</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=facebook&amp;url=https%3A//www.facebook.com/MaltemConsulting/videos/601700443645314/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.xx.fbcdn.net%252Fv%252Ft15.5256-10%252Fp200x200%252F65555872_601772396971452_8174299263757451264_n.jpg%253F_nc_cat%253D108%2526_nc_oc%253DAQkz8ArS5J_Bz1wLTh7XY1Xa9WWZCBsWqqMn4JZy1vGsMPokUQ-qY0daDGB7c_2Gzrk%2526_nc_ht%253Dscontent-iad3-1.xx%2526oh%253D7f227bd80e6c7f68f3dafc3a1217b09e%2526oe%253D5DBBA0C6%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="600" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/861a0b0fbb57386bd9865282f8e6f95e/href">https://medium.com/media/861a0b0fbb57386bd9865282f8e6f95e/href</a></iframe><p>The slides are available here below.<br>You can contact me via guenoledc@yahoo.fr and</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*uFIs5obypM_Fh5NyZe4zxw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*MTfJjk9NyWWXEjjUbBcGcg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*yvgd30meWyLo_vnWdBCR_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*25W1B2V1e06Zop-02iP-kA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*PyxG_mUmTSenHV-kZnQ3Tg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*4a2fdBBa7n1It43o4vDvng.png" /></figure><blockquote>Read the details of this use case on <a href="https://medium.com/ethereum-research/ethereum-privacy-use-case-call-for-tender-20a7141b46">https://medium.com/ethereum-research/ethereum-privacy-use-case-call-for-tender-20a7141b46</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bpVSlK-bhqSvhK6GSA95mg.gif" /></figure><blockquote>Read the detail of how it works on <a href="https://medium.com/ethereum-research/private-transaction-over-ethereum-7e1a07928453">https://medium.com/ethereum-research/private-transaction-over-ethereum-7e1a07928453</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*TUs2X1KOJf9OQAsJu-gchA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*YhrLmCWrNDHTCiltNaRcLA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*sIkLZMW52t3VK1FlX4LxeQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*FU_mY9wTcBCQm1BoCt7tdg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*C4gggo7VUtjDAPVmR3g3HQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*hFfWZTl36jG2N8slLZjvQw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bf344efdf66" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ethereum-research/ethereum-privacy-presented-to-asseth-3bf344efdf66">Ethereum Privacy presented to AssEth</a> was originally published in <a href="https://medium.com/ethereum-research">Ethereum Research</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Totally in line with the approach.]]></title>
            <link>https://medium.com/ethereum-research/totally-in-line-with-the-approach-bd407914df5?source=rss----b3ad8715019c---4</link>
            <guid isPermaLink="false">https://medium.com/p/bd407914df5</guid>
            <dc:creator><![CDATA[Guénolé de Cadoudal]]></dc:creator>
            <pubDate>Wed, 15 May 2019 06:23:56 GMT</pubDate>
            <atom:updated>2019-05-15T06:23:55.866Z</atom:updated>
            <content:encoded><![CDATA[<p>Totally in line with the approach.</p><p>However, I’d like to raise 2 concerns</p><ul><li>Using light synchronisation of Blockchain allow man in the middle attacks since the node does not validate the state against the transaction in blocks</li><li>When reading a Blockchain we often rely on third party software that wrap the smart contracts into an API. Here again, if the api is remote or code gets compromised, man in the middle attack is possible.</li></ul><p>In any case this transformation is useful for the community.</p><p>Thanks</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd407914df5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ethereum-research/totally-in-line-with-the-approach-bd407914df5">Totally in line with the approach.</a> was originally published in <a href="https://medium.com/ethereum-research">Ethereum Research</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ethereum Privacy use case : Call for tender]]></title>
            <link>https://medium.com/ethereum-research/ethereum-privacy-use-case-call-for-tender-20a7141b46?source=rss----b3ad8715019c---4</link>
            <guid isPermaLink="false">https://medium.com/p/20a7141b46</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[call-for-tender]]></category>
            <dc:creator><![CDATA[Guénolé de Cadoudal]]></dc:creator>
            <pubDate>Tue, 07 May 2019 18:32:19 GMT</pubDate>
            <atom:updated>2019-05-07T18:32:19.775Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Ethereum Privacy use-case: Call for tender</strong></h3><p>Further to the introduction of <a href="https://medium.com/ethereum-research/private-transaction-over-ethereum-7e1a07928453">Ethereum Privacy</a>, an easy way to leverage public blockchain infrastructure while maintaining business confidentiality, and the technical dive into the technology, let’s discover how to implement a use case.</p><p><strong>Background of the use case:</strong></p><p>Wholesale Rice Corp (WRCorp) is an American rice importer who regularly purchases from several different Indian, Chinese and Thai companies. They compete against each other for maintaining their share in the American market.</p><p>WRCorp leverages this situation by running calls for tenders where none of the potential suppliers shall be aware of the consulted competitors nor what was the price and conditions of the selected supplier.</p><p>Since WRCorp currently submits individual faxes or emails to consult with the suppliers the process is cumbersome and prone to frauds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*_6EFOdCrR96cLbBUPZORCg.png" /><figcaption>Ethereum Privacy</figcaption></figure><p><strong>Decision is taken to use Ethereum Privacy to perform the next call for tender over <br>blockchain technology <br>without investing into <br>a large infrastructure.</strong></p><p>A call for tender of rice is initiated by WRCorp with a (simplified) request for a quantity, a variety, a quality range, a date of delivery and an expected payment scheme. The suppliers must respond within 3 days with a minimum and maximum quantity in oz, the quality, the variety, the price per oz, the payment delay financing cost, the related tax price, the shipping method and the expected delivery date.</p><p>WRCorp may terminate the call for tender at any moment and after the response delay can select one or several proposals by confirming the desired quantity (without anyone but the supplier knowing). Non-selected suppliers are notified of the termination of the process (for them). Selected supplier(s) must confirm the trade to WRCorp to seal the sell transaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TvGApWYsN4rVJ6JdLu_c5w.png" /><figcaption>Example of a call for tender</figcaption></figure><p><strong>One-off actions to get ready:</strong></p><ul><li>WRCorp <a href="https://medium.com/ethereum-research/ethereum-privacy-get-started-now-44b313d137a1">installs Ethereum Privacy</a> and get its public key.</li><li>WRCorp communicates with all its suppliers, giving its public key and asking them to install Ethereum Privacy then share their own public key.</li><li>WRCorp and its suppliers may have to sign terms &amp; conditions that confirms <a href="https://medium.com/ethereum-research/ethereum-privacy-proof-of-transaction-59f1077c55f2">Ethereum Privacy proofs</a> are enforceable proofs in court (legal work needed)</li></ul><p>Blockchain infrastructure is now ready. It relies on the always available public <a href="https://etherscan.io/">mainnet</a> accessible freely via providers like Infura or Etherscan.</p><ul><li>WRCorp gets a smart contract and a static website designed (see draft below). The website pages can be given to the suppliers or the suppliers can design their own based on the smart contract definition.</li><li>All <a href="https://www.buybitcoinworldwide.com/ethereum/buy/">actors buy ether</a> for fuelling the communication over the public blockchain. A 10$ equivalent would be enough for a few call for tender (today 1 ether = 170$) and</li></ul><p><strong>Executing the call for tender:</strong></p><ul><li>WRCorp issues the call for tender by deploying the smart contract to the desired suppliers’ public keys.</li><li>All actors then follow the protocol described above, enforced by the smart contract business logic.</li><li>WRCorp and selected supplier(s) can extract the <a href="https://medium.com/ethereum-research/ethereum-privacy-proof-of-transaction-59f1077c55f2">transaction proofs</a> to have a legally binding contract of sell and purchase. This can also be done at any later time.</li></ul><p><strong>Conclusion:</strong></p><p>As this realistic use case shows, using public blockchain secured with Ethereum Privacy is simple and can be implemented in a few weeks’ elapse time.</p><p>When comparing this setup with a consortium (eg Komgo, Clipeum, MarcoPolo) approach to implement a private blockchain network (Corda, Quorum, Pantheon or Hyperledger) you realise quickly the benefits of leveraging the public blockchain infrastructure instead of investing into a dedicated infrastructure.</p><p><strong>Smart contract </strong>(example)<strong>:</strong></p><p>The smart contract implementation follows the Ethereum standard. However, it must be designed taking in consideration that not all participants see all transactions.</p><p>For instance, in the below contract issuer is always involved, each supplier is involved one by one. So, the data structure and function parameters and conditions reflects this.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2636c1f8820bd12dc0803ae77e72d686/href">https://medium.com/media/2636c1f8820bd12dc0803ae77e72d686/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20a7141b46" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ethereum-research/ethereum-privacy-use-case-call-for-tender-20a7141b46">Ethereum Privacy use case : Call for tender</a> was originally published in <a href="https://medium.com/ethereum-research">Ethereum Research</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ethereum Privacy: Proof of transaction]]></title>
            <link>https://medium.com/ethereum-research/ethereum-privacy-proof-of-transaction-59f1077c55f2?source=rss----b3ad8715019c---4</link>
            <guid isPermaLink="false">https://medium.com/p/59f1077c55f2</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Guénolé de Cadoudal]]></dc:creator>
            <pubDate>Sat, 27 Apr 2019 21:19:35 GMT</pubDate>
            <atom:updated>2019-04-27T21:17:43.527Z</atom:updated>
            <content:encoded><![CDATA[<p>This third publication on Ethereum Privacy explains how to extract a proof of a private transaction done over a public blockchain.</p><p>Read the <a href="https://medium.com/ethereum-research/private-transaction-over-ethereum-7e1a07928453">introduction</a> and <a href="https://medium.com/ethereum-research/ethereum-privacy-get-started-now-44b313d137a1">how to get started</a> articles to get familiar with the concepts.</p><p>When a transaction is done between two or several parties through <br>“Ethereum Privacy”, in case of conflict, a party will certainly need to prove to the other that he has received and processed what he was supposed to, or that he has sent what he needed to via the public chain.</p><p>This is naturally possible, thanks to the fact that the transaction content is stored, encrypted, in the smart contract in the public blockchain (and therefore not alterable over time).</p><p>Say that Alice submits an offer to Bob in the context of a tender implemented via Ethereum Privacy and that Bob accepts Alice’s offer. Bob should be able to prove Alice offer price and content and Alice should be able to prove that Bob has accepted her offer. Let’s see what happen.</p><p><strong>Understanding the sending of a private transaction</strong></p><p>Each of Alice and Bob actions (making and accepting the offer) are private transactions. A private transaction is a standard Ethereum transaction created and signed by the sender’s wallet (Alice and respectively Bob’s wallet), that gets stored in the <a href="https://ropsten.etherscan.io/address/0xd5d36550a1d7971b4fa68be066ed4ef4f85a46e1#code">PrivateTxStorage</a> smart contract in the public blockchain by a privacy node (Alice and respectively Bob’s node).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ETwyJ-nAFgInX2PrkdEt8g.png" /></figure><p>First, at the level of the private transaction created by Alice (or Bob) the action is encoded as an interaction with a smart contract that has been created before. This transaction is signed with Alice’s wallet, ie Alice must have access to the private key of that wallet.</p><p>Alice’s privacy node generates a json web token that gets signed with the private key of Alice’s node. Alice (or someone she trusts) must control that private key. The JW Token contains a gzip of the transaction and the public key of the privacy node.</p><p>Alice’s privacy node generates a symmetric 32 bytes key and a 16 bytes random init vector for AES-256-CBC encryption algorithm, and a unique id for the transaction.</p><p>Alice’s privacy node then sends to the public blockchain the symmetrically encrypted JWT via transactions signed by a local wallet that it must have the private key for. The transactions contains 320 bytes parts of the encrypted JWT to reduce the size of each transaction and facilitate its inclusion into the public chain of blocks. Then for each receivers (itself and Bob’s node) Alice’s node encrypts with the public key of the recipient the entry id of the transaction and the aes elements to decrypt the JWT and generates events in the public smart contract</p><p><strong>Receiving the private transaction</strong></p><p>When Bob’s privacy node sees an event in the public smart contract, it can (try) decrypt(ing) the aes elements with its private key to get the id of the transaction and the symmetric key.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*reFFQ9Oj0lUJqTaZ3FY1VA.png" /></figure><p>It can then extract from the smart contract the encrypted JWT parts and get the public key of the sender from it. It then checks that Alice node’s public key exists in its PKI and that it is trusted and still valid.</p><p>Alice raw transaction can then be extracted and sent to the local private Ethereum VM to be executed by Bob’s copy of the smart contract. Smart contract logic can check that Alice’s wallet is authorised to place the offer.</p><p>Alice’s privacy node performs the same process, except that since she always trusts her own public key (derived from her private key) checking it against the PKI is not necessary.</p><p>The process for Bob’s transaction accepting Alice’s offer is identical and does not need to be described here.</p><p><strong>Getting the transaction proof</strong></p><p>Bob can query his privacy node to extract a transaction proof corresponding to the hash of Alice’s transaction by calling the <em>admin_getTransactionProof </em>rpc method with the private tx hash as single parameter. Doing so Bob will get a json object with the following information</p><blockquote><strong>ofTxHash</strong>: the private tx hash this proof relates to<br><strong>input</strong>: address of the smart contract in the public blockchain and the id of the entry. The aes key and init vector are not retrieved as they are not needed for the proof<br><strong>decryptedPayload</strong>: the decrypted JWT that can be verified with the sender’s public key<br><strong>sender</strong>: the public key in PEM format, the PKI response for this public key at the time of transaction received and as of the generation of the proof<br><strong>request</strong>: the json rpc request that was submitted by the sender that contains a raw transaction from the JWT<br><strong>storedAt</strong>: the public blockchain transaction and block where the event notifying the local privacy node has been made, including the wallet used by the sending privacy node<br><strong>transactionFromRequest</strong>: the decoded raw transaction from the JWT, showing in particular the “hash”, that must be the same as the “ofTxHash” field and the “from” field that refers to the sending wallet (Alice’s wallet)<br><strong>transactionReceipt</strong>: a standard web3 transaction receipt of this private transaction processed by the local private ethereum virtual machine.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*68tMGnOiNK95YoK4DUOYeA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YYFy0Fyet73SxG3MCJYXaA.png" /></figure><p><strong>How to answer contestations with the proof ?</strong></p><ul><li>Let’s say, Alice contests the details of the offer Bob has received: Bob can get the transaction where Alice has made her offer and extract the related proof from the public blockchain. In that proof, Bob will be able to show that the transaction he has received was signed by Alice’s privacy node (<em>decryptedPayload</em> is a JWT that can be verified with Alice’s public key). <br>The content of the JWT can be decoded into the raw transaction that in turn can show what values have been passed to the tender smart contract.<br>It is not possible for anyone, without Alice’s private key, to fake a JWT signed by Alice, so it must Alice who made that submission.</li><li>If Alice says she had her private key stolen: It is still her responsibility what has been done with that private key. She would be responsible to declare the corresponding public key as invalid to all participants and communicate a new public key to be used. This would be the function of the PKI (public key infrastructure) to handle declaration and removal of public key. This is the reason why Ethereum Privacy relies on third party PKI solutions.<br>If Alice can prove that she has declared the private key stolen and communicated her new public key, but that Bob accepted the old public key, then it becomes Bob’s responsibility to have accepted the forged transaction. This implies that the PKI solution must also check the certificate revocation list before accepting the transaction.</li><li>Now, let’s say Alice claims that she never received Bob acceptation of her offer and therefore has no reason to honour her offer. Bob can then extract the transaction where he responded to Alice and extract the proof from the blockchain. The <em>storedAt</em> field is an autonomous proof that Bob’s transaction exists in the public blockchain. With that element, the event notifying Alice can be located in the blockchain (event with aes elements encrypted with Alice’s public key). That event is the proof that Alice was able to read Bob’s transaction and it becomes Alice’s responsibility to monitor the public blockchain for events that can be decoded with her private key. Note that this requires that the public key used for Alice is kept even if Alice changes her private key after the facts.</li><li>There may be other cases to discuss and that can be handled with elements in the proof.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59f1077c55f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ethereum-research/ethereum-privacy-proof-of-transaction-59f1077c55f2">Ethereum Privacy: Proof of transaction</a> was originally published in <a href="https://medium.com/ethereum-research">Ethereum Research</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ethereum Privacy : Get started now.]]></title>
            <link>https://medium.com/ethereum-research/ethereum-privacy-get-started-now-44b313d137a1?source=rss----b3ad8715019c---4</link>
            <guid isPermaLink="false">https://medium.com/p/44b313d137a1</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[getting-started]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Guénolé de Cadoudal]]></dc:creator>
            <pubDate>Mon, 08 Apr 2019 20:05:02 GMT</pubDate>
            <atom:updated>2019-04-27T21:20:10.170Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ethereum Privacy : Get started now.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/70/1*imrN50Kx_Fls3yXehINxfw.png" /></figure><p><strong><em>Ethereum Privacy leverage the public blockchain infrastructure while maintaining the confidentiality of your transactions</em></strong></p><p>This is the first tutorial to get started with <strong><em>Ethereum Privacy</em></strong> technology.</p><p>In 10 minutes, get <strong><em>Ethereum Privacy</em></strong> running on your developer’s machine and understand</p><ul><li>where the <strong><em>Ethereum Privacy</em></strong> process sits between your web3 program and your usual Ethereum client node</li><li>what configurations are required to have the technology ready to use</li><li>how to specify with whom your transaction mus be shared</li></ul><p><strong>1.Before we start, some requirements for your target machine</strong></p><p>The packaging as of now (v 0.1.2) uses docker image, so you need <strong>docker</strong> and <strong>docker-compose</strong>. This has been tested on the following version but it should work with others</p><pre>Docker version 18.09.2, build 6247962<br>docker-compose version 1.23.2, build 1110ad01</pre><p>2. <strong>Download the get-started package</strong></p><pre>~ $ git clone --depth 1 <a href="https://gitlab.com/guenoledc-perso/offchainprivatetx/get-started.git">https://gitlab.com/guenoledc-perso/offchainprivatetx/get-started.git</a></pre><p>This will give you a folder structure with the following</p><blockquote><a href="https://gitlab.com/guenoledc-perso/offchainprivatetx/get-started/blob/master/docker-compose.yml"><strong>docker-compose.yml</strong></a>: the docker services description and configuration<br><a href="https://gitlab.com/guenoledc-perso/offchainprivatetx/get-started/blob/master/default-conf.json"><strong>default-conf.json</strong></a>: common configuration file for all the privacy nodes<br><a href="https://gitlab.com/guenoledc-perso/offchainprivatetx/get-started/blob/master/setup-env.sh"><strong>setup-env.sh</strong></a>: shell script to prepare the public and privacy nodes<br><strong>node1/keystore</strong>: contains a standard Ethereum wallet for node1<br><strong>node2/keystore</strong>: same for privacy node2<br><strong>node3/keystore</strong>: same for privacy node3<br><strong>client</strong>: a node js command line projet that interacts with the privacy nodes</blockquote><p>3. Deploy the environment</p><pre>~/get-started $ ./setup-env.sh</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xzuzs8vVIcrSvKQRRCboqQ.png" /></figure><ol><li>Starts the public node: here a simple geth in local dev mode with PoA consensus mining when a transaction is received</li><li>Launching a <em>geth attach — exec javascript</em> to the public node, to credit each of the wallets that will be used by the Ethereum Privacy nodes to interact with the public node.</li><li>Deploying in the public node the smart contract (<a href="https://ropsten.etherscan.io/address/0xd5d36550a1d7971b4fa68be066ed4ef4f85a46e1#code">PrivacyTxStorage</a>) used to store the encrypted transaction and the encrypted notifications. <a href="https://medium.com/ethereum-research/private-transaction-over-ethereum-7e1a07928453">See the previous article</a>. The generated contract address must be given to the privacy nodes so they know to what they should communicate with. This deployment is done using one of the privacy node command line.</li><li>Starting each of the 3 Ethereum Privacy nodes (node A, node B, Node C)</li><li>From each node, collect the other nodes public key (from their url) and store it in the local PKI.</li></ol><p>Setup is now ready and operational (also look at the <a href="https://gitlab.com/guenoledc-perso/offchainprivatetx/get-started/blob/master/README.md">readme</a> for additional details). You can test the setup by running for each url</p><pre>$ geth attach <a href="http://localhost:8546/">http://localhost:8546</a><br>Welcome to the Geth JavaScript console!</pre><pre>instance: Ethereum-Standalone-Node/v0.0.1/6000<br>coinbase: 0x1778fef1adf67b8d904a73f64da4d29c1f13ec0b<br>at block: 0 (Sat, 09 Feb 2019 18:53:29 CET)<br> modules: admin:1.0 eth:1.0 net:1.0 parked:1.0 personal:1.0 web3:1.0</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZXjQHTr-8Q-S38dLSPE70A.png" /><figcaption>This is how the deployed environment looks like (but with a single public node)</figcaption></figure><p>geth public node listens for JSON RPC requests at <a href="http://localhost:8590/">http://localhost:8590</a></p><p>Privacy Node A listens for Web3 JSON RPC requests at <a href="http://localhost:8546,">http://localhost:8546,</a> Node B and C at <a href="http://localhost:8547/">http://localhost:8547</a> and :8548 respectively.</p><p>4. Test the setup <br>with a NodeJS client using a simple key/value smart-contract.</p><p>The client test program uses the following smart contract as a mean to simulate private interactions between each other while going through the public blockchain</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TjmXQvJlhNki0yHNRnrcHg.png" /></figure><ul><li>The smart contract has the following behaviour</li><li>Each key is globally unique, belong to the first person setting a value.</li><li>Only the owner can change the value.</li><li>An event is generated on first set and subsequent change</li><li>Every one can read the value</li></ul><p>Below is the recording of a test session that you can replicate easily on your machine.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FQgCX-G_r2sU%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQgCX-G_r2sU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FQgCX-G_r2sU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bd29cc25e98bc68f8321f7d40a9bbba0/href">https://medium.com/media/bd29cc25e98bc68f8321f7d40a9bbba0/href</a></iframe><pre># On top left terminal<br>$ node main.js --smartcontract create --listen --url <a href="http://localhost:8546/">http://localhost:8546</a></pre><pre># On top right terminal<br>$ node main.js --smartcontract auto --listen --url <a href="http://localhost:8547/">http://localhost:8547</a></pre><pre># On bottom left terminal<br>$ node main.js --smartcontract auto --listen --url <a href="http://localhost:8547/">http://localhost:854</a>8</pre><pre># On bottom right terminal<br>$ node main.js --smartcontract auto --url <a href="http://localhost:8546/">http://localhost:8546</a> --key Hello --value World<br>$ node main.js --smartcontract auto --url <a href="http://localhost:8546/">http://localhost:8546</a> --key Hello2 --value World-A-And-C --target &#39;node C&#39;<br>$ node main.js --smartcontract auto --url <a href="http://localhost:8546/">http://localhost:8546</a> --key Hello3 --value World-A-And-B --target &#39;node B&#39;</pre><p>5. Extracting the proof of transaction</p><p>The proof of a private transaction extract a json with all the needed elements to demonstrate that an action has been done and communicated to the participants. Read article <a href="https://medium.com/ethereum-research/ethereum-privacy-proof-of-transaction-59f1077c55f2">Ethereum Privacy: Proof of transaction</a></p><p>You can do it in the demonstrator with the following command</p><pre># Find the transaction hash output by the commands abobe<br>$ node main.js --proof 0xa4c65e561cb4db45b80c07616f103872e94746014e637fa69e5dbdedb6c6935e</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44b313d137a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ethereum-research/ethereum-privacy-get-started-now-44b313d137a1">Ethereum Privacy : Get started now.</a> was originally published in <a href="https://medium.com/ethereum-research">Ethereum Research</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Private transactions over a public blockchain made easy.]]></title>
            <link>https://medium.com/ethereum-research/private-transaction-over-ethereum-7e1a07928453?source=rss----b3ad8715019c---4</link>
            <guid isPermaLink="false">https://medium.com/p/7e1a07928453</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[transactions]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[private]]></category>
            <dc:creator><![CDATA[Guénolé de Cadoudal]]></dc:creator>
            <pubDate>Tue, 02 Apr 2019 18:04:24 GMT</pubDate>
            <atom:updated>2019-06-27T18:52:10.310Z</atom:updated>
            <content:encoded><![CDATA[<h3>Private transaction over a public blockchain made easy.</h3><p>This subject has been on the blockchain researchers and developers agenda for some time and many solutions have been proposed (ZKSnark, Quorum, Aztec, etc).</p><p>Ethereum is one of the most popular blockchain solution because it brings a ready to use infrastructure (tests and production public blockchains, free tools, huge community of share-minded people etc…).</p><p>But when companies starts understanding the benefits of decentralised platforms and launch an initiative that involves working with clients and competitors, they quickly reject the public blockchain option because of their genuine need of business confidentiality and turn to either a centralised operator with distributed systems or launch their own private blockchain network with their partners where they will control who enters and who stays outside.</p><p>This decision means large investments in IT infrastructure and IT skilled people to create, maintain and supervise the network and this has important costs implication and some centralisation effect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/120/1*9Wzs4ts8eZIMYukmJvX0aA.png" /><figcaption>Ethereum Privacy</figcaption></figure><h4><strong>“There is a need for a simple solution for business confidentiality over existing public blockchain infrastructure”</strong></h4><p>Ethereum Privacy is a new initiative offering that simplicity yet not compromising with security and confidentiality and leveraging the Ethereum ecosystem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Br6uY4oRe7lnbp-TZarxaA.jpeg" /></figure><p><strong>Ethereum Privacy</strong>’s proposal is to let businesses plug into the public Ethereum blockchain, pay for the use of the infrastructure (rather than invest in it), yet transact with each other via standard smart contracts and using their standard technology (public key infrastructure) to identify their partners.</p><p>Typically, two or more compagnies will discuss terms of their transaction and upon agreement all parties should sign a contract. A private smart contract can be exactly this, collecting the signatures by recording a private key signed transaction into the blockchain but it needs to be exchanged in full confidentiality.</p><p>All they need is to install a simple standalone program that interacts with the public blockchain encrypting and decrypting all data. Developers can then create on top of it standard DApps (distributed apps) as the program is web3 compatible.</p><p>If they need to prove their actions to a court or third party, the public blockchain would have an encrypted record of all activities that combined with the one-off usage key could decrypt that particular action.</p><p>This technology is intended to be open sourced and is currently in alpha version deployed for testing onto the public test ethereum network.</p><p>A functional <strong><em>demonstrator is deployed </em></strong><a href="https://guenoledc-perso.gitlab.io/offchainprivatetx/website"><strong><em>here</em></strong></a><strong><em> </em></strong>and contains instructions on how to proceed (see the screenshots below). Gitlab repository is given at the end to get started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tUgvhDsfLLV1F5JxFsLOgA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZA9Fmy22em1WC60WHjKmMQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Kt7wGafBQPlznK9Mx0U9A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LnaX2QCdysIBxJO07GVIRw.png" /></figure><h4>Use cases</h4><p>They are of course infinite number of possible usage for this technology, but to give ideas here are some examples</p><ul><li><strong>Invoicing</strong>: Your company has numerous clients and you need to track your valuable invoices and eventually transfer them to your bank for financing or sell them to a third party for collection. But of course no one but your client need to know that you are in business and what is your volume of activity.</li><li><strong>Trade Finance</strong>: A letter of credit involves 4 or more parties but only them. Difficult to implement an infrastructure to exchange between each other for a few trades per months. You can easily start your cooperation with Ethereum Privacy just exchanging each other’s public key and buying a few ethers.</li><li><strong>Loan Syndication</strong>: A corporate lending that is syndicated between multiple banks, and later to investors, can be privately shared in the public blockchain with all actors, signed and the life cycle of the financing followed throughout the years of this kind of product without investing in large infrastructure.</li><li><strong>Issuing diploma</strong>: The details of the diploma can become numeric (rather than the hash of a document) and to get access to a diploma, someone should share its public key and will be granted access to that particular record at any point in time.</li><li>You have an idea, share it and let’s see if it applies</li></ul><h4>How does it work ?</h4><p>Let’s dive into the technical scheme making this possible.</p><p>It is principally based on a mix of symmetrical and asymmetrical cryptography applied on event sourcing architectural scheme.</p><p>Symmetric encryption for what should be shared by several parties, private key signature to identify the origin of the data and public key encryption for sharing the symmetric encryption key and notifying one party.</p><p>Each actor of the transaction must install and run the Ethereum Privacy node (or connects to one it trusts).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*37RThNvgd7K1TfJnkTeRJg.png" /></figure><ol><li>The initiator prepares a standard Ethereum transactions and sends it to his Privacy Node (pnA) and specify the Privacy Nodes (pnC) this transaction should be shared with</li><li>The pnA node retrieves the public keys of all the target nodes (pnC) from a PKI and adds its own public key</li><li>The pnA node compress then signs the transaction data with its RSA private key, generates a one time use symmetric AES 256 key and encrypt the signed transaction. The symmetric key is then encrypted with the public key for each of the target nodes (pnA, pnC)</li><li>The symmetric encrypted transaction and each asymmetrically encryption of the symmetric key are published into the PrivateTransactions smart contract in the public blockchain (here transaction fee applies) making a permanent record of action.</li><li>The public transactions are transmitted in the P2P network and mined in the public blockchain</li><li>All Privacy Nodes (and anyone else) see a new transaction in the public blockchain, but view encrypted data only without knowledge of who are the recipients.</li><li>All Privacy Nodes attempt to decrypt the symmetric key with its own private key. In case of success (i.e. the transaction is intended for it) else the transaction is simply ignored.</li><li>The sending Privacy Node’s public key is checked against the PKI to ensure it is known and trusted</li><li>With the symmetric key the Privacy Node decrypts the transaction data (signed by the initiator)</li><li>With the decrypted transaction, the Privacy Node injects it in the private local blockchain where the effect takes place.</li></ol><h4><strong>Want to get involved or know more ?</strong></h4><ul><li>This prototype is the result of research done by <a href="https://www.linkedin.com/in/guenoledecadoudal/">Guénolé de Cadoudal</a> and is intended to be open-sourced.</li><li>Get in touch via <a href="https://www.linkedin.com/messaging/compose/?recipient=guenoledecadoudal">linkedIN messages</a> or via <a href="/service/mailto:guenoledc@yahoo.fr?subject=Ethereum%20Privacy%20Project">guenoledc@yahoo.fr</a></li><li>Leave feedbacks directly on <a href="https://gitlab.com/guenoledc-perso/offchainprivatetx/website/issues/new">gitlab issues</a> or by sending emails to <a href="/service/mailto:incoming+guenoledc-perso-offchainprivatetx-website-11341400-issue-@incoming.gitlab.com">gitlab issues</a>.</li><li>Git repo is on <a href="https://gitlab.com/guenoledc-perso/offchainprivatetx">gitlab.com</a> and is open for clone, fork and issue submission. Anyone wishing to contribute can be added to the repo by asking</li><li>You can also <a href="https://etherdonation.com/d?to=0x1a1a265c772bbfa736013a62e06172e153502673">donate ETH</a> to contribute to the development efforts</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/310/1*ddnyES5enOS1rtOO5rnEFw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e1a07928453" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ethereum-research/private-transaction-over-ethereum-7e1a07928453">Private transactions over a public blockchain made easy.</a> was originally published in <a href="https://medium.com/ethereum-research">Ethereum Research</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>