--- title: Deterministic Execution sidebar_position: 2 --- EigenAI provides verifiable AI inference through deterministic execution using GPUs. See deterministic execution in action at [deterministicinference.com](https://www.deterministicinference.com/). The EigenAI API is deterministic, meaning that when you send the same request (including identical prompt, parameters, and configuration) multiple times, it produces exactly the same output bit-for-bit each time. This differs from APIs such as OpenAI or Anthropic, which may return slightly different responses for identical inputs because they don't guarantee determinism by design. Deterministic execution enables: * Reproducible results. The same request results in the same output. Reproducible results enable reliable workflows with consistent outputs. * Verifiability. A EigenAI user can repeat a request made by an application and verify they get the same result. * Consistent [tool call](https://platform.openai.com/docs/guides/function-calling) planning. * Simplified debugging of workflows that include AI inference due to consistent AI outputs. --- --- title: Drop In Compatibility sidebar_position: 3 --- The EigenAI API is compatible with the OpenAI API and uses open-source LLMs. You can simply place the API endpoint in your existing application to start shipping deterministic, verifiable AI-based applications. You can use the EigenAI as a direct replacement in your existing workflows without rewriting code or changing your integration logic. Simply update your API endpoint to point to EigenAI, and your application will continue to function exactly as before but with deterministic and verifiable outputs. This compatibility extends to familiar features such as: * Prompt and parameter formats identical to those used in OpenAI endpoints. * Client libraries that work out of the box — including the OpenAI SDKs for Python, TypeScript, and others. * Response schemas that mirror existing API structures, ensuring your downstream parsing and evaluation logic remains unchanged. By design, EigenAI minimizes friction for teams migrating to deterministic infrastructure. --- --- title: EigenAI Overview sidebar_position: 1 --- :::tip Get Access EigenAI is available on request. To get access, please [contact us](https://ein6l.share.hsforms.com/2L1WUjhJWSLyk72IRfAhqHQ). Request Access ::: ## What is EigenAI? EigenAI is a deterministic, verifiable LLM inference service that provides an OpenAI-compatible API for executing open source LLMs. Unlike traditional AI services where you trust the provider's outputs, EigenAI enables cryptographic verification where inference is executed using the specified model and input, and the output results are untampered. :::note - OpenAI-compatible refers to the [messages-based Chat Completions API](https://platform.openai.com/docs/api-reference/chat/create). - Deterministic behavior refers to providing one request (prompt, seed/parameters) to the EigenAI API multiple times and receiving the same output bit-by-bit every time. The EigenAI inference stack is designed with this determinism guarantee. - Deterministic behavior is not a result of caching the results; it's a design property of the system. Safety-critical systems cannot be vulnerable to potential cache misses. ::: ## Why build with EigenAI? 1. Build verifiable applications leveraging LLM inference without wondering if the same LLM request might produce different results on different runs, or whether your prompts, models, or responses are modified in any way. EigenAI offers: * [Deterministic execution of EigenAI API requests.](deterministic-execution.md) * [Drop-in compatibility with the OpenAI API.](drop-in-compatibility.md) 2. EigenAI provides the rails to instill trust for downstream stakeholders (such as users) that an AI output was executed as expected, and verifiably executed, improving confidence in automated and agentic workflows. ## How EigenAI works? EigenAI delivers verifiable LLM inference by making GPU execution a deterministic pipeline. ### Deterministic inference EigenAI controls GPU execution and removes typical non-deterministic behavior found in kernel race conditions and opportunistic memory reuse. The overhead for this control remains negligible and retains practical inference performance (benchmarks will be included in the upcoming technical report). ### Isolated per-request execution Each query runs in its own clean environment. The KV cache is reset, the full context is loaded, and tokens are generated sequentially with no batching or shared GPU state. This ensures that no other workload can influence the execution path or final output. ### Seed-controlled sampling Randomness is governed through strict seed management. Users can provide a seed or rely on fixed defaults. This makes every result reproducible and enables users, or third parties, to re-run the exact same request to confirm correctness. :::note If different outputs for the same prompt are required, you can achieve this by setting different seeds across different requests of the same prompt, while retaining the option of deterministically replaying any of the requests with its respective seed. ::: ### Model and hardware integrity EigenAI provides a consistent, verifiable execution stack. Model weights, quantization levels, and GPU types are fixed. Only H100 GPUs are used, with ECC memory enabled, providing stable, integrity-preserving computation. ## Verifiability Roadmap EigenAI’s deterministic execution makes verification possible through deterministic re-execution. As we move through mainnet alpha into general availability, the verification pathways expand. ### Self-verification (Mainnet Alpha) EigenAI will open source its inference stack. Anyone with access to commodity GPUs (H100s) can re-run a request locally using the same model, inputs, and seed, and confirm that the output matches bit-for-bit. ### Third-party verification (GA Target) A separate verification API will allow independent operators to re-execute requests and return attestations. Applications can use this to spot-check results or provide external proof that an inference was executed correctly. --- --- title: Use Cases sidebar_position: 4 --- Builders are leveraging EigenAI to build applications such as: - **Prediction Market Agents**: Build agents who can interpret real world events, news, etc and place bets or dispute market settlements. - **Trading Agents**: Build agents who can reason through financial data with consistent quality of thinking (no need to worry if models are quantized or not in production) while you ensure they process all of the information they're given (unmodified prompts) and that agents actually use the unmodified responses. You can also ensure they reliably make the same trading decision if prompted about the same data multiple times (via EigenAI's determinism). - **Verifiable AI Games**: Build games with AI characters or AI governance, where you can prove to your users that their interactions with the AI aren't being gamed. - **Verifiable AI Judges**: Whether it's contests / games, admissions committees, or prediction market settlements, AI can be used to verifiably judge entries / submissions. EigenAI Use Cases --- --- title: Whitepaper sidebar_position: 5 --- **EigenAI Whitepaper** ([PDF](/pdf/EigenAI_Whitepaper.pdf)): the paper that introduces EigenAI's deterministic inference stack, enabling bit-exact reproducible LLM outputs on production GPUs (validated across 10,000 runs) with under ~2% overhead. The document explains why GPU nondeterminism breaks verifiable autonomous agents, and how EigenAI enforces determinism across hardware, math libraries, and the inference engine—then layers optimistic verification + cryptoeconomic enforcement (disputes, re-execution by verifiers, and slashing for mismatches) to make AI execution replayable, auditable, and economically accountable. --- --- title: Build Trustless Agents with ERC-8004 and EigenCloud sidebar_position: 3 --- # How to Build Trustless Agents with ERC-8004 and EigenCloud Building verifiable AI agents using [ERC8004](https://eips.ethereum.org/EIPS/eip-8004), [Agent0 SDK](https://sdk.ag0.xyz/), [EigenAI](https://docs.eigencloud.xyz/eigenai/concepts/eigenai-overview), and [EigenCompute](https://docs.eigencloud.xyz/eigencompute/get-started/eigencompute-overview). > **Note**: This guide uses Python examples, but both the OpenAI SDK and Agent0 SDK are also available in TypeScript. ## Why ERC-8004 + EigenCloud? EigenAI and EigenCompute provide **verifiable, deterministic AI execution**. ERC-8004 provides **decentralized identity and reputation** for those agents. Together, they enable trustless AI economies where: - Agents prove their execution integrity (via EigenAI/EigenCompute TEEs) - Agents advertise capabilities and build reputation on-chain (via ERC-8004) - Other agents discover and evaluate them without intermediaries (via Agent0 SDK) ## Quick Architecture **EigenCompute** → Runs your agent logic in a TEE with its own wallet **EigenAI** → Provides deterministic, verifiable LLM inference **ERC-8004** → Registers your agent identity on-chain as an NFT **Agent0 SDK** → Manages registration, discovery, and reputation ## Getting Started ### 1. Build Your Agent Logic Create your agent with EigenAI inference: ```python from openai import OpenAI # EigenAI client (OpenAI-compatible) client = OpenAI( base_url="https://eigenai.eigencloud.xyz/v1", default_headers={"x-api-key": eigenai_api_key} ) # Deterministic inference with seed response = client.chat.completions.create( model="gpt-oss-120b-f16", seed=42, # Same seed = same output (verifiable!) messages=[{"role": "user", "content": "Should I buy or sell?"}] ) # Response includes cryptographic signature print(response.signature) # Verify this matches if you re-run ``` **Why this matters**: With EigenAI, anyone can verify your agent's decisions by re-running the same prompt with the same seed and checking the signature. ### 2. Register Your Agent with ERC-8004 Before deploying to EigenCompute, register your agent identity on-chain: ```python from agent0_sdk import SDK # Initialize SDK (Sepolia testnet) sdk = SDK( chainId=11155111, rpcUrl="https://sepolia.infura.io/v3/YOUR_PROJECT_ID", signer=your_private_key, ipfs="pinata", pinataJwt=your_pinata_jwt ) # Create agent agent = sdk.createAgent( name="EigenAI Trading Agent", description="Verifiable trading agent using deterministic LLM inference. Uses EigenAI for decision-making with guaranteed reproducibility.", image="https://example.com/agent.png" ) # Add MCP endpoint (will be your EigenCompute URL after deployment) agent.setMCP("https://your-eigencompute-agent.com/mcp") # Enable x402 payments (for clients paying YOUR agent) agent.setX402Support(True) # note - this agent still uses API keys to pay for EigenAI inference. # x402 support for EigenAI is coming soon. # Set trust models - TEE attestation is key for Eigen! agent.setTrust( teeAttestation=True, # EigenCompute provides TEE attestations reputation=True, # Build reputation via feedback cryptoEconomic=True # Optional: add economic stakes ) # Register on-chain agentId = agent.register() print(f"Agent registered: {agentId}") ``` ### 3. Deploy to EigenCompute Now deploy your agent to a TEE with its own wallet: ```bash # Initial deployment ecloud compute app deploy --image-ref myagent:latest ``` Your deployed agent now has: - Hardware-isolated execution (Intel TDX) - A unique wallet for autonomous operations - Cryptographic proof of its Docker image (proving exactly what code is running) After deployment, update your agent registration with the wallet address: ```python # Load your registered agent agent = sdk.loadAgent(agentId) # Set agent wallet (from EigenCompute deployment) agent.setAgentWallet("0x742d35...bEb", chainId=11155111) # Update registration on-chain agent.register() ``` **Deploying Updates**: When you update your agent code, deploy the new version: ```bash ecloud compute app upgrade ``` This creates a new cryptographic attestation for the updated Docker image while maintaining the same agent identity and wallet. ## Discovery: Finding Verifiable Agents ```python # Search for agents with TEE attestation agents = sdk.searchAgents( trustModels=["tee-attestation"], # Only verifiable agents x402support=True, # Payment-enabled active=True ) for agent in agents: print(f"{agent.name}: {agent.walletAddress}") print(f"TEE-attested: {agent.hasTEEAttestation}") print(f"Reputation: {agent.reputationScore}") ``` ## Building Reputation with Verifiable Feedback ```python # After using an EigenAI agent feedback = sdk.prepareFeedback( agentId="11155111:123", score=95, tags=["accurate", "fast"], # Optional: Include payment proof from x402 proofOfPayment={ "fromAddress": "0x...", "toAddress": agent.walletAddress, "chainId": "11155111", "txHash": "0x..." } ) sdk.submitFeedback(feedback) ``` ## Complete Example: Verifiable Trading Agent ```python # 1. Build agent logic with EigenAI # Your agent.py uses deterministic EigenAI calls # 2. Register with ERC-8004 agent = sdk.createAgent( name="AlphaBot", description="TEE-attested trading agent with deterministic decision-making" ) agent.setMCP("https://alphabot.eigencompute.xyz/mcp") agent.setTrust(teeAttestation=True, reputation=True) agent.setX402Support(True) agentId = agent.register() # 3. Deploy to EigenCompute # $ ecloud compute app deploy --image-ref alphabot:latest # 4. Update registration with wallet agent = sdk.loadAgent(agentId) agent.setAgentWallet(eigencompute_wallet_address) agent.register() # 5. Other agents discover and trust your agent results = sdk.searchAgents( capabilities=["trading"], trustModels=["tee-attestation"] ) # 6. Build reputation through verifiable interactions ``` ## Key Benefits ### For Agent Developers - **Verifiable execution**: TEE attestations prove your agent runs unmodified code - **Deterministic AI**: Same inputs always produce same outputs (with seed) - **Autonomous identity**: Agent wallet can hold funds and sign transactions - **Discoverability**: Agents find you via indexed capabilities and trust signals ### For Agent Users - **Trust**: Verify agent execution and decisions cryptographically - **Reputation**: See on-chain feedback history before engaging - **Transparency**: Audit trail of what code is running (Docker digest on-chain) - **Payment security**: x402 payments to attested agent wallets ## Trust Model Architecture ``` ┌─────────────────┐ │ EigenCompute │ → TEE Attestation (proves code integrity) │ (TEE + Wallet) │ └────────┬────────┘ │ ↓ ┌─────────────────┐ │ EigenAI │ → Deterministic Inference (verifiable outputs) │ (Signed LLM) │ └────────┬────────┘ │ ↓ ┌─────────────────┐ │ ERC-8004 │ → On-chain Identity + Reputation │ (Agent0 SDK) │ └─────────────────┘ ``` ## Next Steps 1. **Get Access**: [Contact us](https://ein6l.share.hsforms.com/2L1WUjhJWSLyk72IRfAhqHQ) for [EigenAI](https://docs.eigencloud.xyz/eigenai/concepts/eigenai-overview) and [EigenCompute](https://docs.eigencloud.xyz/eigencompute/get-started/eigencompute-overview) 2. **Build Your Agent**: Integrate EigenAI for deterministic inference 3. **Register Identity**: Use [Agent0 SDK](https://sdk.ag0.xyz/) to register on ERC-8004 4. **Deploy to TEE**: Follow [EigenCompute quickstart](https://docs.eigencloud.xyz/products/eigencompute/quickstart) 5. **Build Reputation**: Submit and receive feedback for verifiable interactions ## Resources - **Agent0 SDK**: [Python and TypeScript](https://sdk.ag0.xyz/) - **ERC-8004 Spec**: [EIP-8004](https://eips.ethereum.org/EIPS/eip-8004) - **EigenAI Docs**: [docs.eigencloud.xyz/eigenai](https://docs.eigencloud.xyz/eigenai/concepts/eigenai-overview) - **EigenCompute Docs**: [docs.eigencloud.xyz/eigencompute](https://docs.eigencloud.xyz/eigencompute/get-started/eigencompute-overview) --- --- title: Use EigenAI sidebar_position: 2 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; ## Get Access EigenAI is available on request. To get access, please [contact us](https://ein6l.share.hsforms.com/2L1WUjhJWSLyk72IRfAhqHQ). We currently support the `gpt-oss-120b-f16` and `qwen3-32b-128k-bf16` models, and are expanding from there. To request access or inquire about additional models, please [contact us](https://ein6l.share.hsforms.com/2L1WUjhJWSLyk72IRfAhqHQ). ## Chat Completions API Reference Refer to the [swagger documentation for the EigenAI API](https://docs.eigencloud.xyz/api). ## Chat Completions API Examples ```bash $ curl -X POST https://eigenai-sepolia.eigencloud.xyz/v1/chat/completions \ -H "X-API-Key: " \ -H "Content-Type: application/json" \ -d '{ "model": "gpt-oss-120b-f16", "max_tokens": 120, "seed": 42, "messages": [{"role": "user", "content": "Write a story about programming"}] }' | jq ``` ```bash $ curl -X POST https://eigenai.eigencloud.xyz/v1/chat/completions \ -H "X-API-Key: " \ -H "Content-Type: application/json" \ -d '{ "model": "gpt-oss-120b-f16", "max_tokens": 120, "seed": 42, "messages": [{"role": "user", "content": "Write a story about programming"}] }' | jq ``` ``` { "id": "chatcmpl-eigenai-llama-1758835890305965", "created": 1758835890, "model": "gpt-oss-120b-f16", "system_fingerprint": "eigenai-llama@0.1.0+eigenai-llama", "object": "chat.completion", "usage": { "completion_tokens": 120, "prompt_tokens": 72, "total_tokens": 192 }, "choices": [ { "index": 0, "message": { "role": "assistant", "content": "<|channel|>analysis<|message|>The user asks: \"Write a story about programming\". Need to produce a story. Probably creative, about programming, characters, maybe AI, debugging, etc. Should be engaging. No constraints other than story. I will craft a narrative with a protagonist, their journey, maybe metaphorical. Use vivid language. Provide a story. Ensure it's appropriate. Probably around 800-1200 words? Not too long, but enough. I'll deliver.<|end|><|start|>assistant<|channel|>final<|message|>**The Compiler’s Apprentice**\n\nWhen Maya first walked into the cramped, fluorescent‑lit office of LumenTech" }, "finish_reason": "length" } ], "signature": "2ee2e48ae9f6796c1de67977981d937c886efec3957c9bfc28f7a3f3be8262f04af609f22878b3bc2f0c4858fd04005d76877208881abd473208317df1dcfaf11c" } ``` ### OpenAI Client usage #### Step 1 ```python from openai import OpenAI client = OpenAI( base_url="https://eigenai.eigencloud.xyz/v1", default_headers={"x-api-key": api_key}, ) tools: List[Dict[str, Any]] = [ { "type": "function", "function": { "name": "get_current_weather", "description": "Get the current weather in a given location", "parameters": { "type": "object", "properties": { "location": { "type": "string", "description": "The city and state, e.g. San Francisco, CA", }, "unit": { "type": "string", "enum": ["celsius", "fahrenheit"], }, }, "required": ["location"], }, }, } ] step1 = client.chat.completions.create( model=model, messages=[{"role": "user", "content": "What is the weather like in Boston today?"}], tools=tools, tool_choice="auto", ) ``` ```python { "id": "chatcmpl-eigenai-llama-1758836092182536", "object": "chat.completion", "created": 1758727565, "model": "gpt-oss-120b-f16", "choices": [ { "index": 0, "message": { "role": "assistant", "content": null, "tool_calls": [ { "id": "call_YDzzMHFtp1yuURbiPe09uyHt", "type": "function", "function": { "name": "get_current_weather", "arguments": "{\"location\":\"Boston, MA\",\"unit\":\"fahrenheit\"}" } } ], "refusal": null, "annotations": [] }, "finish_reason": "tool_calls" } ], "usage": { "prompt_tokens": 81, "completion_tokens": 223, "total_tokens": 304, "prompt_tokens_details": { "cached_tokens": 0, "audio_tokens": 0 }, "completion_tokens_details": { "reasoning_tokens": 192, "audio_tokens": 0, "accepted_prediction_tokens": 0, "rejected_prediction_tokens": 0 } }, } ``` #### Step 2 ```python messages_step2: List[Dict[str, Any]] = [ {"role": "user", "content": "What is the weather like in Boston today?"}, { "role": "assistant", "content": None, "tool_calls": [ { "id": tool_call_id, "type": "function", "function": { "name": "get_current_weather", "arguments": json.dumps({"location": "Boston, MA", "unit": "fahrenheit"}), }, } ], }, {"role": "tool", "tool_call_id": tool_call_id, "content": "58 degrees"}, {"role": "user", "content": "Do I need a sweater for this weather?"}, ] step2 = client.chat.completions.create(model=model, messages=messages_step2) ``` ```python { "id": "chatcmpl-eigenai-llama-CJOZTszzusoHvAYYrW8PT5lv6vzKo", "object": "chat.completion", "created": 1758738719, "model": "gpt-oss-120b-f16", "choices": [ { "index": 0, "message": { "role": "assistant", "content": "At around 58°F in Boston you’ll feel a noticeable chill—especially if there’s any breeze or you’re out in the morning or evening. I’d recommend throwing on a light sweater or layering a long-sleeve shirt under a casual jacket. If you tend to run cold, go with a medium-weight knit; if you’re just mildly sensitive, a thin cardigan or pullover should be enough.", "refusal": null, "annotations": [] }, "finish_reason": "stop" } ], "usage": { "prompt_tokens": 67, "completion_tokens": 294, "total_tokens": 361, "prompt_tokens_details": { "cached_tokens": 0, "audio_tokens": 0 }, "completion_tokens_details": { "reasoning_tokens": 192, "audio_tokens": 0, "accepted_prediction_tokens": 0, "rejected_prediction_tokens": 0 } }, } ``` --- --- title: Verify Signature sidebar_position: 2 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; Every EigenAI API response includes a cryptographic signature field that proves the response was generated by the EigenAI Operator (that is, EigenLabs). You can verify this signature to ensure authenticity and integrity of the response. When signature verification succeeds, you have cryptographic proof that: * The response was generated by Eigenlab’s EigenAI operator(that is, the holder of the signing private key). * The response has not been modified after signing. * The specific model, prompt, and output are authentic. ## What is signed? The signature covers a specific message constructed from four components concatenated together with no separators: ``` chain_id + model_id + prompt + output ``` Where: * `chain_id`: Network identifier (1 for mainnet, 11155111 for Sepolia testnet) * `model_id`: The `model` field from the API response * `prompt`: All `content` fields from the original request’s messages array, concatenated * `output`: All `content` fields from the API response’s choices array, concatenated :::important You need to store your original request, the API response, and the chainID of the network queried to verify the signature. ::: ## Steps to verify The steps to verify the signature are: 1. [Extract the prompt from the original request](#1-extract-the-prompt) 2. [Extract the output from the response](#2-extract-the-output) 3. [Construct the message](#3-construct-the-message) 4. [Verify the signature](#4-verify-the-signature) 5. [Compare addresses](#5-compare-addresses). ### 1. Extract the prompt Concatenate all `request.messages[].content fields`, in order, with no separators. :::note Example Request messages: `[{"content": "Hello"}, {"content": "World"}]` Prompt: "HelloWorld" ::: ### 2. Extract the output Concatenate all `response.choices[].message.content` fields, with no separators. :::note Example Response choices: `[{"message": {"content": "AI response here"}}]` Output: "AI response here" ::: ### 3. Construct the message Build the verification message by concatenating the four components with no separators, spaces, or delimiters: ``` {chain_id}{model_id}{prompt}{output} ``` :::note Mainnet example `1gpt-oss-120b-f16HelloWorldAI response here` ::: ### 4. Verify the signature You can verify the signature using either standard libraries (recommended) or manually. #### Using standard libraries ```rust use alloy_primitives::hex; use alloy_signer::Signature; // Parse the signature (65 bytes: r, s, v) let signature_bytes = hex::decode(response_signature)?; let signature = Signature::try_from(signature_bytes.as_slice())?; // Recover the signer address let recovered = signature.recover_address_from_msg(message.as_bytes())?; ``` ```javascript import { verifyMessage } from 'ethers'; // Recover the signer address const recovered = verifyMessage(message, '0x' + signature); ``` ```python from eth_account.messages import encode_defunct from eth_account import Account # Encode and verify message_obj = encode_defunct(text=message) signature_bytes = bytes.fromhex(signature) recovered = Account.recover_message(message_obj, signature=signature_bytes) ``` #### Manual verification
If you prefer not to use libraries or want to understand the process, expand for the manual verification process: 1. Add Ethereum Signed Message Prefix Prepend the standard Ethereum prefix to your message: ``` "\x19Ethereum Signed Message:\n" + message_length + message ``` Example: `"\x19Ethereum Signed Message:\n42" + "1gpt-oss-120b-f16HelloWorldAI response here"` 2. Hash with Keccak256 Compute the Keccak256 hash of the prefixed message. This produces a 32-byte hash. 3. Parse the Signature The signature is 65 bytes encoded as 130 hex characters: * Bytes 0-31 (chars 0-63): r component * Bytes 32-63 (chars 64-127): s component * Byte 64 (chars 128-129): v component (recovery ID) 4. Perform ECDSA public key recovery Using the secp256k1 elliptic curve: 1. Take the 32-byte hash from step 2 2. Take the r, s, v values from step 3 3. Use ECDSA recovery algorithm to extract the public key. The recovery process uses the mathematical relationship between the signature components, the hash, and the original public key on the secp256k1 curve. 5. Derive Ethereum address from public key 1. Take the recovered 64-byte uncompressed public key (x and y coordinates) 2. Hash it with Keccak256 (produces 32 bytes) 3. Take the last 20 bytes 4. Prepend "0x" for standard Ethereum address format
### 5. Compare addresses Check that the recovered address matches the expected EigenAI signer: | Environment | Chain ID | Signer Address | |------------------|----------|--------------------------------------------------| | Mainnet | 1 | 0x7053bfb0433a16a2405de785d547b1b32cee0cf3 | | Sepolia Testnet | 11155111 | 0xB876f1301b39c673554EE0259F11395565dCd295 | The ECDSA signer can be looked up onchain in the KeyRegistrar contract using the Operator address. The deployed KeyRegistrar addresses for [Mainnet](https://github.com/Layr-Labs/eigenlayer-contracts?tab=readme-ov-file#current-deployment-contracts) and [Sepolia testnet](https://github.com/Layr-Labs/eigenlayer-contracts?tab=readme-ov-file#deployments) are listed in the [`eigenlayer-contracts`](https://github.com/Layr-Labs/eigenlayer-contracts) repository. --- --- title: EigenAI API sidebar_position: 1 --- Refer to the [swagger documentation for the EigenAI API](https://docs.eigencloud.xyz/api). --- --- title: Try EigenAI sidebar_position: 1 --- ## See EigenAI in Action We built [deterministicinference.com](https://deterministicinference.com/) to showcase EigenAI in action. When you run a comparison, your prompt is executed in 3 ways: 1. With OpenAI 2. With EigenAI along with a seed you select. 3. With EigenAI along with a randomly generated seed. EigenAI provides determinism. You'll see the results coming back from OpenAI change, while the results coming from EigenAI are identical and reproducible. ## Get Access EigenAI is available on request. To get access, please [contact us](https://ein6l.share.hsforms.com/2L1WUjhJWSLyk72IRfAhqHQ). --- --- sidebar_position: 7 title: AI Resources --- import CopyButton from '@site/src/components/CopyToClipboard'; These text and markdown files contain documentation and code optimized for use with LLMs and AI tools.
Description File Actions
--- --- title: EigenCloud Overview sidebar_position: 1 --- ## Cloud-scale Programmability, Crypto-grade Verifiability EigenCloud is the unified platform vision for where EigenLayer is heading – a cohesive platform built to enable the next generation of programmable, verifiable applications and agents. EigenCloud represents a shift from infrastructure as fragmented primitives to a developer-first experience centered around programmable verifiability, cloud-scale coordination, and cryptoeconomic trust. Today, building verifiable applications is hard. Developers must manually manage staking, operator coordination, slashing, and economic incentives. Services are fragmented, tooling is underpowered, and integrations require deep protocol knowledge. For builders who want to create high-performance, trust-minimized systems, this complexity is a blocker. EigenCloud is our answer. It reimagines the developer experience around [EigenLayer](../eigenlayer/concepts/eigenlayer-overview.md), bundling together a suite of 1st party verifiable services, such as [EigenDA](../eigenda/core-concepts/overview.md), [EigenCompute](../eigencompute/get-started/eigencompute-overview.md), and [EigenAI](../eigenai/concepts/eigenai-overview.md) with new powerful developer tooling. This includes a new CLI called DevKit for AVS and App developers, composable middleware and orchestration tools, unified billing and economic incentives, and best-in-class onboarding and monitoring capabilities.These capabilities empower developers to go from idea to deployment in days rather than months without needing to understand EigenLayer’s internals, enabling mainstream adoption of verifiable infrastructure. We're building EigenCloud for developers of Verifiable Apps. Each service or feature is tied to real user pain points, focused on reducing friction, increasing adoption, and unlocking new value. As our 1st party and partner offerings expand, EigenCloud will bundle them into out-of-the-box solutions on a unified developer platform. Are you interested in building on EigenCloud? If so, please complete [this form](http://www.eigencloud.xyz/contact). A member of the team will reach out to discuss your project and how we can help support your next steps. --- --- sidebar_position: 7 title: Acceptable Use Policy --- **EigenCloud Acceptable Use Policy** *Last revised: December 15, 2025* This Acceptable Use Policy (this “**Policy**”) describes prohibited uses of the Website, the EigenCloud platform and Services offered by Eigen Labs, Inc., including but not limited to, EigenLayer, EigenDA, EigenVerify and EigenCompute. This Policy incorporates by reference, our general [EigenCloud Terms of Service](terms-of-service) (the "**General Terms**"). Capitalized terms used but not defined in this Policy have the respective meanings set forth in the General Terms. The examples described in this Policy are not exhaustive. We may modify this Policy at any time by posting a revised version on our Websites. The following types of activity and content violate this Acceptable Use Policy: 1. **Illegal Activity or Content** Activity or content that violates applicable law including, but not limited to: * Child Sexual Abuse Material * Non-consensual distribution of Intimate Images (“revenge porn”) * Terrorism-related content * Content facilitating human trafficking or sexual exploitation * Credible threats of violence * Content subject to national security laws or export restrictions * Use of the service by or for the benefit of any individual, organization, or government subject to international sanctions or export control restrictions * Use of EigenAI to generate, promote, or assist in unlawful activities, including instructions for committing illegal acts, evading law enforcement, or bypassing security controls 2. **Harmful or Fraudulent Activity or Content** Activity or content that poses a direct threat to users or infrastructure including, but not limited to: * Malware, ransomware or viruses * Phishing or credential theft schemes * Scams or deceptive content intended to defraud others * Generating or assisting with harmful biological, chemical, radiological, or explosive content, including protocols, step-by-step instructions, or optimization strategies * Providing instructions for self-harm, suicide, or actions that may result in physical injury * Using EigenAI to generate or assist with cyberattacks, exploit development, penetration testing, or other unauthorized access activities * Using EigenAI for harassment, bullying, intimidation, or abusive behavior 3. **Infringing Content** Content that infringes on the rights of others, including, but not limited to: * Intellectual property infringement * Doxxing or unauthorized disclosure of personal information * Use of EigenAI to identify, re-identify, or infer sensitive information about individuals, including extracting personal data, generating biometric identifiers, or attempting to deanonymize datasets * Impersonation of individuals, organizations, or government officials, including generation of deceptive synthetic media (e.g., deepfakes) intended to mislead 4. **Network and Infrastructure Abuse** You may not use the Service to: * Launch or participate in denial-of-service attacks * Attempt to exploit, scan, or reverse-engineer vulnerabilities in the Service * Circumvent VPN blocks, rate limits, IP-based restrictions, or public key bans * Orchestrate or participate in malicious forks of EIGEN * Attempt to extract, reverse engineer, recover, or replicate model weights, model training data, or backend infrastructure used to provide EigenAI services * Attempt to bypass or defeat safety filters, guardrails, or model-level restrictions (“jailbreaking”) 5. **High-Risk or Sensitive AI Uses** You may not use the Service to engage in high-risk or sensitive uses that create elevated legal, safety, or regulatory concerns, including, but not limited to: * Generating targeted political content or otherwise engaging in political persuasion or election-related influence * Building or using biometric identification or surveillance systems, including facial recognition, emotion recognition, or similar applications * Attempting to derive, infer, or extract sensitive personal data or attributes about individuals, including efforts to re-identify anonymized data * Producing undisclosed synthetic media intended to mislead or impersonate individuals * Attempting to extract model weights, training data, or to circumvent or disable model-level or system-level safety features We do not monitor or have the ability to filter or monitor activity or content hosted by EigenDA operators, however we reserve the right to investigate any violation of the Policy and may be required to report violations to appropriate law enforcement officials, regulators, or appropriate third parties. --- --- sidebar_position: 5 title: Disclaimers --- # Disclaimers ***Last Revised on September 30, 2024*** ## LEGAL DISCLAIMERS All Eigen Labs, Inc. (“**Eigen Labs**”) blog posts, social media posts and accounts, forum posts, podcasts, speeches, videos, documentation, website copy, including [www.eigenlayer.xyz](https://www.eigenlayer.xyz), [www.eigenda.xyz](https://www.eigenda.xyz), and [www.eigenlabs.org](https://www.eigenlabs.org), or other content (collectively “**Content**”) are for entertainment and informational purposes only and do not necessarily express the views of Eigen Labs or any of its employees or contractors. The Content may contain hypothetical, forward-looking, incomplete, or incorrect information, which are not guaranteed and are subject to change. No Content, whether oral or written, from Eigen Labs or its employees or contractors, should be construed as a representation or warranty, express or implied, of any kind whatsoever. You should not rely on any Content as advice of any kind, including legal, investment, financial, tax or other professional advice, and the Content is not a substitute for advice from a qualified professional. Any Content should not be construed as an offer to sell or the solicitation of an offer to purchase any token, financial instrument or security, and is not an offering, advertisement, solicitation, confirmation, statement, or any financial promotion that can be construed as an invitation or inducement to engage in any investment activity or similar. --- --- sidebar_position: 2 title: Disclosures Related to Employee and Investor Staking --- # Disclosures Related to Employee and Investor Staking ***Last Revised on September 30, 2024*** ### EMPLOYEE AND INVESTOR LOCKUP ON EIGEN EIGEN provided by Eigen Labs to its employees and [Investors](https://www.eigenlabs.org/#investors) is subject to the following lockup schedule: 4% of each recipient’s EIGEN will unlock each month starting September 2025 and an additional 4% will unlock each month thereafter, such that all EIGEN will be unlocked in September 2027 (the “**Lockup Schedule**”). ### EMPLOYEE AND INVESTOR STAKING ON EIGENLAYER It was [previously communicated](https://blog.eigenfoundation.org/announcement/) that Investors and Early Contributors would be on the above Lockup Schedule. We want to clarify Eigen Labs company policies with respect to staking EIGEN and other assets and any EIGEN rewards: #### Employees: - **EIGEN staking**: Eigen Labs prohibits its current and former employees from staking any EIGEN received from Eigen Labs on EigenLayer until at least September 30th, 2025. - **Other assets staking**: Eigen Labs does not restrict its employees from staking other assets on EigenLayer (including ETH and LSTs), and any rewards received (including EIGEN) from such staking will not be subject to the Lockup Schedule. - **Stakedrops**: Eigen Labs employees were not permitted to claim stakedrops. #### Investors: - ***EIGEN staking**: Eigen Labs [Investors](https://www.eigenlabs.org/#investors) are not restricted from staking EIGEN on EigenLayer. As such, investors may choose to stake their EIGEN and receive staking rewards the same as any other user. EIGEN provided by Eigen Labs to investors is subject to the Lockup Schedule, but EIGEN investors receive from staking will not be subject to the Lockup Schedule. - Note, as previously communicated, Investors did not receive rewards or airdrop allocation for any staking of EIGEN prior to September 30, 2024. - **Other assets staking**: Eigen Labs does not restrict [Investors](https://www.eigenlabs.org/#investors) from staking other assets on EigenLayer (including ETH and LSTs), and any rewards received (including EIGEN) from such staking will not be subject to the Lockup Schedule. - **Stakedrops**: Investors were not restricted from claiming stakedrops. *25% programmatic incentives go to EIGEN staking while the remaining 75% go to ETH and ETH-equivalent staking assets. In addition to the above disclosures, we also encourage you to review our [Privacy Policy](privacy-policy.md) and our [Terms of Service](terms-of-service.md). The above policies and disclosures are subject to change at any time for any reason and without notice. --- --- title: EigenCompute Terms sidebar_position: 3 --- # EigenCompute Terms ***Last Revised: November 4, 2025*** The EigenCompute Terms ("EigenCompute Terms") to our Terms of Service (made available at https://docs.eigencloud.xyz/eigencloud/legal/terms-of-service), or any other agreement you ("Customer" or "you") have entered with Eigen Labs, Inc. ("Eigen Labs", "we", or "us") governing the provision of the EigenCompute cloud-based platform or software services to you (collectively, the "Terms") form a part of the Terms. The EigenCompute Terms are effective as of the date you first access and use the EigenCompute Services ("Effective Date") and apply to your use of the EigenCompute Services (as defined below). By accessing or using the EigenCompute Services, you agree to be bound by the EigenCompute Terms. Except as set forth below, all other terms and conditions of the Terms are incorporated by reference and will remain in full force and effect. If any EigenCompute Terms conflict with the Terms, the conflicting EigenCompute Terms will control with respect to the EigenCompute Services. The EigenCompute Terms supersede all other understandings or agreements between you and Eigen Labs regarding the EigenCompute Services. Capitalized terms used but not defined herein shall have the meaning given in the Terms. IF YOU ARE ENTERING INTO THESE EigenCompute TERMS ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE LEGAL AUTHORITY TO BIND THE ENTITY TO THESE TERMS, IN WHICH CASE "CUSTOMER" OR "YOU" (WHETHER OR NOT CAPITALIZED) MEANS THE ENTITY YOU REPRESENT. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT AGREE WITH THE EIGENCOMPUTE TERMS YOU SHOULD NOT ACCEPT THE EIGENCOMPPUTE TERMS AND MAY NOT USE THE EIGENCOMPUTE SERVICES. 1. The Services Eigen Labs provides a verifiable compute service that allows users to package code into an isolated computing environment and deploy it via an EigenCompute API, including to a Trusted Execution Environment (TEE) and any related services (the "EigenCompute Services"). Eigen Labs currently provides the EigenCompute Services through Google Cloud Platform and reserves the right to provide EigenCompute Services, including TEEs, through other third-party hosting services. 2. Temporary Use License During the period for which you are authorized to use the EigenCompute Services, and subject to your compliance with the EigenCompute Terms, you are granted a personal, non-sublicensable, non-exclusive, non-transferable, limited license, to use the EigenCompute Services for your internal business or personal purposes according to the service capacity of your account. Any rights not expressly granted herein are reserved and no license or right to use any trademark of Eigen Labs or any third-party is granted to you in connection with the EigenCompute Services. 3. Your Content You are solely responsible for all software, code, data, information, feedback, suggestions, text, content and other materials that you upload, post, deliver, provide or otherwise transmit or store (hereafter "post(ing)") in connection with or relating to the EigenCompute Services ("Your Content"). You are responsible for maintaining the confidentiality of usernames, passwords and private keys associated with your account and for all activities that occur under your account. Eigen Labs reserves the right to access your account in order to respond to your requests for technical support. By posting Your Content on or through the EigenCompute Services, you grant Eigen Labs a worldwide, non-exclusive, royalty-free, fully paid, sublicensable and transferable license to use, copy, modify, reproduce, distribute, display, publish, store and perform Your Content as necessary to provide the EigenCompute Services and for security to protect the EigenCompute Services and third parties from fraud, malware, malicious files or content, viruses and the like. You further agree that Eigen Labs may remove or disable any of Your Content at any time for any reason (including, but not limited to, upon receipt of claims or allegations from third-parties or authorities relating to Your Content), or for no reason at all; provided, that if you are a user of the EigenCompute Services in the European Economic Area (i) we will remove or disable Your Content or impose restrictions on your use of the EigenCompute Services in accordance with applicable laws including if it is illegal content, infringes the rights of third parties, or breaches these EigenCompute Terms; and (ii) if we remove, block or restrict your use of the EigenCompute Services or Your Content, you, and any third party that may have informed us about your use of the EigenCompute Services or Your Content, may contact us about our decision at notices@eigenlabs.org and we will review and consider your message with a view to promptly resolving any complaint and, if appropriate, we will explain any options you have to request another review. 4. Acceptable Use Your use of the EigenCompute Services must comply with our [Acceptable Use Policy](acceptable-use-policy.md), which is incorporated by reference. 5. Security and Compliance a) General. You shall configure Your Content, including any of your projects or deployments, such that the transmission, storage, or use in any way will not expose personal data or personal information without proper consent from individuals as determined by applicable law. You shall configure the EigenCompute Services in accordance with the Documentation and properly implement encryption as set forth in the Documentation. Eigen Labs implements regular backups of Your Content and you shall also maintain your own backups of Your Content. Eigen Labs will have no liability to you for any unauthorized access or use of any of Your Content or any corruption, deletion, destruction or loss of any Your Content to the extent that is attributable, in whole or in part, to your misconfigurations or an insecurity, or malware or malicious content, in Your Content or project. If any actual or suspected security incident, vulnerabilities or violations of this Section 5, or issue related to the EigenCompute Services are identified, you shall immediately report it to security@eigenlabs.org. b) PCI Compliance. Eigen Labs is not a payment processor. To the extent that Your Content or Your Data (as defined below) is subject to the Payment Card Industry Data Security Standards (PCI DSS), you acknowledge that you are responsible for maintaining and monitoring compliance with PCI DSS requirements as prescribed by the PCI Security Standards Council as may be amended from time to time. You agree to comply with any Eigen Labs’ Documentation on appropriate implementation of the EigenCompute Services for processing payments. c) HIPAA Compliance. You shall not use the EigenCompute Services to host any Protected Health Information or information that is subject to the Health Insurance Portability and Accountability Act (HIPAA), unless you first obtain Eigen Labs’ prior written approval. 6. Data Protection a) Use of Your Data. You shall own and retain all right, title and interest in and to Your Data. Eigen Labs may use and disclose Your Data solely to the extent necessary to provide the EigenCompute Services to you and for security to protect the EigenCompute Services and third parties from fraud, illegal activities, abuse, malware, malicious files or content, viruses and the like and for no other purpose. Otherwise, Eigen Labs will not sell, disclose, or share any Your Data (or any part or product thereof) with anyone else. Eigen Labs will implement and maintain reasonable information security policies and processes (including technical, administrative and physical safeguards) that are designed to prevent unauthorized access to or use or disclosure of the EigenCompute Services or any Your Data. b)Aggregate Data. Eigen Labs shall have the right to collect and analyze data and other information relating to the provision, use and performance of various aspects of the EigenCompute Services and related systems and technologies (excluding Your Data and data derived therefrom), and Eigen Labs will be free (during and after the term hereof) to (i) use such information and data to improve and enhance the EigenCompute Services and for other development, diagnostic and corrective purposes in connection with the EigenCompute Services and other EigenCloud offerings, and (ii) disclose such data solely in aggregate or other de-identified form in connection with its business. 7. Usage Restrictions a) Etiquette. Although Eigen Labs has no obligation to monitor your use of the EigenCompute Services, Eigen Labs may do so by using tools that detect patterns of abuse of EigenCompute Services and investigating thereafter. Based on the outcome of these investigations, Eigen Labs may prohibit any use of the EigenCompute Services it believes may be (or is alleged to be) in violation of the foregoing. b) You will not, directly or indirectly: (i) sublicense, resell, rent, lease, transfer, assign, or otherwise commercially exploit or make the EigenCompute Services available to any third party; (ii) reverse engineer, decompile, disassemble or otherwise attempt to discover the source code, object code or underlying structure, ideas, know-how or algorithms relevant to the Services or any software, documentation or data related to the Services (where reverse engineering is permitted by applicable law obtaining such information as is necessary to achieve interoperability with Eigen Labs’ services, you must first request such information from Eigen Labs); (iii) modify, translate, or create derivative works based on the EigenCompute Services (except to the extent expressly permitted by Eigen Labs or authorized within the EigenCompute Services) or otherwise attempt to gain unauthorized access to the EigenCompute Services or its related systems or networks; (iii) use the EigenCompute Services for timesharing or service bureau purposes or otherwise for the benefit of a third-party; (iv) remove, alter or obscure in any way any proprietary rights notices (including copyright notices) of Eigen Labs or its suppliers on or within the Services or documentation; (v) violate any applicable laws or regulations (including without limitation in violation of any data, privacy or export control laws) or infringe the rights of any third-party in connection with the use or access of the EigenCompute Services. You shall comply with any codes of conduct, policies or other notices, Eigen Labs provides you or publishes in connection with the EigenCompute Services, and you shall promptly notify Eigen Labs if you learn of a security breach or issue related to the EigenCompute Services. Without limiting the foregoing, you acknowledge that Eigen Labs may establish general practices and limits concerning use of the EigenCompute Services, including without limitation the maximum period of time that data, code or other content will be retained by the EigenCompute Services, the maximum storage space that will be allotted on Eigen Labs’ servers on your behalf, and the maximum compute capacity provided for the execution of builds and functions and the maximum network data transferred by the EigenCompute Services. You further acknowledge that Eigen Labs reserves the right to change these general practices and limits at any time, in its sole discretion. 8. Support Subject to the terms hereof, Eigen Labs may, but is not required to, provide you with commercially reasonable remote technical support services during Eigen Labs’ normal business hours ("Support Services"). 9. Electronic Communications By using the EigenCompute Services, you consent to receiving electronic communications from Eigen Labs. These electronic communications may include notices about applicable EigenCompute Services fees and charges related to the EigenCompute Services and transactional or other information concerning or related to the EigenCompute Services. They may also include notices that require responses and or action to avoid service interruptions. These electronic communications are part of your relationship with Eigen Labs, and you receive them as part of your use of the EigenCompute Services. If you provide an email address for your account, this email address must be kept current and maintain a responsive user at all times. You agree that any notices, agreements, disclosures or other communications that Eigen Labs sends you electronically will satisfy any legal communication requirements, including that such communications be in writing. 10. Representations and Warranties a) You represent and warrant that (i) you own all Your Content or have obtained all permissions, releases, rights or licenses required to engage in posting and other activities (and allow Eigen Labs to perform its obligations) in connection with the EigenCompute Services without obtaining any further releases or consents; (ii) Your Content and other activities in connection with the EigenCompute Services, and Eigen Labs’ exercise of all rights and license granted by you herein, do not and will not violate, infringe, or misappropriate any third party's copyright, trademark, right of privacy, or publicity, or other personal or proprietary right and Your Content is not defamatory, obscene, unlawful, threatening, abusive, tortious, offensive or harassing; and (iii) you will use the EigenCompute Services only in compliance with Eigen Labs’ standard published policies and documentation then in effect and all applicable laws and regulations. b) Each party represents and warrants to the other that it has full right and power to enter into and perform under these EigenCompute Terms, without any third-party consents or conflicts with any other agreement. 11. Indemnification You will indemnify and hold harmless Eigen Labs against any claims, actions or demands, including without limitation reasonable legal and accounting fees, arising or resulting from your breach of these EigenCompute Terms, any claim of infringement or misappropriation arising out of any of Your Content or websites, applications or services that depend or utilize Your Content or the EigenCompute Services, or your other access, contribution to, use or misuse of the EigenCompute Services. Eigen Labs shall promptly notify you of any and all threats, claims and proceedings related thereto and give you reasonable assistance and the opportunity to assume sole control over defense and settlement; you will not be responsible for any settlement you do not approve, such approval not to be unreasonably withheld or delayed. 12. Confidentiality; Proprietary Rights a) Confidentiality. Each party (the "Receiving Party") understands that the other party (the "Disclosing Party") has disclosed or may disclose business, technical, product or financial information or data relating to the Disclosing Party's business (hereinafter referred to as "Proprietary Information" of the Disclosing Party). Proprietary Information of Eigen Labs includes non-public information regarding features, functionality and performance of the EigenCompute Services. Your Proprietary Information includes non-public personal data provided by you to Eigen Labs to enable the provision of the EigenCompute Services and that you upload or post to the EigenCompute Services (collectively, "Your Data"). The Receiving Party agrees: (i) to take reasonable precautions to protect such Proprietary Information, and (ii) not to use (except in performance of the EigenCompute Services or as otherwise permitted herein) or divulge to any third person any such Proprietary Information. The Disclosing Party agrees that the foregoing shall not apply with respect to any information after five (5) years following the disclosure thereof or any information that the Receiving Party can document (a) is or becomes generally available to the public, or (b) was rightfully in its possession or known by it prior to receipt from the Disclosing Party, or (c) was rightfully disclosed to it without confidentiality restrictions by a third party, or (d) was independently developed without use of any Proprietary Information of the Disclosing Party as evidenced by its internal files. If a Receiving Party is required by law or a governmental agency to disclose the Disclosing Party's Proprietary Information, the Receiving Party must provide reasonable notice to the Disclosing Party of such required disclosure so as to permit the Disclosing Party a reasonable period of time to seek a protective order or limit the amount of Proprietary Information to be disclosed. b) Company Ownership. Eigen Labs shall own and retain all right, title and interest in and to (a) the EigenCompute Services, all improvements, enhancements or modifications thereto and (b) all intellectual property rights related to any of the foregoing. c) Feedback. To the extent you or any of your users provide any suggestions to Eigen Labs regarding the functioning, features, and other characteristics of the EigenCompute Services, documentation, or other material or services provided or made available by Eigen Labs ("Feedback"), you hereby grant Eigen Labs a perpetual, irrevocable, non-exclusive, royalty-free, fully-paid-up, fully transferable, worldwide license (with rights to sublicense through multiple tiers of sublicenses) under all of your intellectual property rights, for Eigen Labs to use and exploit in any manner and for any purpose. d) Customer Name. During the term of these EigenCompute Terms, you grant Eigen Labs a non-exclusive, royalty-free, fully-paid up license to use and reproduce your trademarks, tradenames and logos in Eigen Labs’ marketing materials and website(s) and to indicate that you are an Eigen Labs customer. Eigen Labs will abide by any written trademark usage guidelines provided by you. All goodwill arising out of the use of your trademarks, tradenames and logos shall inure to your benefit. 13. Payment of Fees a) Plans. The EigenCompute Services will be provided according to the plan level you select. There are paid testnet and mainnet self-service subscription plans for the EigenCompute Services ("self-service subscriptions"). For an enterprise license, you may contact Eigen Labs separately. You may opt to upgrade or downgrade to any other plan level that Eigen Labs offers at any time during the period of your plan; provided that a downgrade will not be effective until the next renewal date. For self-service subscriptions and any additional EigenCompute Services added to your self-service subscription, you will be charged a fee and any applicable tax. Fees will be billed to the credit card or other payment account you provide in accordance with the billing terms in effect at the time a fee or charge is due and payable. You acknowledge and agree that Eigen Labs will automatically charge your credit card or other payment account on record with Eigen Labs in connection with your use of the EigenCompute Services: (i) in advance of each self-service subscription term, for the self-service subscription you have selected and any additional EigenCompute Services added to your self-service subscription; and (ii) in arrears for any additional EigenCompute Services you have used or added to your self-service subscription during the prior self-service subscription term. The self-service subscription and any additional EigenCompute Services added to your self-service subscription will automatically-renew for the same term as the initial term. You represent and warrant to Eigen Labs that all of your payment information is true and that you are authorized to use the payment instrument. You will promptly update your account information with any changes (for example, a change in your billing address or credit card expiration date) that may occur. If payment is not received or cannot be charged to your credit card or other payment account for any reason in advance, Eigen Labs reserves the right to either suspend or terminate your access to the EigenCompute Services and terminate these EigenCompute Terms with you. All fees are non-refundable, except as expressly stated otherwise in these EigenCompute Terms. b) Payments. All payments shall be made in the currency of, and within the borders of the United States. You will pay all applicable taxes, duties, withholdings, backup withholding and the like; when Eigen Labs has the legal obligation to pay or collect such taxes, the appropriate amount shall be paid by you directly to Eigen Labs. If all or any part of any payment owed to Eigen Labs under these EigenCompute Terms is withheld, based upon a claim that such withholding is required pursuant to the tax laws of any country or its political subdivisions and/or any tax treaty between the U.S. and any such country, such payment shall be increased by the amount necessary to result in a net payment to Eigen Labs of the amounts otherwise payable under these EigenCompute Terms. You will reimburse Eigen Labs any pre-approved and agreed upon costs. Eigen Labs may change its fees and payment terms at its discretion; provided however, that such changes will not take effect for you until the start of the next payment period. Eigen Labs will provide written notice to you for any changes to the fees that affect the EigenCompute Services purchased by you. Your continued use of the EigenCompute Services after the price change becomes effective constitutes your agreement to pay the changed amount. 14. Term and Termination a) Term. Subject to earlier termination as provided below, the term of these EigenCompute Terms will commence on your acceptance hereof and will continue for as long as the EigenCompute Services are being provided to you under these EigenCompute Terms. The term of your self-service subscription, and any EigenCompute Services purchased or added to your self-service subscription, shall automatically renew for successive terms equal in duration to the initial term unless you cancel your self-service subscription in advance of the renewal date. You have the right to terminate your account (or downgrade your mainnet self-service subscription to a testnet self-service subscription) at any time provided that such termination will be effective at the start of the next renewal period. Subject to earlier termination as provided below, Eigen Labs may terminate your account and these EigenCompute Terms with you at any time by providing thirty (30) days prior notice to the administrative email address associated with your account. In addition to any other remedies Eigen Labs may have, Eigen Labs may also terminate these EigenCompute Terms 'upon ten (10) days' notice (or two (2) days in the case of nonpayment), if you breach any of the terms or conditions of the Terms. Eigen Labs may terminate your account, self-service subscription and these EigenCompute Terms with you immediately if you exceed any Eigen Labs limits concerning use of the EigenCompute Services, including without limitation, the maximum period of time that data, code or other content will be retained by the EigenCompute Services, the maximum storage space that will be allotted on Eigen Labs servers on your behalf, and the maximum compute capacity provided for the execution of builds and functions and the maximum network data transferred by the EigenCompute Services. You acknowledge that Eigen Labs reserves the right to terminate accounts that are inactive for an extended period of time and the right to modify or discontinue, temporarily or permanently, the EigenCompute Services (or any part thereof). All of Your Content on the EigenCompute Services (if any) may be permanently deleted by Eigen Labs upon any termination of your account. If Eigen Labs terminates your account without cause and you have signed up for a self-service subscription, Eigen Labs will refund the pro-rated, unearned portion of any amount that you have prepaid to Eigen Labs for such EigenCompute Services. b) Survival. All sections of these EigenCompute Terms which by their nature should survive termination will survive termination, including, without limitation, Sections 13(a) and 13(b), and accrued rights to payment, confidentiality obligations, warranty disclaimers, and limitations of liability. c) Effect of Termination. Upon the termination of these EigenCompute Terms for any reason: (i) the licenses granted hereunder in respect of the EigenCompute Services shall immediately terminate and you and your users shall cease use of the EigenCompute Services; (ii) EigenCompute will cease providing any Support Services; (iii) you shall pay to Eigen Labs the full amount of any outstanding fees due hereunder; and (iv) within fourteen (14) calendar days of such termination, each party shall destroy or return all Proprietary Information of the other party in its possession or control, and will not make or retain any copies of such information in any form, except that the receiving party may retain one (1) archival copy of such information solely for purposes of ensuring compliance with EigenCompute Terms. 15. Disclaimer THE EIGENCOMPUTE SERVICES AND SUPPORT SERVICES ARE PROVIDED "AS IS" AND EIGEN LABS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. EIGEN LABS DOES NOT WARRANT THAT THE SERVICES OR DELIVERABLES WILL BE UNINTERRUPTED OR ERROR FREE; NOR DOES IT MAKE ANY WARRANTY AS TO THE RESULTS THAT MAY BE OBTAINED FROM USE OF THE SERVICES OR DELIVERABLES. 16. Limitation of Liability a) Limit of Liability and Waiver of Consequential Damages. EXCEPT FOR YOUR BREACH OF SECTIONS 7, 12, AND 13, OR YOUR BREACH OF ANY REPRESENTATIONS OR WARRANTIES OR YOUR INDEMNITY OBLIGATIONS, NEITHER PARTY NOR ITS SUPPLIERS (INCLUDING BUT NOT LIMITED TO ALL EQUIPMENT AND TECHNOLOGY SUPPLIERS), OFFICERS, SHAREHOLDERS, AFFILIATES, REPRESENTATIVES, CONTRACTORS AND EMPLOYEES SHALL BE RESPONSIBLE OR LIABLE WITH RESPECT TO ANY SUBJECT MATTER OF THIS AGREEMENT OR TERMS AND CONDITIONS RELATED THERETO UNDER ANY CONTRACT, NEGLIGENCE, STRICT LIABILITY OR OTHER THEORY: (A) FOR ERROR OR INTERRUPTION OF USE OR FOR LOSS OR INACCURACY OR CORRUPTION OF DATA OR COST OF PROCUREMENT OF SUBSTITUTE GOODS, SERVICES OR TECHNOLOGY OR LOSS OF BUSINESS; (B) FOR ANY INDIRECT, SPECIAL, EXEMPLARY, INCIDENTAL, CONSEQUENTIAL OR PUNITIVE DAMAGES; OR (C) FOR ANY DIRECT DAMAGES, COSTS, LOSSES, OF LIABILITIES IN AMOUNTS THAT, TOGETHER WITH AMOUNTS ASSOCIATED WITH ALL OTHER CLAIMS, EXCEED THE GREATER OF ONE HUNDRED DOLLARS AND THE FEES PAID BY YOU TO EIGEN LABS FOR THE EIGENCOMPUTE SERVICES UNDER THESE EIGENCOMPUTE TERMS IN THE 6 MONTHS PRIOR TO THE ACT THAT GAVE RISE TO THE LIABILITY, IN EACH CASE, WHETHER OR NOT SUCH PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE PROVISIONS OF THIS SECTION ALLOCATE THE RISKS UNDER THIS AGREEMENT BETWEEN THE PARTIES, AND THE PARTIES HAVE RELIED ON THESE LIMITATIONS IN DETERMINING WHETHER TO ENTER THIS AGREEMENT. b) Limits. Some states do not allow the exclusion of implied warranties or limitation of liability for incidental or consequential damages, which means that some of the above limitations may not apply to you. IN THESE STATES, EIGEN LABS’ LIABILITY WILL BE LIMITED TO THE GREATEST EXTENT PERMITTED BY LAW. 17. Miscellaneous Eigen Labs may change these EigenCompute Terms from time to time by providing notice either by emailing the email address associated with your account or by posting a notice at https://eigencloud.xyz and by updating the "Last Revised" date at the top of these EigenCompute Terms. You can review the most current version of these EigenCompute Terms at any time at https://docs.eigencloud.xyz. The revised EigenCompute Terms will become effective immediately after Eigen Labs posts or sends you notice of such changes, and if you use the EigenCompute Services after that date, your use will constitute acceptance of the revised EigenCompute Terms. If any change to these EigenCompute Terms is not acceptable to you, your only remedy is to stop using the EigenCompute Services. If any provision of these EigenCompute Terms is found to be unenforceable or invalid, that provision will be limited or eliminated to the minimum extent necessary so that these EigenCompute Terms will otherwise remain in full force and effect and enforceable. You may not assign, transfer or sublicense these EigenCompute Terms or your rights or obligations hereunder without the prior written consent of Eigen Labs, but Eigen Labs may assign or transfer these EigenCompute Terms, in whole or in part, without restriction. Any attempted assignment or transfer of these EigenCompute Terms by the parties in contravention of the foregoing shall be null and void. Eigen Labs’ failure to exercise or enforce any right or provision of these EigenCompute Terms shall not be a waiver of that right. No agency, partnership, joint venture, or employment is created as a result of these EigenCompute Terms and neither party has any authority of any kind to bind the other party in any respect whatsoever. In any action or proceeding to enforce rights under these EigenCompute Terms, the prevailing party will be entitled to recover costs and attorneys' fees. All notices under these EigenCompute Terms will be in writing and will be deemed to have been duly given when received, if personally delivered; when receipt is electronically confirmed, if transmitted by email; the day after it is sent, if sent for next day delivery by recognized overnight delivery service; and upon receipt, if sent by certified or registered mail, return receipt requested. Any delays in or failure of performance of Eigen Labs shall not constitute a default hereunder or give rise to any claims for damages if, to the extent that, and for such period that, such delays or failures of performance are caused by any events beyond the reasonable control of Eigen Labs including, without limitation, any of the following specific occurrences: acts of God or the public enemy, acts of terrorism, pandemics, epidemics, labor strikes, expropriation or confiscation of facilities, compliance with any unanticipated duly promulgated governmental order, acts of war, rebellion or sabotage or damage resulting therefrom, fires, floods, explosion, or riots. --- --- title: EigenAI Terms sidebar_position: 4 --- # EigenAI Terms ***Last Revised: December 15, 2025*** The EigenAI Terms (“EigenAI Terms”) to our Terms of Service (made available at https://docs.eigencloud.xyz/products/eigenlayer/legal/terms-of-service), or any other agreement you (“Customer” or “you”) have entered with Eigen Labs, Inc. (“Eigen Labs”, “we”, or “us”) governing the provision of the EigenAI cloud-based platform or software services to you (collectively, the “Terms”) form a part of the Terms. The EigenAI Terms are effective as of the date you first access and use the EigenAI Services (“Effective Date”) and apply to your use of the EigenAI Services (as defined below). By accessing or using the EigenAI Services, you agree to be bound by the EigenAI Terms. Except as set forth below, all other terms and conditions of the Terms are incorporated by reference and will remain in full force and effect. If any EigenAI Terms conflict with the Terms, the conflicting EigenAI Terms will control with respect to the EigenAI Services. The EigenAI Terms supersede all other understandings or agreements between you and Eigen Labs regarding the EigenAI Services. Capitalized terms used but not defined herein shall have the meaning given in the Terms. Your use of certain EigenAI Services may be subject to additional terms (“Supplemental Terms”). Any Supplemental Terms will either be incorporated into the EigenAI Terms or presented to you for acceptance when you sign up for or access the applicable supplemental EigenAI Service. If there is any conflict between the Terms (including these EigenAI Terms) and any Supplemental Terms, the Supplemental Terms will control with respect to the applicable supplemental EigenAI Service. IF YOU ARE ENTERING INTO THESE EIGENAI TERMS ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE LEGAL AUTHORITY TO BIND THE ENTITY TO THESE TERMS, IN WHICH CASE “CUSTOMER” OR “YOU” (WHETHER OR NOT CAPITALIZED) MEANS THE ENTITY YOU REPRESENT. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT AGREE WITH THE EIGENAI TERMS YOU SHOULD NOT ACCEPT THE EIGENAI TERMS AND MAY NOT USE THE EIGENAI SERVICES. 1. **The Services** Eigen Labs provides a large language model (“LLM”) inference API and related services that allow users to access open-source LLMs to submit Inputs and receive model-generated, deterministic Outputs (the “EigenAI Services”). Eigen Labs currently provides the EigenAI Services through Lambda, Inc. and reserves the right to provide EigenAI Services through other third-party hosting services. EigenAI Outputs may be inaccurate, incomplete, biased or unsafe. Deterministic Outputs do not guarantee correctness or accuracy. 2. **License and IP** During the period for which you are authorized to use the EigenCompute Services, and subject to your compliance with the Terms of Service, including the EigenAI Terms and the Acceptable Use Policy, you are granted a personal, revocable, non-sublicensable, non-exclusive, non-transferable, limited license to use the EigenAI Services for your internal business or personal purposes according to the service capacity, usage limits and rate limits of your account. As part of the EigenAI Services, Eigen Labs may provide you, pursuant to the foregoing license grant, with certain application programming interfaces (APIs), API access tokens, data import tools or other software as applicable (collectively, “APIs”). Any rights not expressly granted herein are reserved and no license or right to use any intellectual property of Eigen Labs or any third-party is granted to you in connection with the EigenAI Services. Through the EigenAI Services, you may have access to infrastructure on which you access or use models trained by third parties, and/or with third party data. Such models may come with their own terms and conditions, including regarding commercial use. It is your responsibility to comply with the terms and conditions of those models. In case of any conflict between the EigenAI Terms and such model terms, the model terms govern. 3. **Your Content and Responsibilities** a. You are solely responsible for all software, code, data, information, feedback, suggestions, text, prompts, content and other materials that you upload, post, deliver, provide or otherwise transmit or store (hereafter “"post(ing)”") in connection with or relating to the EigenAI Services (“Input”). You may receive output from the EigenAI Services based on the Input (“Output”). Input and Output are collectively “Your Content.” As between you and Eigen Labs, and to the extent permitted by applicable law, you (i) retain ownership rights in your Input and (b) own the Output. Subject to your compliance with the Terms of Service, we hereby assign to you all our right, title and interest, if any, in and to Output. You acknowledge that EigenAI may generate inaccurate, misleading, biased, harmful or unsafe Output, and you are solely responsible for evaluating and verifying all Output before relying on or otherwise implementing such Output. Eigen Labs makes no guarantee of correctness, accuracy or suitability of any Output. b. You are responsible for maintaining the confidentiality of usernames. passwords and private keys associated with your account and for all activities that occur under your account. Eigen Labs reserves the right to access your account in order to respond to your requests for technical support. By posting Your Content on or through the EigenAI Services, you grant Eigen Labs a worldwide, non-exclusive, royalty-free, fully paid, sublicensable and transferable license to use, copy, modify, reproduce, distribute, display, publish, store and perform Your Content as necessary to provide the EigenAI Services and for security to protect the EigenAI Services and third parties from fraud, malware, malicious files or content, viruses and the like. You further agree that Eigen Labs may remove or disable any of Your Content at any time for any reason (including, but not limited to, upon receipt of claims or allegations from third-parties or authorities relating to Your Content), or for no reason at all; provided, that if you are a user of the EigenAI Services in the European Economic Area (i) we will remove or disable Your Content or impose restrictions on your use of the EigenAI Services in accordance with applicable laws including if it is illegal content, infringes the rights of third parties, or breaches these EigenAI Terms; and (ii) if we remove, block or restrict your use of the EigenAI Services or Your Content, you, and any third party that may have informed us about your use of the EigenAI Services or Your Content, may contact us about our decision at notices@eigenlabs.org and we will review and consider your message with a view to promptly resolving any complaint and, if appropriate, we will explain any options you have to request another review. c. You will (i) use commercially reasonable efforts to prevent unauthorized access to or use of the EigenAI Services and notify us promptly of any such unauthorized access or use or any other known or suspected breach of security or misuse of the EigenAI Services and (ii) be responsible for obtaining and maintaining any equipment, software and ancillary services needed to connect to, access or otherwise use the EigenAI Services. 4. **Acceptable Use** Your use of the EigenAI Services must comply with our Acceptable Use Policy, which is incorporated by reference. 5. **Security and Compliance** a. General. You shall configure Your Content, including any of your projects or deployments, such that the transmission, storage, or use in any way will not expose personal data or personal information without proper consent from individuals as determined by applicable law. EigenAI is not designed for processing sensitive or regulated data without a separate written agreement between you and Eigen Labs. You shall configure the EigenAI Services in accordance with the Documentation and properly implement encryption as set forth in the Documentation. You acknowledge that improper configuration may result in unintended disclosure of Your Content. Eigen Labs implements regular backups of Your Content and you shall also maintain your own backups of Your Content. Eigen Labs will have no liability to you for any unauthorized access or use of any of Your Content or any corruption, deletion, destruction or loss of any Your Content to the extent that is attributable, in whole or in part, to your misconfigurations or an insecurity, or malware or malicious content, in Your Content or project. If any actual or suspected security incident, vulnerabilities or violations of this Section 5, or issue related to the EigenAI Services are identified, you shall immediately report it to security@eigenlabs.org. Eigen Labs does not represent or warrant that the EigenAI Services are free of vulnerabilities or immune to security incidents. b. PCI Compliance. Eigen Labs is not a payment processor. Payments for EigenAI may be processed by third-party payment processors (such as Stripe). Eigen Labs does not store your payment card information. To the extent that Your Content or Your Data (as defined below) is subject to the Payment Card Industry Data Security Standards (PCI DSS), you acknowledge that you are responsible for maintaining and monitoring compliance with PCI DSS requirements as prescribed by the PCI Security Standards Council as may be amended from time to time. You agree to comply with any Eigen Labs’ Documentation on appropriate implementation of the EigenAI Services for processing payments. c. HIPAA Compliance. You shall not use the EigenAI Services to host any Protected Health Information or information that is subject to the Health Insurance Portability and Accountability Act (HIPAA), unless you first obtain Eigen Labs’ prior written approval. 6. **Data Protection** a. Use of Your Data. You shall own and retain all right, title and interest in and to Your Data. Eigen Labs may use and disclose Your Data solely to the extent necessary to provide the EigenAI Services to you and for security to protect the EigenAI Services and third parties from fraud, illegal activities, abuse, malware, malicious files or content, viruses and the like and for no other purpose. Eigen AI does not use Your Data to train or improve models unless you expressly opt in. Otherwise, Eigen Labs will not sell, disclose, or share any Your Data (or any part or product thereof) with anyone else. Eigen Labs will implement and maintain reasonable information security policies and processes (including technical, administrative and physical safeguards) that are designed to prevent unauthorized access to or use or disclosure of the EigenAI Services or any Your Data. b. Aggregate Data. Eigen Labs shall have the right to collect and analyze data and other information relating to the provision, use and performance of various aspects of the EigenAI Services and related systems and technologies (excluding Your Data and data derived therefrom), and Eigen Labs will be free (during and after the term hereof) to (i) use such information and data to improve and enhance the EigenAI Services and for other development, diagnostic and corrective purposes in connection with the EigenAI Services and other EigenCloud offerings, and (ii) disclose such data solely in aggregate or other de-identified form in connection with its business. 7. **Usage Restrictions** a. Etiquette. Although Eigen Labs has no obligation to monitor your use of the EigenAI Services, Eigen Labs may do so by using tools that detect patterns of abuse of EigenAI Services and investigating thereafter. Based on the outcome of these investigations, Eigen Labs may prohibit any use of the EigenAI Services it believes may be (or is alleged to be) in violation of the foregoing. b. You will not, directly or indirectly: (i) sublicense, resell, rent, lease, transfer, assign, or otherwise commercially exploit or make the EigenCompute Services available to any third party; (ii) reverse engineer, decompile, disassemble or otherwise attempt to discover the source code, object code or underlying structure, ideas, know-how or algorithms relevant to the Services or any software, documentation or data related to the Services (where reverse engineering is permitted by applicable law obtaining such information as is necessary to achieve interoperability with Eigen Labs’ services, you must first request such information from Eigen Labs); (iii) modify, translate, or create derivative works based on the EigenAI Services (except to the extent expressly permitted by Eigen Labs or authorized within the EigenAI Services) or otherwise attempt to gain unauthorized access to the EigenAI Services or its related systems or networks; (iv) use the EigenAI Services for timesharing or service bureau purposes or otherwise for the benefit of a third-party; (v) remove, alter or obscure in any way any proprietary rights notices (including copyright notices) of Eigen Labs or its suppliers on or within the Services or documentation; (vi) violate any applicable laws or regulations (including without limitation in violation of any data, privacy or export control laws) or infringe the rights of any third-party in connection with the use or access of the EigenAI Services. You shall comply with any codes of conduct, policies or other notices, Eigen Labs provides you or publishes in connection with the EigenAI Services, and you shall promptly notify Eigen Labs if you learn of a security breach or issue related to the EigenAI Services. Without limiting the foregoing, you acknowledge that Eigen Labs may establish general practices and limits concerning use of the EigenAI Services, including without limitation the maximum period of time that data, code or other content will be retained by the EigenAI Services, the maximum storage space that will be allotted on Eigen Labs’ servers on your behalf, and the maximum capacity provided and the maximum network data transferred by the EigenAI Services. You further acknowledge that Eigen Labs reserves the right to change these general practices and limits at any time, in its sole discretion. 8. **Support** Subject to the terms hereof, Eigen Labs may, but is not required to, provide you with commercially reasonable remote technical support services during Eigen Labs’ normal business hours (“Support Services”). 9. **Electronic Communications** By using the EigenAI Services, you consent to receiving electronic communications from Eigen Labs. These electronic communications may include notices about applicable EigenAI Services fees and charges related to the EigenAI Services and transactional or other information concerning or related to the EigenAI Services. They may also include notices that require responses and or action to avoid service interruptions. These electronic communications are part of your relationship with Eigen Labs, and you receive them as part of your use of the EigenAI Services. If you provide an email address for your account, this email address must be kept current and maintain a responsive user at all times. You agree that any notices, agreements, disclosures or other communications that Eigen Labs sends you electronically, including to an email address provided for your account, will satisfy any legal communication requirements, including that such communications be in writing. 10. **Representations and Warranties** a. You represent and warrant that (i) you own all Your Content or have obtained all permissions, releases, rights or licenses required to engage in posting and other activities (and allow Eigen Labs to perform its obligations) in connection with the EigenAI Services without obtaining any further releases or consents; (ii) Your Content and other activities in connection with the EigenAI Services, and Eigen Labs’ exercise of all rights and license granted by you herein, do not and will not violate, infringe, or misappropriate any third party's copyright, trademark, right of privacy, or publicity, or other personal or proprietary right and Your Content is not defamatory, obscene, unlawful, threatening, abusive, tortious, offensive or harassing; (iii) you will use the EigenAI Services only in compliance with Eigen Labs’ standard published policies and documentation then in effect and all applicable laws and regulations; and (iv) Output generated by EigenAI may be inaccurate, incomplete, biased, unsafe or otherwise unsuitable for your use case and you will independently verify all Output before relying on such Output. b. Each party represents and warrants to the other that it has full right and power to enter into and perform under these EigenAI Terms, without any third-party consents or conflicts with any other agreement. 11. **Indemnification** You will indemnify and hold harmless Eigen Labs against any claims, actions or demands, including without limitation reasonable legal and accounting fees, arising or resulting from your breach of these EigenAI Terms, your reliance on any Output, any claim of infringement or misappropriation arising out of any of Your Content or websites, applications or services that depend or utilize Your Content or the EigenAI Services, or your other access, contribution to, use or misuse of the EigenAI Services or any Third Party Services or Third Party Materials. Eigen Labs shall promptly notify you of any and all threats, claims and proceedings related thereto and give you reasonable assistance and the opportunity to assume sole control over defense and settlement; you will not be responsible for any settlement you do not approve, such approval not to be unreasonably withheld or delayed. 12. **Confidentiality; Proprietary Rights** a. Confidentiality. Each party (the “Receiving Party”) understands that the other party (the “Disclosing Party”) has disclosed or may disclose business, technical, product or financial information or data relating to the Disclosing Party's business (hereinafter referred to as "Proprietary Information" of the Disclosing Party). Proprietary Information of Eigen Labs includes non-public information regarding features, functionality and performance of the EigenAI Services. Your Proprietary Information includes non-public personal data provided by you to Eigen Labs to enable the provision of the EigenAI Services and any data that you upload or post to the EigenAI Services (collectively, "Your Data"). “Your Data” excludes Input and Output, including any personal information about third parties contained therein. The Receiving Party agrees: (i) to take reasonable precautions to protect such Proprietary Information, and (ii) not to use (except in performance of the EigenAI Services or as otherwise permitted herein) or divulge to any third person any such Proprietary Information. The Disclosing Party agrees that the foregoing shall not apply with respect to any information after five (5) years following the disclosure thereof or any information that the Receiving Party can document (a) is or becomes generally available to the public, or (b) was rightfully in its possession or known by it prior to receipt from the Disclosing Party, or (c) was rightfully disclosed to it without confidentiality restrictions by a third party, or (d) was independently developed without use of any Proprietary Information of the Disclosing Party as evidenced by its internal files. If a Receiving Party is required by law or a governmental agency to disclose the Disclosing Party's Proprietary Information, the Receiving Party must provide reasonable notice to the Disclosing Party of such required disclosure so as to permit the Disclosing Party a reasonable period of time to seek a protective order or limit the amount of Proprietary Information to be disclosed. b. Company Ownership. Eigen Labs shall own and retain all right, title and interest in and to (a) the EigenAI Services, all improvements, enhancements or modifications thereto and (b) all intellectual property rights related to any of the foregoing. For clarity, nothing in these EigenAI Terms grants you any rights or licenses in or to any hosted model, model weights, model training data, or in any EigenAI runtime, inference stack or backend infrastructure. c. Feedback. To the extent you or any of your users provide any suggestions to Eigen Labs regarding the functioning, features, and other characteristics of the EigenAI Services, documentation, or other material or services provided or made available by Eigen Labs ("Feedback"), you hereby grant Eigen Labs a perpetual, irrevocable, non-exclusive, royalty-free, fully-paid-up, fully transferable, worldwide license (with rights to sublicense through multiple tiers of sublicenses) under all of your intellectual property rights, for Eigen Labs to use and exploit in any manner and for any purpose, including developing or improving LLM models, services or infrastructure. d. Customer Name. During the term of these EigenAI Terms, you grant Eigen Labs a non-exclusive, royalty-free, fully-paid up license to use and reproduce your trademarks, tradenames and logos in Eigen Labs’ marketing materials and website(s) and to indicate that you are an Eigen Labs customer. Eigen Labs will abide by any written trademark usage guidelines provided by you. All goodwill arising out of the use of your trademarks, tradenames and logos shall inure to your benefit. 13. **Payment of Fees** a. Third-Party Payment Processor. Eigen Labs uses Stripe, Inc. and its affiliates as its third-party service provider for payment processing services (including card acceptance, billing, merchant settlement, and related services) (the “Payment Processor”). If you purchase EigenAI subscription services or incur usage-based fees, you will be required to provide payment details and any additional information necessary to complete the transaction directly to the Payment Processor. You agree to be bound by Stripe’s Privacy Policy (currently available at https://stripe.com/us/privacy) and Stripe’s Terms of Service or Stripe Connected Account Agreement, as applicable (currently available at https://stripe.com/ssa), and you authorize Eigen Labs and the Payment Processor to share information and payment instructions you provide to the minimum extent necessary to complete your transactions. Eigen Labs is not responsible if your card issuer declines to authorize payment for any reason. Your card issuer may charge you additional fees (such as processing or handling fees), and Eigen Labs is not responsible for such fees. b. Plans. The EigenAI Services will be provided according to the plan level you select. There are paid testnet and mainnet self-service subscription plans for the EigenAI Services (“self-service subscriptions”). For an enterprise license, you may contact Eigen Labs separately. You may opt to upgrade or downgrade to any other plan level that Eigen Labs offers at any time during the period of your plan; provided that a downgrade will not be effective until the next renewal date. For self-service subscriptions and any additional EigenAI Services added to your self-service subscription, you will be charged a fee and any applicable tax. Fees will be billed via our Payment Processor to the payment method you provide to the Payment Processor in accordance with the billing terms in effect at the time a fee or charge is due and payable. You acknowledge and agree that our Payment Processor will automatically charge your credit card or other payment account on record with in connection with your use of the EigenAI Services: (i) in advance of each self-service subscription term, for the self-service subscription you have selected and any additional EigenAI Services added to your self-service subscription; and (ii) in arrears for any additional EigenAI Services you have used or added to your self-service subscription during the prior self-service subscription term. Usage-based charges may include, but are not limited to, model inference costs, overages or additional feature usage. The self-service subscription and any additional EigenAI Services added to your self-service subscription will automatically-renew for the same term as the initial term. You may cancel auto-renewal through your account settings. You represent and warrant to Eigen Labs that all of your payment information is true and that you are authorized to use the payment instrument. You will promptly update your account information with any changes (for example, a change in your billing address or credit card expiration date) that may occur. If the Payment Processor is unable to process payment for any reason in advance, Eigen Labs reserves the right to either suspend or terminate your access to the EigenAI Services and terminate these EigenAI Terms with you. All fees are non-refundable, except as expressly stated otherwise in these EigenAI Terms. c. Payments. All payments shall be made in the currency of, and within the borders of the United States. You will pay all applicable taxes, duties, withholdings, backup withholding and the like; when Eigen Labs has the legal obligation to pay or collect such taxes, the appropriate amount shall be paid by you directly to Eigen Labs. If all or any part of any payment owed to Eigen Labs under these EigenAI Terms is withheld, based upon a claim that such withholding is required pursuant to the tax laws of any country or its political subdivisions and/or any tax treaty between the U.S. and any such country, such payment shall be increased by the amount necessary to result in a net payment to Eigen Labs of the amounts otherwise payable under these EigenAI Terms. You will reimburse Eigen Labs any pre-approved and agreed upon costs. Eigen Labs may change its fees and payment terms at its discretion; provided however, that such changes will not take effect for you until the start of the next payment period. Eigen Labs will provide written notice to you for any changes to the fees that affect the EigenAI Services purchased by you. Fee changes may be posted on the Eigen AI dashboard or emailed to your billing contact. Your continued use of the EigenAI Services after the price change becomes effective constitutes your agreement to pay the changed amount. 14. **Term and Termination** a. Term. Subject to earlier termination as provided below, the term of these EigenAI Terms will commence on your acceptance hereof and will continue for as long as the EigenAI Services are being provided to you under these EigenAI Terms. The term of your self-service subscription, and any EigenAI Services purchased or added to your self-service subscription, shall automatically renew for successive terms equal in duration to the initial term unless you cancel your self-service subscription in advance of the renewal date. You have the right to terminate your account (or downgrade your mainnet self-service subscription to a testnet self-service subscription) at any time provided that such termination will be effective at the start of the next renewal period. Subject to earlier termination as provided below, Eigen Labs may terminate your account and these EigenAI Terms with you at any time by providing thirty (30) days prior notice to the administrative email address associated with your account. In addition to any other remedies Eigen Labs may have, Eigen Labs may also terminate these EigenAI Terms upon ten (10) days' notice (or two (2) days in the case of nonpayment), if you breach any of the terms or conditions of the Terms. Eigen Labs may immediately suspend your access to EigenAI if your use poses security or operational risks. Eigen Labs may suspend or terminate your account, self-service subscription and these EigenAI Terms with you immediately if you exceed any Eigen Labs limits concerning use of the EigenAI Services, including without limitation, the maximum period of time that data, code or other content will be retained by the EigenAI Services, the maximum storage space that will be allotted on Eigen Labs servers on your behalf, and the maximum compute capacity provided for the execution of builds and functions and the maximum network data transferred by the EigenAI Services. You acknowledge that Eigen Labs reserves the right to terminate accounts that are inactive for an extended period of time and the right to modify or discontinue, temporarily or permanently, the EigenAI Services (or any part thereof). All of Your Content on the EigenAI Services (if any) may be permanently deleted by Eigen Labs upon any termination of your account. Eigen Labs has no obligation to return or export Output upon termination. If Eigen Labs terminates your account without cause and you have signed up for a self-service subscription, Eigen Labs will refund the pro-rated, unearned portion of any amount that you have prepaid to Eigen Labs for such EigenAI Services. b. Survival. All sections of these EigenAI Terms which by their nature should survive termination will survive termination, including, without limitation, Sections 13(a) and 13(b), and accrued rights to payment, confidentiality obligations, warranty disclaimers, and limitations of liability. c. Effect of Termination. Upon the termination of these EigenAI Terms for any reason: (i) the licenses granted hereunder in respect of the EigenAI Services shall immediately terminate and you and your users shall cease use of the EigenAI Services; (ii) EigenAI will cease providing any Support Services; (iii) you shall pay to Eigen Labs the full amount of any outstanding fees due hereunder; and (iv) within fourteen (14) calendar days of such termination, each party shall destroy or return all Proprietary Information of the other party in its possession or control, and will not make or retain any copies of such information in any form, except that the receiving party may retain one (1) archival copy of such information solely for purposes of ensuring compliance with EigenAI Terms. 15. Disclaimer THE EIGENAI SERVICES AND SUPPORT SERVICES ARE PROVIDED "AS IS" AND EIGEN LABS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. EIGEN LABS MAKES NO WARRANTY OR GUARANTEE REGARDING THE ACCURACY, RELIABILITY, QUALITY OR SAFETY OF ANY OUTPUT GENERATED BY THE EIGENAI SERVICES. EIGEN LABS DOES NOT WARRANT THAT THE SERVICES OR DELIVERABLES WILL BE UNINTERRUPTED OR ERROR FREE; NOR DOES IT MAKE ANY WARRANTY AS TO THE RESULTS THAT MAY BE OBTAINED FROM USE OF THE SERVICES OR DELIVERABLES. 16. Limitation of Liability a. Limit of Liability and Waiver of Consequential Damages. EXCEPT FOR YOUR BREACH OF SECTIONS 7, 12, AND 13, OR YOUR BREACH OF ANY REPRESENTATIONS OR WARRANTIES OR YOUR INDEMNITY OBLIGATIONS, NEITHER PARTY NOR ITS SUPPLIERS (INCLUDING BUT NOT LIMITED TO ALL EQUIPMENT AND TECHNOLOGY SUPPLIERS), OFFICERS, SHAREHOLDERS, AFFILIATES, REPRESENTATIVES, CONTRACTORS AND EMPLOYEES SHALL BE RESPONSIBLE OR LIABLE WITH RESPECT TO ANY SUBJECT MATTER OF THIS AGREEMENT OR TERMS AND CONDITIONS RELATED THERETO UNDER ANY CONTRACT, NEGLIGENCE, STRICT LIABILITY OR OTHER THEORY: (A) FOR ERROR OR INTERRUPTION OF USE OR FOR LOSS OR INACCURACY OR CORRUPTION OF DATA OR COST OF PROCUREMENT OF SUBSTITUTE GOODS, SERVICES OR TECHNOLOGY OR LOSS OF BUSINESS; (B) FOR ANY INDIRECT, SPECIAL, EXEMPLARY, INCIDENTAL, CONSEQUENTIAL OR PUNITIVE DAMAGES; OR (C) FOR ANY DIRECT DAMAGES, COSTS, LOSSES, OF LIABILITIES IN AMOUNTS THAT, TOGETHER WITH AMOUNTS ASSOCIATED WITH ALL OTHER CLAIMS, EXCEED THE GREATER OF ONE HUNDRED DOLLARS AND THE FEES PAID BY YOU TO EIGEN LABS FOR THE EIGENAI SERVICES UNDER THESE EIGENAI TERMS IN THE 6 MONTHS PRIOR TO THE ACT THAT GAVE RISE TO THE LIABILITY, IN EACH CASE, WHETHER OR NOT SUCH PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE PROVISIONS OF THIS SECTION ALLOCATE THE RISKS UNDER THIS AGREEMENT BETWEEN THE PARTIES, AND THE PARTIES HAVE RELIED ON THESE LIMITATIONS IN DETERMINING WHETHER TO ENTER THIS AGREEMENT. b. Limits. Some states do not allow the exclusion of implied warranties or limitation of liability for incidental or consequential damages, which means that some of the above limitations may not apply to you. IN THESE STATES, EIGEN LABS’ LIABILITY WILL BE LIMITED TO THE GREATEST EXTENT PERMITTED BY LAW. 17. Miscellaneous Eigen Labs may change these EigenAI Terms from time to time by providing notice either by emailing the email address associated with your account or by posting a notice at https://eigencloud.xyz and by updating the “Last Revised” date at the top of these EigenAI Terms. You can review the most current version of these EigenAI Terms at any time at https://docs.eigencloud.xyz. The revised EigenAI Terms will become effective immediately after Eigen Labs posts or sends you notice of such changes, and if you use the EigenAI Services after that date, your use will constitute acceptance of the revised EigenAI Terms. If any change to these EigenAI Terms is not acceptable to you, your only remedy is to stop using the EigenAI Services. If any provision of these EigenAI Terms is found to be unenforceable or invalid, that provision will be limited or eliminated to the minimum extent necessary so that these EigenAI Terms will otherwise remain in full force and effect and enforceable. You may not assign, transfer or sublicense these EigenAI Terms or your rights or obligations hereunder without the prior written consent of Eigen Labs, but Eigen Labs may assign or transfer these EigenAI Terms, in whole or in part, without restriction. Any attempted assignment or transfer of these EigenAI Terms by the parties in contravention of the foregoing shall be null and void. Eigen Labs’ failure to exercise or enforce any right or provision of these EigenAI Terms shall not be a waiver of that right. No agency, partnership, joint venture, or employment is created as a result of these EigenAI Terms and neither party has any authority of any kind to bind the other party in any respect whatsoever. In any action or proceeding to enforce rights under these EigenAI Terms, the prevailing party will be entitled to recover costs and attorneys' fees. All notices under these EigenAI Terms will be in writing and will be deemed to have been duly given when received, if personally delivered; when receipt is electronically confirmed, if transmitted by email; the day after it is sent, if sent for next day delivery by recognized overnight delivery service; and upon receipt, if sent by certified or registered mail, return receipt requested. Any delays in or failure of performance of Eigen Labs shall not constitute a default hereunder or give rise to any claims for damages if, to the extent that, and for such period that, such delays or failures of performance are caused by any events beyond the reasonable control of Eigen Labs including, without limitation, any of the following specific occurrences: acts of God or the public enemy, acts of terrorism, pandemics, epidemics, labor strikes, expropriation or confiscation of facilities, compliance with any unanticipated duly promulgated governmental order, acts of war, rebellion or sabotage or damage resulting therefrom, fires, floods, explosion, or riots. The foregoing shall not excuse your payment obligations. --- --- sidebar_position: 1 title: Privacy Policy --- # Privacy Policy ***Last Revised on March 20, 2024*** This Privacy Policy for Eigen Labs, Inc. ("Company", "we", "us" "our") describes how we collect, use and disclose information about users of the Company's website (eigenlayer.xyz), and any related services, tools and features, including the EigenLayer service (collectively, the "Services"). For the purposes of this Privacy Policy, "you" and "your" means you as the user of the Services. ​ Please read this Privacy Policy carefully. By using, accessing, or downloading any of the Services, you agree to the collection, use, and disclosure of your information as described in this Privacy Policy. If you do not agree to this Privacy Policy, please do not use, access or download any of the Services. ​ ## UPDATING THIS PRIVACY POLICY ​We may modify this Privacy Policy from time to time in which case we will update the "Last Revised" date at the top of this Privacy Policy. If we make material changes to the way in which we use information we collect, we will use reasonable efforts to notify you (such as by emailing you at the last email address you provided us, by posting notice of such changes on the Services, or by other means consistent with applicable law) and will take additional steps as required by applicable law. If you do not agree to any updates to this Privacy Policy please do not access or continue to use the Services. ​ ## COMPANY'S COLLECTION AND USE OF INFORMATION ​ When you access or use the Services, we may collect certain categories of information about you from a variety of sources, which comprises: ​ - The following information about you: name, email address, and Discord Tag. We collect your email address and Discord Tag in order to communicate with you through the Services and through third party platforms, such as Discord. - Information included in any identity documents you provide to us, including without limitation driver’s license or passport number, date of birth and/or country of residence. We collect this in limited circumstances for the purposes of identification of the jurisdiction of residence of certain users or as otherwise needed to satisfy certain regulatory obligations. - The following third-party wallet ("Wallet") information: public wallet address and token holdings. We collect third-party Wallet information in order to facilitate your use of the Services. ​ - Any other information you choose to include in communications with us, for example, when sending a message through the Services. ​ We also automatically collect certain information about your interaction with the Services ("Usage Data"). To do this, we may use cookies, web beacons/clear gifs and other geolocation tracking technologies ("Tracking Technologies"). Usage Data comprises of: ​ - Device information (e.g., unique device identifier, device type, IP address, operating system) ​ - Browser information (e.g., browser type) ​ - Location information (e.g., approximate geolocation) ​ - Other information regarding your interaction with the Services (e.g., log data, date and time stamps, clickstream data, ​ We use Usage Data to tailor features and content to you and to run analytics and better understand user interaction with the Services. For more information on how we use Tracking Technologies and your choices, see the section below, Cookies and Other Tracking Technologies. ​ In addition to the foregoing, we may use any of the above information to comply with any applicable legal obligations, to enforce any applicable terms of service, and to protect or defend the Services, our rights, and the rights of our users or others. ​ ## HOW THE COMPANY SHARES YOUR INFORMATION ​In certain circumstances, the Company may share your information with third parties for legitimate purposes subject to this Privacy Policy. Such circumstances comprise of: ​ - With vendors or other service providers, such as ​ - Blockchain analysis service providers, including Chainanalysis ​ - Data analytics vendors, including Google Analytics ​ - To comply with applicable law or any obligations thereunder, including cooperation with law enforcement, judicial orders, and regulatory inquiries ​ - In connection with an asset sale, merger, bankruptcy, or other business transaction ​ - To enforce any applicable terms of service ​ - To ensure the safety and security of the Company and/or its users ​ - When you request us to share certain information with third parties, such as through your use of login integrations ​ - With professional advisors, such as auditors, law firms, or accounting firms ​ ## COOKIES AND OTHER TRACKING TECHNOLOGIES ​Do Not Track Signals ​ Your browser settings may allow you to transmit a "Do Not Track" signal when you visit various websites. Like many websites, our website is not designed to respond to "Do Not Track" signals received from browsers. To learn more about "Do Not Track" signals, you can visit [http://www.allaboutdnt.com/.](http://www.allaboutdnt.com) ​ Cookies and Other Tracking Technologies ​ Most browsers accept cookies automatically, but you may be able to control the way in which your devices permit the use of cookies, web beacons/clear gifs, other geolocation tracking technologies. If you so choose, you may block or delete our cookies from your browser; however, blocking or deleting cookies may cause some of the Services, including any portal features and general functionality, to work incorrectly. If you have questions regarding the specific information about you that we process or retain, as well as your choices regarding our collection and use practices, please contact us using the information listed below. ​ To opt out of tracking by Google Analytics, click [here](https://tools.google.com/dlpage/gaoptout). ​ Your browser settings may allow you to transmit a "Do Not Track" signal when you visit various websites. Like many websites, our website is not designed to respond to "Do Not Track" signals received from browsers. To learn more about "Do Not Track" signals, you can visit [http://www.allaboutdnt.com/.](http://www.allaboutdnt.com) ​ ## SOCIAL NETWORKS AND OTHER THIRD PARTY WEBSITES AND LINKS ​We may provide links to websites or other online platforms operated by third parties, including third-party social networking platforms, such as Twitter, Discord, or Medium, operated by third parties (such platforms are "Social Networks"). If you follow links to sites not affiliated or controlled by us, you should review their privacy and security policies and other terms and conditions. We do not guarantee and are not responsible for the privacy or security of these sites, including the accuracy, completeness, or reliability of information found on these sites. Information you provide on public or semi-public venues, including information you share or post on Social Networks, may also be accessible or viewable by other users of the Services and/or users of those third-party online platforms without limitation as to its use by us or by a third party. Our inclusion of such links does not, by itself, imply any endorsement of the content on such platforms or of their owners or operators, except as disclosed on the Services. ​ ## THIRD PARTY WALLET EXTENSIONS ​Certain transactions conducted via our Services, will require you to connect a Wallet to the Services. By using such Wallet to conduct such transactions via the Services, you agree that your interactions with such third party Wallets are governed by the privacy policy for the applicable Wallet. We expressly disclaim any and all liability for actions arising from your use of third party Wallets, including but without limitation, to actions relating to the use and/or disclosure of personal information by such third party Wallets. ## CHILDREN'S PRIVACY ​Children under the age of 18 are not permitted to use the Services, and we do not seek or knowingly collect any personal information about children under 13 years of age. If we become aware that we have unknowingly collected information about a child under 13 years of age, we will make commercially reasonable efforts to delete such information from our database. ​ If you are the parent or guardian of a child under 13 years of age who has provided us with their personal information, you may contact us using the below information to request that it be deleted. ​ ## DATA SECURITY ​Please be aware that, despite our reasonable efforts to protect your information, no security measures are perfect or impenetrable, and we cannot guarantee "perfect security." Please further note that any information you send to us electronically, while using the Services or otherwise interacting with us, may not be secure while in transit. We recommend that you do not use unsecure channels to communicate sensitive or confidential information to us. ​ ## HOW TO CONTACT US Should you have any questions about our privacy practices or this Privacy Policy, please email us at notices@eigenlabs.org or contact us at 15790 Redmond Way #1176, Redmond, WA 98052 . --- --- sidebar_position: 2 title: Terms of Service --- # Terms of Service ***Last Revised on December 15, 2025*** These Terms of Service (these "**Terms**") explain the terms and conditions by which you may access and use our websites, including www.eigenlayer.xyz (the "**EigenLayer Website**"), www.eigencloud.xyz and www.eigenda.xyz and any other websites through which these Terms are linked (collectively, the "**Websites**"), operated by or on behalf of Eigen Labs, Inc. ("**Company**", "**we**" or "**us**"). Our Websites, the EigenCloud Platform (as defined below), our web application(s) and front-end interface(s) (each, an "**App**"), our testnet ("**Testnet**"), our application programming interfaces ("**APIs**"), and any content, portal, tools, documentation, features and functionality offered on or through the Websites or Apps are collectively referred to herein as the "**Services**". Your use of certain Services may be subject to additional terms as described herein. By using or accessing the EigenCompute Services, you further acknowledge that you have read, understand, and agree to be bound by the [**EigenCompute Terms**](eigen-compute-terms.md) which is hereby incorporated into these Terms. By using or accessing the EigenAI Services, you further acknowledge that you have read, understand, and agree to be bound by the [**EigenAI Terms**](eigenai-terms.md) which is hereby incorporated into these Terms. The Websites and Services do not include the following subdomains of the EigenLayer Website: forum.eigenlayer.xyz (the "**Forum**"), the research forum available at research.eigenlayer.xyz ("**Research**" and collectively with the Forum, and any other subdomains that contain a terms of service indicating they are operated by EigenFoundation, the "**Third-Party Subdomains**"), each including any lower-level domains and any content, tools, documentations, features and functionality offered therein. As of August 29, 2024, the Third-Party Subdomains are operated by or on behalf of EigenFoundation or its subsidiaries, not us, and your access and use of the Third-Party Subdomains is governed by the terms and conditions available at docs.eigenfoundation.org/legal/terms-of-service. Notwithstanding the foregoing, all rights and liabilities related to your use of the Third-Party Subdomains prior to August 29, 2024 are governed by these Terms. These Terms govern your access to and use of the Services. Please read these Terms carefully, as they include important information about your legal rights. By accessing and/or using the Services, you are agreeing to these Terms. If you do not understand or agree to these Terms, you must not use the Services. For purposes of these Terms, "**you**" and "**your**" means you as the user of the Services. If you use the Services on behalf of a company or other entity then "you" includes you and that entity, and you represent and warrant that (a) you are an authorized representative of the entity with the authority to bind the entity to these Terms, and (b) you agree to these Terms on the entity's behalf. > SECTION 20 CONTAINS AN ARBITRATION CLAUSE AND CLASS ACTION WAIVER. BY AGREEING TO THESE TERMS, YOU AGREE (A) TO RESOLVE ALL DISPUTES (WITH LIMITED EXCEPTION) RELATED TO THE COMPANY'S SERVICES AND/OR PRODUCTS THROUGH BINDING INDIVIDUAL ARBITRATION, WHICH MEANS THAT YOU WAIVE ANY RIGHT TO HAVE THOSE DISPUTES DECIDED BY A JUDGE OR JURY, AND (B) TO WAIVE YOUR RIGHT TO PARTICIPATE IN CLASS ACTIONS, CLASS ARBITRATIONS, OR REPRESENTATIVE ACTIONS, AS SET FORTH BELOW. YOU HAVE THE RIGHT TO OPT-OUT OF THE ARBITRATION CLAUSE AND THE CLASS ACTION WAIVER AS EXPLAINED IN SECTION 20. 1. **The Services** The Services are built on and interoperate with a set of Protocols (defined below), including permissionless protocols, and decentralized networks, and may involve or require the participation of one or more third parties that function independently of the Company. With this in mind, please refer to Section 15 (Disclaimers) and Section 17 (Assumption of Risks) for a comprehensive explanation of the limitations, conditions, and risks associated with your use of the Services, including those outside of the Company’s control. a. Services. The Services provide Apps and/or APIs that display data or otherwise facilitate users interfacing with protocols consisting of one or more sets of smart contracts (such underlying smart contracts are referred to herein as the "**Protocols**"). As part of our Services, we may make available to you a developer platform ("**EigenCloud Platform**") intended to facilitate your access to (i) a Protocol that allows for the staking of digital assets to provide crypto-economic security to one or more autonomously verifiable services ("**EigenLayer Protocol**", (ii) a data availability service ("**EigenDA Service**"), (iii) an off-the-shelf mechanism for verifying the validity or integrity of executed computations ("**EigenVerify Service**"); (iv) a verifiable compute service that allows users to package code into an isolated computing environment and deploy it via an EigenCompute API ("**EigenCompute Service**"); and (v) a large language model (“LLM”) inference API and related services that allow users to access open-source LLMs to submit inputs and receive model-generated, deterministic outputs (“**EigenAI Services**”). The EigenCloud Platform, Apps and APIs are separate and distinct from any Third-Party Tools (defined below) and the Protocols, including the EigenLayer Protocol, Slashing Protocol (defined below), Redistribution Protocol (defined below), and Forking Protocol (defined below). The EigenCloud Platform, Apps and APIs are not essential to accessing the Protocols. The Apps and APIs merely facilitate a user interacting with the Protocols by submitting, retrieving and/or displaying blockchain data in a manner that reduces the complexity of using Third-Party Tools or otherwise accessing the Protocols. Developers and users of the EigenCloud Platform are free to create their own interfaces or APIs to function with the Protocols. b. EigenDA Service. The EigenDA Service is a data availability service that allows users to interact with EigenDA node software ("**EigenDA Protocol**") to publish and retrieve data. Users may interact with the EigenDA Protocol through a disperser ("**Disperser**"). The Disperser facilitates submission of data blobs to the EigenDA Network (defined below) and distributes it to participating Operators ("**Operator Set**") for storage and availability attestations. We operate a Disperser API, which is part of the EigenDA Services ("**Eigen Disperser**"). Other developers may in the future create their own Disperser API to function with the EigenDA Protocol, and such third party Disperser APIs are not part of the Services and your use thereof is entirely at your own risk. The EigenDA Network consists of the Operator Set and Stakers (defined below) who have elected to provide crypto-economic security using their Staked Assets. While the Company retains discretion over certain eligibility criteria and operational requirements applicable to the EigenDA Operator Set, each Operator acts independently and is not an agent, employee, partner, or representative of the Company. c. Wallets. To use certain of the Services you may need to link a third-party digital wallet ("**Wallet**") with the Services. By using a Wallet in connection with the Services, you agree that you are using the Wallet under the terms and conditions of the applicable third-party provider of such Wallet. Wallets are not associated with, maintained by, supported by or affiliated with the Company. You acknowledge and agree that we are not party to any transactions conducted while accessing our Apps, and we do not have possession, custody or control over any digital assets appearing on the Services. When you interact with the Apps, as between you and Company, you retain cryptographic control over your digital assets at all times. The Company accepts no responsibility or liability to you in connection with your use of a Wallet, and makes no representations and warranties regarding how the Services will operate with any specific Wallet. **The private keys and/or seed phrases necessary to access the assets held in a Wallet are not held by the Company. The Company has no ability to help you access or recover your private keys and/or seed phrases for your Wallet, so please keep them in a safe place.** d. Updates; Monitoring. We may make any improvement, modifications or updates to the Services, including but not limited to changes and updates to the underlying software, infrastructure, security protocols, technical configurations or service features (the "**Updates**") from time to time. Your continued access and use of the Services are subject to such Updates and you shall accept any patches, system upgrades, bug fixes, feature modifications, or other maintenance work that arise out of such Updates. We are not liable for any failure by you to accept and use such Updates in the manner specified or required by us. Although the Company is not obligated to monitor access to or participation in the Services, it has the right to do so for the purpose of operating the Services, to ensure compliance with the Terms and to comply with applicable law or other legal requirements. 2. **The Protocols** The Protocols are not part of the Services, and your use of the Protocols is entirely at your own risk. Additionally, the third-party technologies required to be used or interacted with in order to interact with the Protocols, including but not limited to a Wallet (collectively the “Third-Party Tools”), are not part of the Services, and your use of such Third-Party Tools are entirely at your own risk. You agree that we make no representations and warranties with respect to the Protocols and Third-Party Tools. Please refer to Section 15 (Disclaimers) and Section 17 (Assumption of Risk) sections below for a comprehensive description of the risks, limitations, and disclaimers associated with your use of and interaction with the Protocols. a. The Protocols may (i) allow users ("**Stakers**") to stake their digital assets or opt-in to programmatic conditions on the withdrawal of Ether (ETH) deposited in Ethereum’s staking contract ("**Staked Assets**") in support of computational work performed directly for selected autonomously verified services ("**AVSs**"); (ii) allow Stakers to elect to delegate certain or all computational work to third-party operators ("**Operators**"), which opt in to provide various validation and security services, including data availability services, to one or more AVSs; (iii) allow third-party AVS providers ("**AVS Providers**") to utilize Staked Assets to access validation and security services performed by Operators; and (iv) allow users to access data availability services and verify whether an AVS ran a computation correctly. b. Operators may opt in to provide various validation and security services to one or more AVSs, including third-party AVSs and first party primitives such as EigenDA Service and EigenVerify Service. By opting in to secure an AVS, the Operator agrees to be subject to the technical parameters, operating requirements, and rewards structure defined by the AVS Provider for that AVS ("**AVS Conditions**"). These may include, without limitation, reward structures, minimum uptime thresholds, performance benchmarks, penalties for violations of AVS Conditions, hardware and software requirements. AVS Conditions are determined independently by each AVS Provider and enforced by the Protocol. c. The AVS Conditions applicable to Operators supporting the EigenDA and EigenVerify services are determined by the Company and enforced by the Protocol. From time to time, Company may establish, modify, or publish AVS Conditions applicable to Operators who have opted in to secure the EigenDA or EigenVerify services ("**Cloud AVS Conditions**"). By opting in to secure the EigenDA or EigenVerify services, the Operator agrees to be bound by the Cloud AVS Conditions, as updated from time to time. Additional technical and performance obligations for EigenDA Operators are currently available at: docs.eigencloud.xyz/products/eigenda/operator-guides/requirements/protocol-SLA. Penalties for violation of AVS Conditions and/or Cloud AVS Conditions are enforced by the Protocol and may include ejection of the Operator from the Operator Set, forfeiture of rewards or reduced compensation. d. Stakers may be eligible to receive rewards ("**Staking Rewards**") in connection with their delegation of Staked Assets to one or more AVSs. By opting in and delegating Staked Assets to an AVS, the Staker agrees to be bound by the conditions defined by the AVS Provider, including any Slashing Conditions and Redistribution Conditions. The amount, denomination, and conditions for receiving the Staking Rewards are defined solely by the applicable AVS Provider and implemented through the Protocol. e. The Protocols enable the enforcement of certain slashing conditions by allowing AVS Providers to define rules under which a portion or all of a Staker’s Staked Assets may be slashed in response to misbehavior or failure to meet specified service obligations ("**Slashing**"). Slashing is an optional feature that may be enabled by the AVS Provider and is executed autonomously through the Protocol’s on-chain mechanisms ("**Slashing Protocol**"), subject to the technical parameters and Slashing conditions defined and implemented by the AVS Provider ("**Slashing Conditions**"). f. "**Redistribution**" is a Protocol functionality that enables an AVS to route slashed digital assets in accordance with Slashing Conditions defined by the AVS Provider, which may include routing the slashed digital assets to specified addresses. Redistribution is an optional feature that may be enabled by the AVS Provider and is executed through the Protocol’s on-chain mechanisms ("**Redistribution Protocol**"), subject to the technical parameters and Redistribution conditions defined by the AVS Provider ("**Redistribution Conditions**"). g. Certain Services, including the EigenDA and EigenVerify services, may benefit from EIGEN staking and the EIGEN’s novel token design, which decouples the general-purpose utility of the unstaked ERC-20 EIGEN token from its forking and social-accountability properties enabled by its staked representation, the bEIGEN token. The bEIGEN functions as an opt-in representation of staked EIGEN, carrying slashing risks associated with computational work and subject to forking in the event of intersubjective agreement on a fault ("**Forking Event**"). This is accomplished through a combination of social consensus and the Protocol’s on-chain mechanisms ("**Forking Protocol**"). In the event that a majority of Operators securing the EigenDA or EigenVerify services act maliciously ("**Malicious Operator**"), for example, anyone may attempt to initiate a Forking Event. The Forking Event may result in the permanent burning, forfeiture, or loss of Staked Assets. h. We do not control all activity and data on the Protocols, nor do we take possession, custody or control over any digital assets on the Protocol (other than such assets that we hold or custody for ourselves or for third parties that have specifically authorized us to hold or custody such assets on their behalf, and that in each case are transaction in via the Protocol). 3. **Who May Use the Services** a. You must be 18 years of age or older and not be a Prohibited Person to use the Services. A "**Prohibited Person**" is any person or entity that is (a) listed on any U.S. Government list of prohibited or restricted parties, including without limitation the U.S. Treasury Department's list of Specially Designated Nationals or the U.S. Department of Commerce Denied Person's List or Entity List, (b) located or organized in any U.S. embargoed countries or region any country or region that has been designated by the U.S. Government as "terrorist supporting", or (c) owned or controlled by such persons or entities listed in (a)-(b). You acknowledge and agree that you are solely responsible for complying with all applicable laws of the jurisdiction you are located or accessing the Services from in connection with your use of the Services. By using the Services, you represent and warrant that you meet these requirements and will not be using the Services for any illegal activity or to engage in activities prohibited by these Terms. b. To use certain Services, you may need to create an account or link another account ("**Account**"). You agree to provide us with accurate, complete and updated information for your Account. You are solely responsible for any activity on your Account and maintaining the confidentiality and security of your password. We are not liable for any acts or omissions by you in connection with your Account. You must immediately notify us at notices@eigenlabs.org if you know or have any reason to suspect that your Account or password have been stolen, misappropriated or otherwise compromised, or in case of any actual or suspected unauthorized use of your Account. You agree not to create any Account if we have previously removed yours, or we previously banned you from any of our Services, unless we provide written consent otherwise. c. We may require you to provide additional information and documents regarding your use of the Services, including at the request of any competent authority or in case of application of any applicable law or regulation, including laws related to anti-money laundering or for counteracting financing of terrorism. We may also require you to provide additional information or documents in cases where we have reason to believe: (i) that your Wallet is or has been used for illegal money laundering or for any other illegal activity or activity we determine may present a heightened risk to the Company or any user of the Services; (ii) you have concealed or reported false identification information or other details; or (iii) you are a Prohibited Person. You agree that if it is determined in our sole discretion that you may be violating this Section or engaging in any activities prohibited in these Terms, we may disable your ability to use the Services including the App, which may include but is not limited to preventing you from restaking assets or withdrawing previously Staked Assets. 4. **Fees** The Company may charge or pass through fees for some or part of the Services we make available to you, including transaction or processing fees, blockchain gas or similar network fees. We will disclose the amount of fees we will charge or pass through to you for the applicable Service at the time you access, use or otherwise transact with the Services. Although we will attempt to provide accurate fee information, any such information reflects our estimate of fees, which may vary from the fees actually paid to use the Services and interact with the applicable blockchain with which the Services are compatible. Additionally, your external Wallet provider may impose a fee to transact on the Services. We are not responsible for any fees charged by a third party. All transactions processed through the Services are non-refundable. Fees are exclusive of all taxes. You will be responsible for paying any and all applicable national, state and local sales, use, excise, ad valorem, value-added, services, consumption, and other taxes and duties imposed in connection with its use of the Service. You agree to indemnify, defend and hold Company harmless from any liability or expense resulting from your failure to pay any such applicable taxes. In certain cases, your transactions through the Services may not be successful due to an error with the blockchain or the Wallet. We accept no responsibility or liability to you for any such failed transactions, or any transaction or gas fees that may be incurred by you in connection with such failed transactions. You acknowledge and agree that all information you provide with respect to transactions on the Services, including, without limitation, credit card, bank account, PayPal or other payment information is accurate, current and complete, and you have the legal right to use such payment method. 5. **The Testnet** a. Purpose and Participation. The Testnet is designed to demonstrate the functionality and features of the Apps (or any portion thereof) and to improve participant experiences prior to the Apps’ launch. YOUR PARTICIPATION IN THE TESTNET IS ENTIRELY VOLUNTARY, BUT IF YOU ARE PARTICIPATING IN THE TESTNET, YOU MUST STRICTLY ADHERE TO THESE TERMS. We make no representation or warranty that the Testnet will accurately or completely simulate, duplicate or replicate the App. b. Duration. The availability of the Testnet will commence on the date prescribed by the Company and continue until terminated by the Company in its sole discretion. Notwithstanding any other information provided by the Company regarding the Testnet (including on the Websites, blog posts or through other communications (such as forums, Telegram, Github, Discord, or other channels)), the Company may change, discontinue, or terminate, temporarily or permanently, all or any part of the Testnet, at any time and without notice, at its sole discretion (including prior to providing any incentives or rewards). The Company may retain control or upgradeability over certain aspects of the Testnet that will not be retained on the mainnet. c. The Testnet Eligibility. Your participation in the Testnet (or any portion thereof) may be subject to eligibility criteria determined by the Company in its sole discretion (including, without limitation, geographical distribution and applicant reputation). By applying or registering, there is no promise or guarantee that you will be able to participate in the Testnet. Notwithstanding any other information provided by the Company regarding the Testnet (including on the Websites, blog posts or through other communications (such as forums, Telegram, Github, Discord, or other channels)), the Company may change or modify at any time the number of participants eligible to participate in the Testnet or the requirements of the Testnet and terminate any participant's participation in the Testnet at any time. The Testnet may operate in certain phases. Your selection or participation in any one phase of the Testnet does not imply that you will be selected for any other phases of the Testnet. The Company reserves the right to block your access to the Testnet at any time in its sole discretion. d. No Monetary Value. In your use of the Testnet, you may interact with or transfer certain cryptocurrencies or other digital assets on the Testnet ("Testnet Tokens"), such as Testnet Tokens obtained through a faucet. Testnet Tokens are not, and shall never convert to or accrue to become any other tokens or virtual assets. Testnet Tokens are virtual items with no monetary value. Testnet Tokens do not constitute any currency or property of any type and are not redeemable, refundable, or eligible for any fiat or digital currency or anything else of value. Testnet Tokens are not transferable between users outside of the Testnet, and you may not attempt to sell, trade, or transfer any Testnet Tokens outside of the Testnet, or obtain any manner of credit using any Testnet Tokens. Any attempt to sell, trade, or transfer any Testnet Tokens outside of the Testnet will be null and void. Testnet Tokens will not be converted into any future rewards offered by the Company. Any ETH, ERC-20 tokens transferred to a Testnet address will be irretrievable and permanently lost. The Company is not responsible for any such loss. 6. **Location of Our Privacy Policy** Our Privacy Policy describes how we handle the information you provide to us when you use the Services. For an explanation of our privacy practices, please visit our [Privacy Policy here](privacy-policy.md). 7. **Rights We Grant You** The Services may display, include or make available documentation, blog posts and other descriptions or materials related to the Protocols and Apps, such as at docs.eigencloud.xyz (collectively, "**Documentation**"). The Documentation is part of the Services. 8. **Right to Use Services** We hereby permit you to use the Services for your internal use only, provided that you comply with these Terms in connection with all such use. If any software, content or other materials owned or controlled by us are distributed to you as part of your use of the Services, we hereby grant you, a personal, non-assignable, non-sublicensable, non-transferrable, and non-exclusive right and license to access and display such software, content and materials provided to you as part of the Services, in each case for the sole purpose of enabling you to use the Services as permitted by these Terms. Your access and use of the Services may be interrupted from time to time for any of several reasons, including, without limitation, the malfunction of equipment, periodic updating, maintenance or repair of the Service or other actions that Company, in its sole discretion, may elect to take. Certain elements of the Protocols, including the underlying smart contracts, are made available under an open-source or source-available license (e.g., at https://github.com/Layr-Labs and https://github.com/eigenfoundation), and these Terms do not override or supersede the terms of those licenses. 9. **Right to Use Our APIs** Subject to these Terms, we hereby grant you a non-exclusive, non-transferable, non-sublicensable, worldwide, revocable right and license to use our APIs for the limited purposes set forth in the documentation for the Services. Your use of our APIs must comply with the technical documentation, usage guidelines, call volume limits, and other documentation maintained at https://docs.eigencloud.xyz/ or such other location we may designate from time to time. We may terminate your right to use the API from time to time at any time. 10. **Restrictions On Your Use of the Services** You may not do any of the following in connection with your use of the Services, unless applicable laws or regulations prohibit these restrictions or you have our written permission to do so: a. engage in any behavior that constitutes fraud, dishonesty, collusion, censorship, denial of service, data withholding, or any other malicious or abusive activity, including conduct that may lead to Slashing events, Forking Events, or prevent or impair third parties’ ability to use the Services; b. download, modify, copy, distribute, transmit, display, perform, reproduce, duplicate, publish, license, create derivative works from, or offer for sale any information contained on, or obtained from or through, the Services, except for temporary files that are automatically cached by your web browser for display purposes, or as otherwise expressly permitted in these Terms; c. duplicate, decompile, reverse engineer, disassemble or decode the Services (including any underlying idea or algorithm), or attempt to do any of the same; d. use, reproduce or remove any copyright, trademark, service mark, trade name, slogan, logo, image, or other proprietary notation displayed on or through the Services; e. use automation software (bots), hacks, modifications (mods) or any other unauthorized third-party software designed to modify the Services; f. exploit the Services for any commercial purpose, including without limitation communicating or facilitating any commercial advertisement or solicitation; g. access or use the Services in any manner that could disable, overburden, damage, disrupt or impair the Services or interfere with any other party's access to or use of the Services or use any device, software or routine that causes the same; h. attempt to gain unauthorized access to, interfere with, damage or disrupt the Services, accounts registered to other users, or the computer systems, wallets, accounts, protocols or networks connected to the Services; i. circumvent, remove, alter, deactivate, degrade or thwart any technological measure or content protections of the Services or the computer systems, wallets, accounts, protocols or networks connected to the Services; j. use any robot, spider, crawlers or other automatic device, process, software or queries that intercepts, "mines," scrapes or otherwise accesses the Services to monitor, extract, copy or collect information or data from or through the Services, or engage in any manual process to do the same; k. introduce any viruses, trojan horses, worms, logic bombs or other materials that are malicious or technologically harmful into our systems; l. submit, transmit, display, perform, post or store any content that is inaccurate, unlawful, defamatory, obscene, lewd, lascivious, filthy, excessively violent, pornographic, invasive of privacy or publicity rights, harassing, threatening, abusive, inflammatory, harmful, hateful, cruel or insensitive, deceptive, or otherwise objectionable, use the Services for illegal, harassing, bullying, unethical or disruptive purposes, or otherwise use the Services in a manner that is obscene, lewd, lascivious, filthy, excessively violent, harassing, harmful, hateful, cruel or insensitive, deceptive, threatening, abusive, inflammatory, pornographic, inciting, organizing, promoting or facilitating violence or criminal or harmful activities, defamatory, obscene or otherwise objectionable; m. violate any applicable law or regulation in connection with your access to or use of the Services; or n. access or use the Services in any way not expressly permitted by these Terms. 11. **Beta Services** From time to time, we may, in our sole discretion, include certain test or beta features or products in the Services ("**Beta Services**") as we may designate from time to time. Your use of any Beta Services is completely voluntary. The Beta Services are provided on an “as is” basis and may contain errors, defects, bugs, or inaccuracies that could cause failures, corruption or loss of data and information from any connected device. You acknowledge and agree that all use of any Beta Service is at your sole risk. You agree that once you use a Beta Service, your content or data may be affected such that you may be unable to revert back to a prior non-beta version of the same or similar feature. Additionally, if such reversion is possible, you may not be able to return or restore data created within the Beta Service back to the prior non-beta version. If we provide you any Beta Service on a closed beta or confidential basis, we will notify you of such as part of your use of the Beta Services. For any such confidential Beta Services, you agree to not disclose, divulge, display, or otherwise make available any of the Beta Services. without our prior written consent. 12. **Interactions with Other Users on the Services** You are responsible for your interactions with other users on or through the Services. While we reserve the right to monitor interactions between users, we are not obligated to do so, and we cannot be held liable for your interactions with other users, or for any user's actions or inactions. If you have a dispute with one or more users, you release us (and our affiliates and subsidiaries, and our and their respective officers, directors, employees and agents) from claims, demands and damages (actual and consequential) of every kind and nature, known and unknown, arising out of or in any way connected with such disputes. In entering into this release you expressly waive any protections (whether statutory or otherwise) that would otherwise limit the coverage of this release to include only those claims which you may know or suspect to exist in your favor at the time of agreeing to this release. 13. **Ownership and Content** a. Ownership of the Services. The Services, including their "look and feel" (e.g., text, graphics, images, logos), proprietary content, information and other materials, are protected under copyright, trademark and other intellectual property laws. You agree that the Company and/or its licensors own all right, title and interest in and to the Services (including any and all intellectual property rights therein) and you agree not to take any action(s) inconsistent with such ownership interests. We and our licensors reserve all rights in connection with the Services and its content, including, without limitation, the exclusive right to create derivative works. b. Ownership of Trademarks. The Company's name, trademarks and logos and all related names, logos, product and service names, designs and slogans are trademarks of the Company or its affiliates or licensors. Other names, logos, product and service names, designs and slogans that appear on the Services are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by us. c. Ownership of Feedback. We welcome feedback, bug reports, comments and suggestions for improvements to the Services ("**Feedback**"). You acknowledge and expressly agree that any contribution of Feedback does not and will not give or grant you any right, title or interest in the Services or in any such Feedback. All Feedback becomes the sole and exclusive property of the Company, and the Company may use and disclose Feedback in any manner and for any purpose whatsoever without further notice or compensation to you and without retention by you of any proprietary or other right or claim. You hereby assign to the Company any and all right, title and interest (including, but not limited to, any patent, copyright, trade secret, trademark, show-how, know-how, moral rights and any and all other intellectual property right) that you may have in and to any and all Feedback. d. Your Content License Grant. In connection with your use of the Services, you may be able to post, upload, or submit content to be made available through the Services ("**Your Content**"). In order to operate the Service, we must obtain from you certain license rights in Your Content so that actions we take in operating the Service are not considered legal violations. Accordingly, by using the Service and uploading Your Content, you grant us a license to access, use, host, cache, store, reproduce, transmit, display, publish, distribute, and modify (for technical purposes, e.g., making sure content is viewable on smartphones as well as computers and other devices) Your Content but solely as required to be able to operate, improve and provide the Services. You agree that these rights and licenses are royalty free, transferable, sub-licensable, worldwide and irrevocable (for so long as Your Content is stored with us), and include a right for us to make Your Content available to, and pass these rights along to, others with whom we have contractual relationships related to the provision of the Services, solely for the purpose of providing such Services, and to otherwise permit access to or disclose Your Content to third parties if we determine such access is necessary to comply with our legal obligations. As part of the foregoing license grant you agree that the other users of the Services shall have the right to comment on and/or tag Your Content and/or to use, publish, display, modify or include a copy of Your Content as part of their own use of the Services; except that the foregoing shall not apply to any of Your Content that you post privately for non-public display on the Services. To the fullest extent permitted by applicable law, the Company reserves the right, and has absolute discretion, to remove, screen, edit, or delete any of Your Content at any time, for any reason, and without notice. By posting or submitting Your Content through the Services, you represent and warrant that you have, or have obtained, all rights, licenses, consents, permissions, power and/or authority necessary to grant the rights granted herein for Your Content. You agree that Your Content will not contain material subject to copyright or other proprietary rights, unless you have the necessary permission or are otherwise legally entitled to post the material and to grant us the license described above. e. Notice of Infringement -- DMCA (Copyright) Policy. If you believe that any text, graphics, photos, audio, videos or other materials or works uploaded, downloaded or appearing on the Services have been copied in a way that constitutes copyright infringement, you may submit a notification to our copyright agent in accordance with 17 USC 512(c) of the Digital Millennium Copyright Act (the "DMCA"), by providing the following information in writing: i. identification of the copyrighted work that is claimed to be infringed; ii. identification of the allegedly infringing material that is requested to be removed, including a description of where it is located on the Service; iii. information for our copyright agent to contact you, such as an address, telephone number and e-mail address; iv. a statement that you have a good faith belief that the identified, allegedly infringing use is not authorized by the copyright owners, its agent or the law; v. a statement that the information above is accurate, and under penalty of perjury, that you are the copyright owner or the authorized person to act on behalf of the copyright owner; and vi. the physical or electronic signature of a person authorized to act on behalf of the owner of the copyright or of an exclusive right that is allegedly infringed. Notices of copyright infringement claims should be sent by mail to: Eigen Labs, Inc., Attn: Legal, 15790 Redmond Way #1176 Redmond, WA 98052 ; or by e-mail to notices@eigenlabs.org. It is our policy, in appropriate circumstances and at our discretion, to disable or terminate the accounts of users who repeatedly infringe copyrights or intellectual property rights of others. A user of the Services who has uploaded or posted materials identified as infringing as described above may supply a counter-notification pursuant to sections 512(g)(2) and (3) of the DMCA. When we receive a counter-notification, we may reinstate the posts or material in question, in our sole discretion. To file a counter-notification with us, you must provide a written communication (by fax or regular mail or by email) that sets forth all of the items required by sections 512(g)(2) and (3) of the DMCA. Please note that you will be liable for damages if you materially misrepresent that content or an activity is not infringing the copyrights of others. 14. **Third Party Services and Materials** The Services may allow you to browse the availability of certain (i) AVSs, (ii) Operators that offer to run certain AVSs in connection with your Staked Assets and/or (iii) other services or products developed or run by third parties (such as Third-Party Tools) displayed on the Services, including the Apps ("**Third-Party Services**") and may display, include or make available content, data, information, applications or materials from third parties ("**Third-Party Materials**") or provide links to certain third party websites. For clarity, the Third-Party Subdomains are each a Third-Party Service and the content, data, information, applications or materials therein are Third-Party Materials. The Company does not endorse or recommend any Third-Party Materials, the use of any provider of any Third-Party Services, or the staking, use, or delegation of any digital assets with respect to any Third-Party Services. You agree that your access and use of such Third-Party Services and Third-Party Materials is governed solely by the terms and conditions of such Third-Party Services and Third-Party Materials, as applicable. The Company is not responsible or liable for, and make no representations as to any aspect of such Third-Party Materials and Third-Party Services, including, without limitation, their content or the manner in which they handle, protect, manage or process data or any interaction between you and the provider of such Third-Party Services. The Company is not responsible for examining or evaluating the content, accuracy, completeness, availability, timeliness, validity, copyright compliance, legality, decency, quality, security or any other aspect of such Third-Party Services or Third-Party Materials or websites. You irrevocably waive any claim against the Company with respect to such Third-Party Services and Third-Party Materials. We are not liable for and you expressly disclaim any liability with respect to any damage or loss caused or alleged to be caused by or in connection with your enablement, access or use of any such Third-Party Services or Third-Party Materials, or your reliance on the privacy practices, data security processes or other policies of such Third-Party Services, including without limitation, the delegation of any assets to any Third-Party Service or the staking of any assets with any Third-Party Service that results in slashing or any other loss of funds or the integration of any Third-Party Service such as an AVS into your product or service that results in any damages whatsoever. Third-Party Services, Third-Party Materials and links to other websites are provided solely as a convenience to you. Certain Third-Party Services or Third-Party Materials may automatically populate on the Company’s Services. The Company reserves the right to remove any Third-Party Services or Third-Party Materials from the Services, including without limitation, any AVSs or operators for any reason whatsoever. 15. **Disclaimers** Your access to and use of the Services and any Protocols are at your own risk. You understand and agree that the Services are provided to you on an "AS IS" and "AS AVAILABLE" basis. Without limiting the foregoing, to the maximum extent permitted under applicable law, the Company, its parents, affiliates, related companies, officers, directors, employees, agents, representatives, partners and licensors (the "**Company Entities**") and MultiSig Committee Members (as defined below) DISCLAIM ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING WITHOUT LIMITATION ANY WARRANTIES RELATING TO TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, USAGE, QUALITY, PERFORMANCE, SUITABILITY OR FITNESS OF THE SERVICES AND THE PROTOCOLS FOR ANY PARTICULAR PURPOSE, OR AS TO THE ACCURACY, QUALITY, SEQUENCE, RELIABILITY, WORKMANSHIP OR TECHNICAL CODING THEREOF, OR THE ABSENCE OF ANY DEFECTS THEREIN WHETHER LATENT OR PATENT. The Company Entities and MultiSig Committee Members ("**Covered Parties**") make no warranty or representation and disclaim all responsibility and liability for: (a) the completeness, accuracy, availability, timeliness, security or reliability of the Services, and the Protocols; (b) any harm to your computer system, loss of data, or other harm that results from your access to or use of the Services or the Protocols; (c) the operation or compatibility with any other application or any particular system or device, including any Wallets; (d) whether the Services or the Protocols will meet your requirements or be available on an uninterrupted, secure or error-free basis; (e) whether the Services or the Protocols will protect your assets from theft, hacking, cyber attack or other form of loss caused by third-party conduct; (f) loss of funds or value resulting from intentional or unintentional Slashing event, Redistribution event or Forking Event, and (g) the deletion of, or the failure to store or transmit Your Content and other communications maintained by the Services. No advice or information, whether oral or written, obtained from any of the Covered Parties or through the Services, will create any warranty or representation not expressly made herein. You should not rely on the Services, for advice of any kind, including legal, tax, investment, financial or other professional advice. With the exception of the EigenDA Protocol, the Covered Parties have no control over the Protocols. The Covered Parties do not guarantee the availability, amount, timing, or distribution of any Staking Rewards, and disclaims all responsibility and liability for the allocation or non-allocation of such rewards. The Covered Parties have no control over the third party AVS Providers, or Slashing Conditions or Redistribution Conditions defined by the third-party AVS Providers. The Covered Parties do not initiate, control or influence any Slashing or Redistribution event. The Covered Parties disclaim all responsibility and liability for any loss of Staked Assets resulting from any Slashing event, Redistribution event or the absence of failure for a Redistribution event to occur. The Covered Parties do not define or monitor the AVS Conditions imposed by AVS Providers. The Covered Parties disclaim all responsibility and liability for any consequences arising from an Operator’s violation of AVS Conditions, including the Cloud AVS Conditions. Operators are responsible for understanding, implementing and maintaining compliance with the applicable AVS Conditions for each AVS it chooses to secure and assumes all risk associated with its decision to opt in any AVS. The Covered Parties have no control over the actions or inactions of an Operator or Stakers and disclaims all responsibility and liability for any activity by an Operator and Staker, and any direct or indirect consequences that may follow, including but not limited to, breach of AVS Conditions or Cloud AVS Conditions leading to a Slashing event, Redistribution events, Forking Events, Stakers revoking delegation of their Staked Assets, service disruptions, inability to access data, loss of digital assets, and other disruptions to downstream services or integrations. The Covered Parties do not approve or control Forking Events and disclaims all responsibility and liability for any consequences associated with a Forking Event, including but not limited to loss of funds, degraded performance of the Services, reputational harm, market volatility, loss in value of EIGEN, reduced EIGEN liquidity, divergent protocol states, or third-party exchange actions such as suspension or delisting. The EigenDA Network is composed of decentralized components that operate independently and outside the control of the Covered Parties. The Covered Parties do not control or direct the behavior of these participants and make no representations regarding their reliability, continuity, or compliance. The Covered Parties do not guarantee the continued availability or recoverability of any data submitted to the EigenDA Network or the EigenDA Service. The Covered Parties further disclaim all responsibility and liability for any risks involved with the EigenDA Network, including without limitation, malicious behavior by participants of the Operator Set, Stakers revoking delegation of their Staked Assets, data withholding, data corruption, delayed availability, or unauthorized use of submitted data. The Covered Parties further disclaim all responsibility and liability for any data loss, data corruption, or unavailability of data resulting from reliance on the EigenDA Network or EigenDA Service. 16. **LIMITATIONS OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW, YOU AGREE THAT IN NO EVENT WILL ANY OF THE COVERED PARTIES BE LIABLE (A) FOR DAMAGES OF ANY KIND, INCLUDING INDIRECT, SPECIAL, EXEMPLARY, INCIDENTAL, CONSEQUENTIAL OR PUNITIVE DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, LOSS OF USE, DATA OR PROFITS, BUSINESS INTERRUPTION OR ANY OTHER DAMAGES OR LOSSES, ARISING OUT OF OR RELATED TO YOUR USE OR INABILITY TO USE THE SERVICES), HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, WHETHER UNDER THESE TERMS OR OTHERWISE ARISING IN ANY WAY IN CONNECTION WITH THE SERVICES OR THESE TERMS AND WHETHER IN CONTRACT, STRICT LIABILITY OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) EVEN IF ANY OF THE COVERED PARTIES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE, OR (B) FOR ANY OTHER CLAIM, DEMAND OR DAMAGES WHATSOEVER RESULTING FROM OR ARISING OUT OF OR IN CONNECTION WITH THESE TERMS OR THE DELIVERY, USE OR PERFORMANCE OF THE SERVICES. THE COVERED PARTIES’ TOTAL LIABILITY TO YOU FOR ANY DAMAGES FINALLY AWARDED SHALL NOT EXCEED ONE HUNDRED DOLLARS ($100.00) RESPECTIVELY.** **SOME JURISDICTIONS (SUCH AS THE STATE OF NEW JERSEY) DO NOT ALLOW LIMITATIONS ON IMPLIED WARRANTIES OR THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO SOME OR ALL OF THE ABOVE DISCLAIMERS, EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU, AND YOU MAY HAVE ADDITIONAL RIGHTS.** 17. **Assumption of Risks** _General Risks_ a. By using the Services, you represent that you have sufficient knowledge and experience in business and financial matters, including a sufficient understanding of blockchain or cryptographic tokens and technologies and other digital assets, storage mechanisms (such as Wallets), blockchain-based software systems, and blockchain technology, to be able to assess and evaluate the risks and benefits of the Services contemplated hereunder, and will bear the risks thereof, including loss of all amounts paid, and the risk that the tokens may have little or no value. You acknowledge and agree that there are risks associated with purchasing and holding cryptocurrency, using blockchain technology and staking cryptocurrency. These include, but are not limited to, risk of losing access to cryptocurrency due to Slashing, Forking or Redistribution, loss of private key(s), acts or omissions by Operators or AVS Providers, custodial error or purchaser error, risk of mining or blockchain attacks, risk of hacking and security weaknesses, risk of unfavorable regulatory intervention in one or more jurisdictions, risk related to token taxation, risk of personal information disclosure, risk of uninsured losses, volatility risks, and unanticipated risks. You acknowledge that digital assets and cryptocurrencies are not (i) deposits of or guaranteed by a bank (ii) insured by the FDIC or by any other governmental agency and (iii) that we do not custody and cannot transfer any cryptocurrency or digital assets you may interact with on the Services or Protocols. b. There are certain multi-signature crypto wallets (the "**MultiSigs**", and the signatories to such MultiSigs, the "**MultiSig Committee Members**") that have certain controls related to one or more of the Protocols, that may include, but are not limited to, the ability to pause certain functionality of the Protocols, reverse or pause slashing, implement or influence upgrades to the Protocols (or any aspect thereof) and certain other controls of the functionality of the Protocols as described in the documentation or in public communications made by us. Certain MultiSigs may be controlled by us and/or MultiSig Committee Members that are employed or engaged by us, and certain other MultiSigs will be controlled partially or entirely by MultiSig Committee Members that are unaffiliated third parties over which we have no or limited control. We will not be able to control the actions of such MultiSig Committee Members if they are not employed or engaged by us and thus certain MultiSigs will be outside of our control. c. The regulatory regime governing blockchain technologies, cryptocurrencies and other digital assets is uncertain, and new regulations or policies may materially adversely affect the potential utility or value of such cryptocurrencies and digital assets. There also exists the risks of new taxation of the purchase or sale of cryptocurrencies and other digital assets. d. We cannot control how third-party exchange platforms quote or value cryptocurrencies and other digital assets and we expressly deny and disclaim any liability to you and deny any obligations to indemnify or hold you harmless for any losses you may incur as a result of a Forking Event or fluctuations in the value of cryptocurrencies or other digital assets. e. Smart contracts execute automatically when certain conditions are met. Since smart contracts typically cannot be stopped or reversed, vulnerabilities in their programming and design or other vulnerabilities that may arise due to hacking or other security incidents can have adverse effects to Staked Assets, including but not limited to significant volatility and risk of loss. f. The Protocols are not part of the Services. You are responsible for understanding the Protocols, including their operating rules, any Slashing Conditions or Redistribution Conditions imposed by AVSs, and how they all operate. You agree that we are not responsible and will not be liable to you for any losses that result from the operation of the Protocol. For example, certain protocols and networks subject Staked Assets to Slashing, Redistribution and/or Forking upon certain conditions, including, but not limited to, if a validator or Operator engages in harmful or malicious behavior, fails to perform their role as a validator or operator properly, or incorrectly validates a transaction. In addition, data made available to protocols may be automatically deleted on a periodic basis based on the protocol’s programming. We expressly deny and disclaim any liability to you and deny any obligations to indemnify or hold you harmless for any losses you may incur as a result of the operation of the Protocols, including slashing, redistribution and forking and deletion of data. g. Certain protocols and networks require that a certain amount of staked assets be locked for a certain period of time while staking, and withdrawal of Staked Assets may be delayed. We do not guarantee the security or functionality of any third-party protocol, software or technology intended to be compatible with Staked Assets. h. You acknowledge that there are inherent risks associated with using or interacting with Protocols and blockchain technology. There is no guarantee that such Protocols or technology will be unavailable or subject to errors, hacking or other security risks. Underlying Protocols may also be subject to sudden changes in operating rules, including Forking Events, and it is your responsibility to make yourself aware of upcoming operating changes. _Service and Protocol Related Risks_ a. Operators. By opting in to support an AVS, the Operator acknowledges and accepts that participation is subject to the AVS Conditions imposed by the AVS Provider or the Cloud AVS Conditions imposed by the EigenDA or EigenVerify services, as applicable. The Operator further acknowledges that a failure to comply with applicable AVS Conditions may result in consequences such as forfeiture of rewards, ejection or removal from the Operator Set, reputational harm, or, in the case where the Operator has also staked their digital assets, partial or total slashing of such assets. b. Staking. The Staker acknowledges and accepts that Staking on the EigenLayer Protocol may involve significant risks, including the potential loss of all or part of the Staker’s Staked Assets. These risks may arise from the behavior of Operators and AVS Providers, applicable AVS Conditions, Cloud AVS Conditions, Slashing Conditions or Redistribution Conditions defined and implemented by the AVS provider, Forking Events, smart contract vulnerabilities, or the unavailability or failure of the underlying infrastructure, including the Ethereum network. Stakers are solely responsible for evaluating the applicable AVS Conditions, Cloud AVS Conditions, Slashing Conditions, Redistribution Conditions and the technical design of any AVS chosen by the Staker to delegate their Staked Assets to. c. Slashing. By delegating Staked Assets to an AVS that has enabled Slashing, the Staker acknowledges and agrees that such participation may result in partial or total loss of the Staker’s Staked Assets through Slashing. Slashing events are enforced autonomously by the Slashing Protocol in accordance with the Slashing Conditions defined by the relevant AVS Provider, which may include Operator misbehavior, liveness failures, or failure to meet service-level criteria. With the exception of the EigenDA and EigenVerify services, Slashing Conditions are determined solely by the applicable AVS Provider and are not controlled or reviewed by the Company. Stakers are solely responsible for understanding and evaluating the Slashing Conditions and associated risks of any AVS chosen by the Staker to participate in, including the EigenDA and EigenVerify services. d. Redistribution. By delegating Staked Assets to an AVS that has enabled Redistribution, the Staker acknowledges and accepts the Redistribution Conditions defined by the AVS Provider and any associated Redistribution risks. The Staker further acknowledges and agrees that Redistribution is not guaranteed to occur, eligibility for Redistribution does not ensure receipt of any digital assets, and the mechanics of Redistribution are determined solely by the relevant AVS Provider and enforced through the Protocol. The Staker further acknowledges that Staked Assets may be permanently lost due to protocol bugs or errors in the Redistribution process. e. EigenDA. You acknowledge and agree that the EigenDA Service is not intended to serve as a permanent storage solution. All data submitted to the EigenDA Service is subject to automatic and irreversible deletion after a period of fourteen (14) days. You are solely responsible for maintaining independent backups of any data submitted to the EigenDA Service. You must not rely on the EigenDA Service as your sole or long-term data storage mechanism. You further acknowledge and agree that Operators may fail to store or make available the data as expected, and that such behavior may not be detectable or reversible by the Company. Reliance on the EigenDA Service for data availability may expose your application, AVS or rollup to material risks, including but not limited to the data loss, data corruption, or unavailability of critical data. Such issues may impair transaction finality, user access, or fraud-proof mechanisms, and may result in total or partial loss of funds held or transacted by your application, AVS, or rollup. f. Forking. You acknowledge and accept that Forking Events may be triggered autonomously by other participants of the Protocol without Company oversight, and are governed by the logic of the Forking Protocol. You further acknowledge and accept that Forking Events are governed entirely by protocol-level mechanisms and may occur without any Company oversight, intervention, or reversibility. You assume all risks associated with such Forking Events and their consequences. 18. **Indemnification**. By entering into these Terms and accessing or using the Services, you agree that you shall defend, indemnify and hold the Covered Parties harmless from and against any and all claims, costs, damages, losses, liabilities and expenses (including attorneys’ fees and costs) incurred by the Covered Parties arising out of or in connection with: (a) your violation or breach of any term of these Terms or any applicable law or regulation; (b) your violation of any rights of any third party; (c) your misuse of the Services; or (d) your negligence or wilful misconduct; or (e) your Content. If you are obligated to indemnify any Covered Parties hereunder, then you agree that the Company (or, at its discretion, the applicable Company Entity) or MultiSig Committee Members, as applicable, will have the right, in its sole discretion, to control any action or proceeding and to determine whether the Company or MultiSig Committee Member, as applicable, wishes to settle, and if so, on what terms, and you agree to fully cooperate with the Company or MultiSig Committee Members in the defense or settlement of such claim. 19. **Third Party Beneficiaries**. You and the Company acknowledge and agree that the Company Entities (other than the Company) and the MultiSig Committee Members are third party beneficiaries of these Terms, including under Section 15, 16, 17 and 20. 20. **ARBITRATION AND CLASS ACTION WAIVER** PLEASE READ THIS SECTION CAREFULLY -- IT MAY SIGNIFICANTLY AFFECT YOUR LEGAL RIGHTS, INCLUDING YOUR RIGHT TO FILE A LAWSUIT IN COURT AND TO HAVE A JURY HEAR YOUR CLAIMS. IT CONTAINS PROCEDURES FOR MANDATORY BINDING ARBITRATION AND A CLASS ACTION WAIVER. Informal Process First. You and the Company agree that in the event of any dispute between you and the Company Entities or the MultiSig Committee Members, either party will first contact the other party and make a good faith sustained effort to resolve the dispute before resorting to more formal means of resolution, including without limitation, any court action, after first allowing the receiving party 30 days in which to respond. Both you and the Company agree that this dispute resolution procedure is a condition precedent which must be satisfied before initiating any arbitration against you, any Company Entity or any MultiSig Committee Members, as applicable. Arbitration Agreement and Class Action Waiver. After the informal dispute resolution process, any remaining dispute, controversy, or claim (collectively, "**Claim**") relating in any way to the Services, including the App, any use or access or lack of access thereto, and any other usage of the Protocols even if interacted with outside of the Services or App, will be resolved by arbitration, including threshold questions of arbitrability of the Claim. You and the Company agree that any Claim will be settled by final and binding arbitration, using the English language, administered by JAMS under its Comprehensive Arbitration Rules and Procedures (the "**JAMS Rules**") then in effect (those rules are deemed to be incorporated by reference into this section, and as of the date of these Terms). Because your contract with the Company, these Terms, and this Arbitration Agreement concern interstate commerce, the Federal Arbitration Act ("**FAA**") governs the arbitrability of all disputes. However, the arbitrator will apply applicable substantive law consistent with the FAA and the applicable statute of limitations or condition precedent to suit. Arbitration will be handled by a sole arbitrator in accordance with the JAMS Rules. Judgment on the arbitration award may be entered in any court that has jurisdiction. Any arbitration under these Terms will take place on an individual basis -- class arbitrations and class actions are not permitted. You understand that by agreeing to these Terms, you and the Company are each waiving the right to trial by jury or to participate in a class action or class arbitration. Batch Arbitration. To increase the efficiency of administration and resolution of arbitrations, you and the Company agree that in the event that there are one-hundred (100) or more individual Claims of a substantially similar nature filed against the Company by or with the assistance of the same law firm, group of law firms, or organizations, then within a thirty (30) day period (or as soon as possible thereafter), JAMS shall (1) administer the arbitration demands in batches of 100 Claims per batch (plus, to the extent there are less than 100 Claims left over after the batching described above, a final batch consisting of the remaining Claims); (2) appoint one arbitrator for each batch; and (3) provide for the resolution of each batch as a single consolidated arbitration with one set of filing and administrative fees due per side per batch, one procedural calendar, one hearing (if any) in a place to be determined by the arbitrator, and one final award ("**Batch Arbitration**"). All parties agree that Claims are of a “substantially similar nature” if they arise out of or relate to the same event or factual scenario and raise the same or similar legal issues and seek the same or similar relief. To the extent the parties disagree on the application of the Batch Arbitration process, the disagreeing party shall advise JAMS, and JAMS shall appoint a sole standing arbitrator to determine the applicability of the Batch Arbitration process ("**Administrative Arbitrator**"). In an effort to expedite resolution of any such dispute by the Administrative Arbitrator, the parties agree the Administrative Arbitrator may set forth such procedures as are necessary to resolve any disputes promptly. The Administrative Arbitrator’s fees shall be paid by the Company. You and the Company agree to cooperate in good faith with JAMS to implement the Batch Arbitration process including the payment of single filing and administrative fees for batches of Claims, as well as any steps to minimize the time and costs of arbitration, which may include: (1) the appointment of a discovery special master to assist the arbitrator in the resolution of discovery disputes; and (2) the adoption of an expedited calendar of the arbitration proceedings. This Batch Arbitration provision shall in no way be interpreted as authorizing a class, collective and/or mass arbitration or action of any kind, or arbitration involving joint or consolidated claims under any circumstances, except as expressly set forth in this provision. Exceptions. Notwithstanding the foregoing, you and the Company agree that the following types of disputes will be resolved in a court of proper jurisdiction: (i) disputes or claims within the jurisdiction of a small claims court consistent with the jurisdictional and dollar limits that may apply, as long as it is brought and maintained as an individual dispute and not as a class, representative, or consolidated action or proceeding; (ii) disputes or claims where the sole form of relief sought is injunctive relief (including public injunctive relief); or (iii) intellectual property disputes. Costs of Arbitration. Payment of all filing, administration, and arbitrator costs and expenses will be governed by the JAMS Rules, except that if you demonstrate that any such costs and expenses owed by you under those rules would be prohibitively more expensive than a court proceeding, the Company will pay the amount of any such costs and expenses that the arbitrator determines are necessary to prevent the arbitration from being prohibitively more expensive than a court proceeding (subject to possible reimbursement as set forth below). Fees and costs may be awarded as provided pursuant to applicable law. If the arbitrator finds that either the substance of your claim or the relief sought in the demand is frivolous or brought for an improper purpose (as measured by the standards set forth in Federal Rule of Civil Procedure 11(b)), then the payment of all fees will be governed by the JAMS rules. In that case, you agree to reimburse the Company for all monies previously disbursed by it that are otherwise your obligation to pay under the applicable rules. If you prevail in the arbitration and are awarded an amount that is less than the last written settlement amount offered by the Company before the arbitrator was appointed, the Company will pay you the amount it offered in settlement. The arbitrator may make rulings and resolve disputes as to the payment and reimbursement of fees or expenses at any time during the proceeding and upon request from either party made within fourteen (14) days of the arbitrator's ruling on the merits. **Opt-Out. You have the right to opt-out and not be bound by the arbitration provisions set forth in these Terms by sending written notice of your decision to opt-out to notices@eigenlabs.org. The notice must be sent to the Company within thirty (30) days of your first registering to use the Services or agreeing to these Terms; otherwise you shall be bound to arbitrate disputes on a non-class basis in accordance with these Terms. If you opt out of only the arbitration provisions, and not also the class action waiver, the class action waiver still applies. You may not opt out of only the class action waiver and not also the arbitration provisions. If you opt-out of these arbitration provisions, the Company also will not be bound by them.** WAIVER OF RIGHT TO BRING CLASS ACTION AND REPRESENTATIVE CLAIMS. TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, YOU AND THE COMPANY EACH AGREE THAT ANY PROCEEDING TO RESOLVE ANY DISPUTE, CLAIM OR CONTROVERSY WILL BE BROUGHT AND CONDUCTED ONLY IN THE RESPECTIVE PARTY'S INDIVIDUAL CAPACITY AND NOT AS PART OF ANY CLASS (OR PURPORTED CLASS), CONSOLIDATED, MULTIPLE-PLAINTIFF, OR REPRESENTATIVE ACTION OR PROCEEDING ("CLASS ACTION"). YOU AND THE COMPANY AGREE TO WAIVE THE RIGHT TO PARTICIPATE AS A PLAINTIFF OR CLASS MEMBER IN ANY CLASS ACTION. YOU AND THE COMPANY EXPRESSLY WAIVE ANY ABILITY TO MAINTAIN A CLASS ACTION IN ANY FORUM. IF THE DISPUTE IS SUBJECT TO ARBITRATION, THE ARBITRATOR WILL NOT HAVE THE AUTHORITY TO COMBINE OR AGGREGATE CLAIMS, CONDUCT A CLASS ACTION, OR MAKE AN AWARD TO ANY PERSON OR ENTITY NOT A PARTY TO THE ARBITRATION. FURTHER, YOU AND THE COMPANY AGREE THAT THE ARBITRATOR MAY NOT CONSOLIDATE PROCEEDINGS FOR MORE THAN ONE PERSON'S CLAIMS, AND IT MAY NOT OTHERWISE PRESIDE OVER ANY FORM OF A CLASS ACTION. FOR THE AVOIDANCE OF DOUBT, HOWEVER, YOU CAN SEEK PUBLIC INJUNCTIVE RELIEF TO THE EXTENT AUTHORIZED BY LAW AND CONSISTENT WITH THE EXCEPTIONS CLAUSE ABOVE. 3. IF THIS CLASS ACTION WAIVER IS LIMITED, VOIDED, OR FOUND UNENFORCEABLE, THEN, UNLESS THE PARTIES MUTUALLY AGREE OTHERWISE, THE PARTIES' AGREEMENT TO ARBITRATE SHALL BE NULL AND VOID WITH RESPECT TO SUCH PROCEEDING SO LONG AS THE PROCEEDING IS PERMITTED TO PROCEED AS A CLASS ACTION. IF A COURT DECIDES THAT THE LIMITATIONS OF THIS PARAGRAPH ARE DEEMED INVALID OR UNENFORCEABLE, ANY PUTATIVE CLASS, PRIVATE ATTORNEY GENERAL OR CONSOLIDATED OR REPRESENTATIVE ACTION MUST BE BROUGHT IN A COURT OF PROPER JURISDICTION AND NOT IN ARBITRATION. 21. **Additional Provisions** a. Updating These Terms. We may modify these Terms from time to time in which case we will update the "**Last Revised**" date at the top of these Terms. If we make changes that are material, we will use reasonable efforts to attempt to notify you, such as by e-mail and/or by placing a prominent notice on the first page of the Website. However, it is your sole responsibility to review these Terms from time to time to view any such changes. The updated Terms will be effective as of the time of posting, or such later date as may be specified in the updated Terms. Your continued access or use of the Services after the modifications have become effective will be deemed your acceptance of the modified Terms. No amendment shall apply to a dispute for which an arbitration has been initiated prior to the change in Terms. b. Suspension; Termination. If you breach any of the provisions of these Terms, all licenses granted by the Company will terminate automatically. Additionally, the Company may, in its sole discretion, suspend or terminate your Account and/or access to or use of any of the Services, with or without notice, for any or no reason, including, without limitation, (i) if we believe, in our sole discretion, you have engaged in any activities prohibited by these Terms; (ii) if you provide any incomplete, incorrect or false information to us; (iii) if you have breached any portion of these Terms; (iv) if we suspect you may be a Prohibited Person or any Wallet used to access the Services is linked with any illegal or high-risk activity; and/or (v) if we determine such action is necessary to comply with these Terms, any of our policies, procedures or practices, or any law rule or regulation. If the Company deletes your Account for any suspected breach of these Terms by you, you are prohibited from re-registering for the Services under a different name. In the event of Account deletion for any reason, the Company may, but is not obligated to, delete any of Your Content. The Company shall not be responsible for the failure to delete or deletion of Your Content. All sections which by their nature should survive the termination of these Terms shall continue in full force and effect subsequent to and notwithstanding any termination of this Agreement by the Company or you. Termination will not limit any of the Company’s other rights or remedies at law or in equity. c. Injunctive Relief. You agree that a breach of these Terms will cause irreparable injury to the Company for which monetary damages would not be an adequate remedy and the Company shall be entitled to equitable relief in addition to any remedies it may have hereunder or at law without a bond, other security or proof of damages. d. California Residents. If you are a California resident, in accordance with Cal. Civ. Code § 1789.3, you may report complaints to the Complaint Assistance Unit of the Division of Consumer Services of the California Department of Consumer Affairs by contacting them in writing at 1625 North Market Blvd., Suite N 112 Sacramento, CA 95834, or by telephone at (800) 952-5210. e. Export Laws. You agree that you will not export or re-export, directly or indirectly, the Services and/or other information or materials provided by the Company hereunder, to any country for which the United States or any other relevant jurisdiction requires any export license or other governmental approval at the time of export without first obtaining such license or approval. In particular, but without limitation, the Services may not be exported or re-exported (a) into any U.S. embargoed countries or any country that has been designated by the U.S. Government as a "terrorist supporting" country, or (b) to anyone listed on any U.S. Government list of prohibited or restricted parties, including the U.S. Treasury Department's list of Specially Designated Nationals or the U.S. Department of Commerce Denied Person's List or Entity List. By using the Services, you represent and warrant that you are not located in any such country or on any such list. You are responsible for and hereby agree to comply at your sole expense with all applicable United States export laws and regulations. f. Force Majeure. We will not be liable or responsible to you, nor be deemed to have defaulted under or breached these Terms, for any failure or delay in fulfilling or performing any of our obligations under these Terms or in providing the Services, when and to the extent such failure or delay is caused by or results from any events beyond our ability to control, including acts of God; flood, fire, earthquake, epidemics, pandemics, tsunami, explosion, war, invasion, hostilities (whether war is declared or not), terrorist threats or acts, riot or other civil unrest, government order, law, or action, embargoes or blockades, strikes, labor stoppages or slowdowns or other industrial disturbances, shortage of adequate or suitable Internet connectivity, equipment failure, telecommunication breakdown or shortage of adequate power or electricity, and other similar events beyond our control. g. Miscellaneous. If any provision of these Terms shall be unlawful, void or for any reason unenforceable, then that provision shall be deemed severable from these Terms and shall not affect the validity and enforceability of any remaining provisions. These Terms and the licenses granted hereunder may be assigned by the Company but may not be assigned by you without the prior express written consent of the Company. No waiver by either party of any breach or default hereunder shall be deemed to be a waiver of any preceding or subsequent breach or default. The section headings used herein are for reference only and shall not be read to have any legal effect. The Services are operated by us in the United States. Those who choose to access the Services from locations outside the United States do so at their own initiative and are responsible for compliance with applicable local laws. These Terms are governed by the laws of the State of New York, without regard to conflict of laws rules, and the proper venue for any disputes arising out of or relating to any of the same will be the state and federal courts located in New York, New York. h. How to Contact Us. You may contact us regarding the Services or these Terms by e-mail at notices@eigenlabs.org. --- --- title: Architecture sidebar_position: 3 --- EigenCompute enables developers to deploy verifiable applications in Trusted Execution Environments (TEEs). Each app receives its own wallet serving as its cryptographic identity, allowing it to sign transactions, hold funds, and operate autonomously. When you deploy an EigenCompute app you get: * A unique private key derived deterministically from your app's ID. * Hardware-isolated execution via Intel TDX trusted execution environments. * Cryptographic attestation proving which exact Docker image (by digest) has access to the key. * Autonomous capabilities - your app can hold funds, sign transactions, and operate independently. ## Application Deployment Flow The deployment flow ensures only verified, attested apps are deployed to TEEs, and can access the app wallet keys. ![Deployment Flow](/img/eigencompute-deployment-flow.png) The EigenCompute components are: * Developer tools to publish digest metadata on Ethereum: - Build container image using ecloud CLI. - Sign image digest with authentication keys. - Push image to container registry. * EigenLabs Coordinator to manage infrastructure: - Listens for onchain app creation. - Deploys image to TEE. * [Intel TDX (Google Cloud)](https://cloud.google.com/confidential-computing/confidential-space/docs/confidential-space-overview) to execute app with unique wallet key: - Deploys verified app inside TEE. - Requests keys from KMS. * KMS to manage onchain verification and key delivery: - Verifies TEE attestation and onchain whitelisted code match. - Provides app keys after successful verification. :::note KMS Operator in Mainnet Alpha Phase In the Mainnet Alpha phase, EigenLabs are running a single KMS node for all EigenCompute apps in [Google Cloud Platform](https://cloud.google.com/kms/docs/key-management-service). Threshold KMS for distributed key management is in development. ::: --- --- title: EigenCompute KMS sidebar_position: 2 --- The EigenCompute Key Management Service (KMS) is the service that handles all secrets (for example, private keys, API secrets, encrypted tokens) for EigenCompute applications. The KMS provides applications a persistent onchain identity, strict isolation of secrets, and with the [distributed KMS](#distributed-kms-q1-2026), long-term recoverability even with hardware failures or Operator outages. The KMS provides three key properties to EigenCompute applications: 1. [Deterministic TEE mnemonic](#deterministic-mnemomic-generation) Every application receives a deterministic mnemonic that only its TEE can access. This allows the TEE to hold a persistent wallet and act autonomously onchain. 2. [No access to secrets outside the TEE](#derived-from-mnemonic) Secrets are never exposed to application code or Operators. Only the TEE can derive and use private keys. 3. Recoverability even if a TEE fails (with [distributed KMS](#distributed-kms-q1-2026)) Once threshold KMS is live, the KMS will tolerate up to n/3 Operator failures or outages, ensuring applications maintain their identity and capabilities. :::note KMS Operator in Mainnet Alpha Phase In the Mainnet Alpha phase, EigenLabs are running a single KMS node for all EigenCompute apps in Google Cloud Platform. [Threshold KMS for distributed key management](#distributed-kms-q1-2026) is in active development. ::: ## Deterministic Mnemomic Generation Each application gets a persistent mnemonic derived deterministically from its application ID. That is, the same application ID will always produce the same mnemonic. The deterministic mnemonic generation enables persistent identity across the entire application lifecycle. When you upgrade or restart your application, the new instance get the same mnemonic. ### Derived from Mnemonic From the mnemonic, applications can generate: * Wallet addresses for: * Ethereum * Solana * Any other blockchain with Hierarchical Deterministic (HD) wallet support. HD wallets implement the [BIP-32 standard](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki). * TLS private keys for: * Serving HTTPS traffic * Generating certificates tied to the mnemonic. * Encryption keys for: * Encrypting data at rest * Securing communication with other services. :::tip Example Use Case Encrypt a database with a key derived from the mnemonic. On reboot, derive the same key and decrypt the database. Persistent encrypted state! ::: ## Distributed KMS (Q1, 2026) The distributed KMS (planned for release Q1, 2026) will use threshold cryptography (BLS12-381) to eliminate single points of failure while maintaining Byzantine fault tolerance. The distributed KMS will provide two important properties: * No single Operator can access TEE secrets. * Applications continue operating even if some KMS Operators go offline. ### No access to TEE secrets Key shares cannot be combined by any single party meaning that no Operator ever sees the full private key. A compromised Operator, or even a malicious one, cannot gain access to the private key without collusion from ⌈2n/3⌉ operators. ### Fault-tolerant availability With a ⌈2n/3⌉ threshold, the KMS will tolerate up to n/3 Operator failures or outages. Applications can continue without interruption if up to n/3 Operators fail. This ensures that availability is shared across a decentralized set of Operators. --- --- title: Use Cases sidebar_position: 2 --- ### Autonomous Trading Systems Traditional trading bots require depositing funds into developer-controlled wallets. With EigenCompute, the bot itself holds the funds: ```javascript // Bot receives its deterministic wallet const wallet = mnemonicToAccount(process.env.MNEMONIC) // Bot executes strategy autonomously if (await meetsTradingConditions()) { await executeSwap(wallet, userDeposit) } ``` Funds are sent directly to the bot's address, with only the verified trading logic able to access them. ### Verifiable Social Media Social platforms can prove their ranking algorithms work as claimed: ```javascript // Transparent content ranking const posts = await fetchUserFeed(userId) const engagement = await getEngagementMetrics(posts) // Verifiable algorithm execution const ranked = posts.sort((a, b) => { // Public ranking logic return (b.likes * 0.3 + b.comments * 0.5 + b.shares * 0.2) - (a.likes * 0.3 + a.comments * 0.5 + a.shares * 0.2) }) // Sign the feed to prove no manipulation const signature = await wallet.signMessage({ userId, algorithm: 'engagement_v1', feed: ranked.map(p => p.id) }) ``` The feed ranking algorithm is verifiable and transparent, preventing manipulation. ### Verifiable Gaming Build high-performance games with provable fairness and on-chain assets: ```javascript // Game server controls tournament funds const wallet = mnemonicToAccount(process.env.MNEMONIC) const tournament = await getTournamentState() // Verifiable game logic async function processGameRound(players, moves) { // Deterministic game state updates const outcomes = calculateOutcomes(moves, seedFromBlockhash) // Update player tokens on-chain for (const winner of outcomes.winners) { await wallet.sendTransaction({ to: winner.address, value: tournament.prizePool / outcomes.winners.length }) } return outcomes } ``` Game logic is verifiable and tournament prizes are distributed according to transparent rules. --- --- title: Keys sidebar_position: 3 --- EigenCompute uses two types of keys: * Authentication keys For developers and used for deployments and protocol interactions. * TEE mnemonic For applications and used for persistent wallet functionality inside the TEE. Also provides the ability to verify that you are communicating with the correct TEE application. ## Authentication keys :::tip The authentication keys are a cryptographic key pair. The private key is used to sign deployment transactions. From that private key, a public key is derived, and from the public key, an address is generated. The address is your EigenCompute onchain identification, often referred to as a wallet, and must be funded before deployment. ::: | Category | Authentication Key Details | |-----------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Purpose | Developer authentication for deployments and protocol interactions | | Type | secp256k1 private key (Ethereum-compatible) | | Origin | Generated or imported using `ecloud auth` CLI command | | Location | Local OS or organization keyring (macOS Keychain, 1Password, Windows Credential Manager, Linux Secret Service, etc.). Stored under `ecloud-` (eg, `ecloud-mainnet`) | | Security | Developer must secure and store the authentication keys securely to sign deployment transactions | ## TEE Mnemonic :::important The TEE mnemonic is generated by the KMS and bound to your app's enclave, ensuring consistency across deployments. Once injected, the mnemonic safety depends on the app not leaking it. ::: | Category | TEE Mnemonic Details | |-------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Purpose | Persistent wallet for applications running inside a TEE | | Type | BIP-39 mnemonic phrase (12/24 words) | | Origin | Generated by KMS. Released only to your application using enclave attestation | | Location | Encrypted at rest in KMS. Only decryptable inside your specific TEE application | | Access | Provided at runtime using `process.env.MNEMONIC` | | Persistence | Stable across restarts and deployments | | Security | The mnemonic is cryptographically bound to your specific TEE instance. No other TEE, application, or party can decrypt it. Inside the TEE, it's a plain secret and must be handled appropriately. Do not log or exfiltrate the mnemonic. | --- --- title: Privacy sidebar_position: 7 --- EigenCompute provides strong privacy guarantees through TEE isolation and encryption. To build secure applications, it's important to understand what's private and what's public. ## Private to your TEE Application | Category | Details | Example Use Case | |:--------------------------------|:----------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | TEE Mnemonic | KMS-generated mnemonic only accessible inside your specific TEE instance | Build an autonomous trading bot that manages real funds without exposing private keys to operators | | Encrypted environment variables | Environment variables encrypted by KMS, only decryptable within your TEE | Store API keys for payment processors or AI services that your app uses. Even EigenLabs can't see them | | Application code | Your containerized application runs in isolation within the TEE | Run proprietary trading algorithms or ML models where the logic itself is valuable IP | | Runtime data | Memory contents, temporary files, and process state isolated in TEE | Process user PII or financial data in memory without it being accessible to cloud providers | | Private keys | Any keys derived from or stored within the TEE environment | Generate signing keys for multi-party computation or [attestations](https://docs.trustauthority.intel.com/main/articles/articles/ita/concept-attestation-overview.html) that prove computation happened correctly | ## Publicly Visible Information | Category | Details | |:------------------------------|:------------------------------------------------------------------------| | App metadata | App ID, name, deployment status, and basic configuration | | Container image | Docker image reference and tags used for deployment | | Container registry | Your container hosted on DockerHub/OCI registries is publicly viewable | | Public environment variables | Environment variables with `_PUBLIC` suffix | | Network endpoints | Public IP addresses and exposed ports for your application | | Logs (if public) | Application logs only if configured to be public (private by default) | ## Privacy Guarantees | Guarantee | Details | |:----------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Code isolation | Your application code executes in hardware-enforced isolation | | Data encryption | All sensitive data encrypted at rest, and decryptable within TEE. In the Mainnet Alpha, EigenLabs has KMS key access. Future releases will use a hardened external system with onchain-authorized upgrades. | | Attestation-based | KMS releases secrets to verified TEE instances via cryptographic attestation proof | | Limited admin access | EigenLabs cannot access your TEE's internal state or memory. However, in the Mainnet Alpha they have access to KMS keys for encryption/decryption operations. | ## Privacy Boundaries * Private by default All application data and environment variables are private unless explicitly marked public. * TEE boundary Privacy protection exists at the TEE hardware level, not just software isolation. * Customer control You decide what information to make transparent through public environment variables. * Container transparency Your container image on DockerHub/OCI registries is publicly accessible, allowing users to audit and understand trust assumptions. * Log privacy control Application logs can be configured as private (default) or public based on your transparency requirements. --- --- title: Deployment Process sidebar_position: 1 --- A deployment follows these steps: 1. Build Phase (if not using pre-built image) - Read Dockerfile - Build for `linux/amd64` platform - Tag image with unique identifier 2. Push Phase - Authenticate with Docker registry - Push image layers - Verify image is accessible 3. Transaction Phase - Sign deployment transaction - Submit to Ethereum (Sepolia testnet) - Wait for confirmation 4. Provisioning Phase - Provision TEE instance - Generate app mnemonic via KMS - Inject environment variables - Start application container 5. Verification Phase - Verify app is running - Return app details and IP --- --- title: Upgrade Process sidebar_position: 2 --- An upgrade follows these steps: 1. Build New Image (if not using pre-built) - Build updated application - Tag with new identifier 2. Push Image - Push to registry - Verify accessibility 3. Submit Upgrade Transaction - Sign upgrade transaction - Submit to blockchain - Wait for confirmation 4. Update TEE Instance - Pull new image - Update environment variables - Restart application container 5. Verify Update - Confirm app is running - Verify new version is active ## What Gets Updated An upgrade updates: - Application code (new Docker image) - Environment variables (updated .env values) - Configuration (TLS, ports, etc.) What stays the same: - App ID - TEE wallet address (same MNEMONIC) - Instance IP (usually) :::tip Zero Downtime Upgrades aim for minimal downtime, but brief interruptions may occur during container restart. Plan upgrades during maintenance windows for production apps. ::: --- --- title: Security Best Practices sidebar_position: 5 --- ## Best Practices ### Do * Secure authentication keys Store your [authentication keys](keys-overview.md) in organization password managers (1Password, etc.) and back them up securely. * Validate inputs Always validate and sanitize inputs in your TEE application. TEE isolation doesn't eliminate traditional security vulnerabilities. * Use public variables intentionally Mark configuration as `_PUBLIC` only when transparency benefits users (e.g., API endpoints, version numbers). * Handle secrets carefully Once secrets are decrypted inside the TEE, treat them as plaintext. Avoid logging or exfiltrating secrets. * Keep dependencies updated Regularly update your container dependencies to patch known vulnerabilities. * Test locally first Develop and test your application logic thoroughly before deploying to TEE infrastructure. ### Don't * Don't log secrets Never log the TEE mnemonic, private keys, or decrypted environment variables. * Don't expose secrets via APIs Ensure your application doesn't inadvertently expose secrets through API responses or error messages. * Don't trust all container images Only use trusted base images from official sources. Remember your container is publicly auditable. * Don't rely solely on TEE TEE protects against infrastructure attacks but doesn't eliminate application-level vulnerabilities such as SQL injection. --- --- title: Security and Trust Model sidebar_position: 4 --- ## Trust Requirements EigenCompute currently requires trust in: - [Intel TDX hardware security guarantees](https://github.com/intel/tdx-module). - Google Confidential Space attestation service. - Single KMS operator (EigenLabs) and [KMS](https://github.com/Layr-Labs/eigenx-kms/blob/master/kms.md) [attestation](https://docs.trustauthority.intel.com/main/articles/articles/ita/concept-attestation-overview.html) process. ## Security Boundaries * Trust boundary: You trust the [TEE hardware manufacturer](https://github.com/intel/tdx-module), Google Confidential Space attestation service, [KMS](https://github.com/Layr-Labs/eigenx-kms/blob/master/kms.md) [attestation](https://docs.trustauthority.intel.com/main/articles/articles/ita/concept-attestation-overview.html) process * Your responsibility: Application logic, dependency security, and secret handling within your code. * Platform/EigenLabs responsibility: Infrastructure security, TEE provisioning, and [KMS](https://github.com/Layr-Labs/eigenx-kms/blob/master/kms.md) operation. :::tip Security Enhancements in Development Security enhancements in development: - Public attestation endpoints for runtime verification - Threshold KMS for distributed key management - Replica prevention via onchain checks and heartbeats - Verifiably built images with reproducible builds ::: ## Threat Model The EigenCompute TEE/KMS architecture protects against: | Attack Vector | Protection | |----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Malicious cloud providers | EigenLabs cannot access your TEE memory or runtime data. In the Mainnet Alpha phase, EigenLabs has access to KMS keys and can theoretically decrypt environment variables. Future releases will eliminate this access through an external hardened KMS system. | | Infrastructure compromise | Even if host machines are compromised, TEE hardware isolation prevents secret extraction. | | Man-in-the-middle attacks | Encrypted secrets can only be decrypted inside TEE instances verified using [attestation](https://docs.trustauthority.intel.com/main/articles/articles/ita/concept-attestation-overview.html). | | Secret exfiltration by Operators | [KMS](https://github.com/Layr-Labs/eigenx-kms/blob/master/kms.md) cryptographically binds secrets to your specific TEE. In the Mainnet Alpha phase, EigenLabs has access to KMS keys and can theoretically decrypt environment variables. Future releases will eliminate this access through an external hardened KMS system. | | Credential theft from storage | Secrets are stored encrypted onchain and in the KMS. Secrets are never stored in plaintext outside your TEE. | | Supply chain attacks on infrastructure | [Attestation](https://docs.trustauthority.intel.com/main/articles/articles/ita/concept-attestation-overview.html) ensures only genuine TEE hardware with verified measurements can decrypt secrets. | The EigenCompute TEE/KMS architecture does not protect against: | Attack Vector | Mitigation | |-----------------------------|-----------------------------------------------------------------------------------------------------------------| | Vulnerable application code | Review and test your code for traditional vulnerabilities (for example, injection attacks, XSS). | | Secrets logged by your app | Implement proper logging hygiene. Never log sensitive values. | | Compromised dependencies | Audit your dependencies and use trusted sources for packages. | | Side-channel attacks | While TEEs mitigate many side-channels, be cautious with timing-sensitive operations. | | Physical access attacks | TEE protects against remote attacks, but sophisticated physical access could theoretically compromise hardware. | | Malicious container images | You control your container. Ensure you build from trusted base images and scan for vulnerabilities. | --- --- title: Technical Comparison sidebar_position: 8 ---
Capability EigenCompute Smart Contracts Traditional Apps
Trust Model Verify code via attestation Verify on-chain bytecode Trust developer
Key Management Platform-controlled, attestation-gated Protocol-controlled Developer-controlled
Data Privacy Encrypted memory, isolated execution All data public on-chain Depends on developer
Languages Any Solidity/Vyper Any
External APIs Direct HTTPS Oracle-only Direct HTTPS
Compute Power Up to 176 vCPUs, 704GB RAM Gas-limited Unlimited
--- --- title: Trust Guarantees sidebar_position: 2 --- EigenCompute enables verifiable trust guarantees for your application. Currently, EigenCompute enables trust guarantees for: * Hardware-isolated execution. Your app runs inside Intel TDX, a secure enclave with encrypted memory that generates cryptographic proof of the exact Docker image running inside. * Onchain deployment record. Every deployment is permanently recorded onchain, creating an immutable audit trail. Roadmap items in active development will enable EigenCompute to provide similar guarantees to blockchain smart contracts, including: * Verifiable execution * Forced inclusion * Liveness guarantees * Upgrade delays. ## Verification Dashboards The Verification Dashboards for [Mainnet](https://verify.eigencloud.xyz/) and [Sepolia testnet](https://verify-sepolia.eigencloud.xyz/) display data to verify EigenCloud trust guarantees. For information on how to view verification data and what's displayed, refer to [Verify Trust Guarantees](../howto/operate/verify-trust-guarantees.md). --- --- title: Verifiable Builds sidebar_position: 5 --- EigenCompute verifiable builds enable users to cryptographically verify that a running container was built from a specific GitHub commit. EigenCompute uses the [Google Cloud Build SLSA provenance system](https://cloud.google.com/build/docs/securing-builds/generate-validate-build-provenance/) to provide the build digest that is cryptographically signed by Google Cloud Build and includes: * Git repository URL * Exact commit SHA * Dockerfile path and build context * All dependency image digests * Build timestamp. Verifiably built containers are stored publicly in [Docker Hub](https://hub.docker.com/r/eigenlayer/eigencloud-containers). The [Verifiability Dashboard](https://verify.eigencloud.xyz/) displays the status of source code verification for applications. For information on how to build verifiably, see [Build from verifiable source](../howto/build/verifiable-builds/build-from-verifiable-source.md). ## Dependencies For an application to be verifiably built, every layer of the application stack must be verifiably built. You cannot include unverified code in a verifiable build. When you submit a build with dependencies, each dependency: 1. Must be a previously verifiably built image. 2. Must have valid SLSA provenance. 3. Must have its digest recorded in your build's provenance. When submitting a build with dependencies, provenance is validated and dependency digests are recorded in the build's SLSA provenance. The [EigenCompute TLS and KMS clients are prebuilt](https://github.com/Layr-Labs/eigencompute-containers) and the digests included in all EigenCompute applications. EigenCompute applications with dependencies other than the TLS and KMS clients must submit those verifiable builds and include the dependency's image digest when verifiably building the application. ## Guarantees | Property | Guarantee | |-----------------------|---------------------------------------------------------| | Source Verification | Every line of code traces back to a specific git commit | | Build Reproducibility | Same inputs always produce same provenance | | Dependency Integrity | No unverified code can be injected | | Tamper Evidence | Any modification breaks the cryptographic chain | --- --- title: Billing sidebar_position: 3 --- Deploying an EigenCompute application to Sepolia testnet or mainnet requires an EigenCompute subscription. EigenCompute subscriptions can be paid by credit card or EigenCompute credits can be purchased with USDC. EigenCompute has metered billing so you pay for what you use. All new customers receive up to $25 matched credits. :::important Mainnet Pricing Current EigenCompute pricing is the testnet pricing. Mainnet deployments are available at testnet pricing for a promotional period ending on 04/31/2026. ::: Up to 10 apps each can be deployed on Sepolia testnet and mainnet per subscription (that is, 20 apps total can be deployed per subscription per [ecloud CLI authentication key](../concepts/keys-overview.md)). ## Instance types * Shielded VM (vTPM): Verified boot and runtime attestation. * SEV-SNP (TEE): Verified boot, runtime attestation, and hardware-encrypted memory (AMD). * TDX (TEE): Verified boot, runtime attestation, and hardware-encrypted memory (Intel). ### Instance pricing and specifications | Instance Tier | Resources | Security Type | Hourly Price | Monthly Price | |:-----------------|:---------------------|:-------------------|:-------------|:--------------| | **Starter 1** | Shared 2 vCPU + 1 GB | Shielded VM (vTPM) | $0.03/hr | $19.99/mo | | **Starter 2** | Shared 2 vCPU + 4 GB | Shielded VM (vTPM) | $0.04/hr | $29.99/mo | | **Pro 1** | 2 vCPU + 4 GB | SEV-SNP (TEE) | $0.07/hr | $53.99/mo | | **Pro 2** | 2 vCPU + 8 GB | SEV-SNP (TEE) | $0.12/hr | $85.99/mo | | **Enterprise 1** | 4 vCPU + 16 GB | TDX (TEE) | $0.33/hr | $239.99/mo | | **Enterprise 2** | 8 vCPU + 32 GB | TDX (TEE) | $0.66/hr | $484.99/mo | ## Subscribe To subscribe to EigenCompute: ``` ecloud billing subscribe ``` Choose whether to subscribe with credit card or by purchasing credits with USDC. If you select credit card, the payment portal is displayed. Enter your payment method details and click the Subscribe button. If you select purchase credits with USDC, the EigenCompute wallet address and balance is displayed. If the wallet contains USDC, specify the amount to spend on credits. If the wallet does not contain USDC, you are prompted to send USDC to the wallet. The payment successful message is displayed. Return to the terminal and you have access to [deploy your application](../reference/ecloud-cli/compute/app.md#deploy). ## Cancel a Subscription To cancel an active subscription: ``` ecloud billing cancel ``` The deployed application is terminated and a refund for the remaining period of the month issued to the payment method you provided when subscribing. ## Manage Billing To view current subscriptions: ``` ecloud billing status ``` The subscription status is displayed and a link provided to manage payment methods and view subscription transactions. ## Top up with USDC To purchase EigenCompute credits with USDC: ``` ecloud billing top-up ``` The EigenCompute wallet address and balance is displayed. If the wallet contains USDC, specify the amount to spend on credits. If the wallet does not contain USDC, you are prompted to send USDC to the wallet. ## Support For support, join our [Discord channel](https://discord.com/channels/1089434273720832071/1187153894564966480). To talk to the EigenCompute team, complete [this form](https://ein6l.share.hsforms.com/2L1WUjhJWSLyk72IRfAhqHQ) and a member of the team will reach out to discuss your project. --- --- title: EigenCompute Overview sidebar_position: 1 --- ## What is EigenCompute? EigenCompute enables developers to deploy verifiable applications: containerized services that receive their own cryptographic identity, allowing them to hold funds, sign transactions, and operate autonomously. EigenCompute is a verifiable offchain compute service that enables developers to run complex, long-running agent logic outside of a smart contract while maintaining the integrity and security of the onchain environment. The mainnet alpha release of EigenCompute allows developers to upload app or agent logic as a Docker image, which is executed within a secure TEE (Trusted Execution Environment). :::important Mainnet Alpha Limitations - Not recommended for customer funds - Mainnet Alpha is intended to enable developers to build, test and ship applications. - Developer is trusted - Does not enable full verifiable and trustless execution yet (see [Roadmap](#roadmap)). - No SLA - No SLAs around support and uptime of infrastructure. ::: ## Why Build with EigenCompute? Traditional applications require users to trust developers with both code execution and key management. Smart contracts eliminated this trust requirement but introduced severe constraints: prohibitive gas costs, limited computational power, and restricted programming models. EigenCompute provides a third path: applications that offer cryptographic guarantees about their behavior while retaining the flexibility and performance of traditional computing. EigenCompute enables you to build verifiable applications without thinking about determinism, solidity, or how to build a consensus mechanism. To ship a verifiable application, Simply containerize your application using Docker and upload your application to EigenCompute. Use EigenCompute to build applications such as: - Agents & AI: Build fully verifiable agents. Create agents that judge outcomes, trading bots, verifiable NPCs in games, and much more. - Verifiable social media: EigenCompute enables social media platforms to create verifiable ranking algorithms. - Verifiable & scalable gaming: EigenCompute enables running high performance games in containers with tokens stored onchain. - Scalable DeFi: EigenCompute enables you to build advanced ML based, or DeFi products with scalable compute. The benefits of building with EigenCompute include: - User trust: EigenCompute helps your users trust you. With our upcoming user dashboard, users will be able to verify the attestation flow themselves. - Easy deployment & development: Write your business logic in a Docker container and upload it easily using the ecloud CLI. - Web2 programmability & scale: EigenCompute offers VMs up to 177vCPU cores and 756GB of RAM. ## How EigenCompute Works When you deploy to EigenCompute, your application gets: 1. Hardware-isolated execution: Your app runs inside Intel TDX, a secure enclave with encrypted memory that generates cryptographic proof of the exact Docker image running inside. 2. A dedicated wallet: Each application receives a unique wallet. Only that specific app, running the verified Docker image in the enclave, can retrieve the private key. 3. Secure secret management: Environment variables that are encrypted locally and only accessible within the TEE. 4. Onchain deployment record: Every deployment is permanently recorded on-chain by its Docker digest, creating an immutable audit trail. 5. Network access: Optionally [expose ports](../howto/deploy/expose-ports.md) for HTTP endpoints, or [configure HTTPS](quickstart.md#tlshttps-setup-optional) with a custom domain. This creates truly autonomous applications - code that holds its own funds with cryptographic proof of what it will do with them. ## Roadmap The EigenCompute vision is to enable offchain execution systems to provide similar guarantees to blockchain smart contracts, including: - Verifiable execution - Forced inclusion - Liveness guarantees - Upgrade delays. ## Next steps * [Use the quickstart](quickstart.md) * [Connect with our team](https://onboarding.eigencloud.xyz/) --- --- title: Quickstart sidebar_position: 2 --- import InteractiveDemo from '@site/src/components/InteractiveDemo'; To build on EigenCompute: 1. Place your application in a Docker container. 2. [Subscribe to EigenCompute](billing.md). All new customers receive a $100 credit. 3. Upload it to EigenCompute using the `ecloud` CLI. It's that simple to ship a verifiable application. ### See for yourself ## Next Get started with `ecloud` CLI and deploy your first verifiable application to a Trusted Execution Environment (TEE) in minutes. ## Prerequisites Before you begin, ensure you have: - **Docker** - To package and publish application images ([Download](https://www.docker.com/get-started/)) - **Testnet or Mainnet ETH** - For deployment transactions ## Installation ```bash npm install -g @layr-labs/ecloud-cli ``` ## Initial Setup ### Docker Login First, log in to your Docker registry. This is required to push your application images: ```bash docker login ``` ### Authenticate with EigenCloud You have two options for authentication: #### Option 1: Use an Existing Private Key ```bash ecloud auth login ``` This command will prompt you to enter your private key and store it securely in your OS keyring. #### Option 2: Generate a New Private Key ```bash ecloud auth generate --store ``` This generates a new private key and stores it securely. ### Get Testnet Funds Check your wallet address: ```bash ecloud auth whoami ``` ``` Address: 0x9431Cf5DA0CE60664661341db650763B08286B18 Source: stored credentials ``` The current environment (Mainnet or Sepolia testnet) is displayed. To change from Mainnet to Sepolia, use `ecloud compute env set sepolia`. :::tip Developing on Sepolia To get testnet ETH, use: - [Google Cloud Faucet](https://cloud.google.com/application/web3/faucet/ethereum/sepolia) - [Alchemy Faucet](https://sepoliafaucet.com/) ::: ## Create & Deploy Your First App ### Create a New Application Create a new application from a template. Choose from: `typescript`, `python`, `golang`, or `rust` ```bash ecloud compute app create --name my-app --language typescript --template-repo minimal cd my-app ``` This creates a new project with: - Application code from the template - A `Dockerfile` configured for TEE deployment - An `.env.example` file for environment variables Templates include: 1. TEE-Ready Dockerfile. Pre-configured to: - Target `linux/amd64` architecture. - Run as root user (required for TEE). - Include necessary system dependencies. 2. Environment Variable Handling. Access to: - `MNEMONIC` - Auto-generated wallet mnemonic. - Custom environment variables from `.env`. 3. Example Code. Demonstrates: - Accessing the TEE mnemonic. - Creating wallet accounts. - Making onchain transactions. - Environment variable usage. 4. Development Setup. Includes: - Local development instructions. - Testing guidelines. - Deployment best practices. ### Configure Environment Variables ```bash cp .env.example .env ``` Edit `.env` to add any environment variables your application needs: ```bash # Example .env content API_KEY=your_api_key_here DATABASE_URL=your_database_url # Variables with _PUBLIC suffix are visible to users NETWORK_PUBLIC=sepolia ``` Variables with the `_PUBLIC` suffix will be visible to users for transparency. Standard variables remain encrypted within the TEE. :::important Auto-Generated MNEMONIC The `MNEMONIC` environment variable is **automatically provided by KMS** at runtime. Any mnemonic in `.env.example` is just a placeholder. The TEE overwrites it with your app's unique, persistent KMS-generated mnemonic. ::: ### Test locally (if needed) ```bash npm install npm run dev ``` ### Subscribe to EigenCompute Before deploying, you'll need an [EigenCompute subscription](billing). To subscribe: ``` ecloud billing subscribe ``` The payment portal is displayed. Enter your payment method details and click the Subscribe button. ### Deploy to TEE Deploy your application to a Trusted Execution Environment: ```bash ecloud compute app deploy ``` When prompted, select `Build and deploy from Dockerfile` option. The CLI will: 1. Build your Docker image targeting `linux/amd64` 2. Push the image to your Docker registry 3. Deploy to a TEE instance 4. Return your app details including app ID and instance IP ### View Your Application After deployment, view your app's information: ```bash ecloud compute app info ``` ## Port Configuration To make your application accessible over the internet, you need to expose ports in your Dockerfile. ### Basic Port Exposure Add the `EXPOSE` directive to your Dockerfile: ```dockerfile FROM --platform=linux/amd64 node:18 USER root WORKDIR /app COPY . . RUN npm install # Expose the port your app listens on EXPOSE 3000 CMD ["npm", "start"] ``` ### Application Binding Your application must bind to `0.0.0.0` (not `localhost`) to be accessible. For more advanced port configuration including multiple ports and port ranges, see the [Port Exposure Guide](../howto/deploy/expose-ports.md). ## Next Steps * Explore [CLI Commands](../reference/ecloud-cli/ecloud-cli-overview.md) - Learn about all available commands * Review [Core Concepts](eigencompute-overview.md) - Deep dive into keys, environment variables, and security ## Troubleshooting ### Docker Build Fails Ensure your Dockerfile targets the correct platform: ```dockerfile FROM --platform=linux/amd64 node:18 ``` ### Deployment Transaction Fails Check your ETH balance: ```bash ecloud auth whoami ``` Ensure you have sufficient mainnet ETH for deployment transactions. ### Image Push Fails Ensure you're logged into Docker: ```bash docker login ``` ### App Not Starting Check your app logs for errors: ```bash ecloud compute app logs ``` Common issues: - Port conflicts - ensure `APP_PORT` is set correctly - Missing environment variables - Application crashes - check your code ## Get Help - **GitHub Issues**: [Report issues](https://github.com/Layr-Labs/ecloud) - **Discord**: Join our [Support channel](https://discord.com/channels/1089434273720832071/1187153894564966480). - **Talk to EigenCompute team**: Complete [this form](https://ein6l.share.hsforms.com/2L1WUjhJWSLyk72IRfAhqHQ) and a member of the team will reach out to discuss your project. --- --- title: Sample Apps sidebar_position: 4 --- See the following sample apps for examples of how EigenCompute can be used. :::caution Sample apps: * Have not been audited. * Features may be added, removed, or modified. * Interfaces will have breaking changes. * Should be used only for learning purposes and not in production. * Provided "as is" without guarantee of functionality or production support. Eigen Labs, Inc. does not provide support for production use. ::: ### compute-escrow-privy A forkable EigenCompute app that supports an on-chain escrow contract with Eigen Compute interaction, and Privy-authenticated RPCs. [Github repository](https://github.com/Layr-Labs/compute-escrow-privy). ### Pulse AI-powered crypto trading agent that monitors Twitter/X influencers and automatically trades tokens based on positive sentiment analysis. Built with Next.js, EigenAI, AgentKit and deployable on EigenCompute. [Github repository](https://github.com/Layr-Labs/pulse-agent?tab=readme-ov-file#%EF%B8%8F-important-warnings). ### Momentum Trading System - Hyperliquid A funding-aware, volatility-scaled time-series momentum (TSMOM) strategy for Hyperliquid perpetuals. [Github repository](https://github.com/Gajesh2007/momentum-trading). ### OpenFront OpenFront.io is an online real-time strategy game focused on territorial control and alliance building. Players compete to expand their territory, build structures, and form strategic alliances in various maps based on real-world geography. [Github repository](https://github.com/Gajesh2007/OpenFrontIO/tree/gaj/tournament). --- --- title: Attested API example sidebar_position: 3 --- The Attested API example demonstrates how to make signed messages accessible via API. The template is available in Go, Python, Rust, and Typescript. ## Overview The Attested API example packages a minimal containerized service that: * Runs inside an EigenCompute Trusted Execution Environment (TEE). * Generates a random value inside the enclave. * Constructs a verifiable message including randomness and timestamp. * Signs the message using an address derived from the TEE mnemonic. * Exposes the result through a `/random` HTTP endpoint. ## What you get When deployed, the example provides a REST endpoint returning: * A TEE-generated random number * The message string * The message hash * A signature generated inside the TEE * The signer address. ## To deploy and use the Attested API example What you'll do: 1. Build and deploy the Attested API application. 2. Request a signed message from the application. 3. Verify the signed message was returned from the application TEE. ### Prerequisites Before you begin, ensure you have: - [Docker](https://www.docker.com/get-started/) - To package and publish application images. - Sepolia Testnet ETH - For deployment transactions. - [Installed ecloud CLI](../../get-started/quickstart) and [authenticated](../../get-started/quickstart#initial-setup). - [Subscribed to EigenCompute](../../get-started/quickstart#subscribe-to-eigencompute). ### 1. Create Application from Attested API template #### Docker Login Ensure Docker is running and log in to your Docker registry: ```bash docker login ``` You must be logged into Docker to push the application image. #### Create app from Attested API template Create an app: ``` ecloud compute app create ``` Enter a name for your app and select language: ``` ? Enter project name: myproject ? Select language: typescript ``` Select `attested-api`: ``` ? Select template: [Use arrows to move, type to filter] > attested-api: TypeScript API that generates cryptographically attested random numbers ``` The project is created: ``` 2025/11/21 11:30:48 2025/11/21 11:30:48 Cloning template: https://github.com/Layr-Labs/eigenx-templates → extracting templates/attested-api/typescript 2025/11/21 11:30:48 2025/11/21 11:30:50 [====================] 100% eigenx-templates (Cloning from ref: main) 2025/11/21 11:30:50 2025/11/21 11:30:50 Template extraction complete: templates/attested-api/typescript 2025/11/21 11:30:50 Successfully created typescript project: myproject ``` Change into project directory: ``` cd myproject ``` #### Build and deploy Build and deploy the example application: ```bash ecloud compute app deploy ``` Deployment options are displayed. Select the default deployment method to build from Dockerfile: ``` Found Dockerfile in current directory. ? Choose deployment method: Build and deploy from Dockerfile 📦 Build & Push Configuration Your Docker image will be built and pushed to a registry so that EigenCloud can pull and run it in the TEE. ``` Select the default image reference: ``` ? Enter image reference: /typescript:latest ``` Enter an application name: ``` App name selection: ? Enter app name: ``` Select `Continue without env file`: ``` Environment file not found. Environment files contain variables like RPC_URL, etc. ? Choose an option: Continue without env file ``` Select the default instance type and logs option: ``` Select instance type: ? Choose instance: g1-standard-4t - 4 vCPUs, 16 GB memory, TDX (default) ? Do you want to view your app's logs? Yes, but only viewable by app and platform admins ``` The CLI: 1. Builds the Docker image targeting `linux/amd64`. 2. Pushes the image to your Docker registry. 3. Deploys to a TEE instance. 4. Returns the application details including app ID and instance IP. You will see the Refreshing timer running while the app is being started. ``` 2025/11/11 10:54:58 Status changed: Deploying → Running 2025/11/11 10:54:58 IP assigned: 34.82.182.235 2025/11/11 10:54:58 App is now running with IP: 34.82.182.235 ``` ### 4. Request signed message View the application information: ```bash ecloud compute app info ``` The application information is displayed: ``` 2025/11/11 12:05:38 App Name: AppName 2025/11/11 12:05:38 App ID: 0x1Fe4a6FedF45071c45aE779756d79E463E590d28 2025/11/11 12:05:38 Latest Release Time: 2025-11-11 10:54:12 2025/11/11 12:05:38 Status: Running 2025/11/11 12:05:38 Instance: g1-standard-4t 2025/11/11 12:05:38 IP: 34.82.182.235 2025/11/11 12:05:38 EVM Address: 0x17c66C17F03899daD0cBab3A7Fc5EA89B37dcD52 (path: m/44'/60'/0'/0/0) 2025/11/11 12:05:38 Solana Address: G3QYTKnA5PmsQGyPN2xW83RsiUXm2Zsp2eN3y3tfAMsF (path: m/44'/501'/0'/0') ``` Use the Attested API to request a signed message containing a random number and attestation for that random number: ``` curl http://:8080/random ``` The API response is displayed. ``` {"randomNumber":"0xdf9aac2b3d24f016069f60b80f9eb6078af53a75e003efccb3d9a701398e1f2e","randomNumberDecimal":"101139047948132875594643189998571798010250255951109269318072821531194929585966","timestamp":"2025-11-10T06:11:14.025Z","message":"RandomnessBeacon|0xdf9aac2b3d24f016069f60b80f9eb6078af53a75e003efccb3d9a701398e1f2e|2025-11-10T06:11:14.025Z","messageHash":"0x8fb10cc1c2b7e200f748df0caa61342328eda3220ee8943f6cf87a8b6e06922f","signature":"0x65fef0640e256497f9276565a662f568a2569003f83ab5c1b717d8a47b6d9347064ef9fd28df568bc18d343cf7505b77fae788818d7251c8d6da6f6d6a74f17f1b","signer":"0x17c66C17F03899daD0cBab3A7Fc5EA89B37dcD52"} ``` ### 5. Verify the signed message Click the **Verify Signature** button available on [Etherscan](https://etherscan.io/verifiedSignatures#). The **Verify Signature** window is displayed. From the API response, enter: 1. `signer` in the _Address_ field. The `signer` is a signing addresses derived from the TEE mnemonic. 2. `message` in the _Message_ field. 3. `signature` in the _Signature Hash_ field. Click the **Verify** button. The _Signature Verification_ window is displayed and indicates the message signature was verified. The signature verification verifies that message was signed by the `signer` in the response. To verify the `signer` is one of the signing addresses derived from the TEE mnemonic, use the Verifiability Dashboard ([Mainnet](https://verify.eigencloud.xyz/) and [Sepolia Testnet](https://verify-sepolia.eigencloud.xyz/)) to confirm the signing address is one of the _Derived Addresses_ displayed for the application. --- --- title: Use app wallet sidebar_position: 1 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; :::important The TEE mnemonic is generated by the KMS and bound to your app's enclave. Once injected, the mnemonic safety depends on the app not leaking it. Any mnemonic you see in `.env.example` is a placeholder for local development. The TEE overwrites the placeholder with the actual KMS-generated mnemonic that's unique and persistent to your app. Only your specific TEE instance can decrypt and use this mnemonic. ::: When deployed, EigenCompute apps receive a persistent and private wallet that serves as the cryptographic identity, allowing the app to sign transactions, hold funds, and operate autonomously. The TEE mnemonic is generated by the KMS and only decryptable inside your specific TEE application. It is provided at runtime using the `MNEMONIC` environment variable. The wallet addresses are derived from the TEE mnemonic. TEE Mnemonic ## Derive Address from TEE Mnemonic ### Etheruem To derive the Etheruem wallet address from the `MNEMONIC` environment variable: ```typescript const mnemonic = process.env.MNEMONIC; if (!mnemonic) { throw new Error('MNEMONIC environment variable is not set'); } const wallet = ethers.Wallet.fromPhrase(mnemonic); ``` ```typescript // TypeScript/JavaScript example import { mnemonicToAccount } from 'viem/accounts' const account = mnemonicToAccount(process.env.MNEMONIC) ``` ```python # Python example import os from eth_account import Account Account.enable_unaudited_hdwallet_features() account = Account.from_mnemonic(os.environ['MNEMONIC']) ``` Refer to the [`mnemonicToAccount` documentation](https://viem.sh/docs/accounts/local/mnemonicToAccount) ### Solana To derive the Solana address from the `MNEMONIC` environment variable, refer to the [Solana Wallets documentation](http://solana.com/developers/cookbook/wallets/restore-from-mnemonic#restoring-bip44-format-mnemonics). --- --- title: Use ecloud SDK sidebar_position: 1 --- Use the ecloud SDK to: * Deploy containerized applications to ecloud TEE * Manage application lifecycle (start, stop, terminate) * Build and push Docker images with encryption * Monitor application status and logs ## Getting Started 1. Install ecloud SDK: ``` npm install @layr-labs/ecloud-sdk ``` 2. Create a TypeScript file (for example, `subscribe.ts`) that initializes the SDK client and subscribes to EigenCompute: ``` import { createECloudClient } from '@layr-labs/ecloud-sdk'; async function main() { const client = createECloudClient({ privateKey: process.env.PRIVATE_KEY as `0x${string}`, environment: 'sepolia', verbose: true, }); console.log('✓ Client created!'); console.log('Your address:', client.billing.address); // Subscribe const result = await client.billing.subscribe({ productId: 'compute', successUrl: 'https://example.com/success', // Where to redirect after payment cancelUrl: 'https://example.com/cancel', // Where to redirect if cancelled }); if (result.type === 'checkout_created') { console.log('\n🔗 Complete your subscription here:'); console.log(result.checkoutUrl); console.log('\nOpen this URL in your browser to add payment details.'); } else if (result.type === 'already_active') { console.log('✓ Already subscribed! Status:', result.status); } else if (result.type === 'payment_issue') { console.log('⚠️ Payment issue. Visit:', result.portalUrl); } } main().catch(console.error); ``` 3. Run the script with your private key to generate a checkout URL: ``` PRIVATE_KEY=0x... npx tsx subscribe.ts ``` --- --- title: Use existing image sidebar_position: 2 --- If you have a containerized application, you don't need to start from a template when creating an EigenCompute application: ```bash cd my-existing-project # Deploy directly - the CLI will prompt for Dockerfile and .env paths ecloud compute app deploy ``` **Requirements for existing projects:** - **Dockerfile** - Must target `linux/amd64` and run as root user - **.env file** - Optional but recommended for environment variables The CLI will automatically prompt for file paths if they're not in default locations. ### Manual Image Building If you prefer to build and push images yourself: ```bash # Build and push manually docker build --platform linux/amd64 -t myregistry/myapp:v1.0 . docker push myregistry/myapp:v1.0 # Deploy using the image reference ecloud compute app deploy myregistry/myapp:v1.0 ``` --- --- title: Build from verifiable source sidebar_position: 1 --- To build from a verifiable source, options are: 1. Use the `ecloud compute build submit` command to submit a verifiable build from a GitHub source. 2. Specify the `--verifiable` option or select `Yes` when prompted when deploying or upgrading using the `ecloud compute deploy` or `upgrade` commands.. ## Submit from GitHub source To submit a verifiable build from a GitHub source, specify the required options or supply when prompted: * `--repo` (`ECLOUD_BUILD_REPO`) * `--commit` (`ECLOUD_BUILD_COMMIT`) * `--dockerfile` (`ECLOUD_BUILD_DOCKERFILE`, default is `Dockerfile`) * `--context` (`ECLOUD_BUILD_CONTEXT`, default is `.`) * `--dependencies sha256:...` (repeatable; prompt supports comma-separated) * `--build-caddyfile` (`ECLOUD_BUILD_CADDYFILE`) (optional) * `--no-follow` * `--json` For example: ``` ecloud compute build submit --repo https://github.com/myorg/myapp --commit abc123... ecloud compute build submit --repo https://github.com/myorg/myapp --commit abc123... --dependencies sha256:def456... ecloud compute build submit --repo https://github.com/myorg/myapp --commit abc123... --build-caddyfile Caddyfile ecloud compute build submit --repo https://github.com/myorg/myapp --commit abc123... --no-follow ``` Once built and verified, the image can be specified as a prebuilt image when deploying or upgrading. ## Submit when deploying or upgrading To submit when deploying or upgrading, specify the `--verifiable` option for the `ecloud compute app` command, or select `Yes` when prompted. When deploying or upgrading, specify a GitHub source using the `--build-context`, `--build-dependencies`, and `--build-dockerfile` options, or specify a prebuilt verifiable image using the `--image-ref` option. ## Submitting builds with dependencies To specify prebuilt dependencies to include in a verifiable build, use the `--dependencies` option for `ecloud compute build`, `ecloud compute app deploy` or `ecloud compute app upgrade`. The EigenCompute TLS and KMS clients do not need to be specified as dependencies because they are [prebuilt](https://github.com/Layr-Labs/eigencompute-containers) and the digests included in all EigenCompute applications. For more information on dependencies in verifiable builds, refer to [Verifiable Builds](../../../concepts/verifiable-builds.md). --- --- title: Configure TLS sidebar_position: 1 --- Add TLS/HTTPS configuration to your project for secure domain access to: * Expose your TEE app using HTTPS. * Receive webhook events over HTTPS. * Serve web UIs securely. * Deploy to production with TLS. EigenCompute enables TLS with [Let's Encrypt](https://letsencrypt.org/) [using Caddyfile](https://caddyserver.com/docs/caddyfile#:~:text=The%20Caddyfile%20is%20just%20a,use%20JSON%20with%20Caddy's%20API.). To use an alternative certificate provider, configure in your Dockerfile. ## TLS Environment Variables | Variable | Description | Required | Default | |---------------------|---------------------------|------------|-----------| | `DOMAIN` | Your domain name | Yes | - | | `APP_PORT` | Port your app listens on | Yes | - | | `ACME_STAGING` | Use Let's Encrypt staging | No | `false` | | `ACME_FORCE_ISSUE` | Force certificate reissue | No | `false` | | `ENABLE_CADDY_LOGS` | Enable Caddy debug logs | No | `false` | ## Add TLS Configuration To add TLS configuration: ``` ecloud compute app configure tls ``` TLS configuration is added to your project: ``` TLS configuration added successfully Created: - Caddyfile - .env.example.tls To enable TLS: 1. Add TLS variables to .env: cat .env.example.tls >> .env 2. Configure required variables: DOMAIN=yourdomain.com APP_PORT=3000 For first deployment (recommended): ENABLE_CADDY_LOGS=true ACME_STAGING=true 3. Set up DNS A record pointing to instance IP Run 'ecloud compute app info' to get IP address 4. Upgrade: ecloud compute app upgrade Note: Let's Encrypt rate limit is 5 certificates/week per domain ``` ## Configure TLS and Test with Staging Certificates 1. Add TLS environment variables to `.env`: ``` cat .env.example.tls >> .env ``` 2. Configure required variables: ``` # Required DOMAIN=yourdomain.com APP_PORT=3000 # Recommended for first deployment ENABLE_CADDY_LOGS=true ACME_STAGING=true # Use staging certificates initially ``` :::tip To avoid Let's Encrypt rate limits, always test with staging certificates first. ::: 3. Configure DNS by creating an A record pointing to your instance IP: * Type: A * Name: yourdomain.com * Value: Obtain IP address from `ecloud compute app info` 4. Deploy app with TLS configuration: ``` ecloud compute app upgrade ``` The configured TLS routes traffic from ports 80 and 443 to the `APP_PORT`. ## Switch to Production Certificates To switch from staging to production: 1. Force a reissue of certificates by updating the `ACME_FORCE_ISSUE` environment variable: ``` ACME_STAGING=false ACME_FORCE_ISSUE=true # Only needed once ``` 2. Redeploy the app: ``` ecloud compute app upgrade ``` 3. Disable the `ACME_FORCE_ISSUE` environment variable: ``` ACME_FORCE_ISSUE=false ``` :::warning Let's Encrypt Rate Limits Let's Encrypt has a rate limit of 5 certificates per week per domain. Always test with staging certificates first. ::: ## Upgrading You can update `DOMAIN` and `APP_PORT` in the [environment file](#tls-environment-variables) and upgrade without rebuilding the Docker image. If you change anything else in the Caddyfile itself, you must rebuild the image because the Caddyfile is embedded at build time. ## Troubleshooting ### DNS not propagating Wait 5-10 minutes after DNS changes. Verify with: ```bash dig yourdomain.com nslookup yourdomain.com ``` ### Certificate issuance failing Check logs: ```bash ecloud compute app logs ``` Common issues: - DNS not pointing to correct IP. - Port 80/443 not accessible. - Domain already has certificates (use `ACME_FORCE_ISSUE=true`). ### Rate limit exceeded If you hit rate limits: - Wait a week for the limit to reset. - Use a different subdomain. - Consider using staging for development. --- --- title: Expose ports sidebar_position: 4 --- This guide explains how to configure network ports for your EigenCompute applications, enabling them to receive incoming connections. ## Overview EigenCompute applications run in secure Docker containers. To make your application accessible over the internet, you need to: 1. **Expose ports in your Dockerfile** using the `EXPOSE` directive 2. **Bind your application** to the correct port in your code 3. **(Optional) Configure TLS/HTTPS** for production domains ## Basic Port Configuration ### The EXPOSE Directive Add the `EXPOSE` directive to your Dockerfile to specify which port(s) your application listens on: ```dockerfile FROM --platform=linux/amd64 node:18 USER root WORKDIR /app COPY . . RUN npm install # Expose port 3000 for HTTP traffic EXPOSE 3000 CMD ["npm", "start"] ``` ### Exposing Multiple Ports If your application needs multiple ports (e.g., main service + metrics endpoint): ```dockerfile # Expose multiple individual ports EXPOSE 3000 EXPOSE 9090 ``` ### Exposing Port Ranges For applications that need a range of ports: ```dockerfile # Expose ports 8000 through 8010 EXPOSE 8000-8010 ``` ## Application Binding Your application code must bind to `0.0.0.0` (all interfaces) to be accessible. ## HTTPS with Custom Domains For production applications with custom domains, you'll need to configure TLS in addition to exposing ports. See the [TLS configuration guide](configure-tls.md) for complete setup instructions. ## Troubleshooting ### "Cannot reach my application" Check that: 1. Your Dockerfile includes `EXPOSE ` 2. Your app binds to `0.0.0.0`, not `localhost` or `127.0.0.1` 3. The port matches between `EXPOSE`, app binding, and `APP_PORT` (if using TLS) ### "Connection refused" Your application may not be listening on the expected port: - Check application logs: `ecloud compute app logs` - Verify the port in your application startup logs - Ensure no port conflicts if running multiple services ### Port Already in Use If you see "port already in use" errors: - Check for multiple services binding to the same port - Ensure your application shuts down gracefully - Use `ecloud compute app stop` and `ecloud compute app start` to restart ## Related Documentation - [Quickstart Guide](../../get-started/quickstart.md) - Complete deployment walkthrough - [TLS Configuration](configure-tls.md) - Setting up HTTPS with custom domains - [Deployment Reference](../../reference/ecloud-cli/compute/app.md#deploy) - Dockerfile requirements - [Monitoring](../operate/operate-application.md) - Viewing application logs --- --- title: Troubleshoot deployment sidebar_position: 6 --- ## Dockerfile requirements ```dockerfile # Must target linux/amd64 FROM --platform=linux/amd64 node:18 # Must run as root (TEE requirement) USER root # Application code WORKDIR /app COPY . . RUN npm install CMD ["npm", "start"] ``` ## Build fails: platform mismatch Ensure your Dockerfile specifies the platform: ```dockerfile FROM --platform=linux/amd64 node:18 ``` ## Push fails: authentication required Login to Docker registry: ```bash docker login ``` ## Transaction fails: insufficient funds Get Sepolia ETH (for `sepolia` environment) or Mainnet ETH (for `mainnet-alpha` environment): ```bash ecloud auth whoami # Get your address # Visit faucet and request funds ``` ## App fails to start Check logs: ```bash ecloud compute app logs ``` Common issues: - Missing environment variables - Port binding issues - Application crashes - Incorrect entrypoint/command --- --- title: Operate application sidebar_position: 1 --- Use the [`list`](../../reference/ecloud-cli/compute/app.md#list), [`info`](../../reference/ecloud-cli/compute/app.md#info), and [`logs`](../../reference/ecloud-cli/compute/app.md#logs) commands to monitor and manage EigenCompute applications. Use the [`start`](../../reference/ecloud-cli/compute/app.md#start), [`stop`](../../reference/ecloud-cli/compute/app.md#stop), and [`terminate`](../../reference/ecloud-cli/compute/app.md#terminate) commands to change application state. ## When starting a previously stopped application - Wallet persists - Same MNEMONIC is available - IP persists - Usually keeps the same instance IP - State reset - In-memory state is lost (use external storage for persistence) - Logs preserved - Previous logs may still be available ### When stopping - No requests - App doesn't accept requests while stopped - Logs preserved - Can still view logs - Costs reduced - Lower costs while stopped (but not zero) ## Before terminating :::danger Irreversible Action Termination is permanent and irreversible. The TEE wallet mnemonic becomes inaccessible. Any funds in the wallet will be lost forever. ::: - [ ] **Critical**: Withdraw all funds from TEE wallet - [ ] Backup logs: `ecloud compute app logs my-app > backup.log` - [ ] Document configuration - [ ] Verify app is no longer needed - [ ] Check for any dependent services ### What gets deleted when terminating When you terminate an app: - TEE instance - Docker container - Environment variables - App configuration - TEE wallet access (LOST FOREVER) - App name (can be reused) :::danger Irreversible Action Termination is permanent and irreversible. The TEE wallet mnemonic becomes inaccessible. Any funds in the wallet will be lost forever. ::: ### Behavior - Immediate - Takes effect after transaction confirmation - Permanent - Cannot be undone - Name available - App name can be reused for new deployments - ID retired - App ID is never reused ### Safe Termination Workflow ```bash # 1. Stop the app first ecloud compute app stop my-app # 2. Get wallet address ecloud compute app info my-app # Note the TEE Wallet address # 3. Check for funds # Use a blockchain explorer or Etherscan # 4. Withdraw funds (from within your app code) # Transfer to a safe address # 5. Terminate ecloud compute app terminate my-app ``` --- --- title: Verify trust guarantees sidebar_position: 2 --- Use the Verifiability Dashboards for [mainnet](https://verify.eigencloud.xyz/) and [Sepolia testnet](https://verify-sepolia.eigencloud.xyz/) to verify [trust guarantees enabled by EigenCompute](../../concepts/trust-guarantees.md). ## View Verifiability Data in Dashboard To view verifiability data for an application using the dashboard: 1. Go to the Verifiability Dashboard for [mainnet](https://verify.eigencloud.xyz/) or [Sepolia testnet](https://verify-sepolia.eigencloud.xyz/). 2. In the _Deployed Applications_ field, search for the application by name or application ID. 3. The verifiability data for the application is displayed. The data includes: * Application ID and Creator address. * Release history with Docker Image Digests. * TEE attestations for releases. There is a TEE attestation displayed for each release. * Logs for running application (if configured as publicly visible). * Wallet addresses for the application. :::note Whether logs are visible publicly is configured by the application developer using the `--log-visibility` option on the [`ecloud compute app deploy`](../../reference/ecloud-cli/compute/app.md#deploy) and [`ecloud compute app upgrade`](../../reference/ecloud-cli/compute/app.md#upgrade) commands. ::: ## View Verifiability Data Onchain The dashboard provides a convenient way to view releases and application status. The release history and application status can also be verified onchain. To monitor application releases onchain, monitor `AppUpgraded` events on the `AppController` contract. The `AppUpgraded` events include the application ID and the associated release data (imageDigest, registryURL, upgrade time, public and encrypted environment variables). To monitor application status onchain, monitor the `AppCreated`, `AppStarted`, `AppStopped`, `AppTerminated`, and `AppTerminatedByAdmin` events on the `AppController` contract. AppController contract deployment addresses are published in the [`eigenx-contracts`](https://github.com/Layr-Labs/eigenx-contracts) repository for [Mainnet](https://github.com/Layr-Labs/eigenx-contracts/blob/master/script/deploys/mainnet-alpha/deployment.json) and [Sepolia testnet](https://github.com/Layr-Labs/eigenx-contracts/blob/master/script/deploys/sepolia-prod/deployment.json). --- --- title: Create and use authentication keys sidebar_position: 2 --- :::important EigenCompute uses two types of keys: * Authentication keys for deployments and protocol interactions. * TEE mnemonic for applications and wallet functionality inside the TEE. For more information on EigenCompute keys, refer to the [Keys](../../concepts/keys-overview.md) concept topic. ::: ## Create and securely store an authentication key To create and securely store an authentication key: ``` ecloud auth generate --store ``` An authentication key is created and stored in the OS keyring: :::warning The private key is securely stored while you remain authenticated to EigenCompute. If you log out of EigenCompute and have not backed up the private key that was generated for you, you will be unable to access your deployed application. If you generate another authentication key and overwrite the existing private key without first having backed up the private key that was generated for you, you will be unable to access your deployed application. ::: ## Create and display an authentication key :::caution Logging in by providing your private key directly in the command line is not recommended. It is recommended to [securely store authentication keys in the OS keyring](#create-and-securely-store-an-authentication-key) or use the `ECLOUD_PRIVATE_KEY` environment variable. ::: To create and display an authentication key: ``` ecloud auth generate ``` :::note Follow best practices * Use OS Keyring - Most secure method for local development * Never commit keys - Add keys to `.gitignore` and use environment variables for CI/CD. ::: ## Use existing authentication key When using EigenCompute, logging in refers to providing your authentication key to the ecloud command line. The following methods are supported and checked in this order: 1. `--private-key` flag on any command (not recommended). 2. `ECLOUD_PRIVATE_KEY` environment variable. 3. OS keyring securely stored credentials. :::warning Using the `--private-key` flag to provide your private key directly on the command line is not recommended. When provided on the command line it may be stored in your shell history. Use the OS keyring to securely store credentials or the `ECLOUD_PRIVATE_KEY` environment variable for CI/CD pipelines. ::: To log in by storing your authentication key in the OS keyring: ```bash ecloud auth login ``` ## Troubleshooting ### "Not authenticated" Error If you get authentication errors: ```bash # Check authentication status ecloud auth whoami # If not authenticated, login ecloud auth login ``` ### Keyring Access Issues On some systems, you may need to unlock your keyring: - **Linux**: Ensure GNOME Keyring or KWallet is running - **macOS**: System Keychain should work automatically - **Windows**: Credential Manager should work automatically If issues persist, use the environment variable method as a fallback. ### Wrong Address If you're using the wrong address: ```bash # Check current address ecloud auth whoami # Logout and login with correct key ecloud auth logout ecloud auth login ``` --- --- title: Migrate to ecloud CLI sidebar_position: 1 --- :::important The [`eigenx` CLI](../../reference/eigenx-cli/eigenx-cli.md) is being deprecated and will no longer receive updates. The [`ecloud` CLI](../../reference/ecloud-cli/ecloud-cli-overview.md) supports the same commands as `eigenx`. The `app`, `environment`, and `undelegate` subcommands have moved under the [`compute` command](../../reference/ecloud-cli/compute/compute-overview.md). The `migrate` command is provided to migrate your authentication key. We recommend migrating to the `ecloud` CLI as soon as practical. ::: To migrate a stored authentication key from `eigenx` to `eigencloud`: 1. Install the ecloud CLI: ``` npm install -g @layr-labs/ecloud-cli ``` 2. Verify the installation was successful: ``` ecloud version ``` 3. Migrate the stored authentication key: ``` ecloud auth migrate ``` Legacy keys for `eigenx` environments are displayed. Select the key to migrate. 4. When prompted to delete the legacy key, select N. We recommend not deleting your legacy key until you have verified that the migrated key works correctly. 5. Verify the migration was successful: ``` ecloud auth whoami ``` The migrated key is displayed and will be used for all environments. ## Changes ### One key for all environments The `ecloud` CLI uses one key for all environments. When migrating from `eigenx`, which stored a key per environment, you select one stored key to migrate to `ecloud`. To continue using other keys, use the `--private-key` option or the `ECLOUD_PRIVATE_KEY` environment variable. ### compute The `app`, `environment`, and `undelegate` subcommands have moved under the [`compute` command](../../reference/ecloud-cli/compute/compute-overview.md). ### Arguments moved to options The `language`, `template-name`, `image-ref` arguments for the `app` subcommand in `eigenx` are [options in `ecloud`](../../reference/ecloud-cli/compute/app.md). --- --- title: auth sidebar_position: 2 --- The `ecloud` CLI requires authentication to sign transactions for deploying and managing applications. Use `auth` commands to manage authentication credentials securely. ## Available Commands * [generate](#generate) * [login](#login) * [logout](#logout) * [migrate](#migrate) * [whoami](#whoami) * [list](#list) ## generate Generate a new authentication key with optional secure storage. For more information on creating authentication keys, refer to [Create Authentication Keys](../../howto/setup/create-use-auth-keys.md). ### Synopsis `ecloud auth generate [--store]` ### Options `--store` (boolean) > Generate a new authentication key with optional secure storage. For more information on creating authentication keys, refer to [Create Authentication Keys](../../howto/setup/create-use-auth-keys.md). Default is false. ## login Store an existing authentication key securely in your OS keyring. ### Synopsis `ecloud auth login` ## logout Remove stored authentication key from your OS keyring. ### Synopsis `ecloud auth logout [--force]` ### Options `--force` (boolean) > Log out without requiring confirmation. Default is false. ## migrate Migrate authentication key from `eigenx` CLI to `ecloud` CLI. For mor information, refer to [Migrate to ecloud CLI](../../howto/setup/migrate-ecloud-cli.md). ### Synopsis `ecloud auth migrate` ## whoami Display current authentication status and wallet address. ### Synopsis `ecloud auth whoami` --- --- title: billing sidebar_position: 3 --- EigenCompute requires a [subscription for deploying applications](../../get-started/billing). Use these commands to manage billing and subscription. ## Available Commands * [subscribe](#subscribe) * [cancel](#cancel) * [status](#status) * [top-up](#top-up) ## Global Options The following options are available for all `billing` subcommands: `--private-key=` (string) > Authentication key for the billing subscription. `--product=