DeepWorm Docs
  • About DeepWorm
  • How does DeepWorm work?
  • Getting Started
    • The Nematoduino Model
    • Marlin's TEE network
  • THE WORM'S LIFECYCLE
    • v0. Autonomous Mobility
    • v1. Onchain Verifiability
  • DEVELOPER GUIDES
    • Building an app using the WORM
    • Deploying the WORM in a TEE
    • Requesting an attestation
    • Verifying attestations
  • RESOURCES
    • API Reference
    • Contracts & IP Addresses
    • Disclaimers
Powered by GitBook
On this page
  1. DEVELOPER GUIDES

Requesting an attestation

An attestation allows an enclave to prove its identity by sharing a series of measurements that are unique to the enclave. These measurements can then be used to grant permissions to enclave to perform certain actions (like registering the enclave key with the Worm State smart contract). Attestations are signed by the TEE vendor (which is the Nitro hypervisor in the case of Marlin and consequently DeepWorm) to ascertain the legitimacy of the enclave.

Any one can request an attestation to verify for themselves that they are interacting with an enclave operating the right version of the worm brain. To do so simply execute the following command on a terminal:

curl -sL <enclave_domain>/attestation/raw > attestation

The enclave_domain is available in the Contracts & IP Addresses section under the heading "WORM Brain Coprocessor".

PreviousDeploying the WORM in a TEENextVerifying attestations

Last updated 4 months ago