Blind-find NPM

Blind Find v1

Blind Find is a peer-to-peer network allowing private peer search proposed by Barry Whitehat and Kobi Gurkan. This repo implements the first version of Blind Find, Blind Find v1. Please read the spec to learn how it works.

Install

You can install Blind Find either with npm or building it from the repo.

Install with npm

npm install -g blind-find

Build from the repo

git clone git@github.com:mhchia/blind-find.git
cd blind-find

Install our rust dependency zkutil, which perform proof generation/verification and other stuffs.

npm run install_zkutil

Extract proving and verifying keys from parameters generated from the circuits and trusted setups.

npm run extract_keys

Install NPM dependencies.

npm install

Optional: Symlink the package folder. This step makes you able to use Blind Find CLI in your shell by calling blind-find instead of npx ts-node src/cli/index.ts.

npm link

Get Started

Before proceeding, you should read the sections Introduction and Roles in the spec to understand what each role is doing.

Testnet

Kovan

Public Hub

Kovan
- hostname: blindfind.mhchia.com
- port: 5566
- hubPubkeyBased64: R3GJfyLwN3JjHyfnBLHhCPannm1rr1XBlMJAh/h0pS4=

[WARNING]: There is no guarantee on public hubs' running and all data are subject to be erased.

Command Line Interface (CLI)

See CLI document for all available commands.

Play with User CLI

This section goes through how to use User CLI to interact with the public hub. You will learn how to 1. Join a hub. 2. Search for yourself through the hub and generate a Proof of Indirect Connection. 3. Verify the proof.

Ensure Blind Find is correctly installed and shell command blind-find exists. If not, run CLI with npx ts-node src/cli/index.ts instead.

A data directory $HOME/.blind_find along with a config file $HOME/.blind_find/configs.yaml are created when you execute the command first time.

$ blind-find
ConfigError: ~/.blind_find/configs.yaml is not found and thus a template is generated. Complete the template and try again.
    at Function.loadFromDataDir (/Users/mhchia/projects/work/applied-zkp/blind-find/lib/cli/configs.js:205:23)
    at async main (/Users/mhchia/projects/work/applied-zkp/blind-find/lib/cli/index.js:52:20)

Open ~/.blind_find/configs.yaml. You will see the network configurations and a pre-generated valid blindFindPrivkey, i.e. the "XXXXXXXXXXXX" below.

network:
  provider:
    network: kovan
    name: infura
    apiKey: Put your infura api key here
blindFindPrivkey: "XXXXXXXXXXXX"

By default, we use Infura as the network provider. We need an API key to access Infura API. Register an account, create a project, and find the API key. It should be the hexidecimal postfix in your project endpoint. For example, if your endpoint is https://kovan.infura.io/v3/123456abcdef123456abcdef, then 123456abcdef123456abcdef is the the API key. Paste it to the field apiKey like the following.

network:
  provider:
    network: kovan
    name: infura
    apiKey: 123456abcdef123456abcdef
blindFindPrivkey: "XXXXXXXXXXXX"

If you prefer to use a JSONRPC server, change name field to web3 and apiKey to url, and paste the endpoint of the JSONRPC server to url field.

network:
  provider:
    network: kovan
    name: web3
    url: http://localhost:12345
blindFindPrivkey: "XXXXXXXXXXXX"

If your configuration is correct then we're ready to go. As a user, all commands you need are under blind-find user.

$ blind-find user
Usage: blind-find user [options] [command]

user join hubs and search for others

Options:
  -h, --help                               display help for command

Commands:
  join <hostname> <port> <hubPubkey>       join a hub
  search <hostname> <port> <targetPubkey>  search for a user through a hub
  getKeypair                               get user's keypair
  verifyProof <proofBase64Encoded>         verify a Proof of Indirect Connection
  getJoinedHubs                            get the hubs user already joined before
  help [command]                           display help for command

Postfix the flag --help behind a command whenever you want to learn more about a command.

$ blind-find user getKeypair --help
Usage: blind-find user getKeypair [options]

get user's keypair

Options:
  -h, --help  display help for command

Join the public hub. The command succeeds if there is no error.

$ blind-find user join blindfind.mhchia.com 5566 R3GJfyLwN3JjHyfnBLHhCPannm1rr1XBlMJAh/h0pS4=

You should be able to search for yourself. Use getKeypair to learn your keypair. Copy the content in the field pubKeyBase64Encoded.

$ blind-find user getKeypair
{
        "privKey": "PRIVKEY",
        "pubKey": [
                "PUBKEY_X",
                "PUBKEY_Y"
        ],
        "pubKeyBase64Encoded": "PUBKEY_BASE64_ENCODED"
}

Call search with public hub's hostname, port, and paste your public key encoded in base64.

It will take a few minutes or longer depending on how many users have joined the hub. When the command finishes, you will get a Proof of Indirect Connection encoded in base64 in base64Encoded field. Because you are simultaneously the searcher and the target, both pubkeySearcher and pubkeyTarget fields should be your public key encoded in base64.

$ blind-find user search blindfind.mhchia.com 5566 PUBKEY_BASE64_ENCODED
{
        "pubkeySearcher": "PUBKEY_BASE64_ENCODED",
        "pubkeyTarget": "PUBKEY_BASE64_ENCODED",
        "adminAddress": "0xe75B72f46f34D8505382a35f4832FF41761611bB",
        "merkleRoot": "11006367961791971092113606774938408370281609027794134241388950976069851532161",
        "base64Encoded": "PROOF_BASE64_ENCODED"
}

Verify the proof with the command verifyProof with the proof in base64Encoded field. Because the proof is valid, you should see "Proof is correct!", along with the proof information. Otherwise, you might either paste the proof incorrectly or there is anything wrong in the codebase.

$ blind-find user verifyProof PROOF_BASE64_ENCODED
Proof is correct!
{
  pubkeySearcher: 'PUBKEY_BASE64_ENCODED',
  pubkeyTarget: 'PUBKEY_BASE64_ENCODED',
  adminAddress: '0xe75B72f46f34D8505382a35f4832FF41761611bB',
  merkleRoot: '11006367961791971092113606774938408370281609027794134241388950976069851532161'
}

More about Hub and Admin

For normal users, it should be just enough to play with user CLI. Read the following sections to learn how to 1. Set up your own Blind Find v1 network. 2. Register a new hub in a Blind Find v1 network.

Play with Admin CLI

To run a new Blind Find v1 network, deploy a Blind Find v1 contract on Ethereum network and the deployer is the admin. Admin CLI now only works with an Externally Owned Account (EOA), instead of contracts.

To make CLI work with the deployed Blind Find v1 contract, add the address and atBlock (block number where the contract resides) of the contract in the field customContractAddress in configs.yaml.

network:
  provider:
    network: kovan
    name: infura
    apiKey: 123456abcdef123456abcdef
    customContractAddress:
        address: CONTRACT_ADDRESS
        atBlock: CONTRACT_AT_BLOCK
blindFindPrivkey: "XXXXXXXXXXXX"

To allow CLI to commit merkle roots on the contract, add the private key of the EOA which deployed the contract in admin.adminEthereumPrivkey your configs.yaml.

network:
  provider:
    network: kovan
    name: infura
    apiKey: 123456abcdef123456abcdef
    customContractAddress:
        address: CONTRACT_ADDRESS
        atBlock: CONTRACT_AT_BLOCK
blindFindPrivkey: "XXXXXXXXXXXX"
admin:
  adminEthereumPrivkey: "0x1234567890123456789012345678901234567890123456789012345678901234"

To register a hub, get the hub's registry encoded in base64 and add it. Output is the merkle proof of the hub registry in the hub merkle tree. Make sure to send it back to the hub so that the hub can prove itself has been registered.

$ blind-find admin addHub <hubRegistryBase64>
HUB_REGISTRY_WITH_PROOF_BASE64

Play with Hub CLI

To set up a new hub, be registered by the admin first.

Get your hub registry encoded in base64, i.e. the content inside the field base64Encoded in the output.

$ blind-find hub createHubRegistry
{
        "sig": {
          ...
        },
        "pubkey": ...,
        "adminAddress": ...,
        "base64Encoded": "HUB_REGISTRY_BASE64_ENCODED"
}

Send the hub registry encoded in base64 to the admin. Admin should then call admin addHub to add your hub registry to the merkle tree and commit it on chain, and then send you back your hub registry along with the merkle proof encoded in base64.

Set your hub registry along with the merkle proof encoded in base64 in your database. If the command succeeds, then registration is done.

$ blind-find hub setHubRegistryWithProof <HUB_REGISTRY_WITH_PROOF_BASE64>

Listen to users requests.

$ blind-find hub start
{"message":"HubServer: Listening on port 5566","level":"info"}
Hub is listening on { address: '0.0.0.0', family: 'IPv4', port: 5566 } , with pubkey in base64 = ...
Press Ctrl-C to exit

zkp mpc ethereum

await-lock bn.js circom circomlib commander ethers express js-sha256 level maci-circuits maci-config maci-crypto tmp-promise winston ws yaml

@everything-registry/sub-chunk-1244 @zalastax/nolb-bli

3 years ago

3 years ago

3 years ago

3 years ago