Verifiable Data and Compute
for the New Web

Our mission is to empower developers to create engaging and performant web3 services. With Blocky you can turn any web API into a trustworthy source of data, run verifiable computation in your favorite programming languages, and build onchain apps that scale to millions of users.

Our services rely on the security and privacy guarantees of Trusted Execution Environments (TEEs), such as AWS Nitro Enclaves and Google Confidential Spaces. The TEEs powering our services run inside data centers, which allows us to bring web2 levels of performance and scalability to web3.

We currently offer the Blocky Attestation Service (Blocky AS), which allows you to create TEE attestations over API data and verifiable offchain computation, and to bring these attestations on chain into your smart contracts. To learn what you can build with Blocky AS, check out our examples repository, where we cover:

• Hello World - Attesting a Function Call
• Hello World - Bringing A Blocky AS Function Call Attestation On Chain
• Passing Parameters and Secrets
• Error Handling in Attested Function Calls
• Error Handling of Attested Function Call Errors On Chain
• Generating A Verifiably Random Number
• Accessing Wall Clock Time
• Getting Coin Prices From CoinGecko
• Getting Esports Data From PandaScore
• Getting Esports Data From Rimble
• Getting Sports Data from SportRadar
• Tracking a Shipment with DHL
• Attesting A Time-Weighted Average Price
• Bringing An Attestation Of Time-Weighed Average Price On Chain

The above figure gives you a high level overview of what the Blocky Attestation Service does and how you can use it to develop user applications. Let's say that a User Application wants to trigger a Smart Contract action, for example based on the outcome of a sports game. The User Application needs to fetch sports data from External API, for example SportRadar, parse it, and send it to the Smart Contract. The Smart Contract then needs to check the veracity of the data before before using it in its logic.

Blocky Attestation Service supports this flow through a series of steps:

1. A User Application defines a function to call an External API and parses its response Data. The application sends a WebAssembly (WASM) binary of the function to Blocky AS for execution.
2. Blocky AS runs the function in a TEE, makes the function's HTTP calls to fetch Data from external APIs, processes the returned Data in the function, and creates a TEE Attestation of the result.
3. Blocky AS returns the Attestation to the User Application, which can verify it and use the data internally, for example to update the UI.
4. The User Application can also call a Smart Contract with the Attestation in calldata. The Smart Contract can verify the Attestation and use its attested Data to take an onchain action.

If you'd like to learn more, please check out documentation links on the left, or go directly into our examples repository, where you can discover how you can use Blocky AS to implement a variety of oracle and offchain compute use cases for your applications.