Skip to content

Latest commit

 

History

History
90 lines (63 loc) · 3.04 KB

local-development.md

File metadata and controls

90 lines (63 loc) · 3.04 KB
Raw

Deploy on a local network

You can deploy the zk verifier contracts and run an end-to-end test or demo as follows (make sure you have installed rust and foundry):

  1. Start a local testnet with anvil by running:

    anvil

    Once anvil is started, keep it running in the terminal, and switch to a new terminal.

  2. Set environment variables:

    # Anvil sets up a number of default wallets, and this private key is one of them.
export ETH_WALLET_PRIVATE_KEY=0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80

  3. Next, you will use rzup to install cargo-risczero.

To install rzup, run the following command and follow the instructions:

curl -L https://risczero.com/install | bash

Next we can install the RISC Zero toolchain by running rzup:

rzup

You can verify the installation was successful by running:

cargo risczero --version

Now you have all the tools you need to develop and deploy an application with RISC Zero.

  1. Build project:

    cargo build

  2. Deploy verifiers contract by running:

    forge script --rpc-url http://localhost:8545 --broadcast script/Deploy.s.sol

    This command should output something similar to:

    ...
== Logs ==
Deployed RiscZeroGroth16Verifier to 0x5FbDB2315678afecb367f032d93F642f64180aa3
Deployed DcapVerifier to 0xe7f1725E7734CE288F8367e1Bb143E90bb3F0512
...

    Save the DcapVerifier contract address to an env variable:

    export DCAP_VERIFIER_ADDRESS=0xe7f1725E7734CE288F8367e1Bb143E90bb3F0512#COPY DCAP VERIFIER ADDRESS FROM DEPLOY LOGS

    You can also use the following command to set the contract address if you have [jq][jq] installed:

    export DCAP_VERIFIER_ADDRESS=$(jq -re '.transactions[] | select(.contractName == "DcapVerifier") | .contractAddress' ./broadcast/Deploy.s.sol/31337/run-latest.json)

Interact with local deployment

Submit a new proof (this will verify the hardcoded DCAP input and submit the proof and serialized output to DcapVerifier contract)

```bash
RUST_LOG=info RISC0_DEV_MODE=false cargo run --bin publisher -- \
    --chain-id=31337 \
    --rpc-url=http://localhost:8545 \
    --contract=${DCAP_VERIFIER_ADDRESS:?}
```

You will see the output like below, the verification of attestation proof passed, and the submitted DCAP outputs returned:

```bash
0x400000000000000048656c6c6f2c20776f726c6421000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000200000000000000033d8736db756ed4997e04ba358d27833188f1932ff7b1d156904d3f560452fbb2000000000000000815f42f11cf64430c30bab7816ba596a1da0130c3b028b673133a66cf9a3e0e6000000002100000000000000436f6e66696775726174696f6e416e64535748617264656e696e674e656564656402000000000000000e00000000000000494e54454c2d53412d30303238390e00000000000000494e54454c2d53412d3030363135
```