Trust at Scale

Blocky empowers teams to build trusted, glass box applications and services without compromising speed or control. Blocky's Attestation Service (Blocky AS) turns any web API into a provable data source, enables secure and verifiable execution of WebAssembly (WASM) functions, and brings results onchain to trigger smart contract actions.

Blocky AS is built on enterprise-grade Trusted Execution Environments (TEEs), AWS Nitro Enclaves and (soon) Google Confidential Spaces, ensuring strong security and data privacy by design. By leveraging TEEs within modern cloud infrastructure, we bring web2-level performance and scalability to web3 applications - without compromising on trust or transparency.

Blocky AS At a Glance

Let's say you are building an application that fetches data from an API, processes it, and passes the result to a smart contract. The smart contract must verify the authenticity of the processed data before using it to take an onchain action.

Here's how Blocky AS enables this workflow:

1. Function Invocation
   The user application defines a function that sends a request to an API, parses its response, and returns an output after processing the API data. You can compile this function into a WASM binary and invoke it on a Blocky AS server running inside a TEE. As part of the function invocation, you may also pass in parameters and secrets.

2. Function Execution
   The Blocky AS server spins up a WASM runtime to execute the function. The function makes HTTPS requests, processes the API responses, and returns output to the Blocky AS server. Blocky AS WASM runtime and SDK also support verifiably random number generation and wall clock time access.

3. Function Attestation

   Blocky AS creates TEE-backed attestation over the function's name, WASM binary, input, hash of secrets, and output, and sends the attestation back to the application.

4. Attestation Verification

   The application verifies the attestation to take further actions, such as updating its UI, or archiving the attestation for later use. Blocky AS also supports attestation verification inside its WASM runtime allowing applications to implement reentrant computation of time-weighted average prices (TWAPs) and other multi-stage processes.

5. Smart Contract Calls

   Finally, the application passes the attestation as calldata to a smart contract. The smart contract verifies the attestation and uses the confirmed data to perform onchain actions.

Documentation Overview

The rest of this documentation provides a comprehensive guide to using Blocky AS. We also provide examples, of Blocky AS integrations with several data providers, including CoinGecko for coin prices, PandaScore and Rimble for esports data, and DHL for shipment tracking. To help you understand if Blocky AS is right for your use case, we also list its security assumptions and limitations.

If you'd like to get in touch, or follow us on our journey, you can find us on Telegram and X.