<?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 Syed Mohd. Qasim on Medium]]></title>
        <description><![CDATA[Stories by Syed Mohd. Qasim on Medium]]></description>
        <link>https://medium.com/@smdqsm?source=rss-4cdefe5508b7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*v6fkfCu-ns1eq69a.jpg</url>
            <title>Stories by Syed Mohd. Qasim on Medium</title>
            <link>https://medium.com/@smdqsm?source=rss-4cdefe5508b7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:55:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@smdqsm/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[Why to use Quorum as a blockchain based private messaging service.]]></title>
            <link>https://medium.com/@smdqsm/why-to-use-quorum-as-a-blockchain-based-private-messaging-service-13b18d481671?source=rss-4cdefe5508b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/13b18d481671</guid>
            <category><![CDATA[permissioned-blockchains]]></category>
            <category><![CDATA[private-messaging]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[quorum-blockchain]]></category>
            <category><![CDATA[consensus-algorithm]]></category>
            <dc:creator><![CDATA[Syed Mohd. Qasim]]></dc:creator>
            <pubDate>Thu, 14 Mar 2019 14:30:34 GMT</pubDate>
            <atom:updated>2019-03-19T11:43:35.038Z</atom:updated>
            <content:encoded><![CDATA[<p>JP Morgan’s Quorum offers one, the ability to deploy contracts privately, and perform transactions on that contract privately and even between subsets(you can perform transaction between {A,B},{A,C},{A} even if you deployed private contract between {A,B,C}.). But it lacks a key feature: <strong>consensus on private transactions</strong>. Unlike ethereum (on top of which it is built) it does not guarantee that only passing transactions will be written and propagated inside the block to other nodes; so even if a transaction is failing on every node it will be there inside that block.This can cause some serious confusions lets discuss this further in the light of this example.</p><p>Let us deploy a simple contract Bob’s Apple Basket. Bob wants to sell apples privately to Jack and Jill and he has 100 Apples with him. So, this Quorum network has 3 nodes for now. Bob’s, Jack’s and Jill’s. now if chronologically</p><ol><li>Jill privately buys 60 apples from Bob.Now in Bob and Jill’s private state they both have 40 and 60 Apples respectively.And Jack knows that Bob still has 100 Apples.</li><li>When Jack privately Buys 70 apples from Bob, The transaction passes on his node making his state as Bob:30 and Jack:70. but it fails on other two nodes.and their state is still the same as Bob:40 and Jill:60.</li><li>Now here because the transaction will pass on jacks node he gets a <strong>false sense that he has bought the apples</strong> but when the transaction goes to Bob he declines it.</li></ol><p>There is more to this conversation. How do you reach consensus in a private transaction. If you apply 51% to it, It can mean that a transaction happening between 3 parties failing on one and passing on other two will be a valid transaction to the network. It can in turn mean that two people agree on something and the other one does not and the network says that this transaction happened successfully.</p><p>The example of Bob shows that privately deployed contracts have serious problem of integrity. According to the network, all transactions happened.</p><p>This problem arises out of the fundamental architecture of quorum having a public and private state and handling consensus only for the public part.(If Bob’s Apple Basket would have been public this difference in states would have never happened).</p><p>If we take a step back and take a bird’s eye view, we can say that how can we reach consensus on something that is hidden to us. and that only few people know about it.The answer to this questions is not simple. One solution could be to have veto at constellation/tessera/any privacy manager level and along with acknowledgement of private payload also get the status of the transaction, whether the node is okay with it. If it is not maybe that transaction is vetoed, I chose to veto it because currently even if one node is down in the “privateFor” the transaction is unsuccessful and it aligns with that analogy.</p><p><strong>But where is messaging in the picture?</strong></p><p>We saw that private smart contracts will result in different state and can lead to Integrity problems so relying on them in quorum is not a smart move. I would say that each node processes the private transaction according to their private state. a private transaction is a message that is received by the node and the node chooses what to do with it.</p><p>We can instead move the private state outside of our blockchain to an RDBMS and mutate it according to our business logic.We can use the Quorum’s private transactions to just pass messages privately on run time and our application listening to events emitted/messages by our blockchain node decides what to do with that message.This would at least not give a false positive sense.</p><p>So now when Jack sends the private transaction on the network he won’t get the false sense that the transaction successfully passed (because it had earlier passed on his node).Now the transaction will be more of a message that Jack wants to Buy apples from Bob. and Bob can then again send out a private message to bob saying that its not possible as he has only 40 left and you want 70.This sending another transaction in response to previous transaction can be easily achieved by maintaining the state outside and help in providing integrity till there is no way for a type of consensus on private transactions but ….</p><p>What if the transaction is between N members. Using this everyone will have to send out a transaction in response to the original transaction that means for a single transaction between N parties we will be making N transactions to achieve a consensus on that single transaction.This will be a tedious thing to do, but because we don’t have consensus for private transactions at blockchain we would have to implement it at application logic level.</p><p>HyperLedger does provides us with private channels and has logic outside but those channels are predefined. Quorum can be a better secret message propagation medium for a Consortium because privateFor¹ is at transaction Time(runTime).</p><p>Quorum will be a good messaging service for consortium’s, It offers the features of immutability, non repudiation and resilience of blockchain plus private messaging.It will work good for consortium’s with fewer members as the message passing will not be very efficient if the size of the cluster grows to say 5,000 nodes.</p><p>1.“PrivateFor” : it is an additional parameter introduced in quorum which specifies that this particular transaction will be private for which participants. Please see here for more <a href="https://github.com/jpmorganchase/quorum/wiki/Transaction-Processing">details</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13b18d481671" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>