Escrin

website·Indexed 31 days ago

https://escrin.org/docs

A smart worker runtime and framework that enables smart contracts to perform secure, private off-chain computation within Trusted Execution Environments (TEEs). Escrin provides tools for managing identities via an Identity Registry, executing bundles of work called tasks, and a JavaScript runtime known as the Escrin Runner.

Tokens
10.4K
Snippets
38
Records
66
Agent score
52%

What's inside Escrin

  1. Overview of the Escrin smart worker runtime

    Escrin is a smart worker runtime designed for autonomous computing. It allows smart contracts to privately interact with private off-chain data and push the resulting computation back onto the blockchain. It functions as a trusted third party for running private computations within a secure serverless environment.
  2. Overview of Nanobridges in the Escrin Framework

    Nanobridges are special-purpose Escrin Workers designed for cross-chain communication. They leverage Trusted Execution Environments (TEEs), decentralized secret management, and on-chain roots of trust to create secure enclaves of computation. Unlike traditional bridges that only move bytes, nanobridges are user-programmable, allowing developers to execute custom message-passing workflows, complex conditional logic, and multi-chain/off-chain pipelines using JavaScript, Wasm, and Python.
  3. Overview of Escrin Runner

    The Escrin Runner (escrin-runner) is a JavaScript runtime based on the Cloudflare Workerd serverless computing platform. It is extended with trusted execution and blockchain integration to enable 'Smart Workers'—trusted programs backed by the security and integrity of smart contracts.
  4. Overview of the Escrin Identity Framework

    The Escrin identity framework provides a capability-based security system where 'permits' act as trustworthy records of identity (similar to non-transferable NFTs). These permits allow Escrin Smart Workers to bootstrap themselves, gaining access to wallets, APIs, and other valuable assets required to complete tasks. The framework separates the 'how' of task execution from the 'who' (identity) and 'under what conditions' (permissions), serving as a primary defense against data misuse.
  5. Overview of the Simple Secret Sharing Server (SSSS)

    The Simple Secret Sharing Server (SSSS) is a decentralized secret management system used by Escrin workers to securely hold and retrieve secrets (such as OmniKey secret shares). It utilizes Shamir's Secret Sharing to split secrets among distributed, non-colluding shareholders, ensuring that only authorized parties can reconstruct the secret. The SSSS implements the Escrin Identity interface, specifically the acquire_identity and get_omni_key functions.
  6. Overview of the Escrin Network

    The Escrin Network is a decentralized, community-operated hosted offering of the Escrin framework. It provides 'Web3-flavored serverless computing' by offering secure, trust-minimized virtual machines, key management, and storage. It integrates with consensus networks like Ethereum and L2s to enable high-performance, high-integrity off-chain computation for use cases such as AI agents, real-time gaming, and Web3 interconnectivity. The network is powered by the $ESCRIN utility token, which incentivizes node operators.
  7. Understand the role of Identities and OmniKeys

    An Escrin identity is an authenticated record of passing specific checks. When a worker acquires an identity, it can use that permit to obtain an OmniKey from a secret management network (such as Oasis Sapphire). The OmniKey allows the worker to derive wallets, encryption keys, TLS certificates, and other security primitives. This mechanism enables multiple workers to share the same identity, forming the basis for decentralized workflows.
  8. Understand Smart Worker security via TEE

    Smart Workers are executed within a Trusted Execution Environment (TEE). This architecture ensures that the internal operations and data processing of a worker remain private and inaccessible to external observers, including the infrastructure provider.
  9. SSSS Architecture and Components

    The SSSS consists of four primary components designed for portability and efficiency:

    1. API Task: A TLS-enabled HTTP server that handles public network requests.
    2. Sync Task: Monitors the SSSSHub contract on EVM-compatible networks for policy configuration changes and new secret shares. It processes Brotli-compressed CBOR documents and encrypted shares sent via calldata or blobs.
    3. Policy Engine: Validates worker requests for identity permits. Currently, it supports AWS Nitro Enclave attestations; future versions may support JavaScript and Python policies via the Escrin Runner.
    4. Storage Backend: A portable layer that can be implemented using local hosting or cloud storage.
  10. Understand Escrin's security architecture (TEEs and Key Management)

    Escrin relies on three primary architectural pillars to ensure secure, private computation:

    1. Trusted Execution Environments (TEEs): Secure hardware enclaves that protect algorithms and data from unauthorized observers, ensuring that inputs and outputs remain end-to-end encrypted.
    2. Decentralized Key Management: Uses smart contracts to trigger the release of keys from networks that employ secret sharing and threshold encryption. This ensures keys are available only to authorized parties or hardware enclaves.
    3. Decentralized Computing: Distributes computing resources across a network of computers to improve fault tolerance, scalability, and security, allowing algorithms to run on trustworthy hardware globally.
  11. Smart Worker execution environment

    A Smart Worker runs within a JavaScript WorkerGlobalScope. It has access to most global properties found in a browser execution context, including fetch, setTimeout, and crypto.subtle.
  12. Publish changes to the Escrin website

    The website is deployed automatically. To publish updates, push your changes to the default branch of the repository.