Vincenzo Iovino
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # MINI-FE: computing functions on private data without trusted parties Computing functions over private data is one of the key research directions in modern cryptography. The most notable cryptographic tools in this area so far are Multi-Party Computation (MPC), Fully Homomorphic Encryption (FHE), and Functional Encryption (FE). In this blog post, we introduce a new cryptographic primitive called Multi-Input Non-Interactive Functional Encryption (MINI-FE). This primitive allows one party (the evaluator) to run a predetermined computational function over other parties' encrypted input and obtain a result in the clear. With infinite potential applications, this blog post in particular will describe the Quadratic-like boardroom voting application as well as Stream Aggregation solution. Compared to the current cryptographic tools, MINI-FE offers a perfect combination of simplicity and security. Unlike MPC, MINI-FE does not require complex interactive protocols in which the participants need to stay online for several rounds of interaction. Unlike FHE, it does not need advanced cryptographic primitives. And unlike regular FE, which MINI-FE is based on, there is no trusted party (authority) to provide original function encryption. In the following part of the blog post, we first define the algorithms involved in a MINI-FE protocol, and then we present some of the motivating applications of this cryptographic primitive. ## MINI-FE: Definition A MINI-FE protocol for $N$ users and a $N$-variate function $F$ consists of the algorithms $(KeyGen, Encrypt, Eval)$. At the start of the MINI-FE protocol, $N$ users independently setup pairs of public- and secret-keys running the MINI-FE $KeyGen$ algorithm with a given security parameter. To later encrypt their secret input, each user $i\in {1, \ldots,N}$ with the previously generated secret-key $SK_i$ and a secret input $x_i$, uses the MINI-FE $Encrypt$ algorithm. Provided with the list of public-keys of all other participants, secret-key $SK_i$, secret value $x_i$ and a computation identifier $id$, it produces a ciphertext $CT_i$. Here the identifier is used to prevent someone from reusing the $CT_i$ submission in another computation. We say that the user $i$ encoded his input $x_i$ into $CT_i$. The public evaluation algorithm $Eval$ takes as input $N$ ciphertexts $CT_1,\ldots,CT_N$ for the same computation identifier and outputs $F(x_1,\ldots,x_n)$. Note that the MINI-FE scheme allows to reuse the same public keys for an unbounded number of evaluations for different identifiers. The security of the MINI-FE scheme guarantees that for any two tuples of $N$ inputs that map to the same value under $F$, the corresponding tuples of ciphertexts are computationally indistinguishable. Meaning that the adversary would not be able to extract information about the exact values that went into the input besides what is extractable from the output $F(x_1,\ldots,x_n)$. This even holds when adversaries can corrupt up to $n - 2$ users out of $n$ users participating. Next we will describe the MINI-FE protocol for the inner-product (IP) functionality. Specifically, we consider the following scenario: 1. There are two groups of $N$ users and a known prime number $p$. 2. Each user generates their own pair of public- and secret- keys according to the MINI-FE $KeyGen$ algorithm. 3. Each user in the first group holds a secret input $x_i\in Z_p$, and each user in the second group holds a public input $y_i\in Z_p$. 4. Users from both groups encodes their own inputs to produce $2N$ ciphertexts $CT_1,\ldots, CT_{2N}$. 5. The public evaluation algorithm $Eval$, on input ciphertexts $CT_1,\ldots, CT_{2N}$, outputs the inner-product of the vector $(x_1,\ldots,x_N)$ with the vector $(y_1,\ldots,y_N)$ in the field $Z_p$. We stress that the ciphertexts of the users in the second group do not hide the values $y_i$'s. As we will see further, the user $i$ in the first group can be controlled by the person who also controls the user $i$ in the second group (that is both the $i$-th secret key in the first and second group are generated by the same individual). This fact will come in useful in the applications we describe bellow, as it allows the users to submit both a private and a public part to the protocol. ## Motivating applications ### Private Stream Aggregation The setting has a group of $N$ companies that want to compute statistics over their commulitative private data, without disclosing their individual private data. Moreover, the exact statistics that will be computed on the private data is not known in advance to the companies. MINI-FE helps to solve this problem. In particular, for any $i\in[N]$ the company $i$ sets up two pairs of public- and secret-keys for MINI-FE, one as user $i$ and one as user $N+i$ of MINI-FE and publishes such public-keys over a blockchain. On a daily (or hourly) basis, company $i$ sends to the blockchain a MINI-FE ciphertext of its private data $x_i$ tagging it with an identifier $id$ (e.g., the current day or an increasing counter). At any moment in the future the companies can decide to compute a certain statistics on the previously set of encoded data tagged with the same identifier $id$ (e.g., all the data of a specific day). In particular, the statistics we consider is a weighted sum in which the input $x_i$ of company $i$ has to be weighted by the value $y_i$. Then, company $i$ submits to the blockchain the MINI-FE ciphertext for user $N+i$, weight $y_i$ and tag $id$. Given the $2N$ so computed ciphertexts ($N$ for the secret inputs $x_i$'s and $N$ for the public weights $y_i$'s) posted on the blockchain, anyone can then publicly compute the statistics $\sum_{i\in[N]} x_i\cdot y_i \mod p$. The weights can be decided dynamically and collectively: the private data is made available daily (or hourly) while the weights for the statistics might be jointly decided by the companies only, e.g., at the end of each month. To understand why the solution in which each company waits until the end of each month to encode its private data directly in weighted form (i.e., like $x_i\cdot y_i$) is not satisfactory let us explore the following example. The company could decide to change its input $x_i$ after knowing the weights $y_i$'s of all other companies. For this reason, the companies are required to commit to their private data $x_i$'s in the form of a MINI-FE ciphertext posted in the blockchain as soon as these values are available so as to guarantee that the choice of the weights is independent from the private data. ### Quadratic-like boardroom voting In boardroom voting, it is required that each member of an organization to participate in elections. In this setting, very strong privacy requiments can be attained. In particular it is possible to design e-voting protocols without any trusted parties and without requiring the voters to use anonymous channels (e.g. TOR) like in e-voting based on SNArKs and membership proofs. Quadratic voting is a novel voting procedure proposed by Lalley and Weyl to overcome several issues in social choice theory like the Condorcet paradox. In quadratic voting, each voter casts his own preference along with a weight and is required to pay a cost that is quadratic in his weight; after the tally of the election is announced, the collected revenue is shared, e.g., evenly among the voters. Researchers conducted an experiment that showed that when quadratic voting is employed in opinion polls, people tend to express less extreme preferences indicating that the preferences are closer to the actual ones. A MINI-FE for IP can be used to build a system that has features similar (though not identical) to secure quadratic voting system without trusted authorities in the following way. Each voter $i$ has a pair of public- and secret- keys for both user $i$ in the first group and user $i$ in the second group, that is a pair of keys for the user $i$ and another for the user $N+i$. Voter $i\in[N]$ casts their preference $x_i$ computing a MINI-FE's ciphertext as the user $i$ of the first group. The preferences definition is flexible and could be for instance in the domain ${1,-1}$ with the meaning of 1 as YES and -1 as NO. At a later point, the voter $i$ chooses its weight $y_i$ and pays for it the quantity $y_i^2$ and encodes a MINI-FE's ciphertext as the user $N+i$ from the second group. The weight could be for instance defined in the domain $\{1,\ldots,10\}$. The ciphertexts are tallied according to the evaluation procedure of the MINI-FE protocol and thus the result is the inner-product $\sum_{i\in[N]} x_i\cdot y_i$ that measures how many of the voters are in favor or against a given proposal. The capability to cast the weights in separate ciphertexts gives more flexibility with respect to solutions in which preferences and weights are cast together: a voter first commits to its own preference and later on can decide its weight. The choice of the voters' weights can be even done by means of a joint discussion when the preferences are already committed and cannot be longer changed. Indeed, having known how much voters are going to pay for their preferences could affect a voter's preference: our solution does not suffer from this issue. ## MINI-FE: Construction for IP Our construction of MINI-FE for the IP functionality is based on blinear maps and the interested reader is defered to this [preprint](https://drive.google.com/file/d/1E6bmP5yhsAleeu34bBPRwtTEvflrKJf9/view?usp=sharing) that will appear in the proceedings of International Conference on Codes, Cryptology and Information Security (C2SI), Springer, 2023.

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully