index2.ipynb

{"cells":[{"metadata":{},"cell_type":"markdown","source":"Online appendix of the \"Innovative financial design using encryption\" outline - interactive tutorial on replacing the trusted third parties through homomorphic encryption, auctions without auctioneers case\n============\n-----\n\n\n#  Summary \n\n\nThe goal of this notebook is to provide a prototype illustrating how homomorphic encryption coupled with multiparty computation would allow mechanism design schemes that do not rely on the \"mythical central planner\". **For instance auctions ran without an auctioneer acting as trusting third party, but organized by the participating parties themselves**. One can then use such a decentralized auction to automate and improve OTC auctions, for example those operating under BWIC (\"bids wanted in competition\"), which are **prone to misreporting and collusion/conflicts of interest** (*see for instance \"Public Sector Pension Investment Board of Canada v. Saba Capital Management\"*).\n\nIn fact, we will see further that beyond just improving auctions, **such schemes of \"trust and cryptography\" can allow many more exchanges of *economic contracts* themselves** - which will better distribute risk and allocate ressources, according to optimal mechanism design principle rather than contingent to regulatory captures and power brokering. Indeed, we will see how **current *institutional* solutions to these mechanism design problem (e.g. creating a trusted third party collecting bids, and guaranteeing their privacy and fair matching) are either too expansive for many potential applications (SME financing for once), or too susceptible to frauds due to strong weaknesses and negative incentives.**\n\n\n--\n# General structure of notebook :\n\nPart I : specify axioms that are required by some econ application  \nPart II : specify what each piece of encryption technology brings as potential solution to each of the axioms above  \nPart III : using the auction example, see how the different pieces of encryption can be used to improve existing econ applications\n\n\n--\n# Part I : \"Hybrid systems of \"trust and cryptography\" to allow many more exchanges of *economic contracts* themselves - let's define \"*contract*\" :\n\nContracts as agreements between agents. \n\nThe different environments in which these contracts are agreed upon define very different types of contracts. For instance one might ask for any given contract whether it is \"*an informal or formal contract ? Between agents that personally know each other, or through impersonal markets and third parties ?*\" \n\nIndeed if we look for instance at individual debts - an exemple of such economic contract -, being in a village/roomating economy setting in which neighbours temporally helped you out, without expecting an *exact* financiary repayment at *an exact* time, produce a very different form of contract than if the debt was contracted along impersonal markets with \"foreign\" entities - people we don't know personally, with whom there is no preexisting history of trust nor incentive for future collaboration - so sets of rules and guarantees are needed to enforce the repayment by the borrower.\n\nOur goal will be to facilitate the transition from the first \"natural\" village/roomating economy setting to impersonal markets, so that individuals and firms can access more borrowing and lending, insurance, but also consumer services.\n\n**For this transition here we lay out an axiomatic approach of the requirements to be satisfied**. For instance, as mentioned above, sets of rules of guarantees to create trust in the correct execution of the contract. **The correct execution of a contract can be defined as:**\n- one as specified originally by the terms of the contract (ie the contract enforces \"commitment\" on agents, for them to respect the outcomes of it) \n- one that acted on true inputs (and not manipulated/misreported inputs, or lies - ie the contract is manipulation and strategy-proof)\n        \n**Let's now link these requirements for a \"correct\" execution of a contract to this contract's life cycle - so that we can see how these requirements translate to within each step of the contract's life cycle.**\n        \n**1) PRE-TRANSFER : how to negotiate, set up a contract, set up a commitment/collateral scheme** \n\n*what is required there :* <br/> \n- ways to collect information\n- ways to collect information while retaining privacy (FHE-MPC for instance, or trusted third party acting as negotiator/matching engine) \n\n*potential conflicts between stage 1 and stage 2 :* <br/>\n- how to collect/aggregate data that is private\n- solutions :     \n    - privacy-preserving aggregation/computation\n    - setting up a third party with a clear mandate\n\n**2) ACCOUNTING INFRASTRUCTURE** \n\n*what is required there :*\n- some forms of privacy ! (hence the zk \"patch\" to public ledgers)\n\n*potential conflicts between stage 2 and stage 3 :*\n- Michael Lee's example : the agent giving up the asset has to reveal what he has\n- solutions :\n    - banks will check if you have the balance (\"trust the broker dealer\", who might sell or reveal your info. Recognized such as on the JP M/or one of these big banks broker dealer platform who have a clear mandate to retain privacy)\n\n**3) TRANSFER INFRASTRUCTURE**\n\n**These three stages can be independantly designed.**\n\n**With the list above detailing a contract's lifecycle, we can see that current issues and areas of improvement mainly lies with the \"potential conflicts between stage 1 and stage 2, and that relates to the private nature of sensible information.** \n\n\n\n\n--\n##  So the following problem statement : a lack of information infrastructure for accessible and/or secure financial systems , as a consequence of inadequate handling on private information in current systems\n\n\nNB: SME funding problems : many too small to be interesting clients to banks (the required audit work being too costly compared to the amount of funding in question)\n\nEven for big firms : asymmetry in demand when trying to get funding (ex when reaching out to investment banks to organize IPOs)\n\n**Because : the symmetric problem of borrowing and lending (some agents need liquidity, whereas some others have excess liquidity that they want to invest) became asymmetric**, as the borrower *has* to go reach out to potential lenders, which are therefore given some increased negotiation power (they **don't have to** reveal how much they *have* to invest to satisfy their mandate/business objectives, whereas the potential borrower *has* to reveal its funding needs).\n\n**Problems of existing P2P lending platform :** bad security against frauds, capture by some parties, and bad incentives introduced  by business/growth objectives. See sections on problems encountered by institutional solutions like trusted third parties as matching engine.\nExisting P2P lending platforms are also \"one size fit all solutions\" that don't respect the natural truth groups/the heterogeneous nature of company sizes/graphs. It would be better to have a bottom-up solution, in which firms can organize themselves funding platform within their natural group.\n\nOur notebook here outlines a set of solutions to all the above.\n\n**Most important is the definition of a hybrid privacy-preserved information state still accessible to mechanism design optimization computations, in which a piece of information can be kept private while still taking part in some computation.**\n\nThis way, we can start outlining a platform on which potential borrowers can enter their funding needs (which will be encrypted right from the start, so kept private all the time to all but themselves), on which potential lenders can enter their lending objectives (which will also be encrypted right from the start, so kept private all the time to all but themselves), and the platform (potentially distributed among all participants, to make it \"decentralized\" hence secure against capture) performing homomorphic computation (ie computation on top of these encrypted data, which give encrypted results that once decrypted also happen to be the correct results of what these computation on top of unencrypted data would be. More on this in relevant sections below) such as dual matching, ranking, etc.\n\n**So better allocation of resources and risks according to each one's needs.**\n\nThroughout the rest of this notebook we will illustrate this process with the simplest of dual-matching platform, that of an auction (and use them to illustrate both the problems mentioned above and our solution).\n\n--\n\n#  Part II : the use of encryption as a solution to \"*misreporting and collusion/conflicts of interest*\" :\n\n\n**For the first part (\"*misreporting*\"), encryption allows ledgers as financial accounts to be altered with transfers done in a secure way**, which can even ensure privacy (if designed to be so). **For the second part (\"*conflicts*\"), with encryption we can implement optimized contracts and solutions to multi-agent mechanism design problems**.\n\nIn fact, the idea and practice of encryption is ancient, with applications similar to contemporary analogues. **Let us thus describe here through two introductory and historical examples** - that of Mesopotamian clay tokens in sealed envelopes as invoices to accompany the shipment of goods, and that of split English tally sticks to convey debt in such a way as to allow it to be passed through third parties for presentation - **the use of encryption as a solution first to \"misreporting\" (through Mesopotamian clay tokens) and \"conflicts\" (through English split tally sticks)**.\n\n- **Encryption and misreporting : the example of *the Mesopotamian clay tokens* :**\n\nThe idea behind the clay tokens is that tampering by third parties becomes evident by comparing the actual shipment to the envelope. In cases of cheating attempt by the shipper, either the shipments of goods does not match the tokens in the sealed envelope, or the envelop itself is broken. \n\n- **Encryption and collusion/conflicts of interest: the example of *the split English tally sticks* :**\n\nThe idea behind the willow tally sticks is that the uniquely grained wood branches are spit into matching halves as records of the same underlying transaction. One of the halves remains with the issuer/borrower and the other half given to the original lender investor. The latter circulated in the public as money before redemption, with redemption by a third party extinguishing the original debt, but only when the halves matched (the wood's natural cryptographic function thus guaranteeing that **for each half there's only one and one unique other half, thus preventing problems like double spending** - since reproducing prefectly the natural grain of a split wood branch was considered a hard enough problem).\n\nIn this case collusion and conflict of interest can be thought for instance as two people (the \"colluded parties\") who jointly issue tally sticks, with some arbitrary value on them, without intent of redeeming them back together (so, in a way, printing themselves \"free debt/money\"). **Indeed, collusion can be seen as two people trying to \"beat\" the rest of the market together. These two parties will then try to exchange both halves of the split tally to get themselves free money or goods.**\n\nHowever, by making the two halves of the stick of different lengths - the longer part being called stock and being given to the party which had advanced money (or other items) to the receiver, and the shorter portion of the stick being called foil and being given to the party which had received the funds or goods - and by making these two halves very distinct from each other - so that potential \"buyers\" can recognize wether the offered half is a debt or a credit - these \"freely\" generated split tally sticks are prevented from getting \"free money or goods\". Hence here it is the authentification of each half of the tally stick (as being debtor or creditor) that guaranteed that both the asset and liability sides of the tally sticks will always be respected. The clear and fraud proof accounting hence prevents collusions and conflicts of interest. Similarly, the fact that the original names of the debtors/creditors have been marked on the split tallys guarantee in some ways that the debtor side of the colluding party can't hide, lie about not having it, or refuse to redeem the creditor side of the tally, when presented to him (and people will not accept a tally with brushed/unclear names on it as an authenticate token). \n\nIn this example thus, authentication schemes are what prevent collusion and conflicts of interest. We will see below how this authentication can - hence the interest of privacy-preserving schemes.\n\nFurthermore, let's also note that the untampering property of split tally stick - similar to the clay token example above - also prevents price/quantity manipulation variants, as after one tally stick has been split there's no way to modify the value of only one of its half without modifying the value of the other half.  \n\n\n\n##  Systems of \"*trust and cryptography*\"\n\n\nIn each of these ancient systems, there are thus **elements of trust - first in the sense of *fulfilling a commitment***, for instance in the fact that the borrower will repay the loan to original investor or verified third party. But this commitment problem is furthermore mixed with the need for encryption to deal with nefarious behavior from non-trusted parties in between, that is, surreptitiously pilfering goods or the counterfeiting of promises to pay. **The need of trust thus also further covers the fair functioning of the system** (no misreporting and no possibility of conflict). \n\n**It is only once *both* elements of trust have been secured that *contracts themselves* can be exchanged on some kind of anonymous dual matching exchanges**, which allows human and village economies to grow into financial and mercantilist economies (USE ELEMENTS OF SME REPORT HERE TO HIGHLIGHT THIS POINT).\n\n**One could thus think of these mechanism design settings as hybrid or mixed systems, with both trust and cryptography**. The trust part is enforced through social conventions (servicing one's debt as a moral matter), while the misreporting and conflict prevention part are solved with cryptography. \n\nHybrid systems are likewise used today, for instance through institutional arrangements (think of **trusted third parties operating the dual matching engines, guaranteeing true reporting and fair matching while preserving the privacy of sensible informations that are needed in the process**).\n\n\n\n## Issues of \"*trust and cryptography*\" in the case of existing OTC auctions :\n\n\nLet's first note **the conflict between the need of *preserving privacy* and the need of a *guarantee of true reporting and conflict-proof process*** . Indeed, in institutional arrangement involving trusted third parties, a door remains open for the *trusted* third party to behave in an unfair or an untruthful way.\n\nInstitutional safeguards such as audits have been historically built to prevent this (see literature around village economies as in Townsend, *Medieval village economy* book), but in the case of OTC schemes **the fact that the trusted third party operating the scheme is *also* an active participant on one side of the dual matching engine** (for instance BWIC auctions are often organized by entities looking to sell the asset being the object of the auction) provides strong incentives for misreporting and conflicts of interests.\n\nA classical example in current BWIC auctions - ran over the telephone - would be for the seller of the asset in question (also the organizer of the auction) to tell buyer A : \"I prefer you my friend, but buyer B just offered a *slightly* higher price, so if you can just make *sooome* effort the good is yours\", and vice versa with buyer B to prop the price up. This entire trick resides in the fact that neither buyer A or B can check the bid of the other buyer, hence have to trust the seller/organizer of the auction.\n\nHence the need for an auction scheme which provides to the side (of the dual matching exchange) *not organizing or running the auction* ways to solve the trust issues of potential misreporting of potential conflicts.\n\n\n\n\n## Homomorphic encryption, and privacy-preserving audits to make existing mechanism design conflict-proof\n\n\n- **Homomorphic encryption :**\n\nHomomorphic encryption is **a form of encryption that allows computation on ciphertexts** (encrypted messages), generating an encrypted result which, when decrypted, matches the result of the operations as if they had been performed on the plaintext. I.e., if we perform function f on a message m has been homomorphically encrypted into the ciphertext h(m), we have the equivalence $h^{-1}(f(h(m)))= f(m)$ , or equivalently $f(h(m))=h(f(m))$ .\n\nFor example, one can thus perform operations such as addition on underlying messages m1 and m1, or encrypt each to keep them private, sum the encrypted values, and if desired, decipher to get the original sum. \nIn short the spaces of underlying messages and encrypted messages are isomorphic , allowing computations on privately-preserved data.  \n\n\n- **Public/private key encryption :** \n\nWith a public key for encryption and a private key for decryption  of  a message, algorithms on designated spaces make it virtually impossible to decipher an encrypted message without the private key that  was a key in generating it.\n\nHowever, the public key can be used for authentification and to guarantee integrity and commitment of a message ; in that case, the private key is used to generate a digital signature for a message, and such a signature can be verified by using the signer's corresponding public key. In this way the recipient knows who sent the message. Specifically, the receiver can verify the origin of the message (authentication), that the message has not been modified since it was signed (integrity), and the sender cannot falsely claim that they have not signed the message (non repudiation). To be stressed:  that these are extremely useful properties, all without the receiver ever knowing the private key (hence the content of the encrypted messages).\n\n- **Homomorphic encryption + public/private key encryption :**\n\nHomomorphic encryption with public/private key encryption can thus be used for privacy-preserving outsourced storage and computation. \n\nLet's for instance go back to our BWIC auction example, in which the seller of an asset organizes an auction scheme. However, **to limit the seller's incentives to misreport, each buyer's bid will be encrypted by him using his unique secret key, to prevent anyone else (especially the seller/organizer of the auction, who agrees to not possess each buyer's individual secret key) from tampering with it** - in a similar fashion as the Mesopotamian clay token example before.  \n\nFurthermore, the organizer of this BWIC auction agrees to ***only provide* the matching (or ranking) operation of this auction, performed homomorphically on top of each buyer's encrypted bid**. The encrypted bids thus protect buyers' privacy in both keeping it untampered with, and potentially by keeping them anonymous (if the public/private keys are allocated randomly to each participating agent) to reduce potential conflict of interest and collusion between the organizer of the auction and some participants.\n\n\n- **Secret sharing and different potential decryption schemes :**\n\nA question readers might have thought while reading the above would be on \"who/how to decrypt the results provided by the matching/ranking engine\". Here we will introduce the useful notion of secret sharing (for instance that of Shamir). These are methods for distributing a secret amongst a group of participants, each of whom is allocated a *share* of the secret. The secret can be reconstructed only when a sufficient number, of possibly different types, of shares are combined together; individual shares are of no use on their own.\n\nWith such a method the organizer of the auction (or the participants collectively) can then decide on *who* collectively can decrypt the results : that can be each buyer being able to decrypt *all* results, or a combination of *buyers* required to agree to decrypt the results, or a combination of *buyers* and *seller*...\n\nSuch choice will mainly be influenced from the choice of the IT infrastructure (who manages the server doing the computation) and the incentives introduced by it. \n\n\n- **Getting rid of the central server : multiparty computation**\n\nMultiparty computation is a set of techniques created on top of secret sharing, with the goal of creating methods for parties to jointly compute a function over their inputs while keeping those inputs private. \n\nIn such a setting, all agents will first create a common public/secret key pair together, that matches some collective form of their public/secret keys (with again, the choice of how many of the secret keys are involved, which decide how many of them need to agree to decrypt before decryption is possible). Then each buyer can just send his bid, encrypted with this common public/private key pair, to some or all of the other buyers/sellers. \n\nAnd, by passing these bids around, all agents can end up (homomorphically) computing the matching/ranking engine on all bids on their own servers, compare that with one another's results, and when agreed that they have common results, decrypt these results (with again, the choice of how many of them required to agree to decrypt before decryption is possible). \n\nThis way, the central server is not required anymore to perform the matching/ranking engine !\n\n- **Extension to new possible solutions in mechanism design problem, through a hybrid private-but-contributing-state of information**\n\nLet's note furthermore that in the previously described auction scheme, the secrets, the underlying messages before encryption, need never be revealed to the agent or institution performing the matching/ranking operation (if the scheme allows buyers' to keep their secret private keys secret to all but themselves), which can enhance the protection of privacy and could allow for the design of more sophisticated mechanism design scheme allowing hydrid public-private states of information (as **encrypted inputs kept absolutely private can *still* contribute to operations performed homomorphically on top of them, which would provide previously unaccessible information to the mechanism designer/planner - and hence improved computable solutions.)**\n\n\n--\n"},{"metadata":{},"cell_type":"markdown","source":"\n\n# Part III : Two misreporting and conflict-proof prototype schemes here, that can be adapted at your workplace :\n\nThis notebook provides **two** prototypes of such a misreporting, conflict-proof schemes.\n\nThe first is **entirely self-contained in this notebook**, so that you can see both encryption-decryption code for buyers, sellers, and for the matching engine performing the homomorphic encryption. You can then copy-paste and adapt these pieces of code to be run in any fashion between your buyers/sellers, on an architecture/server of your collective choice.\n\nThe second is more sophisticated, and **show how the homomorphic encryption scheme can generate keys and signatures that can be sent from one user interface (the notebook here) to another (the server performing the homomorphic encryption** - thus not seeing any of the content of the encrypted messages, but still performing a function which will give the correct output once each party decrypts its resulting message). Here the server will be one coded in Flask, with the entire code accessible at github.something... and hosted by Google cloud - but it could be any server that you, your buyers/sellers agree upon (for instance a server only performing homomorphic encryption as described in the section above, and collectively managed by buyers, or with an audit door for them, would prevent any misreporting or conflict of interest).\n\nThe good sold can be anything. We just provided here the prototype to organize such a BWIC auction for selling this good, but without the negative incentives current schemes introduce.\n\n\n## The homomorphic encryption scheme used here \n\n\n**Homomorphic encryption refers to a kind of encryption in which some computation on ciphertexts produces an encryption of the desired computation on the plaintexts** (i.e. f(Enc(messages)) = Enc(f(messages)), in which f can be additive, multiplicative, or more sophisticated functions). \n\nThe Paillier encryption scheme used here is for instance homomorphic over the operation of addition. **Namely, given pk, Enc(pk, m1), Enc(pk, m2) one can efficiently compute Enc(pk, m1 + m2)**. *(see Paillier, Pascal (1999). \"Public-Key Cryptosystems Based on Composite Degree Residuosity Classes\". EUROCRYPT. Springer. pp. 223–238. doi:10.1007/3-540-48910-X_16)*\n\n\n<img src=\"Screen Shot 2020-05-27 at 6.55.54 AM.png\" />\n<img src=\"Screen Shot 2020-05-27 at 6.55.08 AM.png\" />"},{"metadata":{},"cell_type":"markdown","source":"## First prototype : the self-contained code all accessible here :"},{"metadata":{"trusted":false},"cell_type":"code","source":"# Importing the Paillier encryption library from https://python-paillier.readthedocs.io\n\nfrom phe import paillier\n\n# Importing a graphic toolbox to plot the distributions in BWIC auctions\nimport matplotlib.pyplot as plt\n","execution_count":1,"outputs":[]},{"metadata":{"trusted":false},"cell_type":"code","source":"# Now we are starting to build the public and private keys\n\npublic_key, private_key = paillier.generate_paillier_keypair()\n \n# If we’re going to have lots of private keys lying around, then we can use a keyring on which to store our PaillierPrivateKey instances:\nkeyring = paillier.PaillierPrivateKeyring()\nkeyring.add(private_key)","execution_count":2,"outputs":[]},{"metadata":{"trusted":false},"cell_type":"code","source":"# Let's decide how many buyers are participating to this auction. \n# For now let's say 3. If you want more you can just copy paste the code below by adding the number of player 4, player 5, etc\n\n# Let's create for all 3 of them a public key and private key pair :\n\npublic_key1, private_key1 = paillier.generate_paillier_keypair(keyring)\npublic_key2, private_key2 = paillier.generate_paillier_keypair(keyring)\npublic_key3, private_key3 = paillier.generate_paillier_keypair(keyring)\n\n# And the list that will receive their three bids :\n\nsecret_number_list = [None] * 3","execution_count":3,"outputs":[]},{"metadata":{},"cell_type":"markdown","source":"# We are now starting to enter the bids for the good. \n\nHere below the cells are collapsable, so that each of your 3 bidding buyer can \"open\" a cell, input their private values in it, then \"close\" the cell to prevent other players to easily see the value it contains"},{"metadata":{"trusted":false},"cell_type":"code","source":"# Call your bidding buyer 1 and let him enter his bid here (without looking at his value !)\n\nbid_from_player_1 = 13.141592653;\n\n# Let's store that bid in the list of bids\nsecret_number_list[0] = bid_from_player_1\n# Let's print out what the encrypted version of this bid is - it is that encrypted value that will be sent to the server \nencrypted_bid_from_player_1 = public_key.encrypt(secret_number_list[0])\nprint(encrypted_bid_from_player_1)","execution_count":4,"outputs":[]},{"metadata":{"trusted":false},"cell_type":"code","source":"# If we wwant, we can now delete the unencrypted value of the bid from agent 1 to make sure there is no trace of it in the system, and that the server will be doing the computations on the encrypted values of the bids only\n\nbid_from_player_1 = [];\nprint(bid_from_player_1)","execution_count":4,"outputs":[]},{"metadata":{"trusted":false},"cell_type":"code","source":"# Now call your bidding buyer 2 and let him enter his bid here (without looking at his value !)\n\nbid_from_player_2 = 10;\n\n# Let's store that bid in the list of bids\nsecret_number_list[1]=bid_from_player_2# Let's print out what the encrypted version of this bid is - it is that encrypted value that will be sent to the server \nencrypted_bid_from_player_2 = public_key.encrypt(secret_number_list[1])\nprint(encrypted_bid_from_player_2)","execution_count":5,"outputs":[]},{"metadata":{"trusted":false},"cell_type":"code","source":"# Now call your bidding buyer 3 and let him enter his bid here (without looking at his value !)\n\nbid_from_player_3 = 8;\n\n# Let's store that bid in the list of bids\nsecret_number_list[2]=bid_from_player_3# Let's print out what the encrypted version of this bid is - it is that encrypted value that will be sent to the server \nencrypted_bid_from_player_3 = public_key.encrypt(secret_number_list[2])\nprint(encrypted_bid_from_player_3)","execution_count":6,"outputs":[]},{"metadata":{"trusted":false},"cell_type":"code","source":"# Let's now encrypt everything\n\nencrypted_number_list = [public_key.encrypt(x) for x in secret_number_list]\nprint(encrypted_number_list)\n# Now the list of bids has been encrypted using the public key ! It can for instance be revealed without any outside agent being able to decrypt it","execution_count":7,"outputs":[{"name":"stdout","output_type":"stream","text":"[<phe.paillier.EncryptedNumber object at 0x10f210350>, <phe.paillier.EncryptedNumber object at 0x117452c10>, <phe.paillier.EncryptedNumber object at 0x10f1f59d0>]\n"}]},{"metadata":{},"cell_type":"markdown","source":"# A \"decentralized auctioneer\"\n\nThis party does not have access to the private keys, and typically performs operations on supplied encrypted data. It can be a server hosted by the seller, a server hosted by one (or more) of the buyers, or a combination of both. Buyers/seller just need to make sure that this party execute correctly the function assigned to it (here, the ranking) - which is the only thing it can mess (since it doesn't have access to the private keys, it can't tamper with the messages, nor with the identities of the messages senders - which can be kept anonymous if the keys are generated anonymously - for instance via random assignment of public/private key pairs at the start, or any other scheme).\n\nOnce this party has received some EncryptedNumber instances, it can perform basic mathematical operations supported by the Paillier encryption, such as:\n\n- Addition of an EncryptedNumber to a scalar\n- Addition of two EncryptedNumber instances\n- Multiplication of an EncryptedNumber by a scalar"},{"metadata":{"trusted":false},"cell_type":"code","source":"#Let's print out the encrypted number for instance to see that they are indeed \"meaningless\"\n\nencrypted_number_list","execution_count":8,"outputs":[{"data":{"text/plain":"[<phe.paillier.EncryptedNumber at 0x10f210350>,\n <phe.paillier.EncryptedNumber at 0x117452c10>,\n <phe.paillier.EncryptedNumber at 0x10f1f59d0>]"},"execution_count":8,"metadata":{},"output_type":"execute_result"}]},{"metadata":{"trusted":false},"cell_type":"code","source":"# Let's now see homomorphically (i.e. performing the comparison function on the encrypted data) which one of the bids is higher\n\nbid1_vs_bid2 = encrypted_number_list[0] - encrypted_number_list[1]\n\n# You can see that the result is also encrypted, hence meaningless for the outside agent looking at it\nprint(encrypted_number_list[0])\nprint(encrypted_number_list[1])\nprint(encrypted_number_list[0] - encrypted_number_list[1])\nprint(bid1_vs_bid2)","execution_count":9,"outputs":[{"name":"stdout","output_type":"stream","text":"<phe.paillier.EncryptedNumber object at 0x11747a110>\n"}]},{"metadata":{},"cell_type":"markdown","source":"## With homomorphic encryption, a piece of code (or a \"smart contract\") can now perform the role of the auctioneer\n\nSuch a code does not have access to the private keys, but can still perform operations on supplied encrypted data, and hence tell all participating agents which one has the highest bid (if in a single round auction), or provide some information between rounds before the bid updating step in a multiround auction (the distribution of bids at each round, the distribution *without the highest bid* at each round...)...\n\nThis guarantees truthfulness of the auctioneer, full and transparent reporting of the informations that has been decided to be revealed at the end of each round, and better privacy for the bidders on the rest."},{"metadata":{},"cell_type":"markdown","source":"### Example of a single round first-price auction based on the previous 3 bids :"},{"metadata":{"trusted":false},"cell_type":"code","source":"if private_key.decrypt(bid1_vs_bid2)>0:\n    bid2_vs_bid3 = encrypted_number_list[0] - encrypted_number_list[2]\n    if private_key.decrypt(bid2_vs_bid3)>0:\n        print('bidder 1 won the auction')\n    else:\n        print('bidder 3 won the auction')\n        \nelse:\n    bid2_vs_bid3 = encrypted_number_list[1] - encrypted_number_list[2]\n    if private_key.decrypt(bid2_vs_bid3)>0:\n        print('bidder 2 won the auction')\n    else:\n        print('bidder 3 won the auction')\n    \n        ","execution_count":10,"outputs":[{"name":"stdout","output_type":"stream","text":"bidder 1 won the auction\n"}]},{"metadata":{},"cell_type":"markdown","source":"### Example of a multiround BWIC auction based on the previous 3 bids :\n\nEach round of the BWIC auction will be based on two steps : first the submission (or the update) of each one's bid, second the revelation of the distribution of the bids **without the highest bid**."},{"metadata":{},"cell_type":"markdown","source":"#### Use the cell below for the submission (or the update) of each one's bid at each round\n\nHere below the cells are collapsable, so that each of your 3 friends can \"open\" a cell, input their private values in it, then \"close\" the cell to prevent other players to easily see the value it contains"},{"metadata":{"trusted":false},"cell_type":"code","source":"# Call your friend player 1 and let him enter his bid here (without looking at his value !)\n\nbid_from_player_1 = 3.141592653;\n\n# Let's store that bid in the list of bids\nsecret_number_list[0] = bid_from_player_1","execution_count":15,"outputs":[]},{"metadata":{"trusted":false},"cell_type":"code","source":"# Now call your friend player 2 and let him enter his bid here (without looking at his value !)\n\nbid_from_player_2 = 10.141592653;\n\n# Let's store that bid in the list of bids\nsecret_number_list[1] = bid_from_player_2","execution_count":16,"outputs":[]},{"metadata":{"trusted":false},"cell_type":"code","source":"# Finally call your friend player 3 and let him enter his bid here (without looking at his value !)\n\nbid_from_player_3 = 23.141592653;\n\n# Let's store that bid in the list of bids\nsecret_number_list[2] = bid_from_player_3","execution_count":17,"outputs":[]},{"metadata":{},"cell_type":"markdown","source":"#### Use the cell below to produce the distribution of the bids without the highest bid at the end of each round"},{"metadata":{"trusted":false},"cell_type":"code","source":"encrypted_number_list = [public_key.encrypt(x) for x in secret_number_list]\n\nbid_distribution_without_highest = [None] * 2\nbid1_vs_bid2 = encrypted_number_list[0] - encrypted_number_list[1]\n\nif private_key.decrypt(bid1_vs_bid2)>0:\n    bid2_vs_bid3 = encrypted_number_list[0] - encrypted_number_list[2]\n    if private_key.decrypt(bid2_vs_bid3)>0:\n        \n        #if we were in a single round then print('bidder 1 won the auction') \n        bid_distribution_without_highest[0] = secret_number_list[1]\n        bid_distribution_without_highest[1] = secret_number_list[2]\n    else:\n        #if we were in a single round then print('bidder 3 won the auction')\n        bid_distribution_without_highest[0] = secret_number_list[0]\n        bid_distribution_without_highest[1] = secret_number_list[1]\n        \nelse:\n    bid2_vs_bid3 = encrypted_number_list[1] - encrypted_number_list[2]\n    if private_key.decrypt(bid2_vs_bid3)>0:\n        #if we were in a single round then print('bidder 2 won the auction')\n        bid_distribution_without_highest[0] = secret_number_list[0]\n        bid_distribution_without_highest[1] = secret_number_list[2]\n    else:\n        #if we were in a single round then print('bidder 3 won the auction')\n        bid_distribution_without_highest[0] = secret_number_list[0]\n        bid_distribution_without_highest[1] = secret_number_list[1]\n        \nplt.hist(bid_distribution_without_highest, bins = 3)\nplt.show()\n","execution_count":20,"outputs":[{"data":{"image/png":"iVBORw0KGgoAAAANSUhEUgAAAXQAAAD4CAYAAAD8Zh1EAAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAALEgAACxIB0t1+/AAAADh0RVh0U29mdHdhcmUAbWF0cGxvdGxpYiB2ZXJzaW9uMy4yLjEsIGh0dHA6Ly9tYXRwbG90bGliLm9yZy+j8jraAAAOOElEQVR4nO3df6zdd13H8edrLROGE3S9LNgfdAkFadCxcVOnKE7GTDdIa9SQNSEiWah/MEQhmhLN0PkPiPFXMtEGcIiyWaZoI5VBYLrEuLk7NubaUryWQW/50TLGDC4yim//uN+Rs7t77/m2O7fn3A/PR3Jzz/d7PrvnnZvcZ7/ne873LFWFJGn1O2fcA0iSRsOgS1IjDLokNcKgS1IjDLokNWLtuB543bp1tXnz5nE9vCStSvfcc89Xq2pqsfvGFvTNmzczMzMzroeXpFUpyeeXus9TLpLUCIMuSY0w6JLUCIMuSY0w6JLUCIMuSY0YGvQk70tyIskDS9yfJH+SZDbJ/UkuHf2YkqRh+hyh3wRsX+b+q4At3ddu4N1PfSxJ0ukaGvSqugP42jJLdgJ/WfPuBJ6d5LmjGlCS1M8orhRdDxwb2J7r9n1p4cIku5k/imfTpk1n/ICb93zkjP9brZwH3/GqcY+gBfxbmUwr9bdyVl8Uraq9VTVdVdNTU4t+FIEk6QyNIujHgY0D2xu6fZKks2gUQd8P/GL3bpfLgEeq6kmnWyRJK2voOfQkNwOXA+uSzAFvB54GUFV/BhwArgZmgUeB16/UsJKkpQ0NelXtGnJ/AW8c2USSpDPilaKS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmN6BX0JNuTHEkym2TPIvdvSnJ7knuT3J/k6tGPKklaztCgJ1kD3AhcBWwFdiXZumDZbwH7quoS4BrgT0c9qCRpeX2O0LcBs1V1tKoeA24Bdi5YU8D3dbefBXxxdCNKkvroE/T1wLGB7blu36DfBl6bZA44ALxpsR+UZHeSmSQzJ0+ePINxJUlLGdWLoruAm6pqA3A18IEkT/rZVbW3qqaranpqampEDy1Jgn5BPw5sHNje0O0bdC2wD6Cq/g14OrBuFANKkvrpE/S7gS1JLkpyLvMveu5fsOYLwBUASV7EfNA9pyJJZ9HQoFfVKeA64DbgMPPvZjmY5IYkO7plbwXekOTTwM3AL1VVrdTQkqQnW9tnUVUdYP7FzsF91w/cPgS8bLSjSZJOh1eKSlIjDLokNcKgS1IjDLokNcKgS1IjDLokNcKgS1IjDLokNcKgS1IjDLokNcKgS1IjDLokNcKgS1IjDLokNcKgS1IjDLokNcKgS1IjDLokNcKgS1IjDLokNcKgS1IjDLokNcKgS1IjDLokNcKgS1IjDLokNcKgS1IjDLokNcKgS1IjDLokNcKgS1IjDLokNaJX0JNsT3IkyWySPUuseU2SQ0kOJvngaMeUJA2zdtiCJGuAG4ErgTng7iT7q+rQwJotwNuAl1XVw0mes1IDS5IW1+cIfRswW1VHq+ox4BZg54I1bwBurKqHAarqxGjHlCQN0yfo64FjA9tz3b5BLwBekORfk9yZZPuoBpQk9TP0lMtp/JwtwOXABuCOJD9cVV8fXJRkN7AbYNOmTSN6aEkS9DtCPw5sHNje0O0bNAfsr6pvVdXngM8yH/gnqKq9VTVdVdNTU1NnOrMkaRF9gn43sCXJRUnOBa4B9i9Y8/fMH52TZB3zp2COjnBOSdIQQ4NeVaeA64DbgMPAvqo6mOSGJDu6ZbcBDyU5BNwO/HpVPbRSQ0uSnqzXOfSqOgAcWLDv+oHbBbyl+5IkjYFXikpSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSIwy6JDXCoEtSI3oFPcn2JEeSzCbZs8y6n09SSaZHN6IkqY+hQU+yBrgRuArYCuxKsnWRdecDbwbuGvWQkqTh+hyhbwNmq+poVT0G3ALsXGTd7wLvBP53hPNJknrqE/T1wLGB7blu33ckuRTYWFUfWe4HJdmdZCbJzMmTJ097WEnS0p7yi6JJzgH+AHjrsLVVtbeqpqtqempq6qk+tCRpQJ+gHwc2Dmxv6PY97nzgxcA/J3kQuAzY7wujknR29Qn63cCWJBclORe4Btj/+J1V9UhVrauqzVW1GbgT2FFVMysysSRpUUODXlWngOuA24DDwL6qOpjkhiQ7VnpASVI/a/ssqqoDwIEF+65fYu3lT30sSdLp8kpRSWqEQZekRhh0SWqEQZekRhh0SWqEQZekRhh0SWqEQZekRhh0SWqEQZekRhh0SWqEQZekRhh0SWqEQZekRhh0SWqEQZekRhh0SWqEQZekRhh0SWqEQZekRhh0SWqEQZekRhh0SWqEQZekRhh0SWqEQZekRhh0SWqEQZekRhh0SWqEQZekRhh0SWqEQZekRvQKepLtSY4kmU2yZ5H735LkUJL7k3wiyfNGP6okaTlDg55kDXAjcBWwFdiVZOuCZfcC01X1I8CtwO+NelBJ0vL6HKFvA2ar6mhVPQbcAuwcXFBVt1fVo93mncCG0Y4pSRqmT9DXA8cGtue6fUu5Fvinxe5IsjvJTJKZkydP9p9SkjTUSF8UTfJaYBp412L3V9XeqpququmpqalRPrQkfddb22PNcWDjwPaGbt8TJHkl8JvAT1XVN0czniSprz5H6HcDW5JclORc4Bpg/+CCJJcAfw7sqKoTox9TkjTM0KBX1SngOuA24DCwr6oOJrkhyY5u2buA7wU+lOS+JPuX+HGSpBXS55QLVXUAOLBg3/UDt1854rkkSafJK0UlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqREGXZIaYdAlqRG9gp5ke5IjSWaT7Fnk/u9J8jfd/Xcl2TzqQSVJyxsa9CRrgBuBq4CtwK4kWxcsuxZ4uKqeD/wh8M5RDypJWl6fI/RtwGxVHa2qx4BbgJ0L1uwE3t/dvhW4IklGN6YkaZi1PdasB44NbM8BP7rUmqo6leQR4ALgq4OLkuwGdneb30hyZMhjr1v4Mybcapp35LNmZZ+XfVf/blfYapp3Nc0KS8z7FP9WnrfUHX2CPjJVtRfY23d9kpmqml7BkUZqNc27mmaF1TXvapoVVte8q2lWOPvz9jnlchzYOLC9odu36Joka4FnAQ+NYkBJUj99gn43sCXJRUnOBa4B9i9Ysx94XXf7F4BPVlWNbkxJ0jBDT7l058SvA24D1gDvq6qDSW4AZqpqP/Be4ANJZoGvMR/9Ueh9emZCrKZ5V9OssLrmXU2zwuqadzXNCmd53nggLUlt8EpRSWqEQZekRkxk0JM8Pcm/J/l0koNJfmfcMw2TZE2Se5P847hnGSbJg0n+I8l9SWbGPc9ykjw7ya1JPpPkcJIfG/dMS0nywu53+vjXfyf51XHPtZQkv9b9fT2Q5OYkTx/3TEtJ8uZuzoOT+DtN8r4kJ5I8MLDvB5J8PMl/dt+/f6XnmMigA98EXlFVFwMvAbYnuWzMMw3zZuDwuIc4DT9dVS9ZBe/p/WPgo1X1Q8DFTPDvuKqOdL/TlwAvBR4FPjzmsRaVZD3wK8B0Vb2Y+Tc8jOrNDCOV5MXAG5i/av1i4NVJnj/eqZ7kJmD7gn17gE9U1RbgE932iprIoNe8b3SbT+u+JvbV2yQbgFcB7xn3LC1J8izg5cy/i4qqeqyqvj7eqXq7Avivqvr8uAdZxlrgGd21I+cBXxzzPEt5EXBXVT1aVaeAfwF+bswzPUFV3cH8O/wGDX4kyvuBn13pOSYy6PCdUxj3ASeAj1fVXeOeaRl/BPwG8H/jHqSnAj6W5J7u4xgm1UXASeAvutNZ70nyzHEP1dM1wM3jHmIpVXUc+H3gC8CXgEeq6mPjnWpJDwA/meSCJOcBV/PEix0n1YVV9aXu9peBC1f6ASc26FX17e6p6wZgW/e0a+IkeTVwoqruGfcsp+EnqupS5j9B841JXj7ugZawFrgUeHdVXQL8D2fhaetT1V2AtwP40LhnWUp3Pncn8/9o/iDwzCSvHe9Ui6uqw8x/guvHgI8C9wHfHutQp6m70HLFzzJMbNAf1z3Fvp0nn5+aFC8DdiR5kPlPonxFkr8a70jL647OqKoTzJ/j3TbeiZY0B8wNPDu7lfnAT7qrgE9V1VfGPcgyXgl8rqpOVtW3gL8DfnzMMy2pqt5bVS+tqpcDDwOfHfdMPXwlyXMBuu8nVvoBJzLoSaaSPLu7/QzgSuAz451qcVX1tqraUFWbmX+a/cmqmsgjHYAkz0xy/uO3gZ9h/intxKmqLwPHkryw23UFcGiMI/W1iwk+3dL5AnBZkvO6j7q+ggl+wTnJc7rvm5g/f/7B8U7Uy+BHorwO+IeVfsCz+mmLp+G5wPu7/7nGOcC+qpr4twOuEhcCH+4+rn4t8MGq+uh4R1rWm4C/7k5jHAVeP+Z5ltX9I3kl8MvjnmU5VXVXkluBTwGngHuZ7Mvq/zbJBcC3gDdO2ovjSW4GLgfWJZkD3g68A9iX5Frg88BrVnwOL/2XpDZM5CkXSdLpM+iS1AiDLkmNMOiS1AiDLkmNMOiS1AiDLkmN+H9c6WaVCIWt8wAAAABJRU5ErkJggg==\n","text/plain":"<Figure size 432x288 with 1 Axes>"},"metadata":{"needs_background":"light"},"output_type":"display_data"}]},{"metadata":{},"cell_type":"markdown","source":"#### Then you can re iterate with your friends over the past two steps, until convergence to a clear winner"},{"metadata":{},"cell_type":"markdown","source":"## The second prototype : creating bids from this notebook, and sending them to a server (which you as a buyer can audit)\n"},{"metadata":{"trusted":false},"cell_type":"code","source":"# TO DO","execution_count":1,"outputs":[]},{"metadata":{},"cell_type":"markdown","source":"## The math of the second prototype; Homomorphic Encryption + MPC\n\nIn this part, we give a more detailed description of the cryptographic algorithms used in our \"auction without auctioneer\" scheme. The intended audience of this section is a reader with a backgroundin lattice cryptography and familiarity with the Ring-Learning with Errors (RLWE) problem. Familiarity with the homomorphic encryption scheme of Brakerski (2012) and Fan and Vercauteren(n.d.) would also be helpful. Familiarity with Asharov et al. (2012) is not necessary to understandthese algorithms.\n  \n \nThe main cryptographic primitive used for our scheme is homomorphic encryption, specifically the scheme of Brakerski (2012) and Fan and Vercauteren (n.d.), from here on referred to as the BFV scheme. Homomorphic operations are defined in this scheme for ciphertexts decryptable with the same secret key. Our approach to designing an MPC algorithm based on the BFV scheme was to design a key generation protocol and corresponding decryption protocol following the work of Asharov et al. (2012), where all parties participating in the MPC protocol could encrypt their data with the same public key, but a ciphertext would only be able to be decrypted if authorization isgiven by all parties. The algorithms described below provide more detail of our specific instantiation of the framework of Asharov et al. (2012).\n\n**Step 0. Distributed Key Generation** :\n\nLet's run our example with two agents, A and B, who want to see whose bid is higher and whose is lower, without relying on a trusted third party but without revealing to each other the exact value of each one's bid.\n\nConsider the standard BFV key generation protocol, which outputs a public-key/secret-key pair of the form \n$$(pk, sk) = \\big( (a, \\delta),  ( \\ s , e ) \\big) $$  \n  \n  \nwhere $a$ and $ \\delta$ are two uniformly random samples over the ring $R_q = Z_q[x]/f(x)$ where $f(x)$ is some degree-$n$ polynomial. The error term e is sampled from a discrete Gaussian with large standard deviation (such noise terms are sometimes referred to as ’flooding’ or ’smudging’ terms).Our key generation protocol relies on the common random string (CRS) model and begins with the assumption that all participants have access to the same truly random seed for a pseudorandom number generator (PRNG). All participants then use this seed to generate the same pseudorandom sample $a$ from $R_q$. Each party $i$ then generates the following key pair:\n$$ (pk_i, sk_i) = \\big( (a, \\delta) , (\\ s_i, e_i \\big) $$  \n\nSo agent A has the following key pair :   $$ (pk_a, sk_a) = \\big( (a, \\delta),  (\\ s_a , e_a) \\big) $$  \n\nAnd agent B the following key pair :  $$ (pk_b, sk_b) = \\big( (a, \\delta) , (\\ s_b, e_b) \\big) $$  \n\n\n**Step 1. Multiparty encryption of each agent's bid**\n\nNow that each agent has its unique secret key, while sharing a public key, they can start using these to encrypt their bids. To describe this encryption process we will follow a sequential description, even though the actual order of the sequences don't matter (both can even happen at the same time).\n\nSo A (let's say A starts, even though it would be the same if it's B first) : A sends to B its bid $m_a$, obfuscated by its secret key, in the following encrypted message (let's call it $ct_a$ , for ciphertext from A) :\n\n$$ct_a= a \\cdot \\ s_a + \\delta \\cdot  m_a + e_a$$ \n\nB cannot guess (from the security proof of the BFV scheme) the value of A's bid $m_a$. He sends similarly his encrypted bid $m_b$ to A (let's call it $ct_b$ , for ciphertext from B) :\n\n$$ct_b= a \\cdot \\ s_b + \\delta \\cdot  m_b + e_b$$ \n\n\n**Step 2. Multiparty addition of each agent's bid**\n\nLet's make each agent \"add in\" his own secret key to the encrypted message he received from the other party. Ie, for agent A, do the operation $ a \\cdot \\ s_a + e_a + ct_b $ and for agent B the operation $ a \\cdot \\ s_b + e_b + ct_a $\n\nSo now agent A has the new ciphertext (by writing $e_a + e_b = e$, and $s_a + s_b = s$ ):     $ct_b\\prime = a \\cdot \\ s + \\delta \\cdot  m_b + e $\n\n\nAnd agent B has the new ciphertext  $ct_a\\prime = a \\cdot \\ s + \\delta \\cdot  m_a + e $\n\nAnd, if both of them resend the ciphertext each one had to the other, then by both can do the operation $ct_a\\prime - ct_b\\prime = ctFinal =  \\delta \\cdot (m_a - m_b) $ , which sign reveals which agent's bid was higher at the start.\n\nLet's note that here with only 2 agents it is a limit case that would reveal, by difference, each agent's bid value to each other. For strictly more than 2 agents, this wouldn't be a problem unless some of the agents coordinate (the Byzantine general problem). For just 2 agents, the original outline on \"Innovative Financial design using encryption\" shows how $\\delta$ can be a value kept secret to each other, hence hiding the real value of both agent's bid.\n\n"},{"metadata":{"trusted":false},"cell_type":"code","source":"","execution_count":null,"outputs":[]}],"metadata":{"kernelspec":{"name":"python3","display_name":"Python 3","language":"python"},"language_info":{"name":"python","version":"3.8.5","mimetype":"text/x-python","codemirror_mode":{"name":"ipython","version":3},"pygments_lexer":"ipython3","nbconvert_exporter":"python","file_extension":".py"}},"nbformat":4,"nbformat_minor":2}