<?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 Noha Abuaesh on Medium]]></title>
        <description><![CDATA[Stories by Noha Abuaesh on Medium]]></description>
        <link>https://medium.com/@noha-abuaesh?source=rss-d848de4d36f9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pKfY83iyts4Nls_wqeWtQQ.jpeg</url>
            <title>Stories by Noha Abuaesh on Medium</title>
            <link>https://medium.com/@noha-abuaesh?source=rss-d848de4d36f9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:37:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@noha-abuaesh/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[SSI COVID Passports: Why, What and How]]></title>
            <link>https://noha-abuaesh.medium.com/ssi-covid-passports-why-what-and-how-6f450fddfabf?source=rss-d848de4d36f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f450fddfabf</guid>
            <category><![CDATA[passport]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[vaccines]]></category>
            <category><![CDATA[self-sovereign-identity]]></category>
            <category><![CDATA[health]]></category>
            <dc:creator><![CDATA[Noha Abuaesh]]></dc:creator>
            <pubDate>Fri, 21 May 2021 11:40:43 GMT</pubDate>
            <atom:updated>2021-05-21T11:40:43.741Z</atom:updated>
            <content:encoded><![CDATA[<p>This article assumes that you already know what self-sovereign identity is. It will build on this knowledge to show one possible use case of this technology in the healthcare industry: COVID passports.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PpEj0jSc7mlfP71i" /><figcaption>Photo by <a href="https://unsplash.com/@artem_kniaz?utm_source=medium&amp;utm_medium=referral">Artem Kniaz</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What are COVID Passports and Why do we need them?</h3><p>Due to the public controversy around COVID passports, this can be a loaded question. Add to that the rumors and conspiracy theories that have surrounded and somehow continue to float around COVID-19 in different communities around the world. While I do not have the medical background or authority to confirm or deny any of it, here is what we all know for sure and without denial: We know that many of us lost dear ones to this virus, and many of us suffered its symptoms, or at least know someone who have suffered from it. We also know that this virus is highly contagious. So, regardless of our personal views, we need to take some extra precautions to ensure we do not fall into crises like the one that recently took place in India, for example. Those precautions include social distancing, quarantine, and isolation of the infected and those who were in close contact with the infected.</p><p>When practically applying these safety measures, we find that we need to be able to easily and quickly do the following steps:</p><p>1. Determine the COVID status for the person: a purely medical procedure that states the information about the person’s COVID test results or vaccinations.</p><p>2. Issue personal proofs with the COVID status for each person.</p><p>3. Allow the person to share their COVID information with the entities that they consent.</p><p>4. Allow different entities to verify the authenticity of a given COVID status.</p><p>These steps have become monotonous procedures in the lives of people and organizations. Presenting proofs of immunity, or proofs of negative test results, is now a necessity to access many major services and places. One of the first services that spawned the use of such proofs was the air travel industry; after which these proofs were called “COVID passports”.</p><h3>The need to digitize COVID Passports</h3><p>In a lot of places around the world, a COVID passport is simply a paper document. This has led to a couple of expected problems, one to mention is <strong>forgery</strong>. Paper documents can easily be forfeited, and paper-based COVID passports are no exception.</p><p>Another major concern is <strong>privacy</strong>. Identity verification needs to be done when verifying a paper-based COVID passport to ensure that the presented COVID passport was issued for the intended holder. As a result, people will have to present identity documents alongside the COVID certificates. In an even worse scenario, those who cannot have the vaccine due to specific health conditions will be required to disclose this sensitive information about themselves. For many people, revealing personal and sensitive information to access places and services; like malls, restaurants, cinemas, etc., is just not acceptable. It is considered as an intolerable violation of privacy. In fact, COVID passports did trigger civil unrest in some countries. It goes without saying that <em>a violation of privacy is a threat to freedom</em>. And, certainly, staying safe shouldn’t be at the cost of freedom.</p><p>To wrap it up, paper-based COVID passports — though still used in many places around the world- are not good enough. That’s why we have seen the rise of digital COVID passports.</p><p>Fortunately, technologies like self-sovereign identity(SSI) can help us work things out with COVID without violating privacy.</p><h3>SSI-Based COVID Passports</h3><p>It is true that with the use of digital COVID passports, the probability of forfeiting a test result or a vaccination is almost zero. However, digitalization of and in itself does not guarantee to protect people’s information. Even with the passport now stored in your mobile app, you will still need to reveal some piece of identity matching information to prove that you are the intended passport holder. I have seen some COVID passport implementations that go as far as tracking your geographical location, under the excuse of notifying you if you crossed paths with a newly discovered case. There are a bunch of already in-use COVID passport apps that display users’ full names, dates of birth, identity numbers and other personal information that is unnecessary to prove neither the authenticity nor the ownership of the passports.</p><p>What if people can prove their COVID status to different entities, prove that they are authentic and prove they were intended for them, without having to reveal any of their personal information; not even their names?</p><p>This is possible with the help of self-sovereign identity (SSI). As the name suggests, self-sovereign means users own their data. SSI can give users full control of what parts of their data they want to share and with whom to share it. And because SSI uses strong cryptography alongside with zero-knowledge proofs, we can ensure that the COVID information being shared by an individual is correct, has not been altered, and was issued by the entity it claims to be issued by — regardless of the level of credibility of the issuer. To solve the identity link problem, fingerprint and/or face recognition can be used to verify that the COVID information being shared belongs to the device holder claiming the information to be theirs. This way we can ensure information privacy and security and at the same time fulfill safety procedures.</p><p>Now, the question that logically rises to the top of our minds is: <em>If SSI-based COVID passports can solve the problems frowned upon by many, why haven’t we seen — yet- mass adoption of this idea?</em> To answer this question, we need to understand that SSI is a fairly new technology. From one side, there are difficulties related to healthcare regulation bodies; namely their tendency and agility to adopt a cutting-edge technology like SSI, especially after the chaos COVID caused — and continues to cause- particularly in this sector. From another side, there are questions related to the maturity of the technology itself; especially in regard to portability and interoperability, and whether or not it is stable enough to build upon a project of this size. It is true there has been a number of initiatives and aggregate efforts to build a large-scale SSI solution for the COVID passport issue. But these efforts are yet to be deployed in real life. As a matter of fact, none of these initiatives are officially released for mass adoption as of the writing of this article. The key to mass adoption is the approval of healthcare authorities in public sectors that remains in the hands of government decision makers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f450fddfabf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“reason”:”client request invalid: InvalidClientRequest(…)” Errors when writing to a Hyperledger…]]></title>
            <link>https://noha-abuaesh.medium.com/reason-client-request-invalid-invalidclientrequest-errors-when-writing-to-a-hyperledger-ee4ac680a409?source=rss-d848de4d36f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee4ac680a409</guid>
            <category><![CDATA[indicio]]></category>
            <category><![CDATA[indy]]></category>
            <category><![CDATA[hyperledger]]></category>
            <category><![CDATA[sovrin]]></category>
            <dc:creator><![CDATA[Noha Abuaesh]]></dc:creator>
            <pubDate>Wed, 24 Feb 2021 05:21:22 GMT</pubDate>
            <atom:updated>2021-02-24T05:21:22.277Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>“reason”:”client request invalid: InvalidClientRequest(…)” Errors when writing to a Hyperledger Indy’s Ledger</strong></h3><p>Most of us developers know that, sometimes, error messages can be confusing. Indy is no exception.<br> To save you the hassle of it, I’m listing here the errors I faced when I tried to write to an Indy ledger for the first time, and how to solve them, with a brief explanation whenever I could.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ywQnsqrDQlYrvpBc" /><figcaption>A Ledger Photo by <a href="https://unsplash.com/@sigmund?utm_source=medium&amp;utm_medium=referral">Sigmund</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a> — Just for fun.</figcaption></figure><p><strong>Error 1 — “reason”:”client request invalid: InvalidClientRequest(‘validation error [SchemaField]: invalid number of parts 1, should contain 2 or 3 (version=1)’,)”</strong></p><p>This error happened when I was trying to write a schema to the ledger.<br> <br> “Versions must have at least 1 dot in them, but could contain as many as 2. The version string must look like a version, apparently. In other words, if your schema version was “1”, change it to “1.0” and that should do the trick. Well, at least it did the trick for me.<br> <br> <strong>More about it:</strong> I looked for documentation to support it, but couldn’t find it. If it wasn’t for Lynn Bendixsen and Adam Burdett <em>from </em><a href="https://indicio.tech/"><em>Indicio Tech</em></a> (A cool Indy implementation that offers you a free testnet and people like Lynn and Adam who are willing to help you out just because), this could’ve gotten the best of me — and the best of everyone who came here by googling this error!</p><h4><strong>Error 2— “reason”:”client request invalid: InvalidClientTaaAcceptanceError(‘Txn Author Agreement acceptance is required for ledger with id 1’,)”</strong></h4><p>Because writing to a ledger is permanent for life, you should sign a transaction author agreement every single time you want to write to an Indy ledger. And this is my implementation of it in python:</p><p><em>#####################################<br>async def add_taaAccept(request):<br>print(“ — — — — — — -TAA PROCEDURE — — — — — — — — — “)</em></p><p><em># 1. Get Latest TAA from ledger<br>taa_request = await ledger.build_get_txn_author_agreement_request(issuer[‘did’], None)<br>latest_taa = await ledger.sign_and_submit_request(issuer[‘pool’], issuer[‘wallet’], issuer[‘did’], taa_request)<br>print(“Step A — TAA Retrieved “)</em></p><p><em># 2. Get Acceptance Mechanisms List(AML)<br>acceptance_mechanism_request = await ledger.build_get_acceptance_mechanisms_request(issuer[‘did’], None, None)<br>aml = await ledger.sign_and_submit_request(issuer[‘pool’], issuer[‘wallet’], issuer[‘did’], acceptance_mechanism_request)<br>print(“Step B — AML Retrieved “)</em></p><p><em># 3. Append acceptance to your request<br>latest_taa = json.loads(latest_taa)<br>taa_digest = latest_taa[‘result’][‘data’][‘digest’]<br>aml = json.loads(aml)<br>timestamp = aml[‘result’][‘txnTime’] # Getting the time from the AML tx<br>timestamp = int (timestamp/(60*60*24)) #Need to set timestamp to beginning of the day to reduce corratability risk<br>timestamp = timestamp*60*60*24 #return back to POSIX timestamp</em></p><p><em># Values for Txn Author Agreement acceptance mechanism is one of:<br># [‘at_submission’, ‘click_agreement’, ‘for_session’, ‘on_file’, ‘product_eula’, ‘service_agreement’, ‘wallet_agreement’]</em></p><p><em>request = await ledger.append_txn_author_agreement_acceptance_to_request(request, None, None, taa_digest, ‘at_submission’, timestamp)</em></p><p><em>request = await ledger.sign_and_submit_request(issuer[‘pool’], issuer[‘wallet’], issuer[‘did’], request)</em></p><p><em>print(“Step C — TAA Appended to your Request “)</em></p><p><em>print(“COMPLETED TAA PROCEDURE — — — — — — — — — — “)</em></p><p><em># 4. Return appended request<br>return request<br>#####################################</em></p><p>So now, you just call this function before submitting a writing request to the ledger to get rid of this error.</p><p>Now this is something they added in 2019. Before the 2019 changes, you just had to accept the TAA once; when connecting to a pool, and that was it. So, you won’t find this extra step in the famous one-and-only Alice-Faber-Acme-Thrift example. You will only find that if you carefully read the documentation that was written after 2019 (or had someone like Lynn <em>from </em><a href="https://indicio.tech/"><em>Indicio Tech</em></a> (A cool Indy implementation that offers you a free testnet and people like Lynn who are willing to help you out just because), to give you hints when you run into trouble.</p><p><strong>More about it: </strong>I found these 2 links talking about the TAA updates:<br> <a href="https://github.com/hyperledger/indy-node/blob/master/docs/source/requests.md#transaction_author_agreement">https://github.com/hyperledger/indy-node/blob/master/docs/source/requests.md#transaction_author_agreement</a><br> and<br> <a href="https://github.com/hyperledger/indy-node/blob/master/docs/source/requests.md#common-write-request-structure">https://github.com/hyperledger/indy-node/blob/master/docs/source/requests.md#common-write-request-structure</a></p><p><strong>Error 3— “reason”:”client request invalid: InvalidClientTaaAcceptanceError(‘Txn Author Agreement acceptance time 1612822227 is too precise and is a privacy risk.’,)”</strong></p><p>When appending the TAA acceptance to your request, the timestamp shouldn’t be the exact current time of accepting the TAA. The reason is the risk of getting to know who you are by following the pattern of you writing to the ledger. So, the timestamp should be the time of the start of the day of accepting the TAA. Check step 3 in the implementation above.</p><p>Sovrin documentation states: “Similarly, the application should not provide the time the user accepts, but only the day. Correlation risk can be further reduced by tracking a different acceptance date per DID on the ledger, or regularly asking the user to reaccept the agreement in order to change the acceptance date — although we acknowledge these approaches may increase the user’s friction when writing to the ledger.” <br> <br> <strong>More about it:</strong> <a href="https://sovrin.org/preparing-for-the-sovrin-transaction-author-agreement/">https://sovrin.org/preparing-for-the-sovrin-transaction-author-agreement/</a></p><p><strong>Error 4 — “reason”:”client request invalid: UnauthorizedClientRequest(‘The action is forbidden’,)”</strong></p><p>This basically means that you are trying to write some duplicate information to the ledger, for example, a schema/credential definition that already exists on the ledger with the same exact ID that.</p><p>To fix this error, you can just change the schema version(or credential definition name) you are trying to write to the ledger. Or, if you don’t need a new version, consider retrieving the old one from the ledger.</p><p>If you faced other problems, please leave a comment below about it, and I will add them to the list inshallah. Let’s try and make this easier for those who come after us!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee4ac680a409" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How can I prove my ownership to my house (or to anything) just by providing some numbers?]]></title>
            <link>https://noha-abuaesh.medium.com/how-can-i-prove-my-ownership-to-my-house-or-to-anything-just-by-providing-some-numbers-87fc82a915c3?source=rss-d848de4d36f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/87fc82a915c3</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[marketplaces]]></category>
            <category><![CDATA[zksnark]]></category>
            <category><![CDATA[sell]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Noha Abuaesh]]></dc:creator>
            <pubDate>Tue, 08 Sep 2020 21:10:53 GMT</pubDate>
            <atom:updated>2020-09-08T21:10:53.864Z</atom:updated>
            <content:encoded><![CDATA[<h3>How can I prove my ownership to my house by simply providing 2 numbers?</h3><p>Dear Students in Udacity’s Blockchain Nanodegree,</p><p>You have every right to wonder how can the capestone project help sell real houses on the Ethereum blockchain. Because I was going crazy wondering that too, until I got this idea.</p><p>Dear Everyone Else,</p><p>If you are not yet familiar with Udacity, I advise you to get yourself familiar with them. They are good. They saved me during a mandatory life-change. But that’s not our point now. We are here to talk about their capestone project in the blockchain nanodegree (that I am about to finish inshallah). I want to talk (and hear from you in the comments) about how, with the impossible hypothesis it makes, can it potentially be used in real-life?</p><p>If you are not familiar with the capstone I am talking about, it basically aims to create a marketplace for real-estate owners to buy and sell their properties safely on the Ethereum blockchain. Here’s how:</p><p>1. The property owner provides their property’s ID (say a ZIP code or any code unique to their property.)</p><p>2. They also provide an undeniable proof that they are the true owner for this property. For generating this proof, they will use zk-SNARKS that we talked about in<a href="https://medium.com/@noha.abuaesh/zk-snarks-how-can-knowing-some-numbers-prove-the-truth-about-anything-in-real-life-bd4cce15710f"> this article</a>.</p><p>3. The user clicks “Mint Token”, et voila, they have their real-life property represented as a unique token owned by them on the Ethereum network.</p><p>4. The owners can now sell their token in OpenSea: a virtual marketplace dedicated for buying and selling Ethereum tokens that represent and hold true value in real-life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GV6oec3Jhv_veGkviWOSYw.jpeg" /><figcaption>A DAPP to tokenize your real-estate.</figcaption></figure><p>P.S. Yes, it can be this simple to buy and sell houses if we adopt the blockchain technology <em>correctly</em>.</p><p>Cool! Except for a tiny problem that has been ruining the party; which is: <em>the silly verification criteria used to prove ownership of the property.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YzKOzHwxEMImprhE8TiH3g.gif" /></figure><p>The project requires the owner to provide two secret numbers to prove their ownership to the property, such that the second number is the squared value of the first. Wait — are we seriously pretending that a number and its squared value are considered a good evidence for proving ownership of real-world property? <em>Really</em>? This is absurd to the point that it becomes confusing.</p><p>In the project’s defense, I would say it was simplified for practice purposes, and of course it shouldn’t be done this way in a real DAPP. But how exactly should this be done if we are to apply it in a real DAPP?</p><p>I agree that there should be some clarification from Udacity’s gurus on how this mysterious step can possibly be done in the real world, instead of leaving us miss the point and fail to see the real importance of zk-SNARKS in our project. For now, let us try to figure this out ourselves. This is how I think about it:</p><p>The usual government entity authorized to issue paper-based title-deeds for property owners will now have to do more than just stamp the deeds. They are going to have to issue with each title deed a unique secret number, or set of numbers, called witnesses. These witnesses are to be given in private only to the property owner; who will use them to generate the proof that the they can submit whenever they need to prove their ownership to the property, for example mint a token for the property. It goes without saying that this same government entity — say the ministry of housing for instance- will have to provide the verifier contract that can easily tell the true proofs from the false ones.</p><p>I believe this is one way things can work. Please share with me in the comments other ways you believe this puzzle can be solved. Thanks and good luck in your project 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87fc82a915c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[zk-SNARKS: How can knowing some numbers prove the truth about anything in real-life?]]></title>
            <link>https://noha-abuaesh.medium.com/zk-snarks-how-can-knowing-some-numbers-prove-the-truth-about-anything-in-real-life-bd4cce15710f?source=rss-d848de4d36f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd4cce15710f</guid>
            <category><![CDATA[zksnark]]></category>
            <category><![CDATA[zokrates]]></category>
            <category><![CDATA[celebrity]]></category>
            <category><![CDATA[trustless]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Noha Abuaesh]]></dc:creator>
            <pubDate>Thu, 27 Aug 2020 18:39:06 GMT</pubDate>
            <atom:updated>2020-08-27T18:39:06.414Z</atom:updated>
            <content:encoded><![CDATA[<p>In the simplest way I can think of, this article will explain the need for, and the concept behind zk-SNARKS.</p><h3>1. What problems can zk-SNARKS help solve?</h3><p>zk-SNARKS help us prove that we are telling the truth about something without having to reveal that specific thing. Here is a scenario:</p><p>Imagine that I am the best buddy of a famous celebrity. And I keep bragging about it everywhere. But, unfortunately, a lot of people don’t believe me and think I am just making this up to get some attention. This really hurts me, because I know that I am telling the truth, so I try to prove it to them by saying: “<em>Hey, I have their personal phone number!</em>”. But they still don’t believe me. They say: “<em>Unless you give us that number and we try calling this celebrity and make sure they pick it up, you don’t have a good enough proof for us to believe you.</em>” Now, I am in a very bad situation, because if I give them the number, I am going to lose my friend’s trust for giving away their personal phone number to random strangers. But, if I don’t give them the number, they will never believe that I am telling the truth. I need to prove to them that I know the celebrity’s phone number, without actually letting them know the number itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/328/1*w8qBkW7n4C9YQ-jlqMTMDQ.jpeg" /><figcaption>A blindfolded cat.</figcaption></figure><p>This is exactly why zk-SNARKS are here, remember: <strong>to help us prove that we are telling the truth about something without having to reveal that specific thing.</strong></p><blockquote>“You must trust and believe in people or life becomes impossible.”</blockquote><blockquote>— Anton Chekhov</blockquote><h3>2. How can zk-SNARKS solve this problem?</h3><p>To solve this problem, I can call my celebrity friend in-front of those people(without letting them see the screen to keep the phone number hidden from them),and put the call on loud speaker to let them listen to me actually talk to my friend. But this solution will still bug my celebrity friend. I can’t just keep calling my celebrity friend whenever I want to prove to somebody that I know her, especially that I want to prove it to the whole world, since I am a very big bragging mouth. Plus, it’s also not a good idea to use your friends like this without their knowledge.</p><p>So, I decided to talk to my celebrity friend about it. I went to her and said: “<em>Hey, I am so proud to be your friend, and I want everybody to know that we are best friends forever. But they don’t believe me. Is it OK with you if I keep calling you to prove it to others?</em>” My friend of course refused. This made me so sad. But my friend is a kind person. She said: “<em>I will really hate if you keep calling me at random times with random strangers listening to our call. And of course I do not want you to give my number to anyone. But, I will help you prove to others that you have my phone number. Let’s talk to my technical advisor who can find smart solutions for every problem.</em>”</p><p>Her technical advisor suggested adding a special section on her official web-page to securely verify her phone number, such that if anyone enters the correct phone number for the celebrity in that secured field, it will display a message confirming that they indeed entered the correct number.</p><figure><img alt="This is how the technical advisor proposed to verify if anyone knows the celebrity’s phone number." src="https://cdn-images-1.medium.com/max/898/1*Yyb0j_Y7l157ar4ACiP-Xg.jpeg" /><figcaption>Thanks to this feature on my friend’s page, I can now prove to anyone that I know her phone number without having to reveal it to others.</figcaption></figure><p>Finally, I can now prove to the whole world that I know the celebrity’s personal phone number without actually revealing it to anyone, and without having to get back to my friend every time I do it! In a way, zk-SNARKS does the same thing that this little script does: verifies the truth without having to reveal it. But of course, there are some different details to it.</p><h3>3. Exactly, how does zk-SNARKS work?</h3><p>Well, of course zk-SNARKS are not web-based scripts. One very important feature of zk-SNARKS is that they are very secure and it is very hard (i.e. impossible)to hack them. So, if my celebrity friend wants to ensure that her phone number stays totally private, and that none of her proud bragging friends have to type it in an online form with others watching as they type, she will have to do more than just add the feature to her official website. Again, we speak to her technical advisor who suggests using zk-SNARKS.</p><p>First, we had to find a way to encode the phone number to a form that no one can figure out the original number by just looking at it. This form is called a “proof”. It is like an undeniable certificate that represents the original piece of information(my friend’s phone number). So, we wrote a program that takes in a phone number, and generates its proof. Now I can keep this proof with me and take it out whenever I want to brag about knowing my friend’s number. Next, we needed to write some code to construct a verifier: a “program” — actually a smart contract- that takes a proof as input, process it, and then tells us whether or not the proof is accepted; i.e. this proof was constructed based on the correct phone number or not.</p><p>Now, my friend is not afraid of her private phone number being exposed to hackers online or typed infront of others, because now I only need to give my proof(which is an complicated encoded version of the phone number). Here is how her web-page looks like now:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/898/1*HpA1Suv_O-0iY_ayPHwl3A.jpeg" /></figure><p>By that, our analogy is over. I hope you were able to understand why we need zk-SNARKS, and how they can enable us take a couple of steps further in building trustless applications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd4cce15710f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>