Blocky Attestation Service

The Blocky Attestation Service gives you access to verifiable serverless computing. You can use it to create TEE attestations over function calls and API calls. You can verify these attestations locally or onchain in a smart contract.

On this page we give a quick overview of the Blocky Attestation Service functionality. To learn more about the service, dive into the links on the left.

Attesting WASM Function Calls

The Attestation Service CLI supports the attest-fn-call command which allows you to send WebAssembly (WASM) functions for execution on a TEE in a serverless compute model. Use the attest-fn-call command to execute resource-intensive tasks over API data to accelerate your smart contracts and lower your gas costs.

At a high level, a User invokes the attest-fn-call command and sends a compiled WASM Function and an Encrypted Environment, containing function parameters, to the Attestation Service running on a TEE. The Attestation Service decrypts the Environment, starts a WASM Runtime, and invokes the user Function with the decrypted parameters. As a part of its execution, the function may also make requests to external web2 APIs. Finally, the Attestation Service returns a TEE Attestation over the WASM function execution and its results to the User.

To learn more the about the attest-fn-call command, explore its documentation.

Attesting API Calls

The Attestation Service CLI supports the attest-api-call command, which allows you to make private requests to any web API and obtain a TEE attestation over response data. Use the attest-api-call command to transform your application with low latency, verifiable data from any web2 API.

At a high level, a User invokes the attest-api-call command and sends a Request Template and an Encrypted Environment to the Attestation Service running on a TEE. The Attestation Service decrypts the Environment and plugs its values, such as an API key, into the Template to transform it into an API Request. Finally, the Attestation Service creates a TEE Attestation over the Response, and returns it to the User.

To learn more the about the attest-api-call command, explore its documentation.

Blocky Chain Integrations

The Blocky Chain Integrations allow you to bring the Attestation Service TEE attestations onchain and trustlessly verify them in your smart contracts. Use Chain Integrations to bring the power of TEEs into your dApp or ecosystem to unlock developer creativity.

At a high level, the User invokes the Blocky Attestation Service and obtains a TEE Attestation. The User calls a Smart Contract with the serialized Attestation as a parameter. Finally, the Smart Contract verifies the Attestation and makes use of the attested data.

To learn more the about bringing attestations on chain, explore Chain Integrations documentation.