blocky.rocks

What it is

Blocky is a trusted computing and attestation service for development teams, positioning itself as a way to help teams build “trusted, glass box applications.” Based on the available content, its core product is the Attestation Service: it generates verifiable proofs for data sources, execution processes, function inputs, and outputs, allowing customers, smart contracts, and AI Agents to verify results without fully trusting the service provider.

Core capabilities

Blocky supports running WebAssembly (WASM) functions inside Trusted Execution Environments (TEEs), with AWS Nitro Enclaves given as an example environment. This means computation can be executed in an isolated, tamper-resistant environment, with hardware attestation used to produce auditable results. It also covers common infrastructure needs for trusted applications: securely passing parameters and sensitive secrets into WASM functions, calling external Web APIs over HTTPS from within the TEE, generating cryptographically secure random numbers, and providing TEE-backed hardware timestamps. Proofs can be verified inside WASM functions to support re-entrant workflows, or passed to smart contracts for trustless on-chain operations.

Pricing and deployment

The collected content does not disclose pricing models, plans, free quotas, or enterprise offerings, nor does it specify supported payment methods. On deployment, the only clear point is its association with TEEs such as AWS Nitro Enclaves; there is no explicit information on whether it supports self-hosting, private deployment, multi-cloud TEEs, or local execution. Its open-source or closed-source status is also not stated.

Pros and cons

Its strengths are a clear positioning and an architecture that connects key elements of trusted computing around TEE, WASM, and attestation, including external data, randomness, timestamps, and on-chain verification. This makes it suitable for systems with high requirements for computational integrity and auditability. WASM also provides a degree of runtime neutrality. The main drawback is the limited amount of public information: specific APIs/SDKs, supported languages, documentation depth, service SLAs, costs, and deployment boundaries are all unclear, so further communication is needed to assess implementation costs.

Who it is for and access from China

Blocky is best suited for Web3 infrastructure teams, smart contract developers who need trusted off-chain computation, AI Agent tool-call verification scenarios, and teams in finance, auditing, data supply chains, and other areas that require provable execution. Access from mainland China is unknown, and payment methods have not been disclosed. If access or compliance is restricted, alternatives to consider include cloud provider TEEs, WASM sandboxes, decentralized oracles, and trusted computing frameworks.