Skip to main content

Explore

Run Your Own IVS​

In the ./start.sh script, you'll find a variable defined as IVS_URL="http://3.110.146.109:3030". IVS stands for Input Verification Service. An operator requires an IVS to prevent spam requests from requestors. When an operator receives a request, it forwards the request to the IVS, which generates relevant signatures to verify the validity of the request.

Is IVS a Centralized Service?​

No, IVS is not a centralized service. It is an enclave that can be hosted by anyone. If you trust the access of an IVS hosted by another party, you can share it with multiple operators. For example, the stagenet version has a shared IVS deployed. Alternatively, you can build and host your own IVS enclave.

Deploying the Attestation IVS Enclave​

The Attestation IVS Enclave is available for deployment. Operators can deploy the Attestation IVS enclave using Marlin Oyster.

Steps to Deploy Your Own IVS​

  1. Deploy the Attestation IVS Enclave

    Use Marlin Oyster to deploy the Attestation IVS Enclave.

  2. Register the Enclave Key

    Once your IVS is deployed, use kalypso-cli to register the enclave key with the smart contracts. Execute the Add IVS Key operation in kalypso-cli: